Google is usually not indexing a page for one of a handful of reasons it names in Search Console's Page indexing report: the page is blocked, marked noindex, a duplicate, a redirect, an error, or Google crawled it and chose not to index it yet. Find the exact reason, fix what is actually broken, then request indexing.
Plenty of "not indexed" URLs are working exactly as intended, so don't treat every gray bar in the report as an emergency. Below is each status, what it means in Google's own words, and what I do about it.
What Is the Page Indexing Report?
The Page indexing report in Google Search Console shows which of your URLs Google has indexed, which it has not, and the reason for each one it left out. It used to be called the Index Coverage report: Google's January 2021 post on Index Coverage data improvements links to the same help page that is now titled "Page indexing report." If you searched for the index coverage report meaning, this is the report you want. I also keep a short definition in the index coverage glossary entry.
The report splits every known URL into two buckets:
- Indexed: Google indexed the URL and it is eligible to appear in search results.
- Not indexed: the URL is out of the index, either because of an error or for a legitimate reason, such as a robots.txt rule or a duplicate page.
The "Why pages aren't indexed" table lists each reason, the URL count, and a Source column; Google says you can generally only fix issues whose source is "Website." Each row opens example URLs, capped at 1,000.
Before you start fixing, remember that Google's How Search Works documentation is blunt: "Indexing isn't guaranteed; not every page that Google processes will be indexed." And indexed is not the same as ranking: Google says an indexed page still isn't guaranteed to show up in your search results.
What Does Each "Not Indexed" Reason Mean, and How Do You Fix It?
Here are the reasons I see most, with Google's labels and definitions from the Page indexing report help page unless I link another source.
Crawled - currently not indexed
What it means: "The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling."
Google gives no specific reason here, but its How Search Works guide lists low content quality as a common indexing issue.
How I fix it: treat this as a quality question, not a technical one. Ask whether the page adds something that other pages on your site, or on the web, do not already say. Thin tag pages and auto-generated variations often land here. Improve the substance, consolidate weak pages, and add internal links from relevant pages. Resubmitting the URL does nothing; the definition says so.
Discovered - currently not indexed
What it means: "The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl." That is why the last crawl date in the report is empty.
How I fix it: If a large share of your site sits here, Google's crawl budget guide names exactly that situation as one it was written for. The levers are server capacity and wasted crawling: Google says that if it spends too much time crawling URLs it shouldn't, its crawlers might not explore the rest of your site. Cut parameter and faceted URLs you don't need crawled, fix slow responses, and link to important pages from pages Google already crawls. Server logs show where Googlebot actually spends its time.
Duplicate without user-selected canonical
What it means: "This page is a duplicate of another page, although it doesn't indicate a preferred canonical page. Google has chosen the other page as the canonical for this page, and so will not serve this page in Search."
Google calls this "not an error." URL Inspection shows which URL Google picked.
How I fix it: If Google picked the right version, leave it, or add a canonical tag so your preference is explicit. Google's canonicalization documentation calls a rel="canonical" link annotation "a strong signal" and recommends a self-referencing canonical on the canonical page itself. If Google picked the wrong page, declare the one you want. If the page is not really a duplicate, Google's advice is to make sure the content "differs substantially" between the two.
Alternate page with proper canonical tag
What it means: "This page is marked as an alternate of another page... This page correctly points to the canonical page, which is indexed, so there is nothing you need to do."
Google's examples include an AMP page with a desktop canonical.
Your canonicals are working; no action needed.
URL marked 'noindex'
What it means: the page is excluded by a noindex rule. Google's wording: "When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it."
How I fix it: If you meant to keep the page out of Google, you are done; Google's own help text says "congratulations!" If you want it indexed, remove the directive. It can live in two places, a robots meta tag in the page head or an X-Robots-Tag HTTP response header, according to Google's noindex documentation, so check both. Leftover staging-site noindex rules are the classic post-launch cause. Once it is gone, run a live test in URL Inspection and request indexing.
Blocked by robots.txt
What it means: Google's help page lists this as "URL blocked by robots.txt": "This page was blocked by your site's robots.txt file."
How I fix it: First decide whether the block is intentional. Google says URLs blocked by robots.txt "are probably intentionally blocked" and you should use your judgment before fixing them. If the page should be crawled, remove or narrow the rule.
If the goal is keeping a page out of Google, robots.txt is the wrong tool. Google's robots.txt introduction says it "is not a mechanism for keeping a web page out of Google," and a blocked page can still be indexed if other pages link to it. Worse, a noindex rule on a blocked page is never seen, because Google can't crawl the page to read it. To keep a page out, allow crawling and use noindex, or put it behind a login.
Soft 404
What it means: "The page request returns what we think is a soft 404 response. This means that it returns a user-friendly 'not found' message but not a 404 HTTP response code."
Per Google's HTTP status code documentation, this covers a 200 response whose content suggests an error, an empty page or an error message.
How I fix it: If the page really is gone, return a real 404 (or 410). If the page is real, Google recommends adding more information so it is clear it is not an error page. Empty category pages and "no results" pages are frequent culprits. Use the live test in URL Inspection and click View tested page to see what Google rendered; a page that relies on JavaScript that fails can look empty to Google.
Not found (404)
What it means: "This page returned a 404 error when requested." Google may have found the URL through a link from another page, or the page existed before and was deleted.
How I fix it: Often you do nothing. Google states that 404 responses "are not necessarily a problem, if the page has been removed without any replacement." If the content moved, add a 301 redirect to the new location. Then fix any internal links and sitemap entries still pointing at the dead URL. Expect Googlebot to keep checking it for a while; Google says there is no way to make it permanently forget a URL, but it will crawl it less and less often.
Page with redirect
What it means: "This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed." The target of the redirect may or may not be indexed, depending on what Google thinks of it.
How I fix it: This is usually correct after a migration. The cleanup: update internal links, canonicals and sitemaps so they point at the final URL instead of the redirecting one. Keep redirects to a single hop where you can. Google's documentation says its crawlers follow up to 10 redirect hops by default, and long chains or loops show up in the report as a separate "Redirect error" reason.
Server error (5xx)
What it means: "Your server returned a 500-level error when the page was requested."
How I fix it: Check server logs and hosting for the time of the failed crawl. Google's HTTP documentation says 5xx and 429 errors prompt its crawlers to temporarily slow down, and any content from a URL returning 5xx is ignored. Errors can be transient, so a live test in URL Inspection may pass even though Google's crawl failed. If errors recur, check capacity, timeouts, bot rules blocking Googlebot, and recent deploys.
How Do You Use URL Inspection and Request Indexing?
The URL Inspection tool shows Google's indexed version of a single URL and can run a live test of the current version. A fix you shipped this morning shows up in the live test, but not in the indexed result until Google recrawls.
My routine for any important URL:
- Inspect the URL and read the indexing status, the user-declared canonical, and the Google-selected canonical.
- Run the live test to confirm the fix is visible to Google: no noindex, crawl allowed, a 200 response, and rendered content that looks right.
- Click Request indexing.
On quotas, Google's help pages do not give a number. They say "There is a daily limit to how many index requests you can submit," and Google's recrawl guide adds that requesting a recrawl multiple times for the same URL won't get it crawled any faster. Requesting indexing also does not guarantee the page will appear in the index.
When you fix a whole category of issue in the Page indexing report, use Validate fix on that reason. Google emails you when validation passes or fails, and says validation "typically takes up to about two weeks, but in some cases can take much longer."
Do Sitemaps Help Pages Get Indexed?
They help Google find URLs, which is not the same thing. Google's sitemap overview says a sitemap "doesn't guarantee that all the items in your sitemap will be crawled and indexed." Its sitemap build guide goes further: submitting one "is merely a hint."
Sitemaps still earn their keep on large sites and sites with pages that are hard to reach through links. Google says a small, well-linked site of about 500 pages or fewer may not need one. The rules that keep a sitemap useful:
- List canonical, absolute URLs only. No redirects, no noindex pages, no URLs blocked by robots.txt.
- Stay under the limits of 50MB uncompressed or 50,000 URLs per sitemap.
- Only set lastmod to the date of the last significant update. Google says it uses lastmod when it is consistently and verifiably accurate.
Bonus: filter the Page indexing report to "All submitted pages" to see only your sitemap URLs, the cleanest view of whether the pages you care about are indexed.
Why Do Internal Links and Content Quality Matter for Indexing?
Google discovers most pages by following links. Its crawlable links guide says Google can generally only crawl a link if it is an a element with an href attribute, and that every page you care about should have a link from at least one other page on your site. Buttons wired to JavaScript click handlers, links injected without an href, and pages reachable only through site search are invisible paths.
Orphan pages, the ones nothing links to, are a common thread behind both "Discovered" and "Crawled" statuses. Link to them from relevant, already-indexed pages.
Quality is the other half. Google's guidance on helpful, people-first content asks whether content offers original information or perspectives that aren't already available elsewhere. A site with hundreds of near-identical pages gives Google little reason to index all of them. When I see a large "Crawled - currently not indexed" count, the fix is more often pruning and consolidating than publishing more. My technical SEO checklist covers the crawl and indexing basics to audit first.
How Long Does Google Take to Index a Page?
Google gives ranges, not promises:
- The Page indexing help page says that when you add new content, "it can take a few days for Google to index it," and that requesting indexing can reduce the lag.
- The URL Inspection help page says indexing "typically takes only a day or so, but can take much longer in some cases."
- The recrawl guide says crawling "can take anywhere from a few days to a few weeks."
If a fixed page is still not indexed after a few weeks, go back to the reason in the report rather than requesting indexing again.
When Is "Not Indexed" Fine?
More often than people expect. Google's help page says outright that you should not expect 100% coverage, only that your canonical pages are indexed. It lists good reasons for a URL to stay out: an expected robots.txt rule, a noindex tag, a duplicate URL, or a 404 for a page you removed with no replacement.
In practice that covers alternates with a proper canonical, duplicates where Google picked the right version, redirects from URLs you moved on purpose, 404s for deleted pages, and noindex on thank-you, login and internal search pages.
What deserves attention: important pages outside the Indexed bucket, and sudden spikes. Google's troubleshooting advice is to look for a rise in non-indexed URLs that lines up with a drop in indexed pages, which often points to a new robots.txt rule, a noindex, or a login wall added by mistake.
Why Does Indexing Matter for AI Overviews and AI Mode?
Indexing is now the entry ticket for Google's AI features too. Google's documentation on AI features and your website says that to be eligible as a supporting link in AI Overviews or AI Mode, "a page must be indexed and eligible to be shown in Google Search with a snippet." A page Google has not indexed cannot be cited there, no matter how good the answer on it is.
So when someone asks why their content isn't showing up in AI answers, the Page indexing report is the first place I look.