Findmetry guide / Indexing

Discovered – Currently Not Indexed: What It Means and What to Check

In simple terms

Google knows this URL exists but has not visited it yet. Because Google has not fetched the page in the reported state, its content has not been assessed for indexing. On a new or small site, this may be a normal wait. On an online store with many filter and variant URLs, excess URLs or a slow host may delay crawling of useful pages. Check which case you are in before changing anything.

Published · Updated

Should I worry?

Usually fine

The site or URL is new, or the URL is a filter, sort or tracking variant you do not need in search. Check that the important pages are linked and in your sitemap, then monitor.

Investigate

Important product or category pages remain in this status for several weeks, or the count keeps growing. Compare the URL inventory with your real pages and check the host status in Search Console.

Likely problem

A large share of important pages is uncrawled and separate evidence shows server errors, slow responses or a flood of parameter URLs. Fix the observed condition and monitor what Google crawls next.

What this status proves, and what it does not

Google's Page indexing report defines Discovered – currently not indexed as a page Google found but has not crawled yet. It says Google typically postponed a crawl because it expected crawling to overload the site; the last crawl date is empty. This report label alone does not prove that your server is overloaded. Google's Page indexing report explanation

The label does not prove the page is thin, duplicate or penalized: Google has not fetched it in this reported state. This differs from Crawled – currently not indexed, where Google fetched the URL and did not index it at that time. Google says advanced crawl budget work mainly matters for very large or rapidly changing sites, or sites with a large portion of URLs in this status. Google's crawl budget guide

Findmetry diagnostic framework

Work through the evidence in this order

  1. Decide whether this URL should be crawled at all.

    Is it a real product, category or content page, or a filter, sort, search or tracking variant? Parameter URLs such as ?color=green or ?sort=price may produce similar views. If the URL is a variant you do not want in search, it may not need fixing. Continue for important pages.

  2. Check the size of the queue against the size of your site.

    Compare the number of URLs Google reports with the number of pages you publish. A large gap suggests an inventory to examine, not proof of the cause. Google calls the known URL set perceived inventory, a factor site owners can influence. Google: crawl demand and inventory

  3. Check how your server looks to Google.

    Open Settings → Crawl stats in Search Console and read the host status. Google can reduce crawling when a site slows down or returns server errors (5xx) or rate limits (429). Check whether bot protection or a firewall affects verified Googlebot requests. Fix confirmed availability problems first.

  4. Check how Google can reach the page.

    Is the intended URL in your sitemap? Is it linked from a crawlable category or navigation page, rather than reachable only through on-site search or infinite scroll? A sitemap helps discovery, but does not force a crawl. Google: sitemaps

  5. Check for crawl waste you can remove.

    Look for soft 404 pages, long redirect chains and permanently removed products that still return 200. Return 404 or 410 for products with no replacement. These are site-level checks; the status does not establish that any applies to this URL. Google: crawl budget best practices

  6. Wait and observe.

    If the sitemap, links and host look healthy, there may be no demonstrated site defect. Google's crawling can take days to weeks; inspect the URL and monitor the reports rather than changing unrelated settings. There is no fixed deadline or indexing guarantee. Google: requesting a recrawl

Decision rule: This status names a crawl state, not a root cause. A fix needs separate evidence: excess URLs, an unhealthy host, a missing path or wasted crawls. A crawl still does not guarantee indexing.

Two illustrative cases, two different decisions

Illustrative technical case / synthetic, not a customer finding

Filter URLs outnumber real products

Suppose a clothing store sells 400 products, but its filters generate thousands of size, color and sort URLs. Search Console lists many as Discovered – currently not indexed, alongside some new product pages. The excess URL inventory merits investigation. Consolidate genuinely duplicate variants; if filtered URLs need not appear in search, consider Google's faceted navigation guidance for preventing unwanted crawling. Keep crawlable paths to individual product pages. Limit: reducing unnecessary URLs does not guarantee when Google will crawl the products, and this scenario does not establish that the filters caused their delay.

Illustrative technical case / synthetic, not a customer finding

Bot protection slows Google down

A store adds a firewall rule that challenges high-volume visitors. Crawl stats shows slower responses and failed requests while new products remain uncrawled. The observed failures warrant checking the firewall logs. Confirm real Googlebot requests by verifying the crawler, not trusting a user agent string alone, and correct a rule that blocks it. Limit: improved availability does not guarantee an immediate crawl or indexing.

Technical deep dive

Queue versus decision: Discovered means no crawl is recorded in this report state. Crawled means Google fetched the URL and did not index it at that time. A noindex tag, canonical declaration or thin content on an unfetched page cannot be evaluated from the status alone. Check URL Inspection for the latest known state.

Crawl capacity: Google limits crawling so it does not overload a host. Stable, fast responses can raise the limit; slow responses, 5xx or 429 can lower it. Each hostname has a separate crawl budget. Google: crawl capacity

Crawl demand and inventory: Without guidance, Google tries to crawl most known URLs. Duplicate and unimportant URLs can consume resources, especially at scale. Consolidate genuine duplicates where appropriate. Google: canonical signals

noindex versus robots.txt: Google requests a page before it can read a noindex tag. Robots.txt prevents crawling but does not guarantee that the URL stays out of search. Google says blocking URLs does not reallocate crawling to other pages unless the site is already at its crawl capacity limit. Block only URLs you do not want crawled. Google: crawl budget practices

Sitemaps: List the canonical URLs you want crawled and use lastmod for real updates. A sitemap helps discovery; it does not force a crawl. Google: sitemaps overview

Removed products: A 404 or 410 is a strong signal not to crawl a permanently removed URL again. A soft 404 can continue to consume crawl resources.

What not to do

  • Do not add noindex to low-value URLs solely to save crawling; Google still requests them.
  • Do not block pages in robots.txt expecting Google to crawl your products instead.
  • Do not request indexing for hundreds of URLs one by one; investigate the affected pattern.
  • Do not rewrite product descriptions to fix this status; Google has not fetched the page in this reported state.
  • Do not list filter, sort or tracking URLs you do not want indexed in your sitemap.

Technical checklist

  1. Decide whether the exact URL should be crawled and identify the intended canonical version.
  2. Compare known URLs with the real pages you publish; check for large parameter groups.
  3. Read host status and response times in Crawl stats; record any 5xx or 429.
  4. Confirm the intended URL is in the sitemap and linked from a crawlable page.
  5. Find soft 404s, long redirect chains and removed products returning 200.
  6. Consolidate duplicates or block only URL patterns you never want crawled.
  7. Monitor URL Inspection for a crawl date; allow time and avoid an indexing guarantee.

Sources and update date

Published and last checked 28 September 2026. Technical references are Google's Page indexing report, crawl budget guide, faceted navigation guidance, canonical guidance, crawler verification and sitemaps overview. Both cases are synthetic teaching examples, not Findmetry or customer findings.

Need to know which case applies?

Findmetry can investigate your public website and show the evidence, scope and next action.

Request a diagnostic →