nextjs-seo-indexing
Fix SEO indexing issues, crawl budget problems, and Search Console coverage errors for Next.js apps. Covers canonical tags, noindex audits, sitemap health, static rendering, and internal linking.
Profile →npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Next.js SEO Indexing & Crawl Budget Skill Fix Google Search Console coverage issues, canonical problems, sitemap errors, and crawl budget waste in Next.js apps. --- ## When to Use - Use when a Next.js site has Google Search Console coverage issues such as duplicate canonicals, accidental noindex, crawl waste, or discovered-but-not-indexed URLs. - Use when auditing sitemap, robots.txt, redirect, internal-linking, or static-rendering problems before an SEO release. - Use when you need framework-specific examples for Next.js App Router metadata, `generateMetadata`, `robots.js`, and sitemap routes. --- ## Understanding Search Console Coverage States | Status | Meaning | Fix | |--------|---------|-----| | Crawled – not indexed | Google crawled but chose not to index | Improve content quality + canonical + internal links | | Duplicate without canonical | Multiple URLs serve same content, no canonical | Add explicit canonical to the preferred URL | | Excluded by noindex | `noindex` tag present | Remove noindex if page should be indexed | | Duplicate, Google chose different canonical | Google prefers a different URL than you specified | Align canonical with the URL Google naturally picks
- When to Use
- Understanding Search Console Coverage States
- Step 1 — Canonical Audit
- Next.js App Router (metadata export)
- Next.js App Router (generateMetadata)
- Common canonical mistakes to fix:
- Step 2 — Noindex Audit
- Step 3 — Sitemap Health
- Verify sitemap routes return 200 + valid XML
- Next.js App Router sitemap (recommended pattern)
- Multiple sitemaps (sitemap index)
- Step 4 — Static Rendering Verification
- Step 5 — Internal Linking Audit
- Step 6 — Redirect Audit
Search for noindex in metadata
rg -n --glob '*.{js,ts,jsx,tsx}' 'noindex|robots.*noindex' app pages
Check layout.js — a noindex here affects ALL pages
grep -n "robots" app/layout.js
curl -sI https://www.yourdomain.com/sitemap.xml | grep -i "content-type\|status"
curl -s https://www.yourdomain.com/sitemap.xml | head -20
Check build output — pages should show ● (static) not λ (dynamic)
npm run build 2>&1 | grep -E "○|●|λ|/blog|/tools"
Find pages that have no inbound links from other pages
grep -r "/blog/my-orphan-post" --include="*.{js,ts,jsx,tsx,md}" . | grep -v "sitemap\|the-page-itself"What does the nextjs-seo-indexing skill do?
Fix SEO indexing issues, crawl budget problems, and Search Console coverage errors for Next.js apps. Covers canonical tags, noindex audits, sitemap health, static rendering, and internal linking.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.