seo-nextjs-implementation
Skill29 starsChanged 38 days agoMITView on GitHub
Implement route-specific Next.js App Router metadata, truthful structured data, canonical URLs, robots, and sitemaps in an authorized codebase. Use for concrete Next.js implementation; inspect the installed version and validate affected routes before claiming compatibility.
In this repository10 other files it gives its agents.
- foundvia-discoverySkill
- seo-ai-geoSkill
- seo-analyticsSkill
- seo-audit-websiteSkill
- seo-content-strategySkill
- seo-growth-engineSkill
- seo-localSkill
- seo-on-pageSkill
- seo-slug-datesSkill
- seo-technicalSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Keep shared defaults in the layout and route-specific title, description, URL, and canonical on the actual page.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Next.js discovery implementation
Inspect package versions, route conventions, existing metadata, and repository instructions before editing. Reuse the app's implementation rather than replacing it with a template. Audit-only requests authorize proposed changes, not edits or deployment.
Metadata and canonical URLs
Keep shared defaults in the layout and route-specific title, description, URL, and canonical on the actual page. A layout cannot infer every child route. Do not canonicalize all pages to the homepage. Confirm file-based metadata precedence and existing title templates before adding another suffix.
scripts/seo.ts is an optional copyable helper requiring Next.js metadata types and React. Replace all Brand/example.com/yourhandle defaults before use. Its generateMetadata() now omits canonical/openGraph.url unless a route URL is provided. getCanonicalUrl(path, removeParams) preserves query parameters by default; explicitly list tracking parameters to remove. Review callers migrating from the old strip-all-query behavior.
Structured data
Choose a schema that describes visible real content; verify feature eligibility separately. The JsonLd component escapes less-than characters before script embedding. Use genuine dates, prices, authors, availability, and ratings. Unknown dateModified, author URLs, and availability are omitted instead of invented. FAQPage remains an optional schema export, not a promise of Google FAQ rich results.
Robots and sitemaps
Preserve private routes and training policy. Keep rendering assets accessible. Build sitemap entries from real canonical public routes and actual content dates. Treat crawler access, indexing, ranking, and AI referrals as separate checks.
Verification and handoff
Run the app's typecheck/build and inspect affected rendered routes, metadata, schema, robots, and sitemap. Test dynamic routes, missing records, and query-dependent pages. Local helper tests do not establish full framework/build compatibility. Distinguish local changes, deployment, and live verification; do not promise rich results in a fixed number of weeks.
Sources: Next.js metadata, safe JSON-LD.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

