You open the Page indexing report in Google Search Console and find a list of URLs under “Discovered – currently not indexed”. There is no error and no warning. Google simply knows the pages exist and has not crawled them yet. A reliable discovered currently not indexed fix starts with understanding what the status really says, then working through the causes that apply to your site rather than clicking “Request indexing” over and over.
Key takeaways
- Google defines this status as “the page was found by Google, but not crawled yet.” It is not a penalty, and the page is not in the index.
- It is different from “Crawled – currently not indexed,” where Google fetched the page and decided not to index it.
- Google says a page needs to be linked from a known page or listed in a sitemap before it can be crawled, so internal links and a clean sitemap come first.
- Requesting indexing has a quota, and repeating the request for the same URL does not make it get crawled faster.
- For a handful of new pages, patience is usually enough. Many URLs stuck for a long time point to a site-level issue such as crawl waste, server limits, or low-value pages.
What “Discovered – Currently Not Indexed” Means
Google’s Page indexing documentation says a URL in this state was found but not crawled yet, and notes that Google rescheduled the crawl because crawling was expected to overload the site. In practice, there are two broad possibilities. Either Google has not yet gotten around to the page, or it has decided other URLs on your site deserve crawling first.
Google’s crawl budget guide is the place this status gets special attention. It recommends that sites with many URLs listed as “Discovered – currently not indexed” read the guide, and it says the thresholds it gives are rough estimates: sites with more than a million unique pages changing about weekly, or more than 10,000 changing daily. For a smaller or slower-changing site, Google says keeping your sitemap current and checking the Page indexing report is usually enough.
Discovered vs Crawled
| Status | What happened | What to work on |
|---|---|---|
| Discovered – currently not indexed | Google found the URL but has not crawled it | Discovery and crawl priority: internal links, sitemap, server health, crawl waste |
| Crawled – currently not indexed | Google crawled the page but has not indexed it, and may or may not index it in the future | The page itself: usefulness, uniqueness, duplication |
For the crawled status, Google says there is no need to resubmit the URL for crawling. For the discovered status, the work is about getting Google to crawl in the first place.
Why Pages Get Stuck: Likely Causes
Google splits crawling into crawl capacity (how much your server can handle) and crawl demand (how much Google wants to crawl). Pages can wait because of either one.
Weak internal linking
Google says every page you care about should have a link from at least one other page on your site, and that it generally follows links built as <a> elements with an href. A page reachable only through a sitemap or a script-driven button is easier to overlook. Our guide to finding and fixing orphan pages covers this in depth.
Server capacity
Google says the crawl capacity limit goes up when your site responds quickly and consistently and goes down when response times slow or the server returns 5xx or 429 errors. If the URL Inspection tool shows “Hostload exceeded,” Google suggests adding server resources.
Crawl waste
Google lists duplicate and unimportant URLs, soft 404 pages, long redirect chains, slow responses, and outdated sitemaps as factors that waste crawl budget. See our crawl budget guide for more.
A sitemap that is not trustworthy
Google’s sitemap documentation says to list canonical URLs you want in search results, and that it uses <lastmod> only if it is consistently and verifiably accurate. It also ignores <priority> and <changefreq>. Submitting a sitemap is a hint, not a guarantee. Review the common XML sitemap mistakes.
Low-value pages and low demand
Crawl demand depends on factors such as the number of URLs Google knows about, how popular they are, and how stale its copies are. Google also says improving content quality is one way to earn more crawl budget, weighing factors like popularity, user value, uniqueness, and serving capacity. Large batches of near-identical or thin pages give Google little reason to prioritize them.
The Fix, Step by Step
- Segment the list. Export the affected URLs from the Page indexing report and sort them by type: articles, products, filters, tags, archives. Decide which ones you actually want indexed.
- Link to the pages that matter. Add contextual internal links from relevant, already-indexed pages to each important URL, using descriptive anchor text. Google advises link text that describes the destination and avoids “click here.”
- Make navigation crawlable. Use standard
<a href>links for pagination and category links. - Clean the sitemap. Include only canonical, indexable URLs. Remove redirects, errors, and noindex pages. Keep
lastmodaccurate, or leave it out. Resubmit it in Search Console. - Check server health. Review the Crawl stats report for slow responses and 5xx errors, and inspect a stuck URL for a “Hostload exceeded” message.
- Reduce crawl waste. Consolidate duplicates, fix redirect chains, return real 404 or 410 codes for removed pages, and fix soft 404s. Google recommends robots.txt for blocking unimportant URLs, but not as a way to free up budget or to hide pages you want dropped.
- Improve or prune. Strengthen thin pages that deserve to exist. For pages that offer little value, merge, redirect, or remove them. Use noindex sparingly, since Google still has to request a page to see the tag.
- Request indexing selectively. Use URL Inspection for a few priority pages after the fixes. Google notes there is a quota, that crawling can take a few days to a few weeks, and that repeated requests for the same URL do not speed things up. For many URLs, rely on the sitemap.
- Monitor. Check the report weekly. Success looks like the count falling because pages move to Indexed, not because pages vanished from your sitemap.
If you are new to the report, our Google Search Console guide explains how to find and export it.
Example Scenario: A New Blog With a Few Stuck Posts
Example scenario: Imagine a three-month-old blog with 40 posts. Six posts sit under “Discovered – currently not indexed.” Checking them reveals that all six were published in the last few weeks, appear only in the sitemap and the paginated archive, and have no links from other posts. The server response times are normal.
The likely issue here is discovery and priority, not penalties or server limits. A sensible response:
- Add two or three relevant links to each post from older, indexed posts.
- Add the new posts to a “related reading” section on a relevant category page.
- Confirm the sitemap lists only canonical URLs and has accurate dates.
- Use URL Inspection to request indexing for the two most important posts, then wait.
- Re-check in a couple of weeks.
This is a hypothetical case. Real timelines depend on your site, and Google does not promise a date.
Example Scenario: A Large Store With Thousands of Filter URLs
Example scenario: Imagine a store with a few thousand genuine product pages and a far larger number of filter and sort combinations. Most “Discovered” URLs are parameter variants. Here, fixing individual pages is the wrong approach. The work is to consolidate the variants with canonicals, stop linking to low-value combinations, keep them out of the sitemap, and make sure the products themselves have strong category links.
Common Mistakes
- Resubmitting the same URL again and again. Google says it does not help.
- Treating the status as a penalty and rewriting pages that Google has not even fetched.
- Padding pages to reach a word count. Google says it does not prefer a particular word count and warns about content made primarily to attract search visits.
- Putting low-value or redirected URLs in the sitemap.
- Blocking URLs in robots.txt and expecting that to remove them from reports.
- Ignoring server errors that reduce Google’s crawl rate.
Frequently Asked Questions
How long will it take for pages to leave this status?
Google does not give a fixed time. Its recrawl documentation says crawling can take a few days to a few weeks. If pages are stuck much longer, look for site-level causes.
Do I need to fix every URL in the list?
No. Filter variants, duplicates, and low-value pages may be better consolidated or left out. Focus on pages you actually want to rank.
Is this the same as a crawl budget problem?
Sometimes. Google says many URLs in this status is a signal to read its crawl budget guidance, but small sites with a few new pages are often simply waiting.
Sources
- Search Console Help: Page indexing report
- Google Search Central: Managing crawl budget for large sites
- Google Search Central: Ask Google to recrawl your URLs
- Google Search Central: Build and submit a sitemap
- Google Search Central: Make your links crawlable
- Google Search Central: Creating helpful, reliable, people-first content
Once your pages are indexed, the next question is visibility; see how to rank in Google AI Overviews. If you would like help diagnosing an indexing backlog, you can contact us at ssaagency.us/contact.