Seo onpage
Add on-page SEO to a Next.js site — title/meta, Open Graph, canonical, structured data (schema.org JSON-LD), and sitemap/robots. Use when building or auditing pages for search visibility and link previews.From its SKILL.md
npx -y skills add m-binimran/dev-pack --skill seo-onpageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 290 tokens by cl100k_base, as published. Nobody here has run it
seo-onpage
Per page
- Unique
<title>(≤ 60 chars) and meta description (≤ 155 chars). In Next.js App Router use themetadataexport orgenerateMetadata. - Open Graph + Twitter tags:
og:title,og:description,og:image(1200×630),og:url,twitter:card. - Canonical URL to avoid duplicate-content splits.
- One
<h1>per page; headings in order.
Site-wide
app/sitemap.tsandapp/robots.ts(Next.js generate these natively).- Structured data (JSON-LD) for the page type:
Organization,LocalBusiness,Product,Article,BreadcrumbList. Hand off complex schemas to a schema-markup skill if available. - Descriptive, keyword-aware URLs; no
?id=for primary pages.
Output
- The
metadata/generateMetadatablock per page. sitemap.ts+robots.ts.- JSON-LD
<script type="application/ld+json">for the right type.
Guardrails
- Don't keyword-stuff. One clear topic per page.
og:imagemust be an absolute URL. Verify the preview actually renders (don't assume).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in 290 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- hand off complex schemas to a schema-markup skill
- output the metadata block per page
- output sitemap and robots files
- output json-ld script for the page type
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.