Indexing & Coverage Troubleshooting Template

Confirm the Problem

You think a page should be indexed but aren't sure it actually isn't.

Start by proving the page is genuinely excluded

Before changing anything, confirm the URL is truly missing from Google's index. A page that ranks for its own title is already indexed.

• Search Console URL Inspection: paste [Full URL] into the inspection bar and read the verdict at the top. "URL is on Google" means it is indexed; "URL is not on Google" means it is not.
• site: query: run a search for [site:example.com/path]. No result is a strong signal, but trust URL Inspection over [site:], which can lag.
• Coverage context: open the Page Indexing report and find which excluded reason this URL falls under.

Record the exact reason string Google reports. The fix for "Crawled - currently not indexed" is completely different from "Blocked by robots.txt," so capturing the precise state now saves wasted effort later.

Inspected URL: [URL]   Reported state: [State]

Crawled-Not-Indexed & Discovered-Not-Indexed

Google knows your URL but has chosen not to index it (yet).

Two different signals, two different responses

These states usually point to value or crawl-budget issues rather than a technical block, so resist the urge to just hit "Request indexing" repeatedly.

• Crawled - currently not indexed: Google fetched the page but decided it wasn't worth indexing. This is most often a quality or value signal: thin, duplicative, or low-demand content.
• Discovered - currently not indexed: Google found the URL (often via your sitemap) but hasn't crawled it yet. This frequently reflects crawl-budget limits or a slow, large site.

For Crawled-not-indexed, strengthen the page: deepen the content, add internal links from relevant indexed pages, and make sure it serves clear intent. For Discovered-not-indexed, reduce crawl waste: fix slow responses, prune low-value URLs, and improve internal linking so important pages are reachable in fewer clicks.

State: [State]   Likely cause: [Quality / Crawl budget]

Blocked by robots.txt / noindex

A directive is actively keeping the page out of the index.

Check for self-inflicted blocks

These are the most fixable causes because the page is excluded by an explicit rule you control. URL Inspection will name the directive directly.

• Blocked by robots.txt: Google was disallowed from crawling. Open your robots.txt and find the rule matching [URL path]. Remember that a robots block prevents crawling, not always indexing, but it stops Google from seeing your content.
• Excluded by noindex tag: the page returns a [noindex] meta robots tag or X-Robots-Tag header. Run the live test in URL Inspection to confirm the directive is still present right now.

Remove or correct the offending rule, then verify with the live test that Google can both crawl the page and that no noindex remains. Watch for the trap where robots.txt blocks the page so Google can't even see that you've removed a noindex. Once clean, move on to requesting indexing.

Directive found: [robots.txt / noindex]

Canonical & Duplicate Issues

Google indexed a different URL than the one you submitted.

When Google picks its own canonical

If a page shows "Duplicate, Google chose different canonical than user" or "Alternate page with proper canonical tag," the content is likely indexed, just under another URL.

• Compare canonicals: in URL Inspection, check "User-declared canonical" against "Google-selected canonical." A mismatch is the heart of the issue.
• Find the chosen page: note which URL Google preferred and decide whether that is acceptable or wrong.

If Google's choice is acceptable, no action is needed: the content is covered. If you want the inspected URL to win, send consistent signals: a self-referencing canonical, internal links pointing to the preferred URL, matching sitemap entries, and genuinely distinct content so the pages aren't seen as duplicates. Conflicting signals are the usual reason Google overrides your declaration.

Declared canonical: [URL]   Google-selected: [URL]

Quality & Thin-Content Causes

The page is crawlable and unique but still not indexed.

Earn the index, don't just request it

When there is no technical block and no canonical conflict, "Crawled - currently not indexed" almost always reflects Google's judgment that the page doesn't add enough value. Treat this as a content problem, not a bug.

• Assess uniqueness: does the page offer something the indexed competitors and your own other pages don't?
• Check depth and intent: thin, templated, or auto-generated pages are common non-index candidates.
• Review internal authority: orphaned pages with no internal links read as low priority.

Improve the page substantively (original detail, clear purpose, and helpful structure) then link to it from related, already-indexed pages to pass relevance and discovery signals. Accept that some pages, like near-empty tag archives or duplicate paginated views, may simply not warrant indexing. Consolidating or removing those can lift the pages that do.

Page value gap: [Notes]

Request Indexing & Validate Fixes

You've fixed the root cause and want Google to recheck.

Close the loop the right way

Once the underlying issue is resolved, prompt Google to recrawl and confirm the fix held. Do this only after the real cause is fixed: requesting indexing on an unfixed page wastes the request.

1. Run the live test: in URL Inspection, click "Test live URL" to confirm the page is now crawlable, indexable, and free of noindex.
2. Request indexing: click "Request indexing" for the single corrected URL. Avoid repeatedly submitting the same page: it does not speed things up.
3. Validate at scale: in the Page Indexing report, open the affected reason and click "Validate fix" so Google rechecks all URLs in that group.

Validation runs over days or weeks; monitor the status until it reads "Passed." For sitewide fixes, lean on Validate Fix rather than inspecting URLs one at a time.

Fix applied: [Description]   Validation status: [Status]

What does Crawled - currently not indexed actually mean?

It means Google fetched the page but chose not to index it. This is usually a quality or value judgment rather than a technical error, so the fix is normally to improve the page's depth, uniqueness, and internal linking rather than to change a setting.

How is Discovered - currently not indexed different?

Discovered means Google knows the URL exists, often from your sitemap, but hasn't crawled it yet. It frequently signals crawl-budget pressure on large or slow sites. Improve site speed, prune low-value URLs, and strengthen internal links to important pages.

Should every page on my site be indexed?

No. Many URLs, such as filtered or sorted listings, near-empty tag pages, and duplicate paginated views, are correctly left out. Aim to get your genuinely valuable pages indexed rather than chasing 100 percent coverage.

Why did Google choose a different canonical than the one I set?

When signals conflict, Google may pick its own canonical and report Duplicate, Google chose different canonical. Align your canonical tag, internal links, sitemap entries, and content so they all point to and support the same preferred URL.

Does requesting indexing guarantee a page gets indexed?

No. Request indexing only asks Google to recrawl sooner; it never overrides a quality decision or a block. If the real cause isn't fixed, the page will remain excluded, so resolve the root issue before requesting.

How long does Validate fix take?

Validation typically runs over several days to a few weeks as Google rechecks the URLs in the affected group. Leave it running and monitor the status; it will move from Started to either Passed or Failed without you re-submitting.