How to Fix "Discovered - Currently Not Indexed" in Google Search Console (2026)
In Google Search Console's Page Indexing report, "Discovered - currently not indexed" means Google knows your URL exists - it found the link, usually from your sitemap or an internal link - but has not crawled it yet. The page is sitting in a queue Google has not gotten around to. That is the key difference from its better-known cousin "Crawled - currently not indexed," where Google already fetched the page and decided against it. Here, the page has not even been read. It cannot rank, cannot earn traffic, and will not appear in search until Google actually crawls and then indexes it. The good news: the causes are a short, predictable list, and most are fixable without a developer.
What the status actually means
"Discovered" is one step earlier in the pipeline than "Crawled." Google's process runs: discover the URL → crawl (fetch) it → index it. This status means you are stuck at the first hand-off: Google logged the URL but keeps postponing the crawl. It is rarely a content-quality verdict - Google has not seen the content yet to judge it. It is almost always a signal about crawl priority: Google is rationing how much of your site it fetches, and this URL keeps losing the queue. The word "currently" matters - the status clears on its own once the page earns enough priority to be crawled.
The handful of causes behind almost every case
The reporting and Google's own guidance converge on the same short list. Work through them roughly in this order - the first two explain the large majority of cases.
| Cause | Why it triggers the status |
|---|---|
| Weak internal linking / orphan pages | If few or no links point to the URL from already-indexed pages, Google reads it as low-priority and keeps deferring the crawl. This is the single most common trigger for "Discovered." |
| Crawl-budget throttling (slow site) | Google limits how hard it crawls so it does not overload your server. On a slow site it fetches fewer URLs per visit, so lower-priority pages wait - sometimes for weeks. |
| Brand-new or very recent pages | A page Google only just discovered may simply be waiting its turn. On low-authority or new sites that wait is longer. |
| Duplicate-pattern / low-value URLs | When Google sees many near-identical URLs (faceted filters, tag archives, thin templated pages), it predicts they are not worth crawling and declines to fetch more of the same pattern. |
| Redirect chains and loops | A URL behind an A→B→C redirect chain wastes crawl budget; a loop stops the crawl entirely, so the destination never gets fetched. |
| Site authority / overall crawl demand | New or low-authority domains get a smaller crawl allocation, so the discovered-but-uncrawled backlog grows faster than Google works through it. |
How to fix it, in priority order
1. Strengthen internal linking to the stuck pages (biggest lever)
Because "Discovered" is a priority problem, the fastest fix is to raise the page's priority. Link to it from pages Google already crawls often - your homepage, high-traffic blog posts, pillar pages, and relevant category or hub pages. A URL that only sits in the sitemap with no internal links gives Google no reason to move it up the queue. Internal links are the strongest "this page matters, crawl it" signal you control.
2. Confirm the URL is in a clean, current sitemap
Make sure the page is listed in an XML sitemap that returns 200, that the sitemap is submitted in Search Console, and that it contains only canonical, indexable URLs (no noindex, no redirects, no 404s). A sitemap bloated with low-value or broken URLs dilutes the crawl signal for the pages you actually care about.
3. Fix redirect chains and speed up the site
Run the affected URLs through a crawler (Screaming Frog or similar) and collapse any redirect chains so old URLs point straight at their final destination. Then check Core Web Vitals and server response time in PageSpeed Insights - a faster site lets Google crawl more URLs per visit, which directly shrinks the discovered-but-uncrawled backlog.
4. Cut the low-value URL bloat
If thousands of near-duplicate URLs (filter combinations, endless tag pages, thin templated pages) are competing for crawl budget, Google deprioritizes the whole pattern - including pages you want indexed. Use canonical tags, noindex the truly low-value variants, or block crawl-trap parameters so Google spends its budget on pages that deserve it.
5. Then - and only then - request indexing
Once the page has real internal links and the technical path is clean, open URL Inspection and click Request Indexing to push it into a priority crawl queue. Use this sparingly - it is a nudge, not a fix. If you request indexing while the page is still orphaned on a slow site, it will likely slide right back to "Discovered." After a genuine change, give it time: crawling and indexing can take days to weeks, and the status clears on its own once Google fetches and accepts the page.
The pattern underneath all six
Notice that nearly every fix is about crawl priority and site structure, not the words on one page. "Discovered - currently not indexed" is Google telling you it does not think your site is worth crawling fast enough - usually because of weak internal linking, a slow site, or low-value URL bloat. That is also why chasing it URL-by-URL is slow: if one important page is orphaned or starved of crawl budget, others on the same site usually are too. The efficient move is to diagnose the whole site's crawlability, internal-link structure, sitemap health and speed at once, then fix in priority order - which is exactly the work we walk through in the 12-point technical SEO checklist you can run yourself and break down by fix priority in what a technical SEO audit checks and how to prioritize the fixes. And if Google has already crawled the page but still left it out, that is the sibling status - how to fix "Crawled - currently not indexed" - which is a content and quality problem rather than a crawl-priority one.
If you would rather not work through it alone, A3E's Technical SEO Audit does exactly this pass for you: it checks crawlability, internal-link structure, sitemap health, indexation and Core Web Vitals, then hands back a prioritized fix list - the high-impact items first - so the pages stuck in "discovered, not indexed" actually get crawled and into search. It is a one-time diagnostic and roadmap, evidence-based and without ranking guarantees. See current details and pricing on the store.
Get your pages crawled and into search
Start with a free AI visibility snapshot to see where you stand, then get the Technical SEO Audit for a prioritized, fix-it-first list covering crawlability, internal links, sitemap health and speed.
Get your free AI score See the Technical SEO AuditFrequently Asked Questions
What does "Discovered - currently not indexed" mean in Google Search Console?
It means Google knows your URL exists - usually from your sitemap or an internal link - but has not crawled (fetched) it yet, so it is not in the index and cannot appear in search. Unlike "Crawled - currently not indexed" (where Google read the page and chose to leave it out), this status means Google has not even read the page. It is almost always a crawl-priority signal, not a content-quality verdict.
How is it different from "Crawled - currently not indexed"?
"Discovered" means Google found the URL but has not crawled it - a crawl-priority and site-structure problem (weak internal links, slow site, crawl budget). "Crawled" means Google fetched the page and decided not to index it - a content-quality or duplication problem. Different stage, different fix: Discovered needs better internal linking and crawl health; Crawled needs stronger, more distinctive content.
How long does it take to fix?
After you add real internal links and clean up the crawl path, Google may take from a few days to several weeks to crawl and index the page, depending on your site's authority and crawl budget. Requesting indexing can speed up the first crawl, but if the page stays orphaned on a slow site it will often return to "Discovered."
Why are so many of my pages showing this status at once?
Usually a shared root cause: weak internal linking, a slow site limiting crawl budget, or thousands of low-value duplicate-pattern URLs eating the budget. When the issue is site-wide, fixing it page-by-page is slow - a structural audit of crawlability, internal links, sitemap health and speed resolves it far faster.