Discovered – currently not indexed: what it means and how to fix it

What the status means

Google's definition in the Page indexing report is: "The page was found by Google, but not crawled yet." It adds that, typically, Google wanted to crawl the URL but expected it to overload the site, so it rescheduled the crawl. That's why the Last crawled date for these URLs is empty.

Google found the URL in a sitemap or a link and put it in a queue. It hasn't fetched it. That separates it from Crawled – currently not indexed, where Google read the page and decided not to index it.

A few URLs in this state are normal, especially right after publishing. Thousands of them, or important pages sitting there for weeks, point to one of the causes below.

Why Google hasn't crawled it

1. The page is new. Google says crawling can take anywhere from a few days to a few weeks. For a page published this week, waiting is the fix.
2. The server is slow or erroring. Google crawls as much as a site can handle without strain. When response times rise, or the server returns 5xx or 429 errors, Google crawls less, and new URLs wait longer.
3. Too many URLs for the site's size and standing. Faceted filters, sort orders, session IDs and calendar pages can create far more URLs than real pages. Google spreads its crawling across all of them.
4. Weak internal linking. A URL that appears only in the sitemap, or is linked from a single deep page, looks low priority.
5. Low perceived value. Google decides how much to crawl partly from how useful the site's pages have been. If many crawled pages ended up not indexed, Google is less eager to crawl new ones.

Google's crawl budget guide is written for large sites (around 10,000 pages or more), but it calls out sites with a large share of URLs in this status too. Small sites usually have a linking or quality problem, not a crawl budget problem.

How to find the cause

• Look at which URLs are affected. Open the status in Search Console and read through the examples. If most are parameter or filter URLs, the problem is URL bloat. If they're your real articles or products, it's linking or value.
• Check Crawl stats. In Search Console, go to Settings, then Crawl stats. Rising average response time, or a high share of server errors, means Google is holding back to protect your server.
• Check how the pages are linked. Crawl the site and see whether the affected pages are reachable from the homepage, and how many clicks deep they are.

The audit reports orphan pages (in the sitemap but never linked), click depth and slow responses. It also flags status codes and redirects that waste crawling.

How to fix it

1. Link to the pages that matter. Add them to category pages, hubs, navigation or related links. A page a visitor can reach in two or three clicks from the homepage is one Google will crawl sooner.
2. Cut URL bloat. Stop linking to filter and sort combinations that don't deserve their own page. Use canonical tags for variants you keep. Block URL patterns that have no search value, such as internal search results or endless calendar pages, in robots.txt, which you can check with the Robots.txt Tester.
3. Speed up the server. Use caching and a CDN, fix slow database queries, and make sure Googlebot isn't being rate-limited by a firewall or bot protection rule.
4. Fix wasteful URLs. Redirect chains, broken links and soft 404s all use up crawls. Google's crawl budget guide notes that soft 404 pages keep being crawled and waste budget.
5. Keep your sitemap clean. List only canonical, indexable URLs that return 200, with accurate lastmod dates. A sitemap full of redirects and noindex pages lowers trust in it. You can pull every URL out of a sitemap with the Sitemap URL Extractor and test them in bulk with the Indexability Checker.
6. Improve or prune weak pages. If much of the site is thin, adding more thin pages won't get crawled faster. Merge or remove the weakest pages.
7. Request indexing for a few key URLs. URL Inspection's Request Indexing is useful for one important page. For many URLs, Google recommends submitting a sitemap.

What not to do

• Don't keep resubmitting the sitemap or requesting indexing. Google says repeated requests for the same URL won't get it crawled faster.
• Don't block the pages in robots.txt to "save budget" if you want them indexed. Blocked pages can't be crawled at all.
• Don't publish hundreds of pages at once on a new site and expect them all to be crawled straight away. Release in batches and link each batch well.

Questions