IndexerNow

Coverage states

Fix: "Discovered – currently not indexed" in Google Search Console

updated 2026-05-28
The symptom

Search Console: "Discovered – currently not indexed"

TL;DR — the fix

Google knows the URL exists (from your sitemap or a link) but has chosen not to crawl it yet — a crawl-priority and site-quality signal. Strengthen internal linking to the page, prove its value, fix any crawl-budget waste, and send an explicit crawl hint through the Indexing API.

"Discovered – currently not indexed" is Google saying: I know this URL exists, but I haven't bothered to crawl it. The page never got fetched, so this isn't a content-quality verdict yet — it's a priority decision. Google is rationing its crawl and your URL didn't make the cut.

Why Google parks URLs as Discovered

  • Crawl budget — on large or slow sites, Google limits how much it fetches and your URL is low in the queue.
  • Perceived low value — thin, templated, or near-duplicate URLs get deprioritized before they're ever crawled.
  • Weak internal linking — a page that's only in the sitemap, with few or no internal links pointing to it, reads as unimportant.
  • Server performance — if your server is slow or returns errors under Googlebot's load, Google backs off crawling.
  • URL flood — programmatically generating thousands of similar URLs trains Google to crawl them lazily.

How to get them crawled

  1. Add real internal links to the page from relevant, already-indexed pages — this is the single biggest lever for crawl priority.
  2. Make the page demonstrably worth crawling: unique content, not a thin variant of a template.
  3. Trim crawl waste — block faceted-navigation junk, parameter explosions, and infinite calendars in robots.txt so Google spends its budget on pages that matter.
  4. Confirm fast, error-free responses for Googlebot (check the Crawl stats report for spikes in response time or 5xx).
  5. Send an explicit crawl hint with the Indexing API — the strongest 'please come look now' signal Google exposes.
  6. Re-check in URL Inspection after a few days; the state should move to Crawled or Indexed once Google fetches it.
Discovered vs Crawled is a useful diagnosis

Discovered = never fetched (a priority problem). Crawled – not indexed = fetched but rejected (a quality problem). Knowing which one you're in tells you whether to work on crawlability or on content.

IndexerNow runs on your own Google account, your own Cloud project, and your own quota — we never pool submissions through a shared account. Connect your GSC and push the URL through Google's Indexing API in two clicks.

Connect your own GSC and index now

Frequently asked

How long does 'Discovered – currently not indexed' last?

There's no fixed timeline — some URLs sit there indefinitely. The state persists until Google decides the page is worth crawling, which is why strengthening internal links and sending an Indexing API hint help break the stall.

Will submitting to the Indexing API fix 'Discovered – not indexed'?

It's the most direct lever for the crawl side of the problem — it explicitly asks Google to crawl the URL. But if the underlying issue is thin content or crawl-budget waste, fix those too, or the page may bounce to 'Crawled – not indexed.'

Is 'Discovered – currently not indexed' a penalty?

No. It's a prioritization decision, not a manual action or penalty. Google simply hasn't allocated crawl budget to the URL yet.

Further reading

Related fixes