# Discovered – Currently Not Indexed: Causes and Fixes

> What "Discovered – currently not indexed" means in Google Search Console, why Google delays crawling, and how to fix it step by step, most important fixes first.

URL: https://seorecheck.com/blog/discovered-currently-not-indexed-fix · Published: 2026-10-01 · [Українська](https://seorecheck.com/ua/blog/discovered-currently-not-indexed-fix.md), [Español](https://seorecheck.com/es/blog/discovered-currently-not-indexed-fix.md)

**"Discovered – currently not indexed"** is a status in Google Search Console's Page indexing report. It means Google has found a URL, usually through a link or a sitemap, but hasn't crawled it yet. Until Googlebot fetches the page, it can't be indexed or ranked. The usual causes are server capacity limits, weak internal linking and a site full of low-value URLs.

This guide covers what the status means, how it differs from its close relative, how to tell whether you have a real problem, and which fixes to make first.

## What does "Discovered – currently not indexed" mean?

Google's Page indexing report documentation defines it like this: "The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl."

So the URL is sitting in Google's crawl queue. Google hasn't judged the content, because it hasn't seen the content. That matters for how you diagnose it. With this status, the question is almost never "is my page good enough?" It's "why doesn't Google think this URL is worth fetching yet?"

In practice there are two reasons, and they often overlap:

- **Crawl capacity:** Google holds back because your server looks slow, unstable or easy to overload.
- **Crawl demand:** Google doesn't see enough value in the URL to fetch it soon. It may be poorly linked, look like a duplicate, or belong to a site with thousands of thin or parameter URLs.

## Discovered vs. crawled – currently not indexed: what's the difference?

People often mix up these two statuses, but they need different fixes. We covered the second one in detail in [Crawled – Currently Not Indexed: Causes and How to Fix It](https://seorecheck.com/blog/crawled-currently-not-indexed-fix).

| | Discovered – currently not indexed | Crawled – currently not indexed |
|---|---|---|
| Has Googlebot fetched the page? | No | Yes |
| Has Google assessed the content? | No | Yes |
| Typical root cause | Crawl capacity or low crawl demand | Quality, duplication or low value |
| "Last crawled" in URL Inspection | Empty / N/A | Shows a date |
| Where to start fixing | Server health, internal links, URL bloat | Content quality, uniqueness, canonicals |

A simple rule: **"discovered" is a crawling problem, "crawled" is an indexing problem.** Rewriting content on a page Google has never fetched won't help much. Making the page easier and more attractive to crawl will.

## Is "Discovered – currently not indexed" always a problem?

No. On most sites, a few URLs in this status are normal. Google finds new URLs all the time and crawls them over the following days or weeks. If you published a batch of new pages yesterday, seeing them here is expected.

It becomes a problem when:

- **Important pages stay in it for weeks:** key product, service or category pages that never move to "Indexed".
- **The count keeps growing:** especially if it's growing faster than your indexed pages.
- **It's a large share of your site:** Google's crawl budget guide calls out sites where "a substantial portion" of URLs are in this status as an audience for crawl-budget work, even if they aren't huge.
- **The URLs shouldn't exist at all:** thousands of filter, sort, session or search-result URLs mean Google is finding junk faster than it can crawl it.

Start by opening the status in Search Console and exporting the example URLs. Sort them into two groups: pages you want indexed, and pages that should never have been discoverable. The fixes for each group are different.

## Why does Google delay crawling a page?

### 1. Your server looks overloaded

Google's crawl budget documentation describes a **crawl capacity limit**. Google sets it so crawling doesn't overwhelm your server, and adjusts it automatically. Fast, stable responses raise the limit. Slow responses and server errors (5xx) lower it. On cheap shared hosting or an overloaded server, Google may just crawl less, and newly found URLs wait in the queue.

Check the **Crawl stats** report in Search Console (Settings → Crawl stats). Look for rising average response time, host status warnings, and spikes in 5xx or timeout responses.

### 2. Weak internal linking

A URL found only in a sitemap, or linked once from page 40 of a paginated archive, sends a weak signal. Pages that are linked prominently from your homepage, main navigation and relevant category pages get crawled sooner. Orphan pages, with no internal links at all, are a classic cause of this status.

### 3. Too many low-value URLs competing for attention

This is the most common cause on e-commerce and large content sites. Faceted navigation (`?color=red&size=m&sort=price`), tracking parameters, internal search pages, calendar archives and near-duplicate tag pages can turn 2,000 real pages into 200,000 crawlable URLs. Google's crawl budget guide lists "perceived inventory" as a factor in crawl demand. If most of what Google finds is duplicate or low value, it spends less effort on the rest.

### 4. Site-wide quality signals

Crawl demand also depends on popularity and perceived value. A new domain with few external links, or a site with a large amount of thin, templated or auto-generated content, often sees slow crawling across the board. If Google has crawled similar pages from your site and found them unhelpful, it has less reason to rush to the next ones.

### 5. Wasted crawls on redirects, errors and soft 404s

Every redirect hop, broken link and soft 404 is a request that doesn't produce an indexable page. Redirect chains in internal links, links to 404s, and sitemaps full of non-canonical or redirected URLs all use up crawl capacity.

## How to fix "Discovered – currently not indexed" step by step

Work through these in order. The first steps fix root causes, and the later ones only help once those are in place.

### Step 1: Remove URLs that shouldn't be discoverable

Cut the crawl queue down before you try to speed it up.

- Block infinite URL spaces (faceted filters, internal search, sort parameters) in `robots.txt` where they have no search value.
- Stop linking to parameter and tracking URLs internally. Link to the clean canonical version.
- Return `404` or `410` for permanently removed pages instead of redirecting everything to the homepage.
- Consolidate true duplicates with 301 redirects or canonical tags.

A typical `robots.txt` pattern for an online shop:

```
User-agent: *
Disallow: /search
Disallow: /*?sort=
Disallow: /*?sessionid=
Disallow: /*&filter_
```

Be careful here. A `robots.txt` block stops crawling, but it doesn't remove URLs that are already indexed, and blocking the wrong pattern can hide pages you need. Also note that `noindex` doesn't save crawl budget: Google still has to crawl a page to see the tag.

### Step 2: Clean up your XML sitemap

Your sitemap should list only canonical, indexable URLs that return `200`. Remove redirected, noindexed, blocked and 404 URLs. Keep `<lastmod>` accurate, updated only when content really changes, as Google's crawl budget guide recommends. A sitemap with 30% junk teaches Google that your sitemap isn't reliable.

### Step 3: Strengthen internal links to the pages that matter

For each important URL in the export, ask: how many internal links point to it, and from where?

- Link key pages from the main navigation, category hubs or the homepage.
- Add contextual links from related, already-indexed articles or products.
- Fix orphan pages. Every page you want indexed needs at least one crawlable `<a href>` link.
- Keep important pages within a few clicks of the homepage.

### Step 4: Improve server response and stability

- Reduce server response time (TTFB) with caching, a CDN, or better hosting.
- Fix recurring 5xx errors and timeouts.
- Support HTTP caching headers (`ETag`, `Last-Modified`) so repeat crawls cost less.
- Make sure firewalls or bot protection aren't rate-limiting or blocking Googlebot.

Faster pages help users too. See our [Core Web Vitals guide](https://seorecheck.com/blog/core-web-vitals-guide) for the user-facing side of performance.

### Step 5: Fix redirect chains, broken links and soft 404s

Update internal links to point straight at final URLs, repair or remove links to 404s, and make sure empty or "no results" pages return a real `404` instead of `200`.

### Step 6: Request indexing, sparingly

Once the page is well linked and your server is healthy, use **URL Inspection → Request indexing** for your few most important URLs. The tool has a daily quota and doesn't guarantee crawling. It's a nudge, not a fix. Submitting hundreds of URLs while the root causes are still there won't clear the backlog.

### Step 7: Validate and monitor

After fixing, click **Validate fix** in the Page indexing report. According to Google's documentation, validation "typically takes up to about two weeks, but in some cases can take much longer." Watch the trend over several weeks rather than day to day.

## Which fix matters most for my site?

It depends on your site type and size. Use this as a starting point:

| Site type | Most likely cause | Fix first |
|---|---|---|
| Small business site (<500 pages) | Weak internal links, new domain, slow hosting | Internal linking, server speed, useful unique content |
| Blog / publisher | Orphan articles, thin tag and archive pages | Contextual links, prune or noindex thin archives, clean sitemap |
| E-commerce store | Faceted navigation and parameter URLs | robots.txt rules, canonical links, sitemap hygiene |
| Large or fast-changing site (10k+ pages) | Crawl capacity and URL bloat | Server capacity, crawl stats monitoring, URL consolidation |

Google says its crawl budget guide is mainly for very large sites: 1 million+ pages changing weekly, or 10,000+ pages changing daily. On a 300-page site, "crawl budget" is rarely the real limit. A small site with this status usually has a linking, quality or server problem, not a budget problem.

## Common mistakes to avoid

- **Repeatedly resubmitting the sitemap.** Google already knows about the URLs, since that's how they became "discovered". Resubmitting doesn't raise crawl priority.
- **Using `noindex` to "save crawl budget".** Google still has to crawl the page to see `noindex`.
- **Blocking CSS or JavaScript in robots.txt.** Google needs these files to render pages. Blocking them can make pages look broken.
- **Rewriting content before checking crawlability.** If Google hasn't fetched the page, content changes can't be what's holding it back.
- **Mass-generating thin pages.** Thousands of near-identical location or tag pages lower crawl demand for the whole site. This matters even more now that AI search features also draw on the indexed pages (see [how to rank in AI Overviews and AI search](https://seorecheck.com/blog/seo-for-ai-search)).

## How an SEO audit helps diagnose this status

Search Console tells you *which* URLs are waiting. It doesn't tell you *why*. To find the cause you have to cross-check several data sources: internal link counts, sitemap contents, status codes, redirect chains, canonical tags, parameter URLs and response times. That's the core of a [technical SEO audit](https://seorecheck.com/blog/technical-seo-audit).

An automated audit crawls your site the way a search engine does, and shows the patterns behind the status. Examples: 40% of sitemap URLs redirect, key product pages have one internal link each, or filter parameters generate thousands of duplicate URLs. You can see what that looks like in a [sample report](https://seorecheck.com/sample) and the [full sample report](https://seorecheck.com/sample/full). Because indexing fixes take weeks to show up, a follow-up check matters too. A [recheck comparison](https://seorecheck.com/sample/compare) shows which issues are fixed, improved, unresolved or new.

## Key takeaways

- "Discovered – currently not indexed" means Google found the URL but **hasn't crawled it yet**. It's a crawling problem, not a content verdict.
- Main causes: server capacity limits, weak internal linking, URL bloat from parameters and duplicates, and low site-wide crawl demand.
- Fix in order: remove junk URLs, clean the sitemap, strengthen internal links, improve server health, fix redirects and soft 404s, then request indexing for key pages.
- `noindex` doesn't save crawl budget, and resubmitting sitemaps doesn't speed crawling.
- Validation typically takes up to about two weeks, according to Google. Judge progress over weeks, not days.

## Find out why your pages aren't being crawled

If important pages are stuck in "Discovered – currently not indexed" and you're not sure why, start with the evidence. [Request a free SEO audit preview](https://seorecheck.com/request) to get your SEO score and real issues found on your own pages. Then decide whether you need the full prioritized plan.

---

## Want to know what to fix on your site?

Get a free SEO audit preview: your score and real issues, with evidence from your pages.

- [Get a free SEO audit](https://seorecheck.com/request)
- [See a sample report](https://seorecheck.com/sample)