Next.js App Router SEO optimization and auditing. Use when implementing or fixing SEO in a Next.js app — metadata and generateMetadata, viewport/themeColor, Open Graph and og/twitter images (file conventions + ImageResponse), web app manifest, favicons/icons, sitemap.xml, robots.txt, canonical URLs, hreflang/i18n alternates, JSON-LD structured data and rich results, Core Web Vitals (LCP/INP/CLS), AI search/GEO and AI crawler rules (GPTBot, OAI-SearchBot), or diagnosing Google indexing problems (
nextjs-seo is a comprehensive SEO reference and auditing skill for Next.js App Router applications. It solves the problem of correctly implementing and diagnosing SEO in modern Next.js by consolidating the framework's Metadata API, file conventions, and current search-engine behavior into one guide, including common gotchas that silently break indexing or social previews.
The skill provides a quick SEO audit checklist (checking robots.txt, sitemap.xml, page metadata, JSON-LD, and Core Web Vitals via PageSpeed Insights and Search Console), plus copy-ready TypeScript for root metadata, the separate viewport export with themeColor, dynamic generateMetadata, app/sitemap.ts, and app/robots.ts. Its deeper reference files cover the full Metadata object, Open Graph and Twitter images via file conventions and ImageResponse, web app manifest and icons, canonical URLs, hreflang/i18n alternates, JSON-LD structured data, AI-search/GEO and AI crawler rules (GPTBot, OAI-SearchBot), and troubleshooting Google indexing states. It emphasizes accuracy details many developers miss, such as viewport needing to be a separate export, Google ignoring the keywords meta tag, the shallow-merge behavior of nested metadata, using real lastModified timestamps, and not disallowing /_next/ in robots.
It targets Next.js developers, technical SEO specialists, and teams auditing or fixing search visibility. As a documentation and code-pattern reference, it advises and generates configuration code; the only commands it suggests are read-only curl checks of a site's own robots.txt and sitemap. It explicitly scopes itself to SEO work rather than general Next.js feature development.
It targets the Next.js App Router and reflects current behavior such as params and searchParams being Promises, v16 typed helpers like PageProps, and Cache Components considerations.
Metadata and generateMetadata, viewport/themeColor, Open Graph and Twitter images, web app manifest and icons, sitemap.xml, robots.txt, canonical URLs, hreflang alternates, JSON-LD, Core Web Vitals, AI-crawler rules, and Google indexing troubleshooting.
Only read-only checks: it suggests curling your own robots.txt and sitemap.xml and viewing page source, plus using external tools like PageSpeed Insights and Search Console for field data.
It flags that viewport must be a separate export, that Google ignores the keywords meta tag, the shallow-merge gotcha where redefining nested metadata drops sibling keys, using accurate lastModified values, and not disallowing /_next/ in robots.txt.
No. It is explicitly scoped to SEO implementation and auditing, not general Next.js feature work unrelated to SEO.
Quick Setup:
.claude/skills/Repository
laguagu/claude-code-nextjs-skills