Page not indexed in Search Console: what each reason means and what to do
You opened the Pages report in Search Console and found a list of “not indexed” pages, each with a reason that reads like code. Many of these reasons are normal and need nothing; others point to a real problem. This guide tells them apart.
Where to find these reasons
In Search Console, open Indexing › Pages. The chart shows how many pages are indexed and how many aren’t; right below it is the table “Why pages aren’t indexed”, with each reason and how many pages it affects. Click a reason to see the list of addresses.
This report lags a few days behind. To check a page’s status right now, use URL Inspection, the search bar at the top of Search Console.
If the problem is that the whole website doesn’t show up on Google, start with Why my website doesn’t show up on Google (and how to fix it).
First, the question that matters
A “not indexed” page is only a problem if you wanted it on Google. Not every page needs to be: an old address that leads to the new one, a duplicate version, a login page, a thank-you page after a form. Before fixing anything, look at the addresses under each reason and ask: should this page show up in a search?
Reasons that are usually fine
Page with redirect
The address leads somewhere else: the www address that redirects to the one without www, http going to https, or a page that moved. Google indexes the destination, not the address that redirects. Nothing to do, as long as the destination is indexed.
Alternate page with proper canonical tag
The page tells Google that its main version is a different one (through the canonical tag), and Google agreed. It happens, for example, with addresses that get campaign parameters such as ?utm_source=instagram. Also normal.
Excluded by “noindex” tag
The page itself asks not to be indexed. If that’s on purpose (client area, test page), it’s right. If the page should show up, it’s a mistake: someone left “noindex” on, often since the website’s testing phase.
Not found (404)
The address no longer exists. If you deleted the page on purpose, that’s fine: Google eventually stops trying. If the page just moved, the right thing is to redirect the old address to the new one, so you don’t lose people arriving through old links.
Reasons that need attention
Discovered – currently not indexed
Google knows the page exists (it found it in the sitemap or in a link) but hasn’t visited it yet. On a new website this is common in the first weeks and usually sorts itself out. If it lasts a long time, the usual causes are few references to the website from elsewhere, many pages with little content, or a slow server, which makes Google visit fewer pages at a time.
What helps: request indexing through URL Inspection, link to the page from other pages on your own website (menu, related articles) and check that it’s in the sitemap.
Crawled – currently not indexed
The most frustrating one: Google visited the page and decided not to add it to the index, at least for now. It’s usually a judgment about the content: the page is too short, too similar to another page on your website or elsewhere, or doesn’t answer any search well.
What helps: make the page more complete and useful, with information that isn’t everywhere already; merge nearly identical pages into one; and link to it from the most important pages of the website. Requesting indexing again without changing anything rarely works.
Duplicate without user-selected canonical
This one and its sibling, “Duplicate, Google chose different canonical than user”, mean the same thing: Google found pages with nearly identical content and picked one of them to show. If the one it picked is the one you want, fine. If not, point to the main version with the canonical tag and make your internal links always use the same address.
Reasons that are real errors
Blocked by robots.txt
The robots.txt file forbids Google from visiting the page. If it should show up, remove the rule that blocks it. One caveat: robots.txt is not the way to remove a page from Google; for that, use “noindex”.
Server error (5xx)
Google tried to open the page and the server failed. If it happened once, it may have been a passing hiccup; if it keeps happening, the hosting needs a look.
Soft 404
The page responds as if it exists, but its content looks like an empty or error page, such as a search with no results or a category with no products. Either the page gets real content, or it should respond as a missing page (404).
Redirect error
The redirect goes nowhere: it loops (A leads to B, which leads back to A), goes through too many addresses or ends at an address that doesn’t open. It has to be fixed in the website or hosting settings.
Fixed it? Tell Google
After fixing, open the reason in the report and click Validate fix. Google checks the pages under that reason again and emails you when it’s done. For a single page, URL Inspection has a Request indexing button. Both can take from a few days to a few weeks and don’t guarantee indexing: they only ask for a new visit.
Summary
- Open Indexing › Pages and look at the addresses under each reason.
- Ignore what really shouldn’t show up: redirects, alternate versions, pages with “noindex” on purpose.
- “Discovered – currently not indexed”: give it time, link to the page and request indexing.
- “Crawled – currently not indexed”: improve the content before asking again.
- Blocks and errors: fix them and click “Validate fix”.