Discovered currently not indexed means Google found the URL but has not crawled it
Get Found on Google — Part 1

HomeGoogle Indexing ProblemsDiscovered — Currently Not Indexed
Quick answer: “Discovered — currently not indexed” means Google found the URL but has not crawled it yet, which is why URL Inspection usually shows no last-crawl date. It is a crawl-stage issue, not a final quality verdict. Improve crawl access, internal links, sitemap quality, and the page’s importance, then inspect the URL.

Seeing “Discovered — currently not indexed” in the Page Indexing report can be confusing because the page exists and the URL is known to Google. According to Google’s definition of “Discovered — currently not indexed”, the URL was found but not crawled — Google often reschedules the crawl to avoid overloading the site, which is why the last-crawl date is empty.

What This Status Means

The URL is in Google’s system, but Googlebot has not downloaded the page content yet. Because nothing has been crawled, Google is not making a content-quality judgment. This is a queue and crawl-priority situation, not a penalty.

Why Google Found the URL but Did Not Crawl It

Google discovers far more URLs than it crawls immediately. It prioritizes crawling based on perceived value, internal links, freshness, and server capacity. Common reasons a URL waits:

Newly published

The URL was just discovered and is still in the crawl queue.

Weak internal links

Few or no relevant internal links point to the page, so Google sees low priority.

Buried too deep

The page is many clicks from the homepage or main hubs.

Low-value URL flood

Large numbers of thin, filter, or parameter URLs dilute crawl budget.

Dirty sitemap

The sitemap contains redirects, noncanonical, or error URLs that reduce trust.

Server strain

Slow responses or timeouts cause Google to throttle crawling.

What to Investigate

  • Internal links: Link the page from relevant body content, navigation, category pages, or hubs — not only archives or footers.
  • Sitemap quality: Include only canonical, indexable, HTTP 200 URLs that matter.
  • Server accessibility: Check for timeouts, security challenges, firewall rules, and unstable hosting.
  • Crawl demand: Strengthen unique value, topical relevance, and internal prominence so Google has a reason to crawl.
  • URL worth: Confirm the page deserves to be indexed at all.

How to Fix “Discovered — Currently Not Indexed”

Work through these steps in order. To understand your Page Indexing report fully, pair this with a Search Console review.

1. Confirm the page is worth indexing

If the URL is a thin tag, filter, or duplicate, the right move may be to leave it excluded or consolidate it.

2. Add contextual internal links

Link from established, related pages using descriptive anchors. A handful of relevant editorial links does more than dozens of footer links.

3. Reduce crawl depth

Bring the page closer to the homepage or a strong hub so Google reaches it faster.

4. Clean the XML sitemap

Include only canonical 200-status URLs and remove redirects, noindex, and parameter URLs.

5. Strengthen the page itself

Make sure it offers clear, unique value that justifies a crawl and an index slot.

6. Inspect and request indexing once

After the page is accessible and improved, use URL Inspection for important URLs and request indexing a single time.

What Not to Do

Do not repeatedly request indexing for every URL without improving access, links, or importance. Do not promise yourself a “days vs weeks” timeline — Google does not provide one for this status. And do not assume the page failed a quality check; it has not been crawled yet.

If structural and trust issues are widespread, review how to improve your website structure and trust signals, which often unblocks discovered-but-not-crawled pages.

How Long to Monitor the URL

After meaningful changes, give Google time to re-crawl. Check the URL Inspection status periodically rather than resubmitting daily. If a high-value URL stays discovered for weeks despite strong links and clean access, audit crawl budget and server health.

See What Google Is Doing With Your URLs

We analyze your Search Console crawl and indexing data, find the URLs stuck in the discovery queue, and build a prioritized plan to get your important pages crawled and indexed.

Get a Search Console Analysis

Frequently Asked Questions

What does “Discovered — currently not indexed” mean?

Google found the URL (usually via a link or sitemap) but has not crawled it yet, so it is not indexed. It is a crawl-stage status, not a quality verdict.

Why is there no last crawl date?

Because Google has not crawled the URL. The crawl was found but deferred, often to avoid overloading the site, so no crawl timestamp exists yet.

How long can a URL remain discovered but not indexed?

There is no fixed limit. Strong internal links, a clean sitemap, and clear value usually shorten the wait, but Google does not publish a guaranteed timeframe.

Does an XML sitemap guarantee that Google will crawl the page?

No. A sitemap aids discovery but does not force crawling or indexing.

Should I keep requesting indexing?

Request indexing once after meaningful improvements. Repeated requests without changes do not help.

Can weak internal links cause delayed crawling?

Yes. Pages with few relevant internal links signal low priority and are often left in the discovery queue.

When should I leave a discovered URL unindexed?

When it is a thin, duplicate, filter, or utility URL that should not compete in search. In those cases, exclusion is correct.