Nextjs Seo

Handles the full SEO setup for Next.js 16+ apps using the App Router's Metadata API. You get working examples for metadata configuration, dynamic sitemaps, robots.txt, and JSON-LD structured data. The guide emphasizes the new "use cache" directive for SEO-critical components and calls out common mistakes like blocking /_next/ in robots.txt or mixing the old next-seo library with the native API. Includes a quick audit checklist and Core Web Vitals targets. Honestly, this is the reference you want open when setting up a new Next.js project or debugging why Google isn't indexing your pages correctly.

skills.sh installs: 2.5K
GitHub stars: 72
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add laguagu/claude-code-nextjs-skills --skill nextjs-seo --agent claude-code

Installs into .claude/skills of the current project.

Files

Next.js SEO

Start from the page's task, production response and observed search behavior. Read the installed Next.js version and relevant node_modules/next/dist/docs/ pages (bundled from 16.2); otherwise use matching official documentation. Metadata, Viewport and MetadataRoute types are also in node_modules/next/dist/lib/metadata/types/metadata-interface.d.ts. Keep framework APIs, caching mode and deployment policy consistent with the project.

Useful, distinct content matters more than a longer page. Give titles, headings and descriptions separate jobs; add a FAQ, summary, badges or extra pages only when they help the reader. Publication dates must reflect meaningful changes. Verify authorship, credentials and factual claims.