Why Google Says "Discovered – Currently Not Indexed" (and How to Actually Fix It)

Open Google Search Console, click into the Pages report, and there it is: Discovered – currently not indexed. Not an error, not a penalty — just a page sitting in limbo. Google knows the URL exists. It just hasn't bothered to crawl it.

That distinction matters, because it changes what actually fixes the problem. This status means Google discovered the URL — through your sitemap, an internal link, or an external link — but decided crawling it wasn't a priority yet, according to Search Engine Land's breakdown of the status. It's a prioritization decision, not a rejection.

What actually causes "discovered - currently not indexed"

Four things drive this status, and they're rarely mutually exclusive — a new site with thin content and no internal links is often hitting all four at once:

1. Low crawl budget. Crawl budget is the number of URLs Google can and wants to crawl in a given window — it's the sum of what your server can handle and what Google actually wants to see, per Google's own crawling documentation. New and small sites start with a modest budget, so Google triages which URLs get crawled first.
2. Weak or missing internal links. Pages with more internal links pointing to them get crawled more often and are treated as more important — Google's own John Mueller has called internal linking "super critical," one of the biggest on-page levers a site controls, according to Backlinko's crawl budget guide. A page with zero internal links is telling Google, in effect, that it doesn't matter.
3. Thin or duplicate content. If a page looks like a near-copy of another page, or doesn't say much, Google has little reason to prioritize crawling it over something more distinct.
4. Server performance issues. A slow or flaky server teaches Google to crawl your site more cautiously, which directly shrinks how many pages get visited per day, as Onely's guide to fixing the issue explains in detail.

How to fix it, in order

1. Confirm the page is still actually stuck

Search Console data lags. Before changing anything, re-check the URL Inspection tool — some pages listed as "discovered, not indexed" get crawled and indexed within days without any action, especially right after a fresh sitemap submission.

2. Add internal links pointing to the page

This is the highest-leverage fix for most sites. If an important page has no internal links, that's very often the entire explanation. Link to it from your homepage, a relevant blog post, or a navigation menu — anywhere a real visitor would naturally click through. Our free internal links checker shows you which of your pages are currently under-linked, so you're not guessing.

3. Make sure it's in your sitemap

An unlisted page is a page Google has to stumble onto by accident. Run your sitemap through our free sitemap checker to confirm the page is actually declared and the file itself is valid XML — a broken sitemap silently fails to help every page in it.

4. Check robots.txt isn't quietly discouraging the crawl

A misconfigured Crawl-delay directive or an overly broad Disallow rule can suppress crawling of pages that should otherwise be fine. Validate yours with our free robots.txt tester.

5. Check whether JavaScript is hiding your content from Googlebot

If your site leans on client-side rendering (React, Vue, Angular), Googlebot may see an empty shell instead of your actual content on first pass, and rendering gets queued for later — sometimes much later, on a constrained crawl budget. Confirm this isn't happening: open the URL Inspection tool, click "View Crawled Page," and check the rendered HTML tab. If your headings, body copy, and links aren't there, that's your answer, not thin content or crawl budget.

The fix is server-side rendering or pre-rendering so the initial HTML response already contains the page's real content, not just a JavaScript bundle that builds it client-side. Our free Core Web Vitals checker flags render-blocking and slow-loading resources that make this worse.

6. Improve the content, don't just resubmit

If the page is thin, duplicate, or low-value, more internal links won't fully fix it — Google's own guidance is to focus on genuinely improving the page's quality, not just pinging it for attention. If you've done 1–5 and it's still stuck after a few weeks, that's usually the real signal.

7. Build authority signals into the page

Pages with at least one external backlink get crawled more often, because a backlink is an outside signal that the page is worth Google's attention — not just something you're claiming internally. You don't need dozens of links; one contextual backlink from a relevant, real site often changes crawl priority more than another round of internal linking does. Pair that with a link from one of your own high-authority pages (your homepage, a well-ranking pillar post) pointing directly at the stuck page.

8. Request indexing — as a nudge, not a strategy

The Request Indexing button in Search Console adds the URL to a priority crawl queue. It's rate-limited to roughly 10–12 requests a day, so it works fine for a handful of important pages, but it doesn't scale to fixing a site-wide indexing problem — and repeatedly resubmitting the same stuck URL rarely changes the outcome if the underlying cause (thin content, no internal links) hasn't changed.

When it's a site-wide problem, not a one-page problem

If dozens of important pages carry this status at once, stop treating it page by page. Export the affected URLs from the Pages report and group them by pattern first — that's usually faster than inspecting pages one at a time, because the fix is often the same across the whole group:

If one entire group is stuck, the fix is usually structural — a canonical tag, a noindex on filtered variants, or a template-level content problem — not a page-by-page internal linking push. That pattern points to a site-wide issue: crawl budget genuinely too small for your page count, a server that's slow or erroring under Googlebot's load, or a content quality problem that spans the whole site. Run a full technical SEO audit to see whether server response times, broken links, or missing sitemaps are the actual root cause before spending hours on individual pages.

FAQ

Does "discovered - currently not indexed" hurt my rankings? Not directly — a page in this state simply isn't in the index yet, so it can't rank at all. It's not a penalty against the rest of your site, but every important page stuck here is invisible in search until it's crawled and indexed.

How long does it take to resolve? It varies widely — some pages clear within days once you add internal links or fix a sitemap; others sit for weeks on sites with genuinely constrained crawl budget. There's no fixed timeline Google publishes.

Should I keep clicking "Request Indexing" every day? No. It's rate-limited and won't fix an underlying cause. Use it once after you've made a real fix (added internal links, resolved a server issue), not as a repeated ritual.

Is this the same as being manually penalized? No. This status has nothing to do with manual actions or algorithmic penalties — it's purely a crawl-prioritization outcome, and it's reversible by making the page more discoverable and more clearly worth crawling.

Is "Crawled - currently not indexed" the same problem? Close, but one step further along. "Discovered" means Google hasn't visited the page yet; "Crawled" means it has, and decided not to index it anyway — usually a content-quality call rather than a crawl-budget one. Steps 1–4 above (internal links, sitemap, robots.txt) matter less here since Google already reached the page; steps 6–7 (content quality, authority signals) are where to focus.