Why Pages Say 'Discovered - Currently Not Indexed'
When Google Search Console shows "Discovered – currently not indexed", Google has found your page but has not crawled it yet. This often happens on new or low-priority pages. Fix this by adding strong internal links, improving page content, and requesting Google to recrawl the page.
What "Discovered – Currently Not Indexed" Means
This status means Google knows the URL exists but has not fetched it yet. In Google’s own words: "The page was found by Google, but not crawled yet… Google rescheduled the crawl". In practice, that often means Google discovered the page (for example via a sitemap or link) but postponed crawling it to avoid overloading your site. Google may come back to crawl the page later when site load or crawl capacity allows.
Common Causes of the "Discovered" Status
Pages stay in this "Discovered" state for several reasons, usually related to how Google finds and values content. Common causes include:
A few discovered pages on a small site might resolve on their own. But if many important pages remain "discovered," it signals a problem you need to fix. In that case, improve the site’s links, content, and performance so Google can crawl those URLs.
How to Fix "Discovered – Not Indexed" Pages
Fixing this issue means helping Google crawl and index those pages. Key steps include:
By following these steps – requesting indexing, improving links and content, and fixing technical limits – you help Google crawl and index those pages. Over time, the "discovered" status should clear up for fixed pages.
In practice, small issues can clear in days or weeks. For example, fixing a few isolated pages might resolve the status in a week or two. On the other hand, site-wide problems may take longer; complex fixes could take weeks or months to fully resolve as Google re-evaluates your site.
Conclusion
"Discovered – currently not indexed" simply means Google saw your page but has not put it in its index yet. It usually points to crawl-queue or site issues, not to anything like a manual penalty. To get these pages indexed, make sure Google can find and handle them: use Search Console’s tools, link the pages well, improve their content, and fix any server or sitemap problems. Once you address the root causes, Google will crawl and index the pages over time.
Frequently Asked Questions
What does "Discovered – currently not indexed" mean?
This status means Google discovered your URL (for example via a sitemap) but hasn’t crawled or indexed it yet. In other words, Google knows the page exists but is waiting to fetch it.
How is "Discovered – currently not indexed" different from "Crawled – currently not indexed"?
"Discovered" means Google has found the URL but not fetched it. "Crawled" means Google fetched and rendered the page but then chose not to index it. The fixes differ: discovered pages need better crawling signals, while crawled pages need better content or relevance.
Why isn’t Google indexing my page?
Pages can stay unindexed if Google finds them but sees issues. Common reasons are weak internal links, low-quality or duplicate content, or server limits. Improving links and content quality, and fixing any site errors, will encourage Google to index the page.
How do I fix a page stuck as "Discovered – currently not indexed"?
To fix it, make sure Google can find and value the page. Add internal links to it, improve its content, and ensure it’s listed in your sitemap. Then use Search Console’s URL Inspection tool to request indexing. These steps tell Google the page is important and ready to be crawled.
How long will my page stay in "Discovered – currently not indexed"?
It varies. If there’s only a few pages, fixing issues and requesting indexing often clears the status in a few days to a couple of weeks. If a larger crawl or site issue exists, it may take longer (weeks or even months) for Google to revisit after you make fixes.
Is "Discovered – currently not indexed" an error or penalty?
No. It is not a penalty or error, just a status in Google’s crawl queue. Google usually comes back on its own, especially if the page is well-linked and has good content. For a few supplementary pages this is normal. Only treat it as a problem if many important pages get stuck there.
