Discovered But Currently Not Indexed: What It Means and How to Fix It

You publish a page, submit the sitemap, and wait. A week later Search Console still says the same thing: discovered, currently not indexed.

Before you start rewriting the content, it is worth knowing that this status usually is not a content problem. It is a crawling problem, and the fix is different.

This guide explains what the status actually means, how it differs from the similar-sounding status people confuse it with, and what to do in what order.

What the Status Actually Means

Discovered – currently not indexed means Google knows the URL exists but has not crawled it yet.

Google found the page, usually through your sitemap or an internal link, and put it in a queue. It has not visited it. That is why the last crawl date on the report is empty.

Google’s documentation explains it as wanting to crawl the URL but expecting that to overload the site, so the crawl was rescheduled. That explanation is accurate sometimes and incomplete often, which we will come back to.

You will find the status in Search Console under Indexing, then Pages, then “Why pages aren’t indexed.”

Discovered vs Crawled: The Distinction That Changes the Fix

These two statuses appear next to each other, sound almost identical, and mean opposite things.

Discovered means Google never looked. Crawled means Google looked and was not convinced.

Plenty of advice online conflates the two and tells you to rewrite the content when the page has not been read. Check which status you actually have before doing anything, because the wrong fix wastes weeks.

Step Zero: Confirm It Is Still Happening

Search Console reports lag. A URL may already have been crawled or indexed since the report generated.

Open URL Inspection, paste the affected URL, and check the indexing status and last crawl date. If it has been crawled recently or is now indexed, the issue is resolving on its own.

This takes thirty seconds and regularly prevents a diagnosis of a problem that no longer exists.

Assess the Severity Before Fixing Anything

Compare the number of affected URLs against the total number of important URLs on the site or in that section.

Three pages out of two thousand is noise. Google does not index everything, and it never claimed it would.

Four hundred out of six hundred is a systemic problem worth real attention.

Also check what the affected URLs actually are. If they are internal search results, filter combinations, tag archives, or paginated URLs, the status is Google behaving sensibly. Those pages arguably should not be indexed anyway, and the fix is to stop making them crawlable rather than to force them into the index.

The Four Real Causes

Your Site Is Slow

Google monitors response times and error rates and reduces crawl rate to avoid overloading a struggling server.

If server response times are high or 5xx errors appear in Crawl Stats, Google backs off, and pages sit in the discovered queue.

Check Search Console Crawl Stats for average response time and the breakdown by response code. Rising response times alongside falling crawl requests is the signature.

Your Site Is Not a Priority

Crawl demand depends on perceived importance. A site with few external links and little authority gets crawled less, so newly discovered URLs wait longer.

This is uncomfortable but useful to know, because it explains why the same technical setup produces different results on an established site and a new one.

The Specific Page Is Not a Priority

Even on a well-crawled site, individual pages compete for attention.

A page with no internal links pointing to it, buried five clicks deep, or sitting in a section Google rarely visits will wait longer than a page linked from the homepage.

This is the most common cause on mid-sized sites and the most fixable.

The Page Is Simply New

Sometimes there is no problem. Google has not got around to it yet, and it will.

Google’s own documentation notes it may return to the URL later without any action from you.

Why Google’s Own Explanation Is Incomplete

Google’s description points at server overload. In practice, many affected sites have perfectly healthy servers.

The more common reality is priority. Google could crawl the page and has chosen to spend its attention elsewhere, either because the site does not warrant more crawling or because the specific URL does not look important.

That reframing matters, because if you read the documentation literally you go hunting for a hosting problem that is not there.

Diagnose both. Check server health first because it is quick, then move to priority signals.

The Fixes, In Order

1. Fix server response times. Anything consistently slow reduces crawl rate directly. This is the only fix that raises crawl capacity rather than redistributing it.
2. Add internal links. The single most effective structural fix. Link affected pages from relevant, already-crawled pages using descriptive anchor text. Three contextual links is a reasonable minimum.
3. Reduce crawl waste. If Googlebot is spending its budget on parameter URLs, filter combinations, and redirect chains, there is less left for the pages you care about. Block sort and view parameters, collapse redirect chains, and remove non-indexable URLs from your sitemap.
4. Confirm sitemap inclusion. Affected pages should be in an XML sitemap containing only canonical, indexable, 200-status URLs. A sitemap full of junk teaches Google not to trust it.
5. Flatten the architecture. Pages more than three or four clicks from the homepage get crawled rarely. Improve category and hub page linking.
6. Improve the page itself. Last, not first. If the page genuinely offers nothing beyond what already ranks, indexing it will not help you anyway.

When Requesting Indexing Helps and When It Doesn’t

For a handful of URLs, use URL Inspection and click Request Indexing. This adds the page to a priority crawl queue.

Two limits worth knowing. There is an undocumented daily cap, commonly reported around 10 to 15 URLs. And if there is an underlying issue, requesting indexing again will not resolve it.

Requesting indexing is a nudge, not a fix. If a page returns to the same status after being requested, stop requesting and start diagnosing.

For larger volumes, the Search Console Inspection API lets you check coverage state in bulk, which is far more practical than clicking through URLs one at a time.

What This Costs You in 2026

One consequence worth naming for anyone deprioritising this.

Google’s AI systems draw exclusively from indexed content. An unindexed page cannot appear in AI Overviews, cannot be cited, and cannot contribute to your visibility on those surfaces.

With AI Overviews appearing on a substantial and growing share of queries, particularly informational ones, indexing has become a prerequisite for a channel that did not exist three years ago.

Unindexed is now invisible in two places rather than one.

When to Do Nothing

Sometimes the correct action is none.

• A small number of URLs on a large site
• URLs you would not want indexed anyway
• Pages published in the last week or two
• Sites in the middle of a migration, where indexing takes time to settle

Forcing low-value pages into the index does not help. It spends crawl budget you would rather spend elsewhere and adds pages that will not rank.

Mistakes That Waste Time

• Rewriting content for a page Google has never crawled.
• Confusing this status with “Crawled – currently not indexed.”
• Requesting indexing repeatedly instead of diagnosing.
• Assuming the cause is server overload because the documentation says so.
• Ignoring the report entirely because a few URLs always appear there.
• Trying to force internal search results and filter URLs into the index.
• Leaving affected pages orphaned with no internal links.

Where to Start

Open the Page Indexing report and export the affected URLs. Sort them into two groups: pages you genuinely want indexed, and pages that should never have been crawlable.

For the second group, the fix is blocking or noindexing them, which frees crawl budget.

For the first group, check internal links before anything else. On most sites, the pages sitting in this status are the pages nothing links to.

FAQs