IndexerNow

"Discovered, currently not indexed" in 2026: what changed and what fixes it now

7 min read · updated 2026-05-18
The short answer

In 2026, 'Discovered — currently not indexed' shows up more because Google's index has tightened: the bar to graduate from discovered to indexed is higher than it was two years ago. Flip URLs out of limbo by strengthening the page's quality and internal links, then pushing it through the Indexing API to prompt the crawl — thin pages stay stuck no matter how often you submit.

"Discovered — currently not indexed" has always meant: Google knows the URL exists (from your sitemap, a link, or a previous push) but hasn't fetched it yet and may never. In 2026, Google's index has tightened: the bar to graduate from Discovered to Indexed is higher than it was two years ago, and the volume of URLs sitting in this limbo has grown.

What changed

  • Google's helpful-content quality classifier runs earlier in the pipeline — sometimes before a URL is even crawled.
  • Sites with a lot of low-quality URLs see those URLs sit in Discovered indefinitely.
  • Sites with high topical authority get URLs out of Discovered faster, sometimes within hours.
  • Programmatic / template-generated URLs are scrutinized harder than they were pre-2024.

The two questions to answer first

  1. Did Google decide not to crawl this URL because the URL itself looks low-priority? (Solvable.)
  2. Did Google decide not to crawl because the surrounding site signals are weak? (Harder — site-wide quality work needed.)

Per-URL fixes

  • Add 2-3 inbound internal links from existing indexed pages. URLs with zero internal links graduate slower.
  • Push through the Indexing API. This doesn't guarantee indexing but it does move the URL up Google's crawl queue.
  • Add structured data (Article, FAQPage, HowTo) — clean schema correlates with faster graduation.
  • Make sure the page is actually substantive. 100 words of body text rarely escapes Discovered in 2026.
  • Confirm the URL isn't a near-duplicate of something already indexed — Google often parks duplicates in Discovered.

Site-wide fixes

  • Prune. A site with 50 indexed pages outranks the same site with 500 indexed pages + 1,500 stuck in Discovered. Delete or noindex thin pages.
  • Improve crawl budget signals — fix 5xx errors, slow server responses, broken redirect chains.
  • Build topical clusters. URLs inside dense topic clusters graduate faster than orphans.
  • Earn external links to your highest-quality pages — those pages' authority flows down to their internal links.

The Indexing API path

Pushing a URL through the Indexing API is the strongest crawl hint Google exposes. For URLs stuck in Discovered, the typical outcome is:

  1. Push the URL.
  2. Within 0-72 hours, Google crawls the URL. URL state moves from "Discovered" to either "Crawled — currently not indexed" or "Indexed."
  3. If it moves to "Indexed" — done.
  4. If it moves to "Crawled — currently not indexed" — Google fetched it and decided it's not worth indexing. You now have a quality problem to solve, but at least the diagnosis is clear.
  5. If it stays in "Discovered" — Google declined to even crawl. Re-check internal links and site-wide signals.
The recheck is the data

Push, wait 24 hours, re-inspect via URL Inspection. The verdict change tells you what's broken — the push itself isn't the diagnostic, the recheck is. IndexerNow runs a 24h recheck automatically on every batch.

When to stop pushing

If a URL has been pushed 3+ times across 30 days and remains in "Discovered" or "Crawled - not indexed," stop pushing. Google has made a verdict and the API call isn't going to override it. Either rewrite the page substantively, consolidate it with a related page, or delete it. Re-pushing the same content is wasted credits.

Push URLs through the Indexing API and get a 24h recheck that tells you whether Google's verdict changed. Free daily quota.

Try IndexerNow free