What Is Index Coverage Report? A Complete Guide for SEO Beginners

November 15, 2026 · Updated: November 5, 2026 · 9 min read · Indexing

An index coverage report shows which pages of your site Google has indexed, and why the rest are not indexed. In Google Search Console it now appears as the Pages report, under Indexing. Older guides call it the Coverage report, and the name change causes confusion, but it is the same report with a new label. If you are looking for “Coverage” in Search Console today, open Indexing, then Pages.

This report is one of the most useful pages in Search Console, and one of the easiest to misread. The total number of indexed pages matters far less than which pages are indexed, and why the important ones are missing. This post explains how to read the report, what each reason means, and what to fix first.

Where to find the report

  1. Open Google Search Console and select the property for your site.
  2. In the left menu, open Indexing, then Pages.
  3. You will see a chart over time, with two main groups: Indexed pages, and Not indexed pages.
  4. Below the chart, a table lists the reasons for the Not indexed group, with a count and example URLs for each reason.

Use the filters at the top to narrow the report. You can filter by sitemap, which is useful if you want to check only the pages in a specific sitemap, for example only blog posts, or only product pages. You can also filter by a date range to see whether a change you made actually moved the numbers.

The two groups, and what to focus on

Indexed pages

These are pages Google has indexed and that can appear in search results. A rising indexed count is good, but only if the pages being added are pages you want in search. If the indexed count rises because tag pages, search pages, or thin auto-generated pages got indexed, that is not progress. It is index bloat, and it makes the report harder to read.

Not indexed pages

These are pages Google knows about but has not indexed, for a stated reason. This group always includes pages you deliberately excluded, such as noindexed pages and pages blocked by robots.txt. A large Not indexed count is not automatically a problem. The question is always: are the pages in this group pages you want indexed, or pages you meant to exclude?

Start with the reasons that affect pages you care about. Ignore, for now, reasons that cover pages you deliberately kept out of search.

Not indexed reasons, what they mean, and what to do

Reason What it means What to do
Discovered – currently not indexed Google knows the URL exists but has not crawled it yet. Wait, and improve internal links to the page. This often clears on its own, especially for new pages.
Crawled – currently not indexed Google crawled the page but chose not to index it. Check content quality, originality, and duplicate content. Add real value, or merge the page into a stronger page.
Excluded by noindex tag The page carries a noindex tag. Nothing, if you meant to exclude it. Remove the tag if you want it indexed, then request indexing.
Blocked by robots.txt Robots.txt stops Googlebot from crawling the page. Nothing, if the block is deliberate. Fix the rule if it blocks a page you want indexed.
Page with redirect The URL redirects to another page. Nothing, if the redirect is correct. Remove the redirecting URL from your sitemap, and keep only the final destination.
Alternate page with proper canonical tag The page is a duplicate, and its canonical tag points to another page. Nothing, if the canonical page is the one you want indexed. This is the correct outcome for duplicates.
Duplicate, Google chose different canonical than user Google picked a different page as the canonical version than the one you specified. Check whether the two pages are too similar. Make the page you want indexed clearly different, and check your internal links point to it.
Duplicate without user-selected canonical Google found duplicate content and you did not specify a canonical page. Add a canonical tag to the version you want indexed, and reduce the duplication if you can.
Not found (404) The URL returns a 404 error. Fix the link, restore the page, or redirect it to a relevant page. Remove it from your sitemap.
Soft 404 The page returns a 200 status but looks like an error page, for example an empty page or a “not found” message with a 200 code. Fix the page content, or return a real 404 if the page does not exist.
Server error (5xx) The server returned an error when Googlebot tried to crawl the page. Fix the server error first. This is a technical problem, not a content problem.
Redirect error The redirect chain is broken, too long, or loops back on itself. Fix the chain so the URL points directly to its final destination.
Crawled – currently not indexed, and other crawl issues Google crawled the page but found a problem that stopped indexing, such as a rendering or loading issue. Check the page in the URL Inspection tool and fix the reported problem.
See also  Indexing for Beginners

How to work through the report, step by step

  1. Filter by sitemap first. If you have separate sitemaps for posts, pages, and products, check each one on its own. A problem in the posts sitemap is easier to fix than a mixed list of everything.
  2. Sort reasons by impact, not by count. A reason with 500 tag pages matters less than a reason with 20 product pages. Open the example URLs for each reason and check whether they are pages you care about.
  3. Fix the root cause, not the report. A 404 reason is fixed by fixing the link or the page, not by hiding the URL. A “crawled, not indexed” reason is fixed by improving the page, not by requesting indexing again.
  4. Use Validate Fix after a bulk fix. In the report, click into a reason, then click Validate Fix. Google will recrawl the affected URLs and report back whether the problem is gone. Validation can take days to weeks, depending on how many URLs are involved.
  5. Check the trend, not a single day. The chart over time shows whether indexed pages are rising and whether a specific reason is shrinking. A single day’s spike often reflects a crawl pattern, not a real change.
  6. Recheck after a month. Indexing changes are slow. A fix made today may not show up in the report for two to four weeks.

Common mistakes when reading this report

Trying to get 100 percent indexed

No large site has every known URL indexed, and trying to reach 100 percent is a waste of time. Tag pages, search pages, filtered URLs, and old redirects will always sit in the Not indexed group, and that is fine. Aim for 100 percent of your important pages indexed, not 100 percent of all URLs.

See also  How Long Does Google Take to Index

Treating every Not indexed reason as an error

Several reasons are not errors at all. “Excluded by noindex”, “blocked by robots.txt”, “page with redirect”, and “alternate page with proper canonical tag” are often the correct outcome for those URLs. Only act on a reason when the pages behind it are pages you want in search.

Requesting indexing for every excluded page

Requesting indexing does not override a noindex tag, a robots.txt block, or a quality decision. Fix the underlying cause first, then request indexing for the fixed pages.

Ignoring the sitemap filter

Without the sitemap filter, the report mixes pages from your sitemap with URLs Google found through links, old sitemaps, and external sites. That mix makes it hard to tell whether your own pages are indexed. Filter by sitemap to get a clean view.

Checking the report once and forgetting it

Indexing drifts over time. New plugins, theme changes, and bulk imports can quietly add noindex tags, break sitemaps, or create duplicate URLs. A monthly check of the Pages report catches these problems before they affect traffic.

What a healthy report looks like

  • Your main posts and pages are in the Indexed group.
  • The Not indexed group is mostly made up of pages you deliberately excluded, plus redirects and canonical duplicates.
  • No important page sits under “crawled, not indexed” or “discovered, not indexed” for more than a few weeks without a reason you can explain.
  • Server errors, redirect errors, and 404s affecting important pages are close to zero.
  • The trend over three months is stable or rising for indexed pages, not falling without explanation.
See also  Indexing Automation Methods

If your report looks like that, you do not have an indexing problem, even if the Not indexed count is large. If your important pages are missing from the Indexed group, work through the reasons for those pages specifically, and ignore the rest for now.

Frequently asked questions

Is the index coverage report the same as the Pages report?

Yes. Google renamed the Coverage report to the Pages report, under Indexing, in Search Console. Older posts and videos still call it the Coverage report, which is why this post uses that name in its title.

How often does the report update?

Search Console data usually lags by two to three days, and the Pages report reflects Google’s last crawl of each URL, not a live check. A fix you made today will not appear in the report tomorrow.

Why does Google know about URLs I never submitted?

Google finds URLs through links on your site, links from other sites, old sitemaps, and URLs it crawled in the past. The report covers all URLs Google knows about, not only the ones in your current sitemap.

Should I remove Not indexed URLs from my sitemap?

Yes, for URLs that should not be indexed. Your sitemap should list only pages you want indexed. Removing a noindexed or redirected URL from the sitemap makes the report cleaner and gives Google a clearer list of what matters.

The index coverage report, or Pages report, is a diagnostic tool, not a scoreboard. Use it to find which important pages are missing, fix the reason behind each one, and check the trend over time. That is all it is for, and that is enough.

Before you submit: Check DA, link type and comment or submission rules on the target site first. Rules change often, so a quick check saves rejected submissions.
Rashed Zaman

SEO specialist with expertise in link building, backlink indexing, and search engine optimization. Contact: hellorashedzaman@gmail.com

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *