Most people open the page indexing report in Google Search Console, see a scary red “Not indexed” number, and panic. That panic is almost always misplaced. The report — renamed from “Index Coverage” a few years back, which is why you’ll still hear people call it the coverage report — is not a list of problems. It’s a ledger of decisions: for every URL Google knows about, it records whether the page made it into the index and, if not, exactly why. Learning to read it means learning which reasons are Google working as intended and which are your site quietly leaking rankings. Confuse the two and you’ll burn a week fixing URLs that were never meant to rank.
What the Page Indexing Report Actually Measures
The page indexing report lives under the “Indexing” section of GSC and splits every known URL into two buckets: Indexed (eligible to appear in search) and Not indexed (known but excluded). Below the chart sits the part that matters — a table of reasons, each with a URL count and a trend line. That reason string is the entire game. “Excluded by ‘noindex’ tag” and “Crawled – currently not indexed” both count as not indexed, but one is your instruction being obeyed and the other is Google declining your content. Treating them the same is the single most common mistake in reading gsc indexing data.
One caveat before you trust any number: the report only covers URLs Google has discovered. A page nobody links to, that isn’t in your sitemap, and that Google has never found simply doesn’t appear here at all. A clean report is not proof of full coverage — it’s proof that the URLs Google knows about are accounted for.
Crawling vs Rendering vs Indexing — Get This Straight First
Almost every confusing status in the report dissolves once you separate three stages that people wrongly treat as one event. Crawling is Googlebot fetching the raw HTML at a URL. Rendering is Google executing the page’s JavaScript in a headless Chromium to see the final DOM — this happens later, in a render queue that can lag the initial crawl by seconds to days. Indexing is Google deciding the rendered result is worth storing and serving.
A URL can pass one stage and fail the next. It can be crawled but never indexed. It can be indexed on its raw HTML before rendering ever completes. When your content is injected client-side and the render queue hasn’t caught up, Google may index an empty shell. Knowing which of the three stages a status refers to tells you where to look: a crawl-stage problem is a server, robots, or link issue; an index-stage problem is almost always about quality, duplication, or canonicalization.
The “Not Indexed” Reasons You Can Safely Ignore
A large chunk of your not-indexed count is Google behaving correctly. Left alone, these are noise:
- Alternate page with proper canonical tag — Google found a duplicate, followed your canonical, and indexed the version you pointed it to. This is your setup working. Do nothing.
- Page with redirect — the URL 301s or 302s elsewhere. Google indexes the destination, not the redirect. Expected.
- Excluded by ‘noindex’ tag — Google saw your
noindexdirective and obeyed it. Only a problem if you didn’t mean to noindex the page. - Duplicate, Google chose different canonical than user — worth a glance (Google disagreed with your canonical choice), but often harmless when the pages are genuine near-duplicates.
If most of your “Not indexed” total sits in these rows, your index coverage is healthy. The number looks alarming only because GSC lumps deliberate exclusions in with real failures under one red headline.
“Crawled – Currently Not Indexed”: The One That Actually Hurts
This is the status that should get your attention, because it’s Google’s polite way of saying the page wasn’t worth keeping. Google fetched it, evaluated it, and chose not to index it. There’s no technical block — the problem is the content itself. Common causes: thin or near-duplicate pages, doorway-style templated pages with the address swapped out, content that adds nothing over what already ranks, or pages Google deems low-priority for a site whose overall quality signal is weak.
The fix is never a technical toggle. It’s consolidation and quality: merge thin pages into one strong resource, add genuine information gain the existing top results lack, strengthen internal links from pages that are indexed, and improve the sitewide quality baseline so Google extends more trust. Requesting indexing on a thin page just gets it re-evaluated and re-rejected. Fix the page first.
“Discovered – Currently Not Indexed”: A Crawl-Budget Signal
Different beast entirely. Here Google knows the URL exists — from your sitemap or a link — but hasn’t crawled it yet, or crawled it and deprioritized returning. On small sites this usually means the page is low-value or freshly published and just needs time. At scale, it’s frequently a crawl-budget symptom: Google is rationing how much of your site it fetches, often because the server is slow, or because thousands of low-value URLs (faceted-navigation permutations, session parameters, infinite calendars) are diluting the crawl. Tighten internal linking to the URLs that matter, prune or block the junk, and speed up server response so Googlebot fetches more per visit.
noindex vs disallow: The Trap That Traps Everyone
These two do completely different things, and mixing them creates a bug that’s invisible until you understand the mechanism. A noindex directive (a meta tag or an X-Robots-Tag HTTP header) tells Google not to index a page it has crawled. A Disallow line in robots.txt tells Google not to crawl the URL at all. Here’s the catch: if you disallow a URL in robots.txt, Googlebot never fetches it — so it never sees the noindex tag on the page. The page can still get indexed (URL-only, no snippet) on the strength of external links, and you have no way to remove it because Google can’t read the very instruction that would.
The rule: to keep a page out of the index, allow crawling and serve a noindex. To keep Googlebot from wasting crawl budget on worthless URLs it doesn’t need to index anyway, use Disallow. Never both on the same URL. A correct robots.txt block for a search-results path looks like this:
User-agent: *
Disallow: /search
Disallow: /*?sort=And a header-level noindex for a staging or thank-you page:
X-Robots-Tag: noindexServer Errors, Soft 404s, and the Status-Code Rows
Several reasons map to HTTP status codes, and these are the ones to fix fast because they signal a broken experience. Server error (5xx) means Google hit a failing response — recurring 5xx during crawl throttles how much Google will fetch. Not found (404) is fine for genuinely dead pages but a problem when internal links or your sitemap still point at them. Soft 404 is the sneaky one: the page returns a 200 OK but looks empty or “not found” to Google (a blank category, an out-of-stock product with no content), so Google treats it as a 404 despite the success code. Fix it by returning a real 404/410 for genuinely gone pages, or by giving the URL actual content if it should live.
How to Use Validation Without Wasting Weeks
When you’ve genuinely fixed a reason, click into that status and hit Validate Fix. GSC re-crawls a sample, and if the fix holds, rolls the validation across the affected URLs — a process that can take anywhere from a few days to a couple of weeks. The mistakes to avoid: don’t validate before the fix is actually live and confirmed with the URL Inspection tool; don’t validate a “Crawled – currently not indexed” batch when all you did was resubmit — you need to have changed the content. And don’t sit refreshing the report daily. Indexing runs on Google’s schedule; validation is a request, not a command.
Turning the Report Into a Monitoring Habit
The real value of the page indexing report isn’t the one-time cleanup — it’s the trend line. A slow climb in “Crawled – currently not indexed” over months is an early quality-erosion warning long before traffic drops. A sudden spike in “Discovered – currently not indexed” flags a crawl-budget or server regression. A jump in “Excluded by ‘noindex'” after a deploy usually means someone shipped a noindex to production by accident — one of the most common and costly SEO mistakes there is.
The problem is that GSC makes you check this manually, per property, and it only shows you Google’s side. This is where continuous auditing earns its keep. SEO Rocket’s real-crawler site audit walks your site the way Googlebot does and surfaces the upstream causes the coverage report only hints at — redirect chains, thin and duplicate pages, orphaned URLs, missing canonicals, 4xx/5xx status codes, and noindex tags where they don’t belong — with each finding paired to the fix. It won’t replace GSC’s ground truth about what Google actually indexed, but it catches the issues that become not-indexed rows before Google ever penalizes you for them, and it tracks the trend continuously instead of on a manual check. Pair that with rank tracking and the client dashboard and you’re watching cause and effect together rather than reacting to a red number after the traffic’s already gone. The workflow was built on a playbook proven across 1,000,000+ ranking pages, and index hygiene was always the unglamorous foundation under it.
Frequently Asked Questions
Why is my page indexed but not showing in Google search?
Being indexed only makes a page eligible to appear — it doesn’t guarantee ranking. If the URL Inspection tool says “URL is on Google” but you can’t find it, the page is indexed but ranking too low to see, or it’s outranked by a canonical version Google chose. Search site:yourdomain.com/exact-url to confirm it’s genuinely in the index, then treat visibility as a ranking problem, not an indexing one.
How long does it take Google to index a new page?
Anywhere from a few hours to a few weeks, depending on your site’s crawl frequency and authority. Established sites with strong internal linking and a submitted sitemap often see new pages indexed within days; new or low-authority domains can wait weeks. Requesting indexing via URL Inspection can nudge a single important page, but it doesn’t override Google’s quality assessment.
Is “Crawled – currently not indexed” bad?
It’s the most important not-indexed status to investigate, because it means Google evaluated the page and chose not to keep it — almost always a content-quality or duplication signal rather than a technical fault. A handful of these is normal; a growing pile across your money pages is a warning that your content isn’t clearing the bar, and no technical fix will change that. Improve or consolidate the pages.
