seoskills.sh

Nextjs SEO

Next.js App Router SEO implementation and audits.

Listed ·Updated

2.6K installs

Install data from skills.sh

About this skill

Implements and audits SEO in Next.js App Router projects, leaving general feature work alone. Give it a route and what you see in search. It reads your installed Next.js version and the matching docs, which ship inside node_modules from 16.2, then works on the affected area: metadata and social images, sitemap and robots, canonicals and localization, JSON-LD, AI crawler policy or indexing. Before adding markup it verifies status codes, redirects, headers and the full production HTML, and confirms metadataBase yields correct absolute URLs. Reports keep evidence apart: Lighthouse lab numbers can't show field INP, and a spoofed user agent only tests how the server responds. It lists any check it couldn't run.

What it needs

  • A Next.js App Router project, ideally 16.2 or later for the bundled docs
  • The live production site, to check status codes, headers and served HTML
  • Google Search Console access (optional, for performance and URL Inspection evidence)
  • Field Core Web Vitals data (optional, for real-user LCP, INP and CLS)

Try asking

  • Why isn't Google indexing the product pages on our Next.js store?
  • Add Open Graph images and canonicals to our Next.js App Router blog
  • Allow search crawlers but block AI training bots on our Next.js site

Compare with

  • Nuxt SEO by onmaxFor Nuxt sites instead: covers the Nuxt SEO meta-module's robots, sitemap, OG image and schema.org pieces.
  • SEO Best Practices by asyrafhussinFor Laravel and Inertia React codebases: a pass or fail checklist audit that cites file and line for each failure.
  • SEO by addyosmaniAny stack: runs live Lighthouse SEO and Agentic Browsing audits on the rendered page, fixes the source and re-checks.
  • Puppeteer JS Rendering Auditor by seoskills-shNarrower and scripted: diffs each URL's raw HTML with its headless Chrome render to show content that needs JavaScript.

SKILL.md

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.

Implementation and audit scope

  • Verify public URLs, redirects, status codes, crawl rules, index directives and canonicals before adding markup. A sitemap supports discovery; it does not make a page indexable or guarantee indexing.
  • Keep important public content available in the served HTML when practical. A Client Component can be server-prerendered; use client alone does not remove content from HTML. Check the raw response for a visible phrase and a data value from each important section: hydration hides a missing section in the browser, and the build can still pass. See Troubleshooting.
  • Use the App Router Metadata API and file conventions. Resolve relative metadata URLs with the correct production metadataBase and verify emitted absolute URLs. Do not rely on missing-base behavior across versions/hosts.
  • Configure refresh/invalidation for data-backed pages, metadata and sitemaps. A database query alone does not guarantee publication updates reach them. With Cache Components enabled, follow the installed Next.js caching docs (node_modules/next/dist/docs/). No cache setting is an SEO directive, but a short cacheLife also decides whether content is in the prerendered HTML.
  • Structured data must describe real visible content and a supported consumer. Check current rich-result eligibility instead of adding every schema type.
  • Preserve the owner's crawler policy. Training, search and user-triggered retrieval have different controls; robots rules are not access control.

Read for the affected area

Separate evidence in the report: a performance export shows queries/traffic; URL Inspection and indexing reports address crawl/index/canonical status; field measurements address Core Web Vitals. Lighthouse is a lab diagnostic and cannot establish field INP. Good field thresholds at the 75th percentile are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1.

Verify status, headers and the complete production response for what changed: page HTML (including relevant bot responses), the sitemap or robots body, or the image URL. When rendering or client code changed, or an audit covers rendering, also open the route directly and test its interaction. A spoofed User-Agent tests response handling, not actual verified bot access. Report unavailable checks explicitly and avoid ranking, indexing or citation promises.

Not using the CLI? Copy the SKILL.md and paste it straight into ChatGPT, Claude, or any agent.

View laguagu/claude-code-nextjs-skills on GitHub

Embed a badge

seoskills.sh listing badge