GSC Indexing Debug Loop
A Search Console troubleshooting loop for pages that are discovered but not indexed or missing from Google results.
Use loop copies the kickoff prompt. Copy Markdown and Download loop include the complete Markdown page with context, source attribution, anchors, and guardrails. Cursor / Claude Code buttons prepare the shorter kickoff prompt only.
Supported agents
Goal
Find technical or content reasons a page may not be indexed.
Feedback gate
curl -I $URLStop condition
The page is technically indexable and remaining indexing uncertainty is clearly documented.
Give the agent these inputs before it starts the loop. This keeps discovery bounded and prevents vague retries.
The loop assumes these commands or integrations are available. Missing tools should be reported as blockers, not ignored.
Two separate pieces: the kickoff prompt starts the loop, while the downloaded Markdown carries the complete reference page.
1. Copy or download
Use the kickoff for a fast agent run. Download the full Markdown when you need source, context, and attribution in one file.
2. Paste into the agent
Start a fresh agent session in the target repo and provide the requested project context if the loop asks for it.
3. Let it self-pace
The agent should act, check evidence, retry only when the gate fails, and stop at the stated exit condition.
The diagram shows the order. This checklist keeps only the action, command, and failure handling needed during a real pass.
1. Check status and robots
Fetch headers and robots.txt.
curl -I $URL && curl -sL $SITE_URL/robots.txt2. Check canonical and noindex
Inspect server-rendered HTML metadata.
curl -sL $URL | rg "canonical|noindex|description|<title"3. Check sitemap/internal links
Ensure the URL is linked and listed where appropriate.
4. Check content usefulness
Assess whether the page is thin, duplicated, or low value.
This is the text copied by Use loop. It is intentionally shorter than the Markdown export.
Debug indexing for the target URL: status, robots, canonical, noindex, sitemap, internal links, and content usefulness. Return exact fixes and uncertainty.
Goal: Find technical or content reasons a page may not be indexed.
Check command: curl -I $URL
Exit condition: The page is technically indexable and remaining indexing uncertainty is clearly documented.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not promise indexing. Only verify technical readiness and recommend fixes.Quality
90/100
Safety
93/100
Expected output
Indexing diagnosis with specific technical and content fixes.
Related loops
Browse allSitemap Freshness Check
Verify that important public pages are present in sitemap.xml with canonical URLs and reasonable lastmod values.
Kickoff preview
Fetch sitemap.xml, compare it against expected public URLs, check exclusions, patch the generator, and re-fetch until coverage is correct. Goal: Ensure sitemap.xml includes canonical public pages and excludes private/admin/API routes. Check command: curl -sL $SITE_URL/sitemap.xml Exit condition: Sitemap contains important public URLs and excludes private/API/admin pages. Max iterations: 3 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not include private, admin, API, or duplicate query URLs in sitemap.
SEO Metadata Audit Loop
Audit title, description, canonical, Open Graph, headings, and indexability for SEO-critical pages.
Kickoff preview
Audit SEO metadata from server-rendered HTML for the target pages. Verify title, description, canonical, H1, Open Graph, and indexability, then fix and re-check. Goal: Ensure SEO-critical pages have unique, server-rendered metadata and indexable content. Check command: curl -sL $URL | head -80 Exit condition: Each target page has unique title, description, canonical, visible H1, and no accidental noindex. Max iterations: 5 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not rely only on client-rendered metadata for SEO-critical pages. Verify server HTML.
Thin Content Expansion Loop
Find pages with shallow content and expand them with practical examples, source context, FAQs, and related loops.
Kickoff preview
Improve a thin page by adding specific examples, operational guidance, source context, FAQs, and related links. Avoid filler and duplicate boilerplate. Goal: Turn a thin page into a useful page with distinct user value. Check command: curl -sL $URL | wc -c Exit condition: The page clearly answers user intent with distinct examples, guidance, and internal links. Max iterations: 4 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not expand pages with filler text. Add specific, actionable value or remove/noindex the page.
Ship PR Until Green
Implement a scoped change, open or update a pull request, inspect CI, and continue until all required PR checks pass.
Kickoff preview
Take this branch to a green pull request. Implement the requested change, run local verification, open or update the PR, run `gh pr checks`, inspect failures, fix root causes, and repeat until every required check passes or you hit the iteration cap. Goal: Open or update a pull request and stop only when all required PR checks are green. Check command: gh pr checks Exit condition: All required pull request checks are successful and the PR is ready for review or merge. Max iterations: 10 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not disable required checks, edit loops to skip jobs, or remove tests to make CI green. - Do not merge the PR unless the user explicitly asked for merge authority.