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.

The diagnostic checklist

  1. Run the URL through the URL Inspection API and read the coverage state and crawl reason, not a guess, Google's own answer.
  2. Audit indexability: word count, canonical tag, internal link count, robots.txt rules, LCP, structured data.
  3. Confirm the URL is in your sitemap. Sitemap inclusion is a stronger discovery signal than a single internal link.
  4. Check for index bloat: a sitemap stuffed with thousands of low-quality URLs devalues every URL in it.
  5. Check for canonicalisation conflicts: is the URL self-canonical, or pointing somewhere else?

The most common real cause: thin content

Google's bar for "worth crawling" keeps rising. Pages under roughly 300 words with little unique content (tag pages, paginated archives, author profiles, templated location pages) land here constantly. The fix is not an Indexing API push; it's making the page substantive enough that the quality classifier changes its mind. Then push.

Order of operations

Fix the content first, then submit. Pushing first spends a quota slot and Google's classifier won't have changed its mind in the meantime.

Second most common: site authority

New domains and low-authority sites get less crawl budget, full stop. If you launched six months ago with a flat backlink profile, the Indexing API helps but won't override Google's lukewarm interest on its own. Build internal links, earn a few real external ones, then push.

When the Indexing API actually fixes this

  • URLs Google discovered weeks ago and left sitting in the queue.
  • URLs that recently changed: you fixed the thin content, added internal links, improved the template.
  • URLs on a healthy domain that should index but got deprioritised for no visible reason.

When it won't

  • URLs Google crawled and explicitly declined to index. That's "Crawled – currently not indexed", a different problem with a different fix.
  • URLs carrying a noindex tag or blocked in robots.txt.
  • URLs that 404, redirect, or error.
  • URLs Google treats as duplicates of a different canonical.

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, because 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