Page not indexed: what Search Console is really telling you

A new service page has been live for three weeks and Google will not show it. You open Search Console, click Indexing → Pages, and there are two numbers: 412 pages indexed, 1,874 not indexed. Below that, a table of reasons, each with a count, none with an explanation. The first reaction is alarm, the second is to fix all of them.

Both send you the wrong way. This piece sorts the messages into three classes (harmless, quality verdict, genuine defect), says what to do about each, and ends with the order to work through them.

Where the page indexing report lives and how to read it

The report is called "Page indexing" and sits under Indexing → Pages. Click a reason for example URLs: a sample of about a thousand rows, never the full list.

Three things first.

The report lags. It summarizes past crawls. What you fix today does not move the curve today. How Google sees one URL right now is a question for URL Inspection at the top.

"Not indexed" is not a penalty. It simply means these URLs are not in the index; on every healthy site a large share is deliberately out.

A sitemap is not an indexing guarantee. Google treats sitemaps as a discovery hint, not an instruction. Submitted means only that Google knows the URL exists; there is no guarantee and no deadline.

How the messages sort out:

The harmless class: messages where doing nothing is correct

Alternate page with proper canonical tag in plain English: we found your canonical and we respect it. That is praise, phrased like an error. A clothing shop whose 1,200 items each expose four size variants as their own URL has 3,600 rows here. Whether your markup is right is a question for your canonical tags, not for this report.

Page with redirect collects every URL that 301s elsewhere. After a relaunch that runs into the thousands, and every row proves the redirect works.

Excluded by 'noindex' tag is the one to look at, exactly once. Cart, thank-you pages, internal search results, tag archives, print views: none of that belongs in the index, and seeing it here proves your setting works. It gets dangerous only when a page that should rank is in the list, usually a checkbox ticked in the CMS six months ago.

The point about this class: these numbers grow with the site, and they are supposed to. 20,000 non-indexed URLs next to 900 indexed ones is normal for a shop with faceted filters and an emergency for a 30-page business site. The absolute number says almost nothing, the slope says everything: which reason is growing this month.

"Crawled - currently not indexed" is a quality verdict, not a bug

The most important message in the report and the one handled wrong most often. Google came, read the page, and decided not to include it. No server error, no tag, no block. That is why the usual advice misleads when it sends you into robots.txt and your meta tags: there is nothing there. This is a verdict, not a defect: the page adds nothing that is not already somewhere else.

An electrical contractor near Manchester has 34 location pages built: "Electrician in Stockport", "Electrician in Oldham". Same copy, swapped town name, one reworded sentence about travel time. Three are indexed, the biggest towns. The other 31 sit under Crawled - currently not indexed. Google did arithmetic, not mischief: whoever reads pages 4 through 34 learns nothing page 3 had not said.

The test is uncomfortably honest: delete everything on the page that appears in the same form on another page of yours. On the location pages, a town name survives.

So the fix is never "submit it again", it is one of three things. Consolidate instead of multiply: 34 thin location pages become one "Areas we cover" page with a town list, travel times and three real projects. Add something of your own: a reference job in that town, with the year, scope and a price range. Or link to it internally.

The second common case: the page is fine, but no link points at it. Google found it through the sitemap alone, and a sitemap is not a relevance signal. A page that is neither in the navigation nor mentioned in body copy looks like one the owner does not value either. How to pull existing pages out of that state is in updating existing content.

"Discovered - currently not indexed" means Google has not got round to it

This message looks almost identical to the previous one and means something else. Google knows the URL, from your sitemap or a link, but has never fetched it. There is no verdict on the content, because the content is unread: a volume problem.

Google only fetches a limited number of URLs per day from any site. That budget is undocumented, and on small sites it is almost never the issue. It becomes one when a site floods itself. An online shop with 1,200 real products, but filters for colour, size, brand and price whose combinations each produce their own indexable URL, submits 41,000 URLs in its sitemap. 38,000 sit under Discovered - currently not indexed. The shop gave Google not too little but far too much.

Second cause: a slow server, which makes Google throttle the crawl rate. Third: click depth, because anything six clicks from the home page sits far back in the queue. So: merge filter combinations with canonicals, trim the sitemap to the pages that should rank, build categories so every product is three clicks away.

In one sentence: Crawled - currently not indexed means read and rejected, Discovered - currently not indexed means not read yet. You fix the first in the content and the second in the structure.

The defect class: server errors, 404s, soft 404s and blocks

This is what is genuinely broken, and it comes first: fixing it works immediately.

Server error (5xx): your server handed Googlebot an error. Check the logs for the day URL Inspection names as the last crawl. Usually it is timeouts under load, or rate limits mistaking Googlebot for an attacker.

Not found (404): not a problem in itself. The only useful question is where the link comes from. Internal link: fix it. External link to a page that used to exist: redirect to the successor. Otherwise leave the 404, it is the correct answer. Never redirect everything to the home page wholesale, that manufactures soft 404s by the dozen.

Soft 404: the URL answers with status 200 but looks like an error page to Google. Typical cases are empty categories, search results with no hits, and JavaScript-loaded content that never reaches Googlebot. Pick one: real content or an honest 404.

Blocked by robots.txt: the one entry that can make an entire website invisible. The classic cause is a Disallow: / from staging that travelled along at launch.

Blocked due to access forbidden (403) and Blocked due to unauthorized request (401): password protection or refused access. With 403 there is often a firewall or CDN rule locking Googlebot out. Test: open URL Inspection, run the live test, look at the status code.

And then the combination people break their teeth on: marking a page noindex and blocking the same URL in robots.txt. Google may not fetch it, cannot read the noindex, and may keep the URL indexed anyway, fed by links and anchor text. That is what Indexed, though blocked by robots.txt reports. Either the block or the noindex, never both. Which fits which purpose is in robots.txt and noindex.

Why "Request indexing" almost never helps

URL Inspection has a "Request indexing" button, the most common waste of time around this report. The daily quota runs from a handful to a few dozen URLs per property; Google gives no exact figure and has said it will not raise the limit, given how much junk gets submitted.

The button does one thing: it puts the URL in the crawl queue. It says nothing about indexing. For a defect you just fixed it is exactly right and often works within hours. For Crawled - currently not indexed it is useless: Google has read the page already, so it fetches it again, finds the same text, reaches the same decision.

What works instead is not on that screen: a link from a strong, well-indexed page in body copy, merging five half-answers into one, and adding numbers or experience not already on 30 other sites. All three change the substance. The button only changes the queue.

How long does it take Google to index a page?

Google publishes no binding deadline here, and any guide promising "24 to 48 hours" is guessing. What you can observe falls into two brackets.

In days: a new page on a site Google visits regularly and links internally is often indexed within hours. A fixed server error clears on the next fetch, and the report follows days later.

In weeks: moving from Crawled - currently not indexed into the index after a real rewrite typically takes weeks, because Google has to fetch and reassess the page. A new domain needs weeks for its first pages, and for validation after a fix Google itself budgets about two weeks.

Waiting is right when three conditions hold: the page is younger than two weeks, URL Inspection reports no problem, and at least one indexed page links to it. If a page instead drops out after weeks of clicks, that is a case for diagnosing lost rankings.

Where to start

1. Open Indexing → Pages, set the range to three months, and read the slopes, not the counts. A reason that went from 200 to 3,000 in four weeks is your topic. One that has sat at 8,000 for a year is not.
2. Clear the defect class in this order: robots.txt block, 401 and 403, Server error (5xx), Soft 404.
3. Check the list under Excluded by 'noindex' tag for pages that should rank. If there are none, tick the harmless class off.
4. Export the example URLs for Crawled - currently not indexed and find the pattern. Usually it is every page of one type: location pages, author archives, product variants. Treat the pattern, not the URL.
5. For Discovered - currently not indexed, compare your sitemap URL count with the number of pages you want to rank. If the first is a multiple of the second, that is where the work is.
6. Only now, and only for pages you changed, request indexing.

If the causes sit further back than the report shows, take a pass through the usual suspects, as described in finding SEO problems.

Frequently asked questions

Why is my page not showing up on Google?

First check whether it is in the index at all: paste the URL into URL Inspection, and the panel names the reason. If the page is indexed and still cannot be found, that is a ranking problem, not an indexing one, and you look in the performance report.

How long does it take Google to index a new page?

Google gives no deadline. On a site crawled regularly that links the page internally it is usually hours to a few days; on a brand new domain, weeks. More than two weeks without movement means something is in the way, most often a missing internal link.

What does "Crawled - currently not indexed" mean?

Google fetched and read the page but did not add it to the index. Technically everything is fine, which is the point. Usually it is a quiet quality verdict: the page offers nothing that is not already elsewhere.

What is the difference between crawling and indexing?

Crawling means fetching, indexing means including. Google reads a page first, then decides separately whether it enters the search index. Hence two messages: "Discovered" means not crawled yet, "Crawled" means read but not included.

Why did my page suddenly drop out of the index?

The usual causes: a noindex added by a plugin, a canonical pointing elsewhere, an accidental redirect, or server errors during the last crawl. URL Inspection names the reason. Without one of those, it is usually a reassessment of the content.

Does requesting indexing in Search Console help?

For a defect you just fixed, yes, it gets the repair in front of Google faster. For "Crawled - currently not indexed", no: Google has already read the page and reaches the same conclusion on a second fetch. The quota is small, do not burn it on unchanged pages.

Does every page of my site need to be indexed?

No, and it is usually a sign of care when they are not. Cart, thank-you pages, internal search results, filter combinations and login areas do not belong in the index. A large "not indexed" count is normal for a shop.

Why is Google not indexing the URLs from my sitemap?

Because a sitemap is a discovery hint, not an instruction. If many of your sitemap URLs sit under "Discovered - currently not indexed", the sitemap is too big for the substance of the site. Trim it rather than resubmit it.