Search Console page indexing report explained
A client emails on a Tuesday morning: "I published that page three weeks ago and it still isn't on Google." You open the page indexing report in Search Console, find the URL under "Crawled - currently not indexed", and now you have to turn that into a sentence a business owner can act on.
That translation job is why this report confuses people. It uses statuses that sound like errors when they are not, and it quietly mixes "your site is broken" with "this is working exactly as designed". Get it wrong and you either panic a client over nothing or miss a real indexing problem for months.
This guide covers what the report measures, what every status means, which ones need action, and how to put indexing into a client report without a jargon dump. For the click-and-impression half of the platform, see Search Console metrics explained for clients.
Last updated: September 2026
Key takeaways
- The page indexing report in Search Console shows which of your known URLs Google has indexed, which it has not, and the reason for each exclusion. It replaced the older index coverage report.
- "Not indexed" is not the same as "broken". Statuses like "Page with redirect" and "Alternate page with proper canonical tag" are normal and usually need no action at all.
- "Crawled - currently not indexed" means Google fetched the page and decided not to index it. That is a quality and duplication signal, not a crawling fault, and re-submitting the URL repeatedly will not change it.
- "Discovered - currently not indexed" means Google knows the URL exists but has not crawled it yet, often because of internal linking depth or server response time.
- Google has never guaranteed that every page will be indexed, so a healthy site can sit permanently below 100% indexed coverage.
- Across the client accounts connected inside ReportsMate, roughly 7 in 10 have Google Analytics 4 connected but only about 1 in 4 have Search Console, so most clients see traffic without ever seeing indexing.
What this guide covers
- What is the page indexing report in Search Console?
- Why pages are not indexed - every status in plain English
- What does crawled - currently not indexed actually mean?
- How the URL inspection tool fits with the report
- How to explain indexing to a client without the jargon
- Putting indexing into your monthly client report
- Common mistakes agencies make with this report
- Frequently asked questions
What is the page indexing report in Search Console?
The page indexing report in Search Console lists every URL Google knows about for your property, splits them into indexed and not indexed, and gives a reason for each URL left out. You will find it in the left-hand menu under Indexing, then Pages.
It used to be called the index coverage report. Google redesigned and renamed it, and the indexing coverage report name still shows up in older agency SOPs, so it is worth knowing both labels mean the same thing.
Three things shape everything else you do with it:
- It only covers URLs Google has discovered. A page nobody links to and no sitemap mentions will not appear as a problem. It will simply be absent.
- It reports on canonical URLs. If three URLs collapse into one canonical, the report tells you about the canonical and files the other two under a duplicate or alternate status.
- It lags. Expect a few days between a fix going live and the chart moving, which matters when a client asks why last week's fix has not shown up.
You can also filter by a submitted sitemap, which is the single most useful control in the interface. Filtering to "All submitted pages" strips out tag archives, parameter URLs and old test pages, and shows whether the pages you care about are indexed. Google's Page indexing report documentation in Search Console Help is the reference to keep open the first few times.
Why pages are not indexed - every status in plain English
Most "not indexed" statuses fall into three groups: intentional exclusions you set up yourself, technical faults that need fixing, and Google's own judgement calls. Knowing which group a status belongs to tells you whether to open a ticket or do nothing.
| Status | What Google is telling you | Group | Typical action |
|---|---|---|---|
| Server error (5xx) | Your server failed while Googlebot was fetching the page | Technical fault | Escalate to hosting or dev; check for load-related timeouts |
| Redirect error | A redirect chain, loop or bad target broke the crawl | Technical fault | Flatten the chain to a single hop |
| Not found (404) | The URL returns a 404 | Usually fine | Redirect only if a genuine equivalent page exists |
| Soft 404 | The page returns a 200 but reads as empty or as an error | Technical fault | Add real content or return a true 404 |
| Blocked by robots.txt | A robots rule stopped Googlebot fetching the URL | Depends | Fix the rule if the block was accidental |
| Excluded by noindex tag | A noindex directive is on the page or in the header | Depends | Remove the tag if the page should rank |
| Blocked due to access forbidden (403) or unauthorised request (401) | The URL sits behind a login or an IP restriction | Usually fine | Only act if a public page is affected |
| Page with redirect | The URL redirects somewhere else, so the target gets indexed | Working as intended | None |
| Alternate page with proper canonical tag | The page correctly points at another canonical | Working as intended | None |
| Duplicate without user-selected canonical | Google found near-identical pages and picked the canonical itself | Judgement call | Add a self-referencing canonical or consolidate the pages |
| Duplicate, Google chose different canonical than user | Your canonical was seen and overruled | Judgement call | Look for thin variants and conflicting signals |
| Crawled - currently not indexed | Fetched, assessed, not indexed | Judgement call | Improve depth and uniqueness; do not spam re-submissions |
| Discovered - currently not indexed | Known about, not yet crawled | Judgement call | Improve internal links and server speed |
One warnings row is worth watching: "Indexed, though blocked by robots.txt". Google indexed a URL it was never allowed to crawl, usually because other pages link to it. If the page is genuinely private, robots.txt is the wrong tool. Google's guidance on blocking search indexing with noindex explains why a crawler that cannot fetch a page also cannot see the noindex directive on it.
The canonical statuses trip up more agencies than anything else. Two of them ("Alternate page with proper canonical tag" and "Page with redirect") are signs the site is set up correctly. Reporting those as errors is how a healthy 400-page site gets described to a client as "300 pages broken".
What does crawled - currently not indexed actually mean?
"Crawled - currently not indexed" means Googlebot successfully fetched the page, evaluated it, and chose not to add it to the index. Nothing is broken. There is no 404, no robots block, no noindex. Google simply did not think the page earned a slot.
It shows up in predictable places: thin location pages spun from one template, e-commerce filter and variant URLs, tag archives, boilerplate posts that restate what fifty other pages already say, and new pages on sites with little authority.
"Discovered - currently not indexed" is a different problem with a different fix. Discovered means Google found the URL, usually in a sitemap or a link, but has not fetched it yet. That skews towards crawl capacity: very large sites, slow servers, or pages buried five clicks deep with almost no internal links pointing at them.
So the split is simple. Discovered is a crawling and architecture problem. Crawled is a value and duplication problem. The fixes barely overlap.
What actually moves a crawled-not-indexed page into the index is consolidation (merge four thin pages into one useful one), genuine differentiation (real specifics rather than a template with the suburb name swapped), and internal links from pages that already perform. Repeatedly hitting "Request indexing" does not work, and Google is explicit that indexing is never guaranteed.
Set that with clients early, because there is no target number here. A site with 900 URLs and 400 indexed can be in perfect health if the other 500 are filters, paginated views and redirects.
How the URL inspection tool fits with the report
The page indexing report tells you how many URLs share a status; the URL inspection tool tells you why one specific URL has it. You need both, and the workflow between them is where the diagnostic work happens.
Open a status, click through to the URL list, then inspect a sample of two or three URLs rather than all of them. Inspection gives you the canonical Google selected, the last crawl date, the crawl user agent, and whether the page was blocked. The URL Inspection tool documentation in Search Console Help covers the full output.
The "Test live URL" button is the part most people skip and the part that saves the most time. It fetches the page as it exists right now rather than as it was at the last crawl, so you can confirm a fix is live before you tell the client it is done.
Once a fix is deployed across a group of URLs, use "Validate fix" on that status. Google re-crawls a sample and reports back over the following days or weeks. It is slow, but it leaves a dated record you can point at later.
One caveat: inspection reflects the property you are looking at, and a domain property and a URL-prefix property for the same site can show different pictures. That is also why organic numbers rarely tie out between platforms, which we unpack in Search Console vs GA4 organic traffic explained.
How to explain indexing to a client without the jargon
Clients do not need the status names. They need to know whether the pages they paid for are showing up, and if not, what you are doing about it. Everything else is internal detail.
The framing that works is a three-line summary: how many of the pages that matter are indexed (from the sitemap-filtered view), what changed this period, and the one action you are taking.
Something like: "All 34 service pages are indexed. Six of the new location pages have not been picked up because Google sees them as too similar to each other, so we are rewriting three with real local detail this month."
Notice what that avoids. No status names, no percentages nobody asked for, no implication that Google made an error. Two terms are still worth teaching clients: crawling is Google fetching the page, and indexing is Google deciding to store it and consider it for search results. A page can be crawled and never indexed, which is exactly what "crawled - currently not indexed" describes.
We built ReportsMate email-first because, after years around agency reporting, the dashboards clients were handed almost never got logged into. An indexing explanation only lands if it arrives in the inbox, in the client's own words, next to the traffic number it explains. If it is sitting behind a portal login, it may as well not exist. See how it works if you want the delivery side handled automatically.
Putting indexing into your monthly client report
Indexing belongs in the client report as context for the traffic line, not as a standalone technical section. It answers the question the traffic number raises: is organic flat because rankings slipped, or because half the new content never made it into the index at all?
Here is a first-party number that surprised us. Across the client accounts with at least one platform connected inside ReportsMate, about 7 in 10 have Google Analytics 4 connected but only around 1 in 4 have Google Search Console. Roughly 6 in 10 of the GA4-connected clients have no Search Console connection at all, and every client that does have Search Console also has GA4. Nobody connects Search Console on its own.
The practical read: most client reporting covers what happened after someone arrived on the site and almost nothing about whether Google can find and store the pages in the first place. That is a blind spot for anyone selling SEO or content retainers, and it surfaces at the worst moment, three months into a content programme when the client asks why nothing has moved.
Connecting the platform is a one-click Google authorisation on our Google Search Console integration, and the Search Console report documentation covers what lands in the client email.
Common mistakes agencies make with this report
The most expensive mistake is reading the all-known-URLs view instead of the sitemap-filtered view. The unfiltered number includes parameter URLs, old staging paths, paginated archives and every redirect the site has ever carried. It is not a health score and should never be pasted into a client report as one.
A few others we see regularly:
- Chasing 100% indexed. Not a real target. Excluded canonicals and redirects are supposed to be there.
- Treating "Crawled - currently not indexed" as a dev ticket. Nobody in engineering can fix a page Google judged as thin. That is a content job.
- Requesting indexing in bulk. Manual submission is for one-off urgent pages, not a workflow.
- Ignoring the warnings row. "Indexed, though blocked by robots.txt" quietly puts pages in results with no description, often pages that should never have been public.
- Only checking when something goes wrong. A monthly glance catches a migration mistake weeks before the traffic chart does.
- Confusing a robots.txt block with a noindex. They do opposite things, and Google's robots.txt documentation is worth ten minutes if that has ever been fuzzy on your team.
Want a second pair of eyes on the numbers each month? Compare plans and pricing and get the indexing picture into the same automated email as everything else.
Frequently asked questions
Q: What is the page indexing report in Search Console?
A: It is the Search Console report that shows which of your pages Google has indexed, which it has not, and the reason for every exclusion. You will find it under Indexing, then Pages. It was previously called the index coverage report, and the indexing coverage report name still appears in older documentation and agency processes. The report only covers URLs Google has already discovered, so a page with no internal links and no sitemap entry will not appear at all.
Q: Why are my pages not indexed by Google?
A: There are three broad reasons. You told Google not to index them, through a noindex tag, a robots.txt rule or a canonical pointing elsewhere. Something is technically broken, such as a 5xx error, a redirect loop or a soft 404. Or Google crawled the page and decided it was not worth indexing, which shows as "Crawled - currently not indexed". The report names the specific reason for each URL, so start there rather than guessing. Several statuses on a healthy site are working exactly as intended and need no action.
Q: What does crawled - currently not indexed mean?
A: It means Googlebot fetched the page successfully and chose not to index it. Nothing is broken. It usually points at thin, templated or near-duplicate content, or a brand-new page on a site without much authority yet. The fix is editorial rather than technical: consolidate overlapping pages, add genuine specifics rather than swapped-out variables, and link from pages that already earn traffic. Re-submitting the URL will not change Google's assessment, and Google has never guaranteed that every page gets indexed.
Q: How is that different from discovered - currently not indexed?
A: Discovered means Google knows the URL exists but has not crawled it yet, so it has made no quality judgement at all. It is typically a crawl capacity issue on large sites, a slow server, or a page buried too deep with too few internal links. Crawled means the fetch already happened and the page was passed over. So discovered is an architecture problem and crawled is a content problem. Confusing the two sends your dev team after a fix that was never theirs to make.
Q: How long does it take for a page to get indexed?
A: There is no guaranteed timeframe. New pages on established sites with good internal linking are often indexed within days, while pages on new or low-authority sites can wait weeks or never get indexed at all. After you fix a technical issue and hit "Validate fix", Google re-crawls a sample and reports back over the following days or weeks. Set that expectation with clients up front, because "we fixed it yesterday" and "Google has processed it" are rarely the same week.
Q: Should I report indexing numbers to clients every month?
A: Report the trend, not the raw table. One line covering how many of the pages that matter are indexed, what changed since last month, and the single action you are taking is enough for almost every client. Use the sitemap-filtered view so the number reflects real pages rather than parameter URLs and archives, and pair it with the ranking and traffic story so the client sees cause and effect. That is the same principle behind how to report keyword rankings to clients.
Q: Can I automate Search Console indexing reporting for clients?
A: Yes. Search Console connects through a single Google authorisation, and from there the data can be pulled on a schedule and delivered as a branded email rather than another login the client will not use. That is the model ReportsMate is built on: connect the platforms once, set the cadence, and reports go out white-labelled under your agency's own sender identity. We are describing our own product, so weigh it accordingly, but the point holds regardless of tool choice. A report a client opens beats a dashboard they never visit.
Final tips
Read the sitemap-filtered view first. It is the difference between a number that means something and a number that starts an unnecessary conversation.
Sort by group, not by count. Split the statuses into "we did this on purpose", "this is genuinely broken" and "Google made a call", then act on the middle group plus the judgement calls affecting pages with commercial value.
Check it monthly rather than reactively. Migrations, plugin updates and a stray staging robots.txt file all cause indexing damage that shows up here days before it shows up in traffic.
And write the client-facing version in their language. Indexing is not a technical footnote, it is the answer to why the content programme has or has not started working. White-labelling means the report carries your agency's branding rather than the tool's, so that explanation reads as your analysis.
Stop losing your Sundays to client reports. Start your free 14-day trial - no credit card, no setup, cancel anytime. Your clients get branded reports in their inbox automatically, including the Search Console numbers that explain the traffic line.