Search Console says your pages aren't indexed. Most of them aren't supposed to be.
Open the Page indexing report on almost any site and the grey bar is bigger than the green one, next to a list of reasons that read like errors. Most of them aren't. Here is how to tell which ones are costing you visitors.
A URL listed under Why pages aren't indexed in Google Search Console isn't a problem on its own. Google's documentation says most sites have some unindexed URLs, and that this is fine when the reason is a good one: a redirect, a duplicate, a page you deliberately marked noindex, or a page you removed. The report only matters when a page you actually want people to find is on that list.
So the useful question isn't how to get the grey number down. It's whether any of your important pages are in it, and which reason Google gave for each one.
Check the pages you care about first
Google is unusually direct about this. Its help page for the Page indexing report says a site with fewer than 500 pages probably doesn't need the report at all, and suggests searching Google for your key pages instead. For most small business and organization websites, that's the right place to start.
Make a short list of the pages that bring in work: the homepage, each service or product category page, location pages, and anything you've published that people genuinely find. Check each one with the URL Inspection tool at the top of Search Console. It tells you whether that exact URL is indexed, which URL Google treats as the canonical version, and when Google last crawled it. The Page indexing report can't answer that for a single page. You can't search it by URL, and its example list stops at 1,000 rows without any promise of being complete.
If every page on your list is indexed, you can read the rest of the report with a lot less anxiety.
The statuses that are usually fine
These make up most of the not indexed count on a typical site, and in most cases they describe the site working as intended.
| Status in the report | What it means | Worth acting on when |
|---|---|---|
Page with redirect | The URL redirects somewhere else. Google indexes the destination, not the old address. | The redirect itself is wrong, or it points somewhere that no longer exists. |
Alternate page with proper canonical tag | The page names another version as the main one, and Google agreed. | Almost never. Google's documentation says there is nothing to do. |
Duplicate without user-selected canonical | Google found near copies and picked one to show. Filter, sort and tracking parameters produce a lot of these. | Google picked the wrong copy of a page that matters to you. |
Excluded by ‘noindex’ tag | The page itself asked not to be indexed. | It's a page you want in search results. More on this below. |
Not found (404) | The URL doesn't exist anymore, or never did. | You still link to it, it's in your sitemap, or the page moved and has no redirect. |
Page indexing statuses that are normal on most websites
WordPress creates plenty of URLs in this group by itself. Attachment pages, tag and author archives, paginated archive pages, feeds and internal search results all turn up here, and on most sites nobody would miss them from Google.
The ones that keep real pages out of Google
When an important page carries one of these, it's worth fixing.
A noindex tag nobody meant to leave there
This is the most damaging status because it's absolute. A page that asks not to be indexed won't be indexed, however good it is.
On WordPress the usual cause is a setting rather than code. The Discourage search engines from indexing this site checkbox under Settings, then Reading, adds a noindex robots tag to every page on the site. It gets ticked while a site is being built and then carried into production during a launch or a move to new hosting, and nothing looks different to a visitor. SEO plugins add a second layer: Rank Math and Yoast can both mark an entire content type as noindex, or a single page, and those settings travel with the database.
To check a page, use URL Inspection and look at Indexing allowed?, or view the page source and search for noindex. The same instruction can also be sent in an X-Robots-Tag HTTP header, which doesn't appear in the page source, so URL Inspection is the more reliable check.
Load the homepage and one inner page, view the source, and search for noindex. It takes under a minute, and a noindex tag that survives a redesign or a hosting move can quietly remove a whole site from Google.
Blocked by robots.txt
A robots.txt file controls crawling, not indexing. A blocked page usually drops out of results, but Google says it can still be indexed without its content if other sites link to it, which is where the Indexed, though blocked by robots.txt warning comes from.
That leads to a common mistake. If you want a page kept out of search, Google's advice is to remove the robots.txt block and use noindex instead. While the page is blocked, Google can't crawl it, so it never sees the noindex tag. If an important section of your site appears under this status, look for a leftover Disallow rule, often one written for a staging copy.
Server error (5xx)
Googlebot asked for the page and the server failed or timed out. The odd error happens and Google tries again later. A steady count usually means one of two things: the server is struggling under load, or a firewall or bot protection service is treating Googlebot as an attack because it requests far more pages than a person would. Google's documentation names that second case specifically, and on managed hosting the fix usually sits with the host rather than inside the website.
The Crawl Stats report, under Settings in Search Console, shows whether Google is seeing availability problems across the site. If the server is simply slow, working out where the time goes comes before anything else.
Redirect error and soft 404
A redirect error means Google hit a chain that was too long, a loop, or a redirect to a broken or empty URL. They tend to build up over successive redesigns, when old redirects are never cleaned up and new ones are layered on top. Point every old URL straight at its final destination.
A soft 404 means the page returned a normal success response but looks empty or missing to Google. An out of stock product with nothing left on the page, an empty category, a search page with no results. Either give the page real content or have it return a proper 404.
Duplicate, Google chose different canonical than user
Your page declares one URL as the main version and Google disagreed. A canonical tag is a hint, not an instruction. Inspect the URL to see which page Google chose instead. If your declared canonical isn't genuinely similar to the page, Google won't use it. After a migration, this is also where you find canonical tags still pointing at the old domain or at a development address.
Crawled, currently not indexed, and discovered, currently not indexed
Discovered - currently not indexed means Google knows the URL exists but hasn't fetched it yet. Google's description says it typically wanted to crawl the page, expected that doing so would overload the site, and rescheduled. On a large store with thousands of filtered URLs, a long list here is normal. On a site with a few hundred pages, it's worth reading as a hint about server response times.
Crawled - currently not indexed means Google fetched the page and decided not to index it for now. Google says the page may or may not be indexed in the future, and that there's no need to resubmit it.
Google doesn't publish the reason for an individual page, so what follows is diagnosis rather than documentation. When this happens to pages that matter, the likely explanations are that the page adds little that isn't already covered elsewhere, that it's a near copy of another page on the same site, or that nothing on the site links to it. Those are the things to fix. Pressing Request Indexing again and again isn't one of them.
What Request Indexing actually does
Request Indexing, in the URL Inspection tool, asks Google to crawl the page again. It doesn't make Google index it. Google's documentation says indexing is never instant even after a direct request, and suggests only asking after an important change that Google hasn't picked up within a week or so.
It's genuinely useful straight after you remove an accidental noindex tag or robots.txt block, and it won't change the outcome for a page Google has already crawled and passed over. For a fix that affects many URLs, use Validate Fix on that issue in the Page indexing report instead, and Google rechecks the affected URLs over the following days.
After a redesign or migration, check this report twice
Most of the serious problems above arrive on launch day. A new site is built on a staging copy with search engines discouraged, the setting goes live with it, canonical tags still name the staging hostname, and old URLs redirect in chains or not at all. None of that is visible to someone browsing the site.
Check your key URLs and the Page indexing report about a week after launch, and again a few weeks later. If a jump in noindex, redirect or 404 counts lines up with the launch date, that's where to look. Our migration checklist covers the rest of what tends to get lost in a move.
Why indexing matters for AI answers too
Google's AI Overviews and AI Mode don't work from a separate index. Google's documentation on AI features says a page has to be indexed and eligible to show a snippet to appear as a supporting link, and that there are no additional technical requirements. A page held back by an accidental noindex tag is missing from the ordinary results and from the AI answers at the same time.
What a healthy report looks like
The indexed count is roughly the number of pages you'd be happy for a stranger to land on. Every page on your important list checks out in URL Inspection. The not indexed reasons are ones you can explain: redirects you set up, duplicates from filters and parameters, pages you chose to keep out, pages you removed on purpose. A large grey number on a site like that is fine.
The warning sign is a change rather than a size. A jump in noindex, server errors or redirect errors after a launch, a plugin update or a hosting change, or an important page moving from indexed into any of the reasons above, deserves attention the same week. Crawling and indexing are the first thing our SEO work looks at, because nothing else in search matters for a page Google won't index.