ProductsMenu
About

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

Google found your URL and has not crawled it yet. The first things to check are internal links pointing to that page and whether your sitemap lists only final, indexable URLs.

On this page
  1. What does "Discovered - currently not indexed" mean?
  2. What did our own Search Console show?
  3. What causes it, in the order to check?
  4. How do you fix "Discovered - currently not indexed"?
  5. What did we change on our site?
  6. When should you request indexing?
  7. Can a free audit find these pages for you?
  8. What mistakes should you avoid?
  9. Questions people ask
  10. What to read next

What does "Discovered - currently not indexed" mean?

The Page indexing report in Google Search Console marks a URL "Discovered - currently not indexed" when Google found the page but has not crawled it yet. Google's own wording: "Typically, Google wanted to crawl the URL but this was expected to overload the site," so Google rescheduled the crawl.

The last crawl date in the report is empty.

How is it different from "Crawled - currently not indexed"?

"Crawled - currently not indexed" means Google visited the page and read it, then chose not to add it to its index. Google Search Console Help notes that Google does not index all pages across the web, so this message is common and does not necessarily point to a problem that needs attention. "Discovered - currently not indexed" is earlier in the process: Google has not visited the page at all.

What did our own Search Console show?

We ran Google's URL Inspection API across every URL in the maitreyalabs.com sitemaps on 18 November 2026 and again on 19 November 2026. The table below shows what we found each day.

Status18 Nov 202619 Nov 2026
Submitted and indexed1007
Discovered - currently not indexed60148
URL is unknown to Google3160
Duplicate, Google chose different canonical131
Crawled - currently not indexed11
Not checked01
Sitemap URLs in total205218
Never crawled91209

The jump from 60 to 148 in the "Discovered" column happened because we moved most pages to new addresses on 18 November. Of the 25 URLs present in both checks, 6 moved from "URL is unknown to Google" to "Discovered - currently not indexed" within one day. One day is too early to judge the full effect of those changes. We will run the same check again and update this page with the date.

What causes it, in the order to check?

Work through these five causes in order.

  1. Too few internal links. Google finds pages by following links. If a page has few or no links from pages Google already crawls, it may sit undiscovered for a long time. Open the URL Inspection tool for the affected page and check whether Google has crawled any page that links to it.
  1. Many thin or near-identical URLs. When a site has a large number of low-value pages, Google may hold back its crawl budget and leave many pages in "Discovered" status. Look at the Page indexing report and count how many unique, meaningful pages you have versus how many are filters, tags or near-duplicates.
  1. A slow server or frequent errors. Google's own wording mentions "overload" as the reason it reschedules the crawl. Check the Crawl stats report in Google Search Console for spikes in server errors or high crawl response times.
  1. A sitemap with problem URLs. A sitemap that lists redirecting URLs, URLs with a noindex tag, or URLs whose canonical points elsewhere tells Google mixed signals. Export the sitemap and check each URL resolves to a final, indexable address.
  1. A large site spread over time. On very large sites, some pages stay in this status while Google works through the queue.

How do you fix "Discovered - currently not indexed"?

Fix the underlying cause first, then ask Google to validate the fix. Requesting indexing for a few key URLs can help while you wait.

Triage checklist: Discovered - currently not indexed

1. Open the Page indexing report in Google Search Console and export the list of affected URLs.
2. For each important URL, check it has internal links from pages Google has already crawled (use the URL Inspection tool).
3. Check the sitemap lists only final, indexable URLs: no redirects, no noindex pages, no URLs whose canonical points elsewhere.
4. Open the Crawl stats report and check for server errors or slow response times that match Google's "overload" wording.
5. Review thin or near-duplicate pages. Decide which ones to merge, improve or remove.
6. After making fixes, use the URL Inspection tool to request indexing for a few key URLs.
7. For the whole issue, click Validate Fix once in the Page indexing report. Do not click it again while validation runs.
8. Check the report again after about two weeks. Google Search Console Help says validation typically takes up to about two weeks, though sometimes longer.
9. If the status persists, re-examine internal linking and check whether new thin pages were added while the fix was in progress.

What did we change on our site?

On 18 and 19 November 2026 we made the following changes to maitreyalabs.com:

The indexed count fell from 100 to 7 the day after the move, which is expected: Google has not yet crawled the new addresses. The effect on indexing is not measured. We will update this page when the next check is complete.

When should you request indexing?

Request indexing for a few important URLs after you have made fixes.

The URL Inspection tool handles one URL at a time, so keep it for a handful of key pages. For a whole issue in the Page indexing report, use the Validate Fix button, and wait for Google to work through the queue. Google Search Console Help says validation typically takes up to about two weeks, though in some cases it takes longer.

Can a free audit find these pages for you?

SEO Audit reads your site's own Google Search Console data, which includes which pages are indexed, and puts technical issues in the order you should fix them.

It shows the pages not indexed alongside the other technical signals from your property. Run a free SEO audit from your Search Console data to see the full picture in about 10 minutes.

What mistakes should you avoid?

Watch out for these common missteps when working through a "Discovered - currently not indexed" issue.

One limit of this article: the numbers in the table above come from one small site over two days. Patterns on larger sites, or on sites that have not recently moved pages, may look different.

Questions people ask

These are the questions site owners ask most often about this status.

Is "Discovered - currently not indexed" a penalty?

Google found the page and has not crawled it yet. Nothing in Google's wording for this status calls it a penalty. Google Search Console Help describes it as Google rescheduling the crawl, typically because of a concern about server load.

How long does a page stay in this status?

No specific number is published. Google Search Console Help says validation of a fix takes up to about two weeks, though in some cases it can take much longer.

Should I resubmit my sitemap?

Resubmitting a corrected sitemap is useful if the sitemap previously listed problem URLs. After correcting it, submit the new version in Google Search Console under Sitemaps.

If you are weighing which tool to use for a full site audit, compare SEO audit tools by the job they do to see how the common options line up against what a site owner actually needs to know.

Get my free audit