Skip to content

Google Search Console Indexing Issues: How to Diagnose and Fix Them

By VantaRank Team

An indexing issue means Google either hasn't crawled a page yet or has crawled it but decided not to add it to the index. Both outcomes look similar from the outside — the page doesn't appear in search results — but they have different causes and different fixes, and Search Console's Page Indexing report is the only place that reliably tells you which one you're dealing with.

A page that isn't indexed can't rank, no matter how good it is. Diagnosing why always comes before trying to improve it.

Reading the Page Indexing Report

Open Search Console and go to Indexing → Pages. The report splits your URLs into indexed and not indexed, then breaks the 'not indexed' group down by specific reason. That reason is the single most useful piece of information for diagnosis — treat every status as a distinct problem with its own fix, not a single generic 'not indexed' bucket.

Common Statuses, What They Mean, and How to Fix Them

StatusWhat it meansTypical fix
Discovered — currently not indexedGoogle knows the URL exists but hasn't crawled it yet, often due to crawl budget prioritizationImprove internal links to the page; wait — this often resolves on its own for important pages
Crawled — currently not indexedGoogle crawled the page but chose not to index itUsually a content depth or quality issue — expand, differentiate, or consolidate the page
Duplicate without user-selected canonicalGoogle found near-identical content and picked a canonical for youAdd an explicit canonical tag to the version you actually want indexed
Alternate page with proper canonical tagThe page correctly points elsewhere via canonical — this is often expected, not an errorConfirm the canonical target is correct; no action needed if intentional
Excluded by 'noindex' tagA noindex directive is present in the HTML or HTTP headerRemove the tag if the page should be indexed; leave it if intentional
Blocked by robots.txtYour robots.txt file disallows crawling of the URLUpdate the disallow rule if the page should be crawlable
Page with redirectThe URL redirects elsewhere, so the original isn't indexedExpected behavior for redirected URLs — verify the destination is correct
Soft 404The page returns a 200 status but looks empty or error-like to GoogleReturn a real 404/410 for genuinely missing content, or add substantive content

Why 'Excluded' Doesn't Always Mean 'Broken'

One of the more common misreadings of this report is treating every row under 'Not indexed' as a problem to fix. Several statuses reflect Google working exactly as intended: a page correctly canonicalized to another version, a URL that legitimately redirects elsewhere, or a duplicate parameter variant Google correctly chose not to index separately. Before spending time on a fix, confirm the status actually represents unintended behavior — a canonical tag pointing where you meant it to point is a success, not an error, even though it shows up in the same 'excluded' list as genuine problems.

A Diagnostic Workflow

  1. Check the specific status in the Page Indexing report rather than assuming the cause
  2. Run a live URL Inspection test on the affected page to see how Googlebot renders and reads it right now
  3. Verify robots.txt isn't blocking the URL or its resources (CSS/JS needed to render it)
  4. Check for a noindex tag in both the HTML head and the HTTP response headers (X-Robots-Tag), since either can cause exclusion
  5. Confirm the canonical tag is self-referencing (or intentionally points elsewhere) and matches what you expect
  6. Assess content depth — thin or largely duplicate pages are common causes of 'Crawled — currently not indexed'
  7. Check internal links — an under-linked page is both harder to discover and signals lower priority to Google
  8. Only use 'Request Indexing' after fixing the underlying cause, not as a substitute for fixing it

This same workflow overlaps closely with a full technical SEO audit — indexation review is one of its core steps, just applied here at a deeper, status-by-status level.

Crawl Budget on Larger Sites

On sites with tens of thousands of URLs or more, 'Discovered — currently not indexed' often isn't a per-page problem at all — it's a symptom of crawl budget being spent elsewhere. Google allocates a finite amount of crawling attention to any given site, roughly in proportion to the site's perceived quality and how efficiently it can be crawled. If a large share of that budget is consumed by low-value URLs — infinite faceted navigation combinations, internal search result pages, or duplicate parameter variations — genuinely important pages can sit undiscovered far longer than they should.

The fix in that situation isn't to individually request indexing for each affected page; it's to reduce the low-value crawl surface first (via robots.txt disallow rules, noindex tags, or parameter handling), then let Google's crawl budget naturally redirect toward the pages that matter. This is a structural fix, and it usually takes longer to show results than a single-page fix, but it addresses the actual cause rather than the symptom.

Common Mistakes

  • Mass-requesting indexing for many URLs at once, which doesn't speed up crawling and can look like spam signaling
  • Treating 'Excluded' statuses as errors by default — some, like a correct canonical or redirect, are working as intended
  • Fixing the symptom (requesting indexing) without fixing the cause (thin content, missing internal links, wrong canonical)
  • Ignoring crawl budget on large sites — spending crawl priority on low-value URLs can starve important pages of attention
  • Not checking rendered HTML — a page can look complete in the browser but render incompletely for Googlebot if key content depends on client-side JavaScript

Indexing Diagnostic Checklist

  • Identified the exact exclusion status for each affected URL, not just 'not indexed'
  • Ran a live URL Inspection test to confirm current crawlability and rendering
  • Verified robots.txt and noindex tags aren't unintentionally blocking the page
  • Confirmed the canonical tag points where you intend
  • Reviewed content depth and internal links for pages stuck at 'Crawled — currently not indexed'
  • Used 'Request Indexing' only after the underlying cause was actually fixed

For sites with recurring indexing problems across many URLs, a structured Google Search Console setup and review — paired with a full technical SEO audit — usually finds the systemic cause faster than fixing individual URLs one at a time. See our sample SEO audit for what that review looks like in practice.

FAQ

How long does it take Google to index a new page?+

It varies widely — from hours to several weeks — depending on crawl frequency for your site, internal linking, and overall site authority. There's no fixed timeline Google publishes.

Does 'Request Indexing' guarantee a page gets indexed?+

No. It only asks Google to prioritize a crawl sooner; whether the page then gets indexed still depends on the same quality and technical factors as any other page.

Is 'Discovered — currently not indexed' something to worry about?+

Not always. For less important pages, it often resolves naturally as Google works through its crawl queue. For pages you actually want ranking soon, improving internal links to them can help.

Can a page be indexed but still blocked by robots.txt?+

Yes, in a limited way — Google can index a URL it's blocked from crawling if it finds links to it elsewhere, but it can only show the URL with no real description, since it never read the content.

Want this reviewed for your own site?

Get a prioritized, written SEO audit of your website — no ranking guarantees, just clear findings and next steps.