"Discovered - Currently Not Indexed" in GSC: Causes and Fixes
Key takeaway"Discovered - currently not indexed" means Googlebot knows the URL exists but has not allocated crawl resources to visit it. The most common cause is crawl budget being exhausted elsewhere; the second is an overall rate reduction caused by slow server responses.
When this applies
- Sites where many pages sit in "Discovered - currently not indexed" in the GSC Pages report
- New or redesigned sites whose sitemap was submitted but whose pages are slow to enter the index
- Sites where crawl activity concentrates on a few pages while the rest are never visited
- Sites where server logs show Googlebot request frequency declining week over week
| Cause | Typical symptom | Severity | Fix direction |
|---|---|---|---|
| Crawl budget exhausted | Other pages on the same site get crawled normally, only this batch is untouched | High | Cut repeated crawling and useless URLs |
| Very slow server responses | Googlebot request intervals stretch week by week | High | Optimize TTFB and concurrency capacity |
| robots.txt blocking by mistake | Blocked path prefixes follow a pattern | High | Review robots.txt and User-agent groups |
| Broken internal link structure | These pages can only be discovered via the sitemap | Medium | Add internal links |
| Site size exceeds processing capacity | New pages go untouched for a long time | Medium | Reduce the total URL count |
| CDN/WAF blocking the crawler | Googlebot UA appears in logs but no corresponding access records exist | High | Allowlist known crawler IP ranges |
Step-by-step diagnosis
- In server logs, count Googlebot daily requests and the number of distinct URLs reached, and plot both curves.
- If request count is also falling, slow server responses are causing an overall rate reduction; optimize TTFB first.
- If request count is stable but URL coverage is not growing, the budget is being consumed elsewhere; converge the URL set.
- Review robots.txt: confirm User-agent groups are written correctly and that no Disallow rule accidentally blocks product directories.
- Check CDN and WAF rules: allowlist Googlebot official IP ranges (e.g., 66.249.64.0/19).
- Confirm every sitemap URL has a clickable entry point in the HTML source rather than being discoverable only through the sitemap.
- After fixes, watch the decline curve of "Discovered - currently not indexed" in GSC; this usually takes 1-3 weeks.
Common mistakes
- Assuming "discovered - not indexed" means a robots.txt block - a block usually shows as "crawled" data or no data at all in GSC.
- Submitting only the sitemap without adding internal links - the sitemap aids discovery, but internal links determine priority and crawl allocation.
- Speeding up the server without fixing repeated crawling - the budget gets eaten all the same.
- Disabling the WAF entirely for the sake of crawling - allowlist by IP range and user agent precisely instead of opening everything up.
- Repeatedly submitting URL inspections in GSC - it only adds crawl pressure and does not change allocation.
FAQ
Does this state require active intervention?
Yes. It is the first break in the indexing chain; if the upstream fails, everything downstream is moot. But the fix depends on the cause: first diagnose whether it is a budget issue or a response-speed issue.
Does submitting a sitemap raise crawl priority?
A sitemap helps discovery and understanding of site structure, but it does not directly raise priority. Priority is mainly determined by internal linking structure and historical crawl performance.
When budget is tight, should you delete pages or add pages?
Converge URLs first: delete worthless and duplicated pages. The number of old pages needing convergence usually far exceeds the number of new pages you plan to add.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Why a Site Burns Through Crawl Budget: Causes and an Optimization ChecklistComplete Troubleshooting Guide for "Crawled - Currently Not Indexed" in Google Search ConsoleFixing Blank Pages Served to AI Crawlers Caused by JavaScript RenderingServer Log Analysis for Independent Sites: Quickly Locating Why Crawlers Stay AwayDynamic URL Parameters Flooding Google's Index with Low-Quality PagesNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.