New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nextjs SEO Indexing

by sickn33 in sickn33/agentic-awesome-skills

Fix SEO indexing issues, crawl budget problems, and Search Console coverage errors for Next.js apps.

MITAuto-check passedMarketing & SEO

Install Nextjs SEO Indexing

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills nextjs-seo-indexing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nextjs-seo-indexing .claude/skills/nextjs-seo-indexing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nextjs-seo-indexing
GitHub stars
47k
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
471 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Fix SEO indexing issues, crawl budget problems, and Search Console coverage errors for Next.js apps.

  • Works in 7 steps: Canonical Audit → Noindex Audit → Sitemap Health → …
  • Tasks that involve Technical SEO
  • SKILL.md covers When to Use, Understanding Search Console…, Step 1 — Canonical Audit and Step 2 — Noindex Audit, plus 7 more sections
  • Calls curl, rg and npm

What it does

Nextjs SEO Indexing is an agent skill from sickn33/agentic-awesome-skills. 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.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Technical SEO and On-page SEO. It works with Next.js and Google Search Console. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Technical SEO
  • Tasks that involve On-page SEO

Example prompts

  • “/nextjs-seo-indexing”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Canonical Audit
  2. Noindex Audit
  3. Sitemap Health
  4. Static Rendering Verification
  5. Internal Linking Audit
  6. Redirect Audit
  7. robots.txt Check

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • rg
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nextjs SEO Indexing loads about 1.9k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 471 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 471 words, ~1,916 tokens.

Download SKILL.mdSave it as .claude/skills/nextjs-seo-indexing/SKILL.md (or your agent's skills folder).
name
nextjs-seo-indexing
description
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.
category
seo
risk
safe
source
self
source_type
self
date_added
2026-05-31
author
Whoisabhishekadhikari
tags
seo, indexing, nextjs, search-console, crawl-budget, canonical, sitemap
tools
claude, cursor, gemini, claude-code
version
1.0.0

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

StatusMeaningFix
Crawled – not indexedGoogle crawled but chose not to indexImprove content quality + canonical + internal links
Duplicate without canonicalMultiple URLs serve same content, no canonicalAdd explicit canonical to the preferred URL
Excluded by noindexnoindex tag presentRemove noindex if page should be indexed
Duplicate, Google chose different canonicalGoogle prefers a different URL than you specifiedAlign canonical with the URL Google naturally picks
Alternative page with proper canonicalCorrect — non-preferred duplicate pointing to canonicalExpected behavior, not a problem
Not found 404Page deleted or URL changedAdd redirect or restore page
Discovered – not indexedGoogle knows it exists but hasn't crawled itImprove internal linking + crawl budget
Page with redirectRedirect chain or redirect to wrong targetShorten redirect chain, verify destination

Step 1 — Canonical Audit

Next.js App Router (metadata export)
js
// app/blog/my-post/page.js
export const metadata = {
  title: 'My Post Title',
  alternates: {
    canonical: 'https://www.yourdomain.com/blog/my-post',
  },
};
Next.js App Router (generateMetadata)
js
export async function generateMetadata({ params }) {
  return {
    alternates: {
      canonical: `https://www.yourdomain.com/blog/${params.slug}`,
    },
  };
}
Common canonical mistakes to fix:
js
// ❌ WRONG — relative URL
canonical: '/blog/my-post'

// ❌ WRONG — missing trailing slash inconsistency  
// (pick one and stick with it sitewide)

// ✓ CORRECT — absolute URL, consistent scheme + subdomain
canonical: 'https://www.yourdomain.com/blog/my-post'

Step 2 — Noindex Audit

Find pages that are accidentally noindexed:

bash
# 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

In Next.js App Router, robots in the root layout applies globally. Only set it there if you want the whole site affected.

js
// app/layout.js — only set robots if you need sitewide control
export const metadata = {
  // ✓ Allow indexing
  robots: { index: true, follow: true },
  // ❌ This would noindex the entire site:
  // robots: { index: false }
};

Step 3 — Sitemap Health

Verify sitemap routes return 200 + valid XML
bash
curl -sI https://www.yourdomain.com/sitemap.xml | grep -i "content-type\|status"
curl -s https://www.yourdomain.com/sitemap.xml | head -20
js
// app/sitemap.js
export default async function sitemap() {
  const baseUrl = 'https://www.yourdomain.com';
  
  // Static pages
  const staticPages = [
    { url: baseUrl, lastModified: new Date(), changeFrequency: 'daily', priority: 1.0 },
    { url: `${baseUrl}/about`, lastModified: new Date(), changeFrequency: 'monthly', priority: 0.8 },
  ];
  
  // Dynamic pages (fetch from DB or CMS)
  const posts = await getPosts(); // your data fetch
  const dynamicPages = posts.map(post => ({
    url: `${baseUrl}/blog/${post.slug}`,
    lastModified: new Date(post.updatedAt),
    changeFrequency: 'weekly',
    priority: 0.7,
  }));
  
  return [...staticPages, ...dynamicPages];
}
Multiple sitemaps (sitemap index)
js
// app/sitemap-tools/sitemap.js  
// app/sitemap-blog/sitemap.js
// Each returns an array of URL entries
Show full SKILL.md (187 more words)Show less

Step 4 — Static Rendering Verification

Pages must be statically generated (or SSR with metadata in HTML) for Google to see SEO tags.

bash
# Check build output — pages should show ● (static) not λ (dynamic)
npm run build 2>&1 | grep -E "○|●|λ|/blog|/tools"
text
○  /about             (static)
●  /blog/[slug]       (SSG)  ← good
λ  /api/data          (serverless) ← expected for APIs

If important pages are λ (fully dynamic with no static generation), add:

js
// app/blog/[slug]/page.js
export async function generateStaticParams() {
  const posts = await getPosts();
  return posts.map(post => ({ slug: post.slug }));
}

Step 5 — Internal Linking Audit

Pages with zero internal links are rarely indexed. Every important page should be reachable from:

  1. Homepage or navigation
  2. A sitemap
  3. At least one other content page
bash
# Find pages that have no inbound links from other pages
# (manual check — grep for the slug across all files)
grep -r "/blog/my-orphan-post" --include="*.{js,ts,jsx,tsx,md}" . | grep -v "sitemap\|the-page-itself"

Step 6 — Redirect Audit

bash
# Find all redirects in Next.js config
grep -A 3 "redirects" next.config.js

# Check for redirect chains (A → B → C — should be A → C)
# Test a suspected chain:
curl -sI https://www.yourdomain.com/old-url | grep -i location
js
// next.config.js — keep redirects flat (no chains)
async redirects() {
  return [
    {
      source: '/old-url',
      destination: '/new-url', // Must NOT itself redirect
      permanent: true, // 308 for SEO
    },
  ];
}

Step 7 — robots.txt Check

bash
curl -s https://www.yourdomain.com/robots.txt
text
# ✓ Good
User-agent: *
Allow: /
Sitemap: https://www.yourdomain.com/sitemap.xml

# ❌ Bad — disallows crawling of important content
Disallow: /blog/
Disallow: /tools/
js
// app/robots.js (Next.js App Router)
export default function robots() {
  return {
    rules: { userAgent: '*', allow: '/' },
    sitemap: 'https://www.yourdomain.com/sitemap.xml',
  };
}

Indexing Checklist

  • All important pages have absolute canonical URLs
  • No important pages accidentally noindexed
  • Sitemap routes return 200 with valid XML
  • Sitemap submitted to Google Search Console
  • Important pages statically generated (●) in build output
  • No redirect chains (A→B→C should be A→C)
  • robots.txt allows important content
  • Every important page has ≥1 internal inbound link
  • generateStaticParams added for dynamic routes with known slugs

Limitations

  • Does not guarantee Google will index a page; final indexing decisions remain with the search engine.
  • Requires access to the codebase, deployed URLs, and ideally Google Search Console data for confident diagnosis.
  • Treat recommendations that change URL structure, redirects, or canonical policy as production-impacting and review them before deployment.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/nextjs-seo-indexing of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Nextjs SEO Indexing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nextjs SEO Indexing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nextjs SEO Indexing this skillsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
SEO Setupalisamadiii/Portfolio180—~1.7kAutomated safety check: PassNone
Google Search SEO Guidelittleben/awesomeAgentskills1892 repos~4.2kAutomated safety check: PassMIT
Geo Meta Tags Auditthedaviddias/Front-End-Checklist74k—~763Automated safety check: PassMIT
Persian SEOTronIsHere/vibefarsiui212—~1.7kAutomated safety check: WarnMIT
SEOgridaco/grida2.7k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • SEO Setup

    alisamadiii/Portfolio

    Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).

    180 GitHub stars~1.7k tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed

  • Google Search SEO Guide

    littleben/awesomeAgentskills

    Answers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation.

    189 GitHub starsUsed in 2 repos~4.2k tokens
    Marketing & SEOAuto-check passed

  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed

  • Persian SEO

    TronIsHere/vibefarsiui

    Technical and on-page SEO for Persian (Farsi) websites: lang and hreflang for fa-IR, RTL-safe metadata, Persian titles and descriptions, slug and URL strategy for Persian content, ZWNJ and keyword…

    212 GitHub stars~1.7k tokensUpdated yesterday
    Marketing & SEOAuto-check: warnings

  • SEO

    gridaco/grida

    SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.

    2.7k GitHub stars~2.1k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • SEO Geo

    ericrisco/rsc-harness

    A skill your agent uses when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web…

    180 GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Nextjs SEO Indexing

What does Nextjs SEO Indexing do?

Fix SEO indexing issues, crawl budget problems, and Search Console coverage errors for Next.js apps. Nextjs SEO Indexing is an agent skill from sickn33/agentic-awesome-skills.js apps.

When should I use Nextjs SEO Indexing?

Nextjs SEO Indexing fits situations like: tasks that involve Technical SEO; tasks that involve On-page SEO.

How do I install Nextjs SEO Indexing in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing -a claude-code`. Or copy the skill folder (skills/nextjs-seo-indexing in sickn33/agentic-awesome-skills) into .claude/skills/nextjs-seo-indexing in your project. Claude Code loads it when a task matches its description.

How do I install Nextjs SEO Indexing in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing -a codex`. Or copy the skill folder (skills/nextjs-seo-indexing in sickn33/agentic-awesome-skills) into .agents/skills/nextjs-seo-indexing in your project. Codex loads it when a task matches its description.

Can I use Nextjs SEO Indexing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill nextjs-seo-indexing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nextjs-seo-indexing, .gemini/skills/nextjs-seo-indexing, .github/skills/nextjs-seo-indexing and .opencode/skills/nextjs-seo-indexing in your project.

What does Nextjs SEO Indexing need to run?

Going by SKILL.md and its folder, Nextjs SEO Indexing needs the command-line tools its instructions call (curl, rg and npm).

Does Nextjs SEO Indexing access the network?

SKILL.md contains no URLs. Its commands use curl and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nextjs SEO Indexing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nextjs SEO Indexing use?

Nextjs SEO Indexing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nextjs SEO Indexing use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nextjs SEO Indexing?

Skills that share tags, products or a category with Nextjs SEO Indexing: SEO Setup (alisamadiii/Portfolio, 180 stars), Google Search SEO Guide (littleben/awesomeAgentskills, 189 stars), Geo Meta Tags Audit (thedaviddias/Front-End-Checklist, 74k stars) and Persian SEO (TronIsHere/vibefarsiui, 212 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nextjs SEO Indexing?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.