SEO
by addyosmani / web-quality-skills
Optimize for search engine visibility and ranking.
Next.js App Router SEO implementation and audits.
Listed ·Updated
Install data from skills.sh
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.
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.
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.metadataBase and verify emitted
absolute URLs. Do not rely on missing-base behavior across versions/hosts.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.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.