Pages Not Indexed by Google: Every Reason and How to Fix It
What each reason in the Page indexing report means, which ones need action, and how to fix and validate them in Google Search Console.
- Any website
- Visits within reach
- Each problem joined to its fix

Pages not indexed by Google are pages Google has found but left out of its index, so they cannot appear in search results. The Page indexing report in Google Search Console gives the reason for each group: usually a noindex tag, a robots.txt block, a duplicate, a server error or a soft 404, or thin content.
To see your own website the way Google does, try our AI website SEO tools, part of our AI SEO Tools.
This article is part of our complete guide: Website SEO Analysis.
- After you press Validate fix in the Page indexing report, validation typically takes up to about 2 weeks, and in some cases much longer (Search Console Help on the Page indexing report).
- Since WordPress 5.3, ticking "Discourage search engines from indexing this site" adds a noindex, nofollow robots meta tag to every page (WordPress documentation on the Reading settings).
- Google refreshes its cached copy of a website's robots.txt file every 24 hours, and the robots.txt report can request a recrawl sooner (Google Search Central on updating robots.txt).
- The Crawl Stats report shows host status as green when Google met no significant availability problems in the past 90 days (Search Console Help on the Crawl Stats report).
Test which of your pages Google leaves out with the AI website SEO checker
Are pages not indexed by Google always a problem?
No: Google says you should not expect every address on a website to be indexed, only the canonical pages. A page needs attention only when you want customers to find it.
A page that Google has not indexed is, as far as search is concerned, a page that does not exist: it cannot rank, be clicked or bring a single enquiry. Pages not indexed by Google are listed in Google Search Console with a short reason beside each group, and those reasons are more useful than most owners realise. Some describe a real fault, such as a server error or a tag left behind after a redesign. Others describe Google working exactly as it should, such as skipping a duplicate copy of a page. Below, each reason is explained with whether it needs action, how to fix it, and how to use URL Inspection and Validate fix to confirm that Google has accepted the change.
Google handles every page in stages: it discovers the address, crawls the page, decides whether to store it in the index, and only then ranks it. A page can drop out at any of those stages, and the Page indexing report tells you which stage and why. A healthy website always has pages that are not indexed, because Google's goal is to index the canonical version of each important page, meaning the main version of each piece of content. Old addresses that now redirect, copies of pages with tracking codes on the end and deliberately hidden thank-you pages all belong in the not indexed group. Seeing them there is a sign the website is sending clear signals, not a fault.
What deserves attention is a page you want customers to find appearing under a reason that should not apply to it. A physiotherapy clinic in Bristol should worry if its sports massage page is excluded by a noindex tag, but not if its booking confirmation page is. The total of not indexed pages tells you very little, because one shop with a filter menu can create thousands of harmless variations. Look instead at which pages sit under each reason, starting with the ones that earn money. If no page of your website appears in Google at all, even for your business name, that is a wider question: why a whole website is not showing on Google, with nine site-wide reasons and their fixes, has its own answer, and it usually starts with a setting, a missing sitemap or a new domain rather than the page-level reasons covered here.
How do you find every reason in the Page indexing report?
Open Google Search Console, select Pages under Indexing, and read the table titled "Why pages aren't indexed", which lists each reason with the number of pages affected.
The chart splits known pages into Indexed and Not indexed, and the table below it groups the not indexed pages by reason. A Source column shows whether a reason comes from your website or from Google, and Google's help notes that, in general, you can fix only the issues where the source is listed as Website. Clicking a reason opens a chart of its history and a list of example addresses you can inspect one by one. The menu above the chart can limit the report to all submitted pages, which is the most useful view, since it shows only the addresses listed in the sitemaps you submitted. Google adds that a website with fewer than 500 pages probably does not need the report at all, because URL Inspection on the important pages is quicker.
Read the labels exactly, because a few sound alike and mean quite different things. The report joins the two halves of the crawled and discovered reasons with a hyphen, and they are written with a comma here. Google's help article also words a couple of reasons differently from the report, for example calling the noindex reason URL marked 'noindex'. The report reflects what Google found the last time it crawled each page, so a fix made this morning will not appear until Google has been back. The table covers the reasons a business website meets most often.
| Reason in the report | What it means | Needs fixing? |
|---|---|---|
| Excluded by 'noindex' tag | The page asks not to be indexed | Only if the page should be found |
| Blocked by robots.txt | Google may not fetch the page | Only if the page should be found |
| Crawled, currently not indexed | Read, then left out for now | Usually, by improving the page |
| Discovered, currently not indexed | Known but not yet crawled | Often, through links and hosting |
| Duplicate without user-selected canonical | Google indexed another version | Only if Google chose wrongly |
| Alternate page with proper canonical tag | Points correctly to its main version | No |
| Page with redirect | Forwards to another address | No, if the redirect is intended |
| Not found (404) | The address does not exist | Only if it has value or links |
| Soft 404 | Looks missing but reports success | Yes |
| Server error (5xx) | The server failed to answer | Yes |
Which reasons come from your own settings?
A noindex rule and a robots.txt block are the two reasons that come straight from your own settings, and both are often left behind by a redesign or a plugin.
Excluded by 'noindex' tag means the page carries a rule, in a robots meta tag or in an X-Robots-Tag response header, telling search engines not to index it. On a thank-you page or a customer account area that is correct, while on a service, product or article page it is almost always an accident. On WordPress, look first at the "Discourage search engines from indexing this site" box under Settings, then Reading, which adds a noindex rule to the whole website. Then check your SEO plugin's settings, since the main SEO plugins can hide a whole content type, such as all pages, as well as a single page in its advanced settings. On other platforms, look in each page's SEO settings for an option that hides it from search engines, and on any platform clear every cache afterwards so Google sees the clean version.
Blocked by robots.txt means a rule in the robots.txt file at the root of your website forbids Google from fetching the address. Open your domain followed by /robots.txt and look for a Disallow line covering the page, such as a rule for a whole folder left over from development. The robots.txt report in the settings of Google Search Console shows the robots.txt files Google found, when it last checked each one and any problems it met. A related status, Indexed, though blocked by robots.txt, means Google stored the address anyway because other pages link to it; to remove such a page you must unblock it and add noindex, because Google's documentation says a noindex rule only works when robots.txt does not block the page. Two rarer reasons belong here too: Blocked due to unauthorized request (401) means a page asks for a login, and Blocked due to access forbidden (403) often means a security plugin or firewall is turning Googlebot away.
What do the duplicate, canonical and redirect reasons mean?
The duplicate, canonical and redirect reasons describe how Google picked one main version of each piece of content, and most of them need no action.
Google stores one version of each piece of content, the canonical, and lists the other copies as duplicates. Duplicate without user-selected canonical means the page is a duplicate of another page and names no preferred version, so Google chose one itself. It becomes a problem only when Google chose the wrong version, such as a print copy or an address with a tracking code. Inspect one of the listed addresses to see the canonical Google selected, and if it is wrong, add a canonical link pointing to the version you prefer. Most WordPress setups already print a canonical link on each page, so on WordPress the cause is usually a mixed signal rather than a missing tag.
Duplicate, Google chose different canonical than user means you named a main version but Google indexed another, usually because internal links, the sitemap or redirects point somewhere else. Make the signals agree by linking to the preferred address everywhere and listing only that address in the sitemap. Alternate page with proper canonical tag is the healthy version of this, and Google says there is nothing you need to do, so a hotel in Salzburg with an address per booking date, all pointing to one room page, can ignore it. Page with redirect lists old addresses that forward to new ones, which is normal after a redesign, and only needs you to update internal links and the sitemap. Redirect error does need fixing, because it covers loops and chains that run too long, so point each old address straight at its final destination.
How do you fix not found, soft 404 and server errors?
Redirect valuable missing pages, make soft 404s either truly missing or genuinely useful, and work with your host to stop repeated server errors.
Not found (404) means the address does not exist, either because a page was deleted or because a link points to an address that never existed. A 404 is a normal answer, so act only when the missing page had visitors, links from other websites or a clear replacement, and then add a permanent 301 redirect to the closest equivalent page. Soft 404 is trickier, because the server reports success while the page tells the visitor it does not exist or looks empty. An online tea shop in Amsterdam whose sold-out product pages show nothing but the word "unavailable" is a typical case. Return a real 404 or a redirect for pages that are truly gone, and give pages that should stay real content, such as a description, alternatives and a note on when stock returns.
Server error (5xx) means Google asked for the page and your server returned a 500-level error. A few errors during maintenance do no lasting harm, but if the error rate rises, Googlebot throttles back its requests to avoid overloading the server, so new and changed pages are crawled more slowly. The Crawl Stats report, in the settings of Google Search Console, shows host status and the responses Google received, so compare those dates with plugin updates, traffic peaks or changes at your host. Overloaded shared hosting, a broken plugin and an aggressive firewall are the usual causes. Share the affected addresses and times with your hosting company, because they can read the server logs that show exactly what failed.
Why are pages crawled or discovered but not indexed?
Crawled, currently not indexed usually means Google judged the page not valuable enough yet; Discovered, currently not indexed means Google knows the address but has not crawled it.
Crawled, currently not indexed means Google fetched and read the page but chose not to store it for now. Google says such a page may or may not be indexed in the future and that there is no need to resubmit it, so pressing Request indexing repeatedly rarely helps. The usual reason is too little value: thin pages, pages that closely repeat others, or pages that add little beside what is already indexed. An accountancy firm in Dublin with twenty town pages, each with the same two paragraphs and a different place name, should expect most of them to land here. Merge pages that say the same thing, redirect the extras, and give each remaining page content a searcher could not get elsewhere on your website, such as prices, examples of past work and local details.
Discovered, currently not indexed is one step earlier: Google has found the address but has not crawled it yet. Google's troubleshooting guide names a server running out of serving capacity as one reason pages go uncrawled, so faster and more reliable hosting helps, and so does cutting low-value addresses such as endless filter combinations. Internal links matter most, because a page linked from your menu and from related pages looks central, while a page reachable only from the sitemap looks like an afterthought. A kitchen fitter in Manchester with new project pages stuck here would link each one from its services page and the relevant gallery. On a website with only a handful of pages in this group, patience and better linking usually solve it within weeks.
How do you check one page with URL Inspection?
URL Inspection, in the search bar at the top of Google Search Console, shows whether one address is on Google and, if not, why.
The report works on groups, while URL Inspection works on one address. It tells you whether the URL is on Google, is on Google but has issues, or is not on Google, and the Page indexing section explains why: how Google found the page, when it was last crawled, whether crawling and indexing were allowed, and the canonical you declared beside the one Google selected. A wedding photographer in Edinburgh puzzled by a missing gallery page can see at once whether it is blocked, noindexed or treated as a copy. Test live URL checks whether Google can reach the page as it is now, which matters after a fix, but no test can guarantee that Google will index the page. When the live result is clean, press Request indexing, keeping in mind that requests are subject to a daily limit.
How do you validate fixes for pages not indexed by Google?
Once every page under a reason is fixed, open that reason in the Page indexing report and press Validate fix, then wait for Google to recheck the listed addresses.
Google's help says validation typically takes up to about two weeks, though in some cases it can take much longer. The status moves through stages such as Started, Looking good and Passed, and Google Search Console notifies you when validation succeeds or fails. If a certain share of the pages Google rechecks still have the problem, validation ends as Failed, and the details show which addresses to fix before starting again. Validate the reasons that come from your website, such as noindex mistakes, soft 404s and server errors, rather than reasons Google expects, such as alternates with a proper canonical. Note the date and the count when you start, so a falling number shows the fix is working.
How does an outside analysis help?
An outside analysis reads your pages the way Google does and flags the settings that keep them out of the index, often before Google Search Console reports them.
Google Search Console tells you what Google decided, but not always which setting caused it, and only after Google has crawled the pages. An outside check fetches your pages directly and reads the same signals Googlebot reads: the robots meta tag, the X-Robots-Tag header, the robots.txt rules, the canonical link and the status code each address returns. That makes it useful straight after a redesign or a platform move, when a stray noindex or a leftover Disallow rule can sit unnoticed for weeks before the report catches up. The AI SEO tools for business websites from AI Web Maker include a website SEO checker that works on any platform and lists the problems it finds page by page. Use it as a second opinion beside Google Search Console rather than a replacement, because only Google can tell you what it actually stored.
Questions business owners ask
How many of my pages should be indexed?
There is no target number, because it depends on how your website is built. The pages that should be indexed are the ones a searcher could usefully land on, such as your home page, service and product pages, location pages with real content, and articles. If the indexed count is close to the number of genuine pages you want found, the not indexed total, however large, is probably made of addresses that do not matter.
Should I keep requesting indexing for a page?
No, once is enough for each change. Google's guide to asking Google to recrawl URLs says requesting a recrawl more than once for the same address will not get it crawled any faster. If a page stays under crawled, currently not indexed, the page itself needs to change before you request again.
Do pages that are not indexed hurt the rest of my website?
Usually not: a page that is not indexed cannot rank, but it does not normally drag down other pages. Genuine 404s, redirected old addresses and deliberate noindex pages are all normal parts of a healthy website. Repeated server errors are the exception, because Googlebot then slows its requests to the whole website, not just the failing pages.
Why is my new page not indexed yet?
Most often because Google has not crawled it yet. Google says crawling can take anywhere from a few days to a few weeks, and requesting it does not guarantee the page will be indexed. Link the new page from your menu or a related page, make sure it is in your sitemap, and request indexing once through URL Inspection.
Does robots.txt keep a page out of Google?
Not reliably. Google says robots.txt is not a mechanism for keeping a page out of Google, because a blocked address can still be indexed, without a description, when other pages link to it. Use a noindex rule on a page Google is allowed to crawl, or protect the page with a password.
A Page indexing review for this month
This month's review sorts every reason into pages that are correct as they are and pages you want found, then fixes and validates the second group.
Open the Page indexing report today and switch the view to all submitted pages, so you are looking at the pages you asked Google to index. Go through each reason and sort its pages into two piles: correct as they are, and pages you want found. Fix the second pile at the source, starting with server errors, noindex mistakes and robots.txt blocks, then improve the thin pages that Google crawled and left out. Test each fixed page live in URL Inspection, request indexing for the most important ones and press Validate fix for each reason you have cleared. Then test your website with an analysis, so the settings that keep pages out of Google are caught before the next crawl rather than after it.
Your score out of 100, the visits within reach, every page read the way Google does and the tool that fixes each problem. Works on any website.
Analyse your website with AI Website SEO Tools →