Page Indexing Report Explained: Every Status and What to Do

The page indexing report in Google Search Console lists the URLs Google knows about and tells you whether each one is in the index. Opening it for the first time can be alarming. A long list under "Not indexed" looks like a pile of errors, yet much of it is normal: redirects, duplicates and pages you chose to block.

This guide is for site owners and developers who want to read the report in order, sort the reasons into "ignore", "fix" and "wait", and confirm each fix. You will leave with a repeatable routine and a clear idea of which reasons deserve your time.

Google's own report page makes one point worth repeating before you start: not indexed is not necessarily bad. The question is whether the pages that matter to you are indexed, and, if not, whether the reason is something you can change.

Before you begin

You need a verified Search Console property, and the report only shows pages Google has found. Decide in advance which pages should be in search: your home page, product or service pages, articles and key landing pages. Everything else (internal search results, login pages, cart pages, filtered duplicates) may be fine to leave out.

Allow an hour for a first review. Reading the report changes nothing on your site, but fixes do. Before changing robots.txt rules, redirects or noindex tags, copy the current file or rule set so you can roll back. If you are not set up yet, see Set Up Google Search Console.

Step-by-step instructions

Step 1: Open the page indexing report and pick a sitemap filter

Open the Page indexing report for your property. The summary shows a chart of indexed and not-indexed pages. Above the chart, a filter lets you choose All known pages (the default), All submitted pages, Unsubmitted pages only, or a specific sitemap. A URL counts as submitted if it is in a sitemap you submitted, even when Google also found it another way.

Start with All submitted pages. A sitemap should list the pages you want indexed, so any submitted page that is not indexed deserves a reason. Then look at Unsubmitted pages only to find URLs Google discovered that you did not intend to list.

What success looks like: You can state how many of your intended pages are indexed and how many are not.

Step 2: Read the Source column

Each not-indexed reason has a Source. "Website" means the cause is on your site, and generally only these can be fixed by you. "Google" means the cause is on Google's side. Do not spend time trying to fix a Google-sourced reason with site changes.

What success looks like: You have separated reasons you can act on from reasons you cannot.

Step 3: Sort the reasons into three groups

Google lists the following reasons under "Why pages aren't indexed". Use this table as a triage guide.

Reason	What it means	Usual action
Server error (5xx)	The server returned a 500-level error	Fix server health and check the Crawl Stats host status
Redirect error	A chain that is too long, a loop, an over-long URL or a bad URL in the chain	Fix the chain; inspect it with a tool such as Lighthouse
URL blocked by robots.txt	robots.txt blocks crawling	Keep it if intended; robots.txt does not reliably keep a page out, so use noindex for that
URL marked 'noindex'	A noindex directive stopped indexing	Remove it if you want the page indexed
Soft 404	The page says "not found" but returns a non-404 code	Return a real 404, or add real content
Blocked due to unauthorized request (401)	The page needs authorization	Remove the requirement or allow verified Googlebot
Not found (404)	The page returned 404	Ignore if removed on purpose; use a 301 redirect if it moved
Blocked due to access forbidden (403)	The server returned 403 to Googlebot, which sends no credentials	Allow unauthenticated access or explicitly allow verified Googlebot
URL blocked due to other 4xx issue	A 4xx error not covered elsewhere	Debug with URL Inspection
Crawled - currently not indexed	Crawled, not indexed, may be indexed later	No resubmission needed
Discovered - currently not indexed	Found but not yet crawled	Usually wait
Alternate page with proper canonical tag	Correctly points to an indexed canonical page	Nothing needed
Duplicate without user-selected canonical	A duplicate with no declared canonical; Google chose another	Not an error; declare a canonical if needed
Duplicate, Google chose different canonical than user	Google disagreed with your declared canonical	Inspect Google's choice and check the pages really are similar
Page with redirect	A non-canonical URL that redirects	Nothing needed; the target may be indexed

Now group them:

Expected, no action: Alternate page with proper canonical tag, Page with redirect, Not found (404) for pages you removed, URL blocked by robots.txt for areas you meant to block.
Fix on your site: Server error (5xx), Redirect error, Soft 404, 401 and 403 blocks on public pages, noindex on pages you want found, and robots.txt blocks on pages you want crawled.
Investigate or wait: Crawled - currently not indexed, Discovered - currently not indexed, and the duplicate reasons.

The deeper guides for these are Crawled, Currently Not Indexed and Discovered, Currently Not Indexed.

What success looks like: Every reason in your report is labeled ignore, fix or wait.

Step 4: Inspect real examples

Click a reason to see example URLs and a history chart. The examples table is limited to 1,000 rows and may not be complete, even when fewer than 1,000 items exist. Treat it as a sample.

Pick a few URLs and run each through the URL Inspection tool. It shows whether Google could fetch the page, whether indexing was allowed, and which canonical Google chose. See URL Inspection Live Test for how to use the live test.

What success looks like: For each reason you plan to fix, you have seen the cause on at least one real URL.

Step 5: Watch the two warnings

Google also lists two warnings under "Improve page experience".

Indexed, though blocked by robots.txt. The page was indexed through links despite the robots.txt block. If you want it out of search, remove the robots.txt block and use noindex, because Google cannot see a noindex tag on a page it is not allowed to crawl. If you want it crawled, remove the block.
Page indexed without content. Google indexed the page but could not read the content. This is not a robots.txt issue; inspect the page.

What success looks like: No page you care about carries either warning, or you know why it does.

Step 6: Fix everything, then validate

Fix all instances of an issue first. Validation stops if even one remains. Then open the issue details page and click Validate fix once. Do not click it again until validation succeeds or fails.

Search Console checks a few sample pages first. If they still show the error, validation ends and nothing changes. Otherwise it rechecks only the known affected URLs, not the whole site. Google says validation typically takes up to about two weeks, sometimes longer. If it fails, use See details to find the failing URL, fix it, and start a new validation. Only Pending and Failed URLs are rechecked.

A tip from Google: validating against a sitemap that contains only your key pages can finish faster.

What success looks like: The validation state moves from Started to Passed.

Step 7: Allow for stale data

Counts change when Google recrawls a page, and Google says it can take a few days to a week or more to crawl new or changed pages. Each URL shows a crawl date. If you fixed the problem after that date, the report may be out of date until the next crawl. An issue also stays open until 90 days after its last instance is gone.

What success looks like: You compare fix dates with crawl dates before concluding a fix failed.

Final verification checklist

Your key pages appear under Indexed, or you know the reason they do not.
Submitted pages that are not indexed each have a labeled reason.
No intended page is blocked by robots.txt, noindex, a 401 or a 403.
No important URL shows Soft 404, Server error (5xx) or Redirect error.
Every fix has a validation request, and you checked its state.
You compared fix dates with last crawl dates.

Common mistakes to avoid

Trying to get every URL indexed. Duplicates, redirects and blocked areas are supposed to be excluded. Focus on pages that matter.
Using robots.txt to hide a page from search. It blocks crawling, not indexing. Use noindex on a crawlable page instead.
Clicking Validate fix before fixing everything. One remaining instance ends validation. Fix all instances first.
Clicking Validate fix repeatedly. Wait for the current validation to finish.
Treating a 404 on a removed page as a bug. If the page was removed on purpose with no replacement, a 404 is correct.
Treating removed and moved pages the same. If a page was removed with no replacement, a 404 is fine. If it moved, use a 301 redirect to the new address.
Trusting the examples list as complete. It is a sample capped at 1,000 rows.
Fixing Google-sourced reasons on your site. Check the Source column first.

Frequently asked questions

What does "Not indexed" mean?

It means Google has not put that URL in its index, either because of an error or for a legitimate reason such as a redirect or a duplicate.

How many not-indexed pages is too many?

There is no safe number. What matters is whether your important pages are indexed and whether the reasons for others are expected.

Will submitting a sitemap index all my pages?

No. A sitemap helps Google discover URLs. It does not make indexing certain.

How long until the report updates after I fix something?

It depends on when Google recrawls. Google says new or changed pages can take from a few days to a week or more, and validation can take up to about two weeks.

Should I use Request Indexing for every fixed page?

Use it sparingly for important pages. A request does not make indexing certain, and there is a daily limit. See Request Google Indexing the Right Way.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.