What does Discovered - currently not indexed mean?

It means Google knows the URL exists, usually from your sitemap or a link, but has not crawled it yet. Google queued the URL and keeps deciding other pages are worth its crawl resources first. It is a crawl-priority problem, not a content-evaluation problem.

How is Discovered different from Crawled - currently not indexed?

Discovered means Google has not fetched the page at all. Crawled means Google fetched and read the page, then chose not to index it. Discovered is about crawl priority and site capacity; Crawled is about content value. The fixes are different.

How do I get Google to crawl a Discovered URL faster?

Link to the page from your strongest existing pages, make sure your server responds fast, keep your sitemap accurate with real lastmod dates, prune large volumes of thin URLs, and submit the URL directly through the URL Inspection tool or the official Google Indexing API so it enters the crawl queue with explicit priority.

Does the Google Indexing API help with Discovered - currently not indexed?

Yes, this is the status where direct submission helps most. Because the page has not been evaluated yet, the bottleneck is purely getting Googlebot to visit. An Indexing API submission typically triggers a crawl within hours instead of weeks. Indexing afterward still depends on page quality.

Is Discovered - currently not indexed bad for SEO?

The page cannot rank while unindexed, so it earns nothing yet. A small number of Discovered URLs right after publishing is normal. A large or growing backlog usually signals weak internal linking, slow server responses, or too many low-value URLs competing for the same crawl budget.

How to Fix "Discovered - Currently Not Indexed" in Google Search Console

Last updated July 16, 2026 · Applies to the Page indexing report in Google Search Console.

"Discovered - currently not indexed" means Google knows your URL exists, probably from your sitemap or a link, but has not even sent Googlebot to look at it. The page is sitting in a crawl queue, and Google keeps deciding that other things are worth its resources first.

This makes it fundamentally different from its cousin, "Crawled - currently not indexed". Crawled is a content verdict: Google read the page and passed. Discovered is a priority verdict: Google has not read it at all, and the fixes are about crawl priority, not content evaluation.

Why Google delays crawling a URL it knows about

Low perceived priority. Nothing on your site or the web signals that this URL matters: no internal links from important pages, no external links, sitemap-only discovery.
Crawl budget pressure. On larger sites, Googlebot allocates a finite crawl capacity. If you publish thousands of URLs, or your site generates endless filter/parameter pages, new pages queue behind them.
Server capacity signals. Google throttles crawling when your server responds slowly or errors under load. It would rather wait than break your site. Slow hosts create Discovered backlogs.
Site-level trust on new domains. Young sites with little authority get crawled conservatively. Google fetches a few pages, evaluates, and expands slowly.
Bulk publishing spikes. Dropping 500 pages in one day queues most of them. Google rarely crawls a spike immediately.

The 6 fixes, in order of leverage

Submit the URLs directly. This is the status where direct submission genuinely shines, because there is no negative evaluation to overcome; the page just needs a visit. The URL Inspection tool in Search Console works for a page or two a day. For anything more, tools built on the official Google Indexing API, like Zeneth Indexer, push URLs into the crawl queue with explicit priority, and crawls typically follow within hours.
Link from your strongest pages. Add internal links from your homepage and most-visited pages to the stuck URLs. Internal links are the loudest priority signal you control. Orphan pages stay Discovered for months.
Fix server speed. Aim for server response times under a few hundred milliseconds. If your host struggles, Googlebot visits less. This single infrastructure fix has cleared Discovered backlogs on many slow-host sites.
Stop feeding Google junk URLs. Faceted filters, calendar pages, session parameters, and tag sprawl eat your crawl budget. Block them in robots.txt or noindex them so your real pages get the crawler's time.
Keep your sitemap honest. A sitemap with accurate lastmod dates that only lists real, canonical, 200-status pages gets trusted. A sitemap full of redirects, 404s, and fake lastmod values gets ignored.
Publish in steady rhythm rather than spikes. Google adapts crawl rate to your publishing pattern. A site that publishes daily gets visited daily. If you must bulk-publish, expect the queue and submit the batch through the API.

What to expect after fixing

Directly submitted URLs are usually crawled within hours to a couple of days. Whether they then index immediately depends on the content itself; a crawled page can still land in Crawled - currently not indexed if it is thin or duplicative. Watch the two statuses together: Discovered shrinking while Indexed grows means the fixes are working. Discovered converting to Crawled-not-indexed means the bottleneck has moved to content quality.

Normal vs problem: a handful of Discovered URLs in the first days after publishing is routine. A backlog that grows week over week, or URLs stuck in Discovered for a month or more, is a real crawl-priority problem worth fixing with the list above.

Where Zeneth Indexer fits

This status is the exact problem Zeneth Indexer was built to remove. It watches your sitemap every 10 minutes, so every new or updated page is submitted through the official Google Indexing API without you touching Search Console. It also pings Bing, Yandex, Naver, and Seznam for free via IndexNow. Then, instead of assuming submission worked, it checks Google Search Console URL Inspection data and shows you each page's true status: Submitted, Indexed, or stuck. You get an alert when pages index, and when they don't.

Stop waiting in Google's queue

Pages submitted within 10 minutes of publishing. Real verification, not guesses. One-time credits from $3.

Get Started →