What Does "Discovered - Currently Not Indexed" Mean?

What the "Discovered - currently not indexed" status says about a URL, why Google postpones a crawl, when the status needs action and what you can change to get the page crawled.

Written by Sebastian Kinzlinger, Founder, Keylogs

Discovered - currently not indexed is a Page indexing status in Google Search Console for a URL that Google has found but not crawled yet. Google knows the address, usually from a link or a sitemap, and has postponed fetching it, typically because the crawl was expected to overload the site. The page is not in the index.

Key takeaways

  • "Discovered - currently not indexed" means Google found the URL but has not crawled it yet, so Google has not read the page.
  • Google's stated typical cause is that crawling the URL was expected to overload the site, so the crawl was rescheduled.
  • The last crawl date is empty for these URLs, and the status cannot be tested with a live test in the URL Inspection tool.
  • After a URL is known, Google says it can take up to a few weeks before it crawls some or all of a site.
  • Google names two ways to get more crawling, more server resources and better content quality, and says you cannot tell it to raise your crawl rate.
On this page

What "Discovered - currently not indexed" means

"Discovered - currently not indexed" is one of the reasons listed under "Not indexed" in the Page indexing report. Google's description is three sentences: 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, so it rescheduled the crawl; and that is why the last crawl date is empty on the report. [1]Google Search Console Help. Page indexing report

The status describes a URL that is stuck between the first two stages of Google Search. Google first finds out which pages exist, a step it calls URL discovery, by following a link from a page it already knows or by reading a sitemap you submitted. [3]Google Search Central. In-depth guide to how Google Search works Once a URL is discovered, Google may crawl the page to find out what is on it, but Googlebot does not crawl all the pages it discovered. [3]Google Search Central. In-depth guide to how Google Search works Google decides algorithmically which sites to crawl, how often, and how many pages to fetch from each. [3]Google Search Central. In-depth guide to how Google Search works

Because Google has not fetched the page, the status says nothing about the page's content. It is a statement about crawling.

Why Google postpones the crawl

Google's crawlers are programmed to avoid crawling a site too fast, and they read the site's responses as a signal; an HTTP 500 error means "slow down". [3]Google Search Central. In-depth guide to how Google Search works The crawl budget guide describes the mechanics. A site's crawl budget is determined by two elements, the crawl capacity limit and crawl demand. [2]Google Search Central. Optimize your crawl budget

ElementWhat it isWhat moves it
Crawl capacity limitHow much Google can crawl without overwhelming your servers.Goes up when the site responds quickly and consistently; goes down when the site slows or returns server errors.
Crawl demandHow much Google wants to crawl the site.Site size, update frequency, page quality and relevance compared to other sites; how many URLs Google knows about; popularity; staleness.

The table follows Google's guide. [2]Google Search Central. Optimize your crawl budget Even when the capacity limit is not reached, Google crawls a site less if crawl demand is low. [2]Google Search Central. Optimize your crawl budget

Server responses feed the capacity side directly. 5xx and 429 responses prompt Google's crawlers to slow down temporarily, and the decrease is proportionate to the number of URLs returning a server error. [5]Google Search Central. How HTTP status codes affect Google's crawlers 4xx status codes other than 429 have no effect on crawl rate. [5]Google Search Central. How HTTP status codes affect Google's crawlers

Is it a problem?

Often not. Google introduces the "Not indexed" list as pages that have not been indexed, but not necessarily because of an error, and says that most sites have at least a few unindexed pages. [1]Google Search Console Help. Page indexing report After a URL is known, it can take up to a few weeks before Google crawls some or all of a site. [1]Google Search Console Help. Page indexing report

SituationReading
A few URLs published in the last days or weeksNormal. Google has found them and not fetched them yet.
URLs you do not want in Search (filters, parameters, internal search results)No loss, but they add to the URLs Google thinks it has to crawl.
Important canonical pages that stay in the status for weeksWorth acting on.
A large share of the site's URLsGoogle's crawl budget guide is written for this case.

The last row is Google's own classification: its crawl budget guide is intended for very large sites, for medium or larger sites with rapidly changing content, and for sites with a large portion of their URLs classified as "Discovered - currently not indexed". [2]Google Search Central. Optimize your crawl budget Google's goal for you is narrower than full coverage: get the canonical version of every important page indexed. [1]Google Search Console Help. Page indexing report

A URL in this status earns no impressions and no clicks, because it is not in the index. If a page that used to appear in the Performance report goes missing, read its indexing status first.

Example: 5,000 URLs, 600 of them discovered and not crawled

The table below is constructed to illustrate the pattern. A shop has 5,000 known URLs, and 600 of them are listed as "Discovered - currently not indexed".

GroupURLsWanted in SearchReading
Filter and sort parameter URLs430NoKeep them out of the crawl.
Product pages published this month110YesWait, and check that they are linked.
Category pages published four months ago45YesAct: old, important, still not crawled.
Tag archives15NoRemove or block.

Of the 600 URLs, 155 are pages the shop wants indexed, and only 45 have waited long enough to justify work. The other 445 are inventory the shop never needed crawled.

How to fix it

  1. Open the Page indexing report, click "Discovered - currently not indexed" under "Why pages aren't indexed", and read the example URLs. The list is limited to 1,000 rows and does not necessarily show every affected URL. [1]Google Search Console Help. Page indexing report
  2. Sort the URLs into pages you want in Search and pages you do not.
  3. Check the server. In Settings > Crawl stats, look at host status and average response time. If the site responds slowly or its server error rate rises, Googlebot throttles back its requests. [6]Google Search Console Help. Crawl Stats report
  4. Reduce the URLs you do not want crawled. Google's list: consolidate duplicate content, block crawling with robots.txt, return a 404 or 410 for permanently removed pages, and keep sitemaps up to date. [2]Google Search Central. Optimize your crawl budget The same guide cautions against using noindex for this. [2]Google Search Central. Optimize your crawl budget
  5. Link the important pages from pages Google already crawls; see internal links to underperforming pages.
  6. For a few important URLs, request indexing in the URL Inspection tool. There is a daily limit, and a request does not guarantee that the page will be indexed. [4]Google Search Console Help. URL Inspection tool The full steps are in how to request indexing.

Google names only two ways to increase crawl budget: add server resources if the server is the limit, and improve the quality of the content. [2]Google Search Central. Optimize your crawl budget You cannot tell Google to increase your crawl rate. [6]Google Search Console Help. Crawl Stats report The other reasons in the report are covered in why is my page not indexed.

The thing people get wrong

The status is read as "Google looked at my page and rejected it". Google has not looked: the page was found, but not crawled yet, and the last crawl date is empty. [1]Google Search Console Help. Page indexing report Rewriting the page changes nothing Google has seen. What Google has seen is the rest of the site and how the server responds.

The second mistake is resubmitting. Requesting a recrawl several times for the same URL does not get it crawled any faster. [8]Google Search Central. Ask Google to recrawl your URLs Adding the URL to a sitemap again does not help either: a sitemap helps discovery, and it does not guarantee that its items are crawled and indexed. [7]Google Search Central. Learn about sitemaps The sitemap guide explains what a submitted sitemap does.

"Discovered - currently not indexed" vs "Crawled - currently not indexed"

Discovered - currently not indexedCrawled - currently not indexed
Google's descriptionFound, but not crawled yetCrawled, but not indexed
Last crawl dateEmptySet
Has Google read the page?NoYes
Where to lookServer capacity, URL inventory, internal linksThe page itself, if it is important

Both descriptions come from the same help page, which calls "Crawled - currently not indexed" a common message that does not necessarily indicate an issue. [1]Google Search Console Help. Page indexing report

Neither status is a duplicate status. Duplicate without user-selected canonical, Alternate page with proper canonical tag and Duplicate, Google chose different canonical than user all describe pages Google has crawled and compared with another URL. When two crawled and indexed pages compete for one query, that is keyword cannibalization, which a content merge addresses.

Where the status can mislead

The report lags. Google updates an issue's count only when it crawls a page with that issue, and the example list is not guaranteed to be complete. [1]Google Search Console Help. Page indexing report For one page, the URL Inspection tool is the current record, and the check if a page is indexed guide covers the other ways to check. To read the status across many URLs at once, the Google Index Checker groups a property's pages by the coverage state Google returns.

The live test cannot confirm the status either way. Google lists "Discovered - currently not indexed" among the issues that cannot be tested in a live test, and says a valid live result does not mean the page will be indexed. [4]Google Search Console Help. URL Inspection tool The live test also does not check whether the URL is in a sitemap or linked from a referring page. [4]Google Search Console Help. URL Inspection tool

Crawl Stats has its own limits. Google aims the report at advanced users, offers it only for root-level properties, and says a site with fewer than a thousand pages should not need it. [6]Google Search Console Help. Crawl Stats report A sitemap matters less on small sites too: Google says a site of about 500 pages or fewer that is comprehensively linked internally might not need one. [7]Google Search Central. Learn about sitemaps On a site that size, a few URLs in this status usually call for links and patience, and crawling can take anywhere from a few days to a few weeks. [8]Google Search Central. Ask Google to recrawl your URLs

Frequently asked questions

Is "Discovered - currently not indexed" bad?
Not by itself. Google lists the status under pages that are not indexed "but not necessarily because of an error", and says most sites have at least a few unindexed pages. It is a problem when the URLs are important canonical pages, or when a large share of the site stays in the status for weeks.
How long does "Discovered - currently not indexed" last?
Google gives no duration for the status. Its general guidance is that after a URL is known it can take up to a few weeks before Google crawls some or all of a site, and that crawling can take anywhere from a few days to a few weeks.
Does requesting indexing fix "Discovered - currently not indexed"?
A request in the URL Inspection tool can put one URL into the indexing queue, but Google says a request does not guarantee that the page will appear in the index. There is a daily limit on requests, and asking several times for the same URL does not get it crawled faster.
What is the difference between "Discovered - currently not indexed" and "Crawled - currently not indexed"?
With "Discovered - currently not indexed" Google has found the URL but has not crawled it. With "Crawled - currently not indexed" Google crawled the page and did not index it. The first is a crawling question, the second is a decision Google made after reading the page.
Does adding the page to a sitemap fix it?
A sitemap helps Google discover URLs, and a page in this status is already discovered. Google says a sitemap does not guarantee that every item in it will be crawled and indexed.

The bottom line

Discovered - currently not indexed is the Search Console status for a URL Google knows about and has not crawled yet. The decision is whether to wait or to act: a handful of new URLs usually only need time, while important pages that stay in the status, or a large share of the site, point at server capacity or at how much Google wants to crawl the site. Check the server's responses in the Crawl Stats report, trim the URLs you do not need crawled, and link the important pages from pages Google already crawls.

Article sources

  1. Google Search Console Help. “Page indexing report”. Accessed Nov 18, 2026.
  2. Google Search Central. “Optimize your crawl budget”. Accessed Nov 18, 2026.
  3. Google Search Central. “In-depth guide to how Google Search works”. Accessed Nov 18, 2026.
  4. Google Search Console Help. “URL Inspection tool”. Accessed Nov 18, 2026.
  5. Google Search Central. “How HTTP status codes affect Google's crawlers”. Accessed Nov 18, 2026.
  6. Google Search Console Help. “Crawl Stats report”. Accessed Nov 18, 2026.
  7. Google Search Central. “Learn about sitemaps”. Accessed Nov 18, 2026.
  8. Google Search Central. “Ask Google to recrawl your URLs”. Accessed Nov 18, 2026.

Keylogs requires writers to use primary sources — Google's own documentation and original Search Console data. Learn more about our editorial standards.

← All glossary terms