"Discovered, currently not indexed" means Google knows the URL exists, usually from a sitemap or a link, but has not crawled it yet. Google may be rescheduling the crawl to avoid overloading your server, or it may not yet judge the page worth the effort. Strengthen internal links, keep the server fast and keep your sitemap limited to useful pages.
Why it matters
Until a page is crawled it cannot be indexed, so it cannot appear in results. On a small site the status is often brief and fades by itself. On a larger site a long list can show that Google has more addresses than it wants to fetch, which is worth acting on.
How to check
- Open the Page indexing report in Google Search Console and select the "Discovered, currently not indexed" reason. Note how many pages are listed and which sections of the site they belong to.
- Check the pages themselves. Open a few and confirm they return status 200, are not redirected and are not accidentally blocked or marked noindex.
- Check server health. Slow responses or frequent server errors make Google crawl more cautiously. Review your hosting performance and the Crawl stats report in Search Console, found under Settings.
- Look at how the pages are linked. If a page can only be reached from the sitemap, it is an orphan. Add links from related, well-visited pages.
- Prune your sitemap. Remove duplicate addresses, parameter variations, redirected pages and anything you do not want indexed, so that Google's attention goes to pages that matter.
- Reduce wasted URLs. Filtered, sorted and session-based addresses can create thousands of near-copies that compete for crawling.
- Give it time, then check again. If the page is important, request indexing once with the URL Inspection tool.
Google's own explanation for this status is that it tried to crawl but the site was overloaded, so the crawl was rescheduled. Making your server more dependable is therefore a sensible first step.
Common mistakes
- Submitting thousands of low-value addresses in a sitemap and expecting all of them to be crawled.
- Ignoring slow hosting, then blaming the content.
- Leaving important pages with no internal links.
- Requesting indexing for hundreds of pages by hand.
- Confusing this status with a block. Nothing is blocked; the crawl just has not happened.
Frequently asked questions
Is this a problem I need to fix?
Not always. A new page may appear here briefly and then move on. Act if important pages stay in the status for a long time or if the count keeps growing.
Does it mean my content is bad?
Not necessarily. The page has not been fetched, so Google has not judged it yet. Quality still matters later, but at this stage the issue is usually crawling priority or server capacity.
How is it different from "Crawled, currently not indexed"?
In this status Google has not fetched the page. In the other, Google has fetched it and decided not to add it to the index.
Related guides
- Discovered, currently not indexed in detail
- Crawl budget explained
- How to fix orphan pages
- The Page indexing report explained
To spot weak links and slow responses on your own site, Try the free website sample.