Skip to content

laguagu/claude-code-nextjs-skills / skills/nextjs-seo

nextjs-seo

Verified

Next.js App Router SEO implementation and audits. Use for metadata and social images, sitemap/robots, canonicals and localization, structured data, Core Web Vitals evidence, AI crawler policy or search-indexing diagnosis. Not for general Next.js feature work unrelated to SEO.

FileKindSize
SKILL.mdskill md4.0 KB
references/ai-search.mdmarkdown7.1 KB
references/checklist.mdmarkdown2.6 KB
references/json-ld.mdmarkdown2.2 KB
references/metadata-api.mdmarkdown3.7 KB
references/sitemap-robots.mdmarkdown2.9 KB
references/troubleshooting.mdmarkdown4.3 KB

references/checklist.md

View on GitHub
# Scoped SEO audit

Select representative route types, languages and deployment environments.
Record production URLs and the relevant Next.js version/configuration.
Do not add every optional feature to make a checklist pass.

1. **Page usefulness:** Does each indexable page answer a distinct task with
   accurate information? Check misleading availability/dates, duplicate pages
   and repetitive UI copy.
2. **Access and discovery:** Check actual status/redirect chains, internal
   links, robots rules, sitemap entries and index directives. Verify public
   versus preview/private intent.
3. **Canonical/localization:** Inspect absolute canonical URLs, query handling
   and reciprocal hreflang where applicable. Compare Google-selected canonicals
   through URL Inspection when available.
4. **Served metadata:** Inspect title/description, social images and icons for
   the route. Check complete responses and streaming behavior for relevant
   bots. Test image URLs; missing optional tags are not automatically defects.
5. **Structured data:** Add only relevant accurate types. Check current
   eligibility, visible facts and safe serialization; validate the production
   output.
6. **Rendering and usability:** Inspect critical public content in the raw
   response ([diagnosis](troubleshooting.md#content-missing-from-the-served-html)),
   then directly open the route and exercise hydration/navigation. Check mobile
   equivalence, media dimensions and the changed interaction.
7. **Performance:** Use field CWV where available and lab tools for diagnosis.
   Distinguish LCP, INP and CLS evidence; lab Lighthouse is not field INP.
8. **Publication:** Change representative content and verify page, metadata
   and sitemap freshness through the real invalidation/rebuild path.
9. **Crawler policy:** Preserve intentional training/search distinctions and
   access protection. Check firewall/access logs when public crawls fail.
   For Google AI eligibility, check the effective Search Console inclusion
   setting (including inheritance); see [AI search policy](ai-search.md#crawlers-and-policy).
10. **Search evidence:** Use indexing/URL Inspection for indexing and canonical
    questions, performance for query/traffic questions, and analytics for
    referrals. A performance export cannot establish all three.

Rank findings by impact and evidence, link affected routes/files and record
checks that could not run. Separate confirmed bugs from hypotheses and
optional improvements. See [troubleshooting.md](troubleshooting.md) and
[Google Search Essentials](https://developers.google.com/search/docs/essentials).
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall