“Discovered - currently not indexed” in Google Search Console

What the status means

Google knows the URL exists, from a link or a sitemap, but hasn't crawled it yet. Google's help gives the usual reason: crawling it was expected to overload the site, so the crawl was rescheduled. Because the page was never fetched, the report shows no last crawl date for these URLs.

The difference from its neighbor matters:

Discovered is a scheduling decision. Crawled is a judgment about the page.

Is it a problem?

Google's guide on crawl budget is written for sites with roughly a million pages or more, sites with 10,000+ pages that change daily, and sites where a large share of URLs sit in Discovered – currently not indexed; Google calls the numbers rough estimates. On a typical small business site with a few hundred pages, a long Discovered list rarely means Google lacks capacity. It means Google doesn't think the pages are worth fetching yet.

Why it happens

1. The URLs are weakly linked. Found only in the sitemap or on page 12 of an archive, they get low priority.
2. The site generates too many URLs. Faceted filters, sort orders, session IDs, tracking parameters and internal search pages multiply URLs faster than Google wants to crawl them.
3. The server is slow or erroring. Google says 5xx and 429 responses make its crawlers slow down. A slow server lowers how much Google crawls.
4. The site is new or has little authority. Google crawls less of a site it doesn't know yet.
5. Similar pages already disappointed. If many pages of the same template were crawled and not indexed, Google may deprioritize the rest of that template.

How to find the cause

1. Export the examples from Indexing → Pages → Discovered – currently not indexed and group them by pattern: folder, parameter, template.
2. Count parameter URLs. If most of the list contains ?, the problem is URL generation, not individual pages.
3. Check Crawl stats (Settings → Crawl stats): average response time and the share of server errors. Rising response times or 5xx errors point at the server.
4. Check how the pages are linked. Can you reach them from the main navigation or related pages in two or three clicks, or only from the sitemap?
5. Check a few URLs with the checker below to rule out redirects or errors that would also waste crawl.

How to fix it

• Link the important pages from pages that are already crawled often: navigation, hubs, related services, relevant articles.
• Stop producing junk URLs. Don't link to filter and sort combinations, keep tracking parameters out of internal links, and set canonicals on the variants that must exist. For URLs that should never be crawled, a robots.txt rule saves crawl; just don't block pages you want indexed.
• Keep the sitemap clean: only canonical, indexable URLs that return 200. A sitemap full of redirects and duplicates teaches Google to trust it less.
• Speed up the server. Faster responses let Google fetch more. Fix any 5xx errors first.
• Request indexing for a few key pages after you've linked them properly. It won't help hundreds of URLs at once.

What not to do

• Don't submit the same URLs in several sitemaps or resubmit the sitemap daily. It doesn't move the queue.
• Don't use noindex to “free up crawl budget”: Google still has to crawl a page to see the noindex.
• Don't panic over a small, stable number of parameter URLs here. Some of this list is Google working as intended.