Discovered, currently not indexed: why Google has not crawled the page
"Discovered, currently not indexed" means Google knows the URL exists, from a link or a sitemap, but has not fetched it yet. On most sites the cause is that the page looks unimportant: few internal links point to it and it sits deep in the site. On large sites it can also mean Google slowed its crawling because the server was slow or returned errors. Link to the page from related pages, keep the sitemap to pages you want indexed, and check the server's response times in the Crawl stats report.
What the status means
Google found the URL but put off fetching it. The last crawl date in URL Inspection is empty, because there was no crawl. Unlike "Crawled, currently not indexed", Google has not judged the content yet; it has only decided the page can wait.
Google's help says it often waits because crawling the site at that moment might have overloaded it. On small sites this is rarely about server load and usually about how important the page looks.
Four causes and how to check each
Start with internal links. It is the most common cause and the cheapest fix.
| Cause | How to check | Fix |
|---|---|---|
| Weak internal linking | Count body links to the page from other pages; check how many clicks it takes from the homepage | Link to it from two or three related pages and from a hub page for its topic |
| Too many low-value URLs | The not-indexed list is full of filters, parameters, tags or near-duplicate pages | Stop linking to them, add noindex or canonicals, and keep them out of the sitemap |
| Slow or failing server | Settings, Crawl stats: high average response time, or 5xx and timeout responses | Fix server errors and slow pages; Google crawls more when the site responds quickly |
| A large batch of new pages at once | Hundreds of new URLs in the sitemap in a short time | Publish in smaller batches and link the best ones first |
Fix it by hand
Splitting the sitemap by section helps here. rankecho.io splits its sitemap into five files (core, learn, resources, compare and tools), so the Page indexing report can be filtered to one section at a time and a weak section stands out.
- Filter the Page indexing report to your sitemap, so you only see pages you asked Google to index.
- Open "Discovered, currently not indexed" and export the example URLs.
- For each page you want indexed, add links from related pages in their body text, not only in menus or footers.
- Remove from the sitemap every URL you do not want indexed, and every URL that redirects or returns an error.
- Open Settings, Crawl stats and check average response time and the share of server errors.
- Request indexing for the few pages that matter most, once each.
- Check again in two to four weeks. Pages often move to indexed, or to crawled but not indexed, which is a different problem.
When crawl budget is the real issue
Crawl budget matters for large sites, roughly those with tens of thousands of URLs or more, or sites whose pages change daily. For a site with a few hundred pages, Google can crawl everything; if pages wait, it is because they look unimportant, not because Google ran out of budget.
On a large site, look at what Google spends its crawling on. If Crawl stats show many fetches of parameter URLs, old redirects or duplicates, cut those off so the crawling goes to the pages you want.
After the page is crawled
Once Google fetches the page, it either indexes it or moves it to "Crawled, currently not indexed". If it moves there, the problem is now the page itself, and the crawled-not-indexed guide covers it. If it is indexed, check that it earns impressions in the Performance report.
SEO/GEO/AEO Intel in RankEcho connects to Search Console with Google's read-only permission, collects up to 16 months of site and page data and the latest 90 days of queries, and shows when a page starts to earn impressions and for which searches. It does not read the Page indexing report or Crawl stats, so check those in Search Console itself. Your team reviews and publishes every change. It is free for 3 days on one site, with no card.
Sources reviewed
Search and publication principles below were checked against primary documentation. The worked examples are fictional; these sources do not establish a traffic outcome or a guaranteed ranking.
3 claim-level source records
| Claim reviewed | Official source | Review record |
|---|---|---|
| The Page indexing report lists the URLs Google knows about, whether each is indexed, and the reason a URL is not indexed, including "Crawled - currently not indexed" and "Discovered - currently not indexed". | Google Search Console: Page indexing report | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · Google describes the statuses. The causes and fixes on this page are RankEcho's guidance, not Google's diagnosis of any one site. · Confidence: High |
| Google's crawl budget guide is written for large sites and sites with rapidly changing content, and explains how server responsiveness and low-value URLs affect crawling. | Google Search Central: managing crawl budget for large sites | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · The size where crawl budget starts to matter is an approximation, not a Google threshold for any one site. · Confidence: High |
| URL Inspection shows Google's indexed version of a URL, can run a live test, and lets a person with access request indexing. | Google Search Console: URL Inspection tool | Checked 2026-11-02 · Google public documentation, reviewed 2 November 2026 · A request to index is not a promise that Google will index the page. · Confidence: High |
Frequently asked questions
It can get one important page crawled sooner, but it does not fix the cause. If many pages are waiting, improve internal links and clean up the sitemap.
Rarely. Google can crawl a site of a few hundred pages easily. On small sites, waiting pages usually look unimportant because few pages link to them.
Open Settings, then Crawl stats in Search Console. Look at average response time and the share of responses that are server errors.