agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/indexing/SKILL.md

indexing

Skill0 starsChanged 3 months agoMITView on GitHub

When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL and indexing …

    line 21
  2. Distinctive:

    Rationale: Not all site content should be indexed.

    line 69
  3. Distinctive:

    Caution: Avoid noindex on important content pages

    line 70
  4. Very specific:

    noindex,follow vs noindex,nofollow: Use noindex,follow for most cases—excludes from SERP but allows link equity.

    line 86
  5. Distinctive:

    When intentionally removing a page from the web, choose the method based on whether a relevant alternative exists and whether the page …

    line 90
  6. Distinctive:

    Before removing: Check the URL's search traffic, backlinks, internal links, and conversion value.

    line 100
  7. Distinctive:

    Remove deleted URLs from XML sitemap.

    line 110
  8. Distinctive:

    Update internal links to point directly to the final URL (avoid relying on redirects)

    line 111

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Technical: Indexing

Guides indexing troubleshooting and fix actions. For how to find and diagnose issues in GSC, see google-search-console.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (Technical SEO)

  • Fix actions: noindex, canonical, content quality, URL Inspection; verify robots.txt does not block (see robots-txt)
  • Noindex: Page-level index control; which pages to exclude and how. Complements robots-txt (path-level crawl control) and google-search-console (Coverage diagnosis)

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL and indexing goals.

Identify issue from GSC (see google-search-console for Coverage report, issue types, diagnosis workflow). Then apply fix below.

Crawled - Currently Not Indexed

CauseAction
Low quality, duplicate, off-topicImprove content, fix duplicates, set correct canonical
Static assets (CSS/JS)See below
Feed, share URLs with paramsUsually OK to ignore; or noindex, canonical to main URL
Important content pagesUse URL Inspection, verify canonical/internal links/sitemap, Request indexing

Static Assets (Next.js / Vercel)

Vercel adds unique dpl= params to static assets per deploy, creating many "Crawled - currently not indexed" URLs.

DoDon't
Keep robots.txt allowing /_next/Do not block /_next/ (breaks CSS/JS loading). See robots-txt
Accept static assets in GSC as expectedDo not block /_next/static/css/ or ?dpl=
Use X-Robots-Tag for static assetsCSS/JS should not be indexed; no SEO impact

Static assets in "Crawled - currently not indexed" is normal and expected.

Other Issue Types (from GSC Coverage)

IssueFix
Excluded by «noindex» tagRemove noindex if accidental; keep if intentional
Blocked by robots.txtSee robots-txt; remove Disallow for important paths
Redirect / 404Fix URL or add redirect
Duplicate / CanonicalSet correct canonical; usually OK
Soft-404Page returns 200 but content says "not found" or empty—Google may treat as 404. Fix: return 404 status for truly missing pages; or add real content for 200 pages

Soft-404

A soft-404 occurs when a page returns HTTP 200 but the content indicates the page doesn't exist (e.g. "Page not found" message, empty state). Google may treat it as 404 and exclude from index.

FixWhen
Return 404Page truly doesn't exist; use proper 404 status
Add contentPage is intentional (e.g. empty search results); ensure substantive content or use noindex
RedirectIf URL moved, use 301 to correct destination

Noindex Usage

  • How: metadata.robots = { index: false } or <meta name="robots" content="noindex"> or X-Robots-Tag
  • Rationale: Not all site content should be indexed; noindex is a valid choice for many pages
  • Caution: Avoid noindex on important content pages
  • With robots.txt: robots.txt = path-level crawl control; noindex = page-level index control. Do not block noindex pages in robots.txt—crawlers must access the page to read the directive. Use both: robots for /admin/, /api/; noindex for /login/, /thank-you/, etc. See robots-txt for when to use which.
  • nofollow ≠ noindex: nofollow controls link equity only; it does not prevent indexing. To exclude from search, use noindex. See page-metadata for meta robots implementation.

Page Types That Typically Need Noindex

CategoryPage TypesTypical MetaReason
Auth & AccountLogin, Signup, Password reset, Account dashboardLogin: noindex,nofollow; Signup: noindex,followNo search value; login indexed = security risk; signup follow allows crawl of Privacy/Terms links
Admin & PrivateAdmin, Staging, Test pages, Internal toolsnoindex,nofollowNot for public; avoid discovery
Conversion EndpointsThank-you, Confirmation, Checkout success, Download gatenoindex,followPost-conversion; no SERP value; allow link equity
System & Utility404, Internal search results, Faceted/filter URLsnoindex,follow or noindex,nofollowThin/duplicate; 404 = error state
LegalPrivacy, Terms, Cookie Policy (optional)Often noindex,followLow-value indexed; reduces clutter
Duplicate & ThinPrinter-friendly, Parameter URLs, Near-duplicatenoindex,follow or canonicalDuplicate content; canonical preferred when possible
Low-ValueMedia kit, Feedback board (external), Thin pressnoindex or index for brand queriesCase-by-case

noindex,follow vs noindex,nofollow: Use noindex,follow for most cases—excludes from SERP but allows link equity. Use noindex,nofollow only for login (security), staging, or temporary test pages.

Page Removal Decision Framework

When intentionally removing a page from the web, choose the method based on whether a relevant alternative exists and whether the page should remain accessible:

ScenarioMethodRationale
Has a closely related replacement page301 redirectPreserves accumulated link signals and user flow
Content merged into a new page301 redirectDirect old URL to the new canonical location
Permanently deleted, no alternative410 GoneExplicitly signals permanent removal to search engines
Deleted, uncertain if permanent404 Not FoundSafe default; can reinstate later if needed
Still accessible but should not be indexednoindexPage remains available to users; excluded from SERP

Before removing: Check the URL's search traffic, backlinks, internal links, and conversion value. If the page has value, consider updating or merging rather than removing.

Common mistakes:

  • 404-ing pages that have relevant alternatives (wastes accumulated signals)
  • Redirecting all deleted pages to the homepage (breaks user intent)
  • Creating redirect chains (A → B → C) instead of direct redirects
  • Removing pages without cleaning up internal links pointing to them
  • Using robots.txt to block noindex pages (crawler must access the page to read the noindex directive)

Post-removal cleanup:

  1. Remove deleted URLs from XML sitemap; update and resubmit
  2. Update internal links to point directly to the final URL (avoid relying on redirects)
  3. For 301 redirects, ensure the target URL is in the sitemap
  4. In GSC, use URL Inspection to verify important pages; use Removals tool for temporary quick-hide (not permanent — use proper HTTP status or noindex)

Google Indexing API

TypeTypical use
JobPostingJob boards
BroadcastEventLive platforms

Requirements: Enable Indexing API, create service account, add owner in Search Console, request quota (default 200 URLs/day).

Output Format

Related Skills

  • google-search-console: Find and diagnose indexing issues in GSC
  • robots-txt: Path-level crawl control; when to use robots.txt vs noindex; do not block /_next/ or noindex pages
  • page-metadata: Meta robots implementation; noindex vs nofollow
  • xml-sitemap: Submit and maintain sitemap
  • indexnow: Faster indexing for Bing
  • canonical-tag: Resolve duplicate content

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.