Discovered - Currently Not Indexed: What It Means and How to Fix It

Discovered - currently not indexed is one of the most common reasons listed under "Why pages aren't indexed" in Google Search Console, and one of the most misunderstood. Google's Page indexing report documentation gives a short definition: "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 guide explains what sits behind that sentence, how to tell a normal backlog from a real problem, and the fixes that move URLs out of the queue. For the full indexing process, see our guide to getting pages indexed by Google.

What does "Discovered - currently not indexed" mean?

Google indexes a page in three stages: discovery (it learns that the URL exists), crawling (Googlebot downloads the page) and indexing (Google analyses the content and decides whether to store it). A URL in this status has passed the first stage only. Google has the address in its queue, has never fetched it, and therefore has not judged its content yet. This is why the "Last crawled" field is empty when you inspect such a URL.

The status is often confused with its neighbour, "Crawled - currently not indexed". The difference decides where you look for the cause.

In short, "Discovered" is a crawling problem, while "Crawled" is an indexing decision. Rewriting the content of a page that Google never downloaded will not change anything until Googlebot comes back to fetch it.

Is "Discovered - currently not indexed" a problem?

It depends on the volume and on which pages are affected. Three situations are normal and need no action:

• New pages published in the last days or weeks. Discovery and crawling are separate steps, and Google schedules them.
• URLs you do not want indexed anyway: filter combinations, internal search results, tag archives, tracking parameters. Their presence in the list is a hint to block or stop linking them, and nothing more.
• A small share of a large site. No site has every URL indexed.

It becomes a problem when your important pages (products, categories, articles, service pages) stay in the list for weeks, or when the count grows faster than the number of indexed pages. Google's own crawl budget guide names this exact signal: sites with "a large portion of their total URLs" classified as Discovered - currently not indexed should look at how Google spends its crawling on them.

What causes "Discovered - currently not indexed"?

Google decides how much to crawl with two inputs described in its crawl budget documentation: the crawl capacity limit (how much your server can take without slowing down) and crawl demand (how much Google wants your URLs, based on size, update frequency, page quality and relevance compared with other sites). Every cause below lowers one of the two. The crawl budget concept matters most on large sites, but a slow server or a weak site structure can trigger the status on a site of a few hundred pages.

1. A slow or unstable server

This is the cause Google mentions first. According to the crawl budget guide, crawl capacity rises when response times "remain stable or improve" and falls when the site slows down or returns server errors. Shared hosting, an overloaded database, a heavy theme or a firewall that throttles Googlebot all reduce the number of URLs Google is willing to fetch per day.

2. Too many low-value URLs competing for crawling

Faceted navigation, sorting parameters, session IDs, endless calendar pages, auto-generated tag pages and near-identical product variants create thousands of URLs. Google's guide warns that duplicate and unimportant URLs consume crawl time and that soft 404 pages "will continue to be crawled, and waste your budget". Your good pages wait in the same queue.

3. Weak internal linking

A URL listed only in the XML sitemap, or linked from a page five clicks deep, sends a weak priority signal. Google's documentation on crawlable links adds a technical trap: Google "can only crawl your link if it's an <a> HTML element" with an href attribute, so menus or "load more" buttons built only with JavaScript events may hide pages from the crawler.

4. Site-wide quality signals

Crawl demand depends partly on how Google rates the rest of the site. If a large share of already crawled pages are thin content or duplicate content, Google has little reason to hurry for the next ones. This is why the status often appears after publishing hundreds of similar pages at once.

5. A new or little-known site

A young domain with few backlinks and a lot of fresh content starts with low crawl demand. Mueller said in the same 2022 session that a newer site with a lot of content should expect much of it to stay in this status for a while.

How do you diagnose it in Search Console?

Work from examples before changing anything. This sequence takes about an hour on most sites.

1. Open the list. In Indexing > Pages, click "Discovered - currently not indexed" and export the example URLs (Search Console shows up to 1,000).
2. Sort them by type. Group the URLs by folder or pattern: products, articles, parameter URLs, pagination, tags. If most are URLs you do not want indexed, the fix is to reduce them, not to push them.
3. Inspect a few important ones. The URL Inspection tool confirms that the page was never crawled and shows whether Google found it in a sitemap or through a referring page.
4. Check the server side. Open Settings > Crawl stats. The Crawl Stats report shows host status over 90 days (robots.txt fetching, DNS resolution, server connectivity), the share of 5XX errors and timeouts, and the average response time. A rising response time with a falling number of requests points to a capacity problem.
5. Check internal links. Count how many internal links point to the affected pages and from where. An internal link analyzer shows orphan pages and pages buried deep in the structure.
6. Read your server logs if you have them. Logs show which URLs Googlebot really requests each day and where it loses time, often on parameter URLs you did not know existed.

How do you fix "Discovered - currently not indexed"?

Match the fix to the cause found during the diagnosis. The table summarises the main cases.

Improve server capacity first

If the Crawl Stats report shows server errors or rising response times, nothing else will work until this is fixed, because Google itself lowers its crawl rate to protect the site. Ask your host about limits, add page caching and a content delivery network, and remove heavy scripts from templates.

Reduce the URLs you do not need

Every useless URL that Googlebot fetches is a useful URL it does not fetch. Remove internal links to filter combinations and tracking parameters, use the robots.txt checker to test Disallow rules before blocking patterns, and fix soft 404 pages. Google's guide is explicit on duplicates: eliminate them "to focus crawling on unique content rather than unique URLs".

Strengthen internal links to the pages that matter

Link the affected pages from pages Google already crawls often: the home page, main categories, popular articles. Use standard <a href> links with descriptive anchors. A clear site architecture keeps every important page within three or four clicks of the home page, which raises its crawl priority.

Clean the sitemap and request indexing sparingly

Submit a clean XML sitemap and use the "Request indexing" button only for a few strategic URLs: it is subject to a daily quota and does not raise your overall crawl capacity. Once you have fixed the cause, click "Validate fix" in the report. Google says validation "typically takes up to about two weeks, but in some cases can take much longer", and you should not click it again until it succeeds or fails.

If pages stay invisible after these steps, the cause may lie elsewhere: our checklist of reasons a website is not showing up on Google covers penalties, noindex tags and canonical errors.

Why does it matter for AI visibility (GEO)?

A page that Googlebot never crawls cannot rank on Google, and it cannot be used as a source by Google's AI Overviews or AI Mode, which draw on Google's index. A crawl backlog therefore delays your visibility in classic results and in AI answers at the same time.

ChatGPT, Perplexity and Claude rely on their own crawlers and partner indexes, so a page can be fetched by them while Google still ignores it, or the reverse. Your server logs show which AI bots visit which pages; our glossary entry on AI crawler logs explains how to read them. The fixes in this guide (fast server, fewer useless URLs, clear internal links) help every crawler, Googlebot and AI bots alike.

Sorank, our product, works on the content side of the problem. Its GEO and SEO dashboard connects to Search Console to follow clicks, impressions and positions after each fix, and its article generator publishes fewer, deeper articles with automatic internal links to existing pages, so new URLs are linked from the day they go live.

The short version: "Discovered - currently not indexed" means Google has your URL but has not spent crawl time on it yet. Ignore it for a few new pages, and act when it covers important pages: speed up the server, cut useless URLs and link the pages that matter. To automate the content and internal linking part, see the Sorank plans, from $49 per month billed annually, with a 3-day free trial.