Discovered Currently Not Indexed: Causes & Fixes (2026)

You published the page, submitted the sitemap, and Google still acts like it does not exist. Search Console says "Discovered - currently not indexed," there is no error to fix, and no button forces the issue.

The status means Google knows the URL and has not crawled it. Google's own definition says it wanted to crawl the URL, expected the crawl to overload the site, and rescheduled it. This guide covers what puts a URL in that state, how it differs from "Crawled - currently not indexed," which pages deserve action, and the fixes in the order I run them. Technical details were checked against Google Search Central and Search Console documentation on Oct 23, 2026.

What discovered currently not indexed means

Google's Page indexing report help defines the status like this: "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. This is why the last crawl date is empty on the report."

So the page has not been fetched, rendered or evaluated. Nothing in its content can be the direct cause, because Google has not read it yet. Note the word "typically": overload is the usual reason Google gives, not the only one.

John Mueller gave three explanations in a February 2022 office-hours session, as Search Engine Journal reported. Google may have tried to crawl while the site was overloaded and rescheduled. The site may not meet Google's quality threshold. And Google does not have unlimited resources, so it does not crawl and index every page. He said the status "can be forever" and that it is normal for a website not to have everything indexed.

That makes it a status about your site as a whole, applied to one URL. It is not a penalty and not an error on the page.

Discovered vs crawled currently not indexed

The two statuses sound alike and sit at different points in the pipeline. The difference tells you what to look at first.

Discovered - currently not indexed: Google knows the URL but has not fetched it, and the last crawl date is empty. Look at crawl capacity, internal links and the number of URLs competing for crawling.
Crawled - currently not indexed: Google fetched the page and did not index it. Google says it "may or may not be indexed in the future" and that there is no need to resubmit it. Google gives no cause for this one. Because it has read the page, the page itself is where I look first.

If the page was never crawled, the content is not the problem yet. If it was crawled and dropped, the content is the problem. Treat them as two separate jobs.

Do you need to act?

Not every URL in this status is a problem. Google's report help says a "not indexed" status is not necessarily bad, because some non-indexed URLs are expected, such as duplicates or pages you blocked on purpose.

A new page on a small site. Google says it can take a week or so to start crawling a new page or site, and up to a few weeks for URLs it already knows about. Wait before changing anything.
A page that should rank and has been stuck for weeks. Act. The steps below apply.
Thousands of URLs you never wanted indexed, such as filters, sort orders and parameters. The status is correct. Fix where those URLs come from, not the status.
A large site. Google's crawl budget guide is written for sites with 1 million or more unique pages that change weekly, or 10,000 or more that change daily. It also names many URLs in this status as a reason to read it. Google adds that these are not exact thresholds.

Start from the list of pages that should earn traffic. Everything else is noise until those are sorted. One practical limit: the report's example list is capped at 1,000 rows, and Google says it is not guaranteed to show every URL in a status. If you split your sitemap by section (products, categories, posts), you can pick each sitemap in the report's dropdown and read the statuses per section.

Why discovered currently not indexed happens

Google's crawl budget guide describes two levers: crawl capacity, which is what your server can handle, and crawl demand, which is what Google wants to fetch. The usual causes follow from those two, plus the quality point from Mueller.

Server strain. Google lowers the crawl capacity limit when response times grow or the site answers with 5xx errors or rate-limiting signals such as HTTP 429. The limit exists to avoid overwhelming your server.
Too many URLs for the value they add. Without guidance, Google tries to crawl all or most of the URLs it knows about. Duplicates, parameter URLs and soft 404 pages join the queue. Google says soft 404s "will continue to be crawled, and waste your budget."
Weak internal links. Google says every page you care about should have a link from at least one other page. A URL that appears only in the sitemap gives Google little reason to hurry, since a sitemap is "merely a hint." Google also says more popular URLs tend to be crawled more often.
Site-level quality. If a large share of the site looks thin or duplicated, Google may crawl less of it. The new page inherits that.
Newness. A new site or page can simply be waiting its turn.

How to fix it, step by step

Work through these in order. The early steps cost nothing and rule out the common cases.

Inspect the URL. Run it through URL Inspection in Search Console and run the live test. Confirm the page is reachable without a login, returns 200 and is indexable. Google does not let you request indexing when the live test shows the page as non-indexable.
Rule out blocks. Check robots.txt, any meta noindex, and the X-Robots-Tag response header. Headers are easy to miss because they are not in the HTML, and I cover how to find a header you did not set in the X-Robots-Tag guide. The HTTP status tool and the robots.txt validator cover both checks.
Check server health. Open Settings in Search Console, then Crawl stats. It shows total crawl requests, average response time and host status. Google says sites with fewer than a thousand pages usually do not need this report, and it exists only for root-level properties. If response times climb or 5xx and 429 responses show up, fix hosting first. No other step outranks it.
Link to the page properly. Add links from relevant pages that are already indexed. Google follows <a> elements with an href attribute, and it cannot reliably extract URLs from links without one, so a click handler on a <span> does not count. Use descriptive anchor text that makes sense out of context.
Clean the sitemap. List only canonical URLs. Google ignores <priority> and <changefreq>, and it uses <lastmod> only when it is consistently and verifiably accurate, so update it when the page changes and not on every build. A single sitemap file is limited to 50 MB uncompressed or 50,000 URLs. Run the file through the sitemap validator.
Reduce crawl waste. Consolidate duplicate pages. Return 404 or 410 for pages you removed for good. Fix soft 404s. Avoid long redirect chains. Google also says faster loading and rendering lets it read more content from the site. On a catalog, the targets are parameter duplicates, faceted URLs and thin pages.
Request indexing for the few that matter. Google says there is a daily limit on index requests and that a request does not guarantee indexing. For many pages, Google points to the sitemap instead.

Steps 4 and 6 are where large sites win, in my experience. Requesting indexing is the step people reach for first and the weakest one.

After the changes, wait. Google says URLs it already knows can take up to a few weeks before it crawls some or all of a site, so a check after two weeks tells you more than a daily refresh.

A real report: 88% of pages out of the index

Here is what this looks like at scale. I audited vagparts.kyiv.ua, a Ukrainian VAG car-parts e-commerce site, and the Page indexing report told the whole story in one screen.

Of all known pages, 1.17K were indexed and 8.26K were not, across nine reasons. That is roughly 88% of known URLs sitting outside the index. Two statuses carried most of the weight: 970 URLs in "discovered currently not indexed" and 2.93K in "crawled currently not indexed," both first detected back in 2022 and still open years later.

This is the classic large e-commerce pattern. A parts catalog generates thousands of near-identical URLs: filter combinations, sort orders, sparse category pages, product variants with almost the same content. Google discovers them through the sitemap and internal navigation, queues them, then declines to spend budget crawling and indexing pages it expects to be low value. The "Crawled" bucket being three times larger than the "Discovered" bucket says Googlebot did fetch a lot of these URLs and decided most were not worth keeping.

The numbers drifted down over the audit window on their own. The structural issue stays until the crawl waste is reduced. For a catalog this size, the fix is not requesting indexing on 8,000 URLs. It is cutting the duplicate and thin URLs so the budget flows to the pages that should rank. A site migration is one of the moments this gets worse before it gets better, which I covered in the WooCommerce domain migration write-up.

How to check index status at scale

URL Inspection answers one URL at a time, and the report's example lists stop at 1,000 rows, so neither scales past a few pages. For a quick read on whether a specific page is in the index, a site: query against the exact URL is faster, and the Google index checker builds that query for you. Use it as a fast directional check, then fall back to URL Inspection for the authoritative answer on any single page you are troubleshooting.

For checking a whole batch of URLs in one pass instead of one at a time, the Google Search Console MCP has an inspect_url tool and a check_alerts tool that flags position drops and pages dropping out of results, which catches a batch of pages sliding into "Discovered" without walking the UI page by page.

FAQ

Is discovered currently not indexed an error?

No. It is a status, not an error or a penalty. Google found the URL and rescheduled the crawl. Mueller called it normal for a site not to have everything indexed. The thing to decide is whether the page should rank, and fix only those.

How long does it take to get indexed?

Google's guidance: a new page or site can take about a week to start being crawled, and known URLs can take up to a few weeks. Past that, there is no fixed number. Mueller said the status can last indefinitely, and that pages often move out of it once Google sees value in focusing more on the site, though that is not guaranteed.

Does requesting indexing fix it?

For a few important pages, it is worth trying. It does not fix a structural problem. Google limits requests per day, does not guarantee indexing, and recommends a sitemap when you have many pages.

What happens if a page is crawled but not indexed?

Google says it may or may not be indexed in the future and that you do not need to resubmit it. Since Google already read the page, improve or consolidate the page itself, or accept that it does not need to be indexed.

Where to start

Write down the ten URLs that should bring traffic. Inspect each one and note which of the two statuses it has. Then open Crawl stats and look at host status and average response time before you touch links or sitemaps.

Discovered Currently Not Indexed: Meaning, Causes and How to Fix It