Page Indexing Report and URL Inspection in Search Console

"My page isn't showing up in Google" is the most frequently asked question in SEO, and the answer is almost always in Search Console's Page indexing report. This report splits every URL Google knows about on your site into two groups — indexed and not indexed — and groups the second one by reason.

That word, reason, is the key. "Not indexed" is not one problem; behind it sit around fifteen completely different situations: a technical block, duplication, a canonical decision, a quality judgement, or simply a queue. Each has its own fix, so the rule is read the reason first, act second.

This article works through every status using Google's official explanations and shows how to use the URL Inspection tool for diagnosis. For the tool as a whole, see what Google Search Console is and how it works.

Crawling versus indexing

These two words are constantly mixed up, yet they are separate processes:

Crawling is Googlebot downloading the URL. It is simply fetching a file.

Indexing is Google processing that content, storing it in the index and making it a candidate for results. That is a decision — and Google may decide against it.

The distinction underpins all diagnosis: a crawled page can go unindexed even when everything is technically correct. Google never guarantees indexing.

How the report is structured

The report has three blocks:

Indexed pages. URLs in Google's index. The number itself is not a target — 500 indexed pages on a 500-page site is not a good sign if half of them are filter URLs and empty categories.

Not indexed pages. A list grouped by reason. Note that not every line here is a problem. "Alternate page with proper canonical tag", for example, is entirely normal and correct.

Warnings. Indexed, but with an issue — for instance a page indexed despite being blocked by robots.txt.

Understanding this split saves time. The practical rule: a large "not indexed" number is not bad in itself — what matters is for which reason and whether those URLs are pages you wanted in the index at all.

Every status and what it really means

The table below pairs Google's official explanation with the practical translation.

Sorting these into three families makes the work easier:

1. Technical blocks (401, 403, 404, 5xx, robots.txt, noindex, redirect errors) — the fix is in your hands and is precise. Most relate to server responses: HTTP status codes and SEO and 404, 410 and soft 404.

2. The canonical/duplicate group — Google sees the same content on several URLs and picks one. The fix: align canonical tags, internal links and redirects.

3. The quality and queue group ("Crawled/Discovered — currently not indexed") — the two hardest. The next section is devoted to them.

The two hardest statuses

"Discovered — currently not indexed" — Google knows the URL but has not crawled it. Officially: "The page was found by Google, but not crawled yet." The usual causes:

• The site is new, or the URL count grew fast — crawl budget does not stretch.
• The server is slow to respond, so Googlebot has reduced its pace.
• Few or no internal links point at the URL, so Google does not treat it as a priority.
• It exists in the sitemap but not in the site structure (an "orphan page").

What to do: strengthen internal linking (the single most effective step — see topical authority and content clusters), improve server response time, clean the sitemap (no 404s or redirected URLs), and reduce pointless URL variants such as filter and sort parameters.

"Crawled — currently not indexed" — Google has seen the page and chose not to index it. Officially: "The page was crawled by Google but not indexed." This is not a technical error but a value judgement. The most common causes:

• The content is thin or repeats your other pages.
• The page adds nothing to what already ranks.
• Template content dominates (identical text, one word changed).
• The page is machine-generated (filter combinations, empty categories).

What to do: strengthen the page (original data, depth, real questions answered), consolidate near-duplicates, and noindex or delete pages that add nothing. For how to structure the topic: what is semantic SEO.

The URL Inspection tool

URL Inspection shows everything Google knows about a single URL. In Google's description, it "provides information about Google's indexed version of a specific page, and also allows you to test whether a URL might be indexable".

There are two distinct sets of data here, and confusing them is the most common mistake:

So immediately after a fix, the indexed version will still show the old problem — that is expected. To verify the fix you must press Test live URL.

Request indexing. This button places the URL in a priority crawl queue. Google states plainly: "submitting a request does not guarantee that the page will appear in the Google Index." There are also daily limits, both on inspection requests and on indexing requests. Submitting hundreds of URLs by hand is not a workflow; at scale the right tool is the sitemap.

On waiting times, Google says: "Indexing typically takes only a day or so, but can take much longer in some cases" — in some cases you should allow a week or two. On new sites it can take longer still.

The tool also reports the page's canonical URL (both your declared one and the one Google selected — they can differ), mobile usability, structured data, and which sitemap it was found in. A canonical mismatch shows up here faster than anywhere else.

A diagnostic sequence

Keep the sequence in this order:

1. Inspect the URL to read the status of the specific page.
2. If the status is a technical block (robots.txt, noindex, 4xx, 5xx) — remove the block and run a live test.
3. If the status is canonical/duplicate — make sure the canonical tag, internal links and sitemap all point at the same URL.
4. If the status is "Discovered" or "Crawled — not indexed" — work on structure and content instead of pressing a button.
5. After the fix, request indexing once and allow a week or two.
6. If the report offers a Validate fix button, use it — Google will re-check the whole group.

Common mistakes

1. Combining noindex with a robots.txt block. If robots.txt blocks the page, Google cannot read the noindex inside it, and the URL may stay in the index. The correct order: unblock robots.txt, let the noindex be seen, then block if you still want to.

2. Trying to drive "not indexed" to zero. That number includes perfectly normal cases (canonical alternates, redirects). The target is not zero but a sensible distribution of reasons.

3. Requesting indexing for the same URL over and over. It does not speed up the queue and it burns your daily limit.

4. Reading a live test result as index status. A live test says "could be indexed", not "is indexed".

5. Not cleaning the sitemap. A sitemap containing 404s, redirects or noindex URLs erodes trust and wastes crawl budget.

6. Expecting results in a day on a new site. Google says indexing typically takes about a day but can take much longer — on new domains, weeks are normal.