Discovered Currently Not Indexed: What It Means, How to Fix

By Ugur Saritepe · July 22, 2026

You opened the Page indexing report in Search Console and found pages marked “Discovered - currently not indexed.” It means Google knows the URL but has not crawled it yet, which is a crawl-priority signal, not a page-quality one. The fix is almost never the “rewrite your content” advice you will read everywhere. Here is how to confirm what you actually have, then fix it.

First, confirm it is Discovered and not Crawled

Before you change anything, make sure you have the status you think you have. Two Search Console labels look almost identical and need opposite fixes:

• Discovered - currently not indexed: Google found the URL, usually from your sitemap or an internal link, but has not visited it yet. This is a crawl-priority problem, covered by the rest of this guide.
• Crawled - currently not indexed: Google did visit the page and decided not to index it. This is a page-quality or duplication problem, and the fix is to make the page distinct and genuinely useful, not to chase crawling.

30-second check: open URL Inspection in Search Console for the page and read the Last crawl line.

• Empty or “N/A”: Google has never crawled it. You have Discovered - currently not indexed. Keep reading.
• A real date: Google crawled it and passed. You have Crawled - currently not indexed, which is a different problem: the page needs a reason to earn a slot, not a nudge to be visited.

Google documents both states in its Page Indexing report help page. The distinction matters because the top-ranking guides for this query hand you the Crawled fix, improve your content, even when your problem is that Google never showed up.

Why Google discovered your page but will not crawl it

For the Discovered state, the causes below are ordered by how often they are the real problem and how cheap they are to check. Work down the list and stop at the first one that matches.

1. Nothing on your site links to the page

Google prioritizes crawling partly by internal links: a page that other pages point to reads as important, and a page reachable only from the sitemap reads as an afterthought. A page with zero internal links, an orphan page, is the single most common reason a URL sits in Discovered.

Say you publish 40 blog posts, but your blog index only lists the latest 10 and nothing else links deeper. Posts 11 through 40 are orphaned: Google knows they exist from the sitemap but has no path of links signalling they are worth a visit.

30-second check: pick the un-indexed URL and ask what links to it. Bad: only the sitemap references it. Good: several already-indexed pages link to it in their body or navigation. Fix: add links to the page from relevant pages that are already indexed, such as a category hub, a related-posts block, or the main navigation.

2. The page is missing from your sitemap, or the sitemap is stale

Your XML sitemap is the list of URLs you are explicitly asking Google to crawl. If a page is not in it, or the sitemap is out of date, you have removed one of the two ways Google prioritizes discovery, leaving only internal links to do the job.

30-second check: open yourdomain.com/sitemap.xml and search for the un-indexed URL. Good: the URL is listed with a lastmod date that reflects real changes. Bad: the URL is absent, or every entry carries the same months-old lastmod. Fix: include the URL, keep lastmod honest, and resubmit the sitemap in Search Console. Our guide on what an XML sitemap is and why Google cannot read yours covers the invalid-sitemap traps.

3. Crawl budget is being spent on junk URLs

Google gives each site a rough crawl capacity. Redirect chains, soft 404s, and auto-generated parameter URLs eat that capacity, so your real pages wait in Discovered while Googlebot burns its visit on pages that should not exist. This is the dominant cause on large sites.

Say your store creates a separate URL for every color-and-size filter combination: a few hundred products balloon into tens of thousands of near-duplicate URLs. Google crawls those before it reaches your actual product pages, and Google's own crawl-budget documentation names exactly this pattern.

30-second check: in Search Console, open Settings then Crawl stats and look at what Googlebot is spending requests on; also scan the Page indexing report for large soft 404 or redirect buckets. Bad: thousands of parameter or filter URLs, or a big soft-404 count. Fix: cut the waste. Block or noindex filter and parameter URLs, collapse redirect chains, and clear soft 404s, which return 200 for pages that are really empty.

4. The site is too new, or the page too thin, to earn priority

On a new domain with little authority, Google crawls conservatively: it will discover your URLs from the sitemap but is in no hurry to visit them. Pages that look near-duplicate to ones Google already holds get the same treatment, because there is no obvious payoff to crawling them.

30-second check: is the site under roughly two to three months old, or is the page substantially similar to others you publish? Bad: a two-week-old site, or a page that restates another one. Good: an established site and a page that covers something distinct. Fix: publish genuinely distinct pages on a steady cadence so Google raises your crawl rate, earn a few external links, and, if the site is new, wait. Our account of getting the first clicks from zero is what patience actually looks like.

5. You are hammering Request Indexing instead of fixing signals

Request Indexing can nudge a handful of genuinely isolated pages, but it does not raise your site's crawl priority, and resubmitting the same URLs over and over does nothing. Treating it as the fix keeps you busy while the real cause, weak internal links or a stale sitemap, goes untouched.

Fix: use Request Indexing once per page that is genuinely ready, then fix causes 1 through 4 and let the normal recrawl happen. If a page is worth indexing, the durable fix is to make Google want to crawl it, not to keep asking.

The verdict: fix exactly one thing this week

Run these in order and stop at the first hit:

1. Last crawl shows a real date, not empty, so you actually have Crawled - currently not indexed. Stop: that is a page-quality problem, not a crawl one, and none of the fixes below apply.
2. The page has no internal links, or is missing from the sitemap (causes 1 and 2). Fix these first. They are the cheapest and move the most pages.
3. The site is large and full of parameter or soft-404 URLs (cause 3). Cut the crawl waste so Googlebot reaches your real pages.
4. None of the above and the site is new or the page is thin (cause 4). Publish steadily, earn a link or two, and wait. Do not spam Request Indexing (cause 5).

How to confirm the fix worked

Give Google one to three weeks, longer on a new site, then re-open URL Inspection for the page. Good: the Last crawl line now shows a date and the status has moved to Indexed. A move to Crawled - currently not indexed is also progress: Google finally visited, so the crawl-priority problem is solved and any remaining issue is page-level. Still empty after three weeks on an established site: a second cause is in play, so go back down the verdict list.

You can also run site:yourdomain.com/the-exact-path in Google. A result means the page is indexed; nothing means it is still waiting. See the rest of our symptom guides if the page indexes but still earns no clicks, which is a separate diagnosis.

From experience: on a new site, this is about time and links

When we launched game-scout.app, a new Next.js site with no authority, its pages showed the same shape as Discovered - currently not indexed: Google knew the URLs from the sitemap but had not gotten around to crawling and indexing them, and Search Console showed nothing for weeks. The first real signal, a five-clicks milestone, did not land until November 22, 2025.

What moved those pages was not clicking Request Indexing on repeat. It was publishing distinct niche pages on a steady cadence and linking them to each other, so Google had both a reason and a path to crawl deeper. The site now pulls around 480 clicks a month, and every click still comes from those interlinked niche pages, never the homepage.

We run the same mechanism on this blog on purpose. New, internally linked guides go up on a regular cadence, which is not a growth hack, it is the crawl-priority signal this article describes, applied to ourselves. And the technical half of the problem, a missing sitemap entry, a stray noindex, a blocked path, is exactly what the index-signals check in our Triage Report is built to catch from the URL alone.

FAQ

How long does Discovered - currently not indexed take to resolve?

On an established site, a page with solid internal links usually moves within days to two weeks once Google crawls it. On a new or thin site it can sit there indefinitely until you fix the signals, because the status is about crawl priority, not a countdown.

What is the difference between Discovered and Crawled - currently not indexed?

Discovered means Google knows the URL but has not crawled it yet, so the last-crawl date in URL Inspection is empty. Crawled means Google did crawl the page and chose not to index it. Discovered is a crawl-priority problem, Crawled is a page-quality one, and they need opposite fixes.

Does requesting indexing fix Discovered - currently not indexed?

It can nudge a handful of genuinely isolated pages, but it does not raise your site's crawl priority, and resubmitting the same URLs repeatedly does nothing. For a site-wide Discovered problem, fix internal links, the sitemap, and crawl waste instead.

Is Discovered - currently not indexed a penalty?

No. It is a scheduling and priority state, not a manual action or a penalty. It is most common on brand-new sites, which have little crawl priority, and on very large sites, where crawl budget runs out before Google reaches every page.