GuidesIndexed

Discovered - currently not indexed: Google knows the page but hasn’t read it

Google has the address and has put off fetching it. For a page published yesterday that is often just a queue. For dozens of pages, it usually says something about the site.

John Geater, founder of IndexFirst5 min read
The short answer

Discovered - currently not indexed means Google has found the URL but has not crawled it, which is why URL Inspection shows no last crawl date. Until Google crawls and indexes it, the page cannot appear in Google Search or in Google’s AI answers. A new page can simply be waiting its turn. When lots of pages sit here, Google’s own staff point to the quality of the site more often than to the server.

Discovered but not crawled: what it means

The URL is on Google’s list and Googlebot has not opened it yet. Google’s help page says that, typically, it “wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl.”

It sits one step before Crawled - currently not indexed, where Googlebot has fetched the page and Google has chosen not to keep it. With Discovered, Google has not seen the content at all, so nothing about the page itself has been judged yet.

Google usually finds the address from your sitemap or from a link. A new location page linked from your services menu and listed in the sitemap might show this status for a few hours or days before Googlebot gets to it. Google says a new page can take “a week or so” to be crawled and indexed, so a page from last Tuesday is not a cause for concern on its own.

Why pages stay in Discovered: your server or your site

The help text points at your server. Google’s Martin Splitt, in a video on this status, gave two causes and said one is far more common than the other.

On the server side, Googlebot slows down if “your server is slow” or struggling, though he said that “usually only matters for sites with very large amounts of pages.” The more common cause, in his account, is quality: when Google sees a pattern of weak pages, “Googlebot knows about these pages but is choosing not to proceed with them.”

So the reason on the help page fits mainly very large sites. For a law firm, IT support company or recruiter with a few hundred pages, look at the site first. Google’s crawl budget guide backs this up: how much Google wants to crawl a site “varies based on a site’s size, update frequency, page quality, and relevance, compared to other sites.”

The two causes Google gives, and where each one pointsYour server, the cause on Google’s help page: slow responses, 5xx errors and 429s; check the Crawl Stats report; mostly matters on very large sites. Your site, the cause Martin Splitt describes as more common: thin, duplicate or low-value pages; applies to sites of any size.Your serverThe cause on Google’s help pageSlow responses, 5xx errors, 429sMostly matters on very large sitesYour siteSplitt: the more common oneThin, duplicate or low-value pagesSites of any size
Two causes from Google, and which sites each one fits. Sources: Google’s Page indexing report help and Martin Splitt, as reported by Search Engine Roundtable (21 August 2024).

Sometimes it is neither. Splitt also said Googlebot may simply not have “got around to crawling the URL yet as it was busy with other URLs,” and that “sometimes it’s just a matter of a bit more patience on your end.” A page you published this week may be exactly that.

How to fix discovered - currently not indexed in Search Console

Take these in order. On a small site, the first three do most of the work.

  1. Read the example URLsOpen the status in the Page indexing report and see what is listed. Contact-form URLs with ?service= or ?office= on the end, ?sort= versions of your news page, WordPress tag archives and job-search URLs often gather here. Google’s crawl budget guide says duplicates and URLs you do not want crawled waste Google’s crawling time on your site. Keep them out of the sitemap and out of your internal links.
  2. Link important pages from pages Google already crawlsYour homepage, the main menu, or a hub such as a services or locations page. Splitt’s advice for pages you care about is to make sure “your internal linking relates this content to other parts of your existing content.”
  3. Make each page worth fetchingHis other piece of advice: “rework the content to be of higher quality.” On service business sites, look hard at town-by-town pages that only change the place name, office pages that hold just an address, and service pages that repeat each other. Give each one something only it says, or merge it into a page that does.
  4. Keep the sitemap cleanList only pages you want indexed, each with an accurate lastmod date. Google only trusts lastmod when it is “consistently and verifiably” accurate, so do not let a plugin stamp today’s date on every page.
  5. Check the serverThe Crawl Stats report in Search Console shows response times and errors. Google crawls less when the site slows down or returns server errors (5xx) or rate limits (429). A firewall or bot-protection rule that answers Googlebot with 429 counts too.
  6. Then ask onceFor a page that matters, press Request indexing in URL Inspection. There is a daily limit, and even a direct request is never instant. Validate fix and the rest work just as described in our crawled - currently not indexed guide.

When Search Console isn’t indexing lots of your pages

Count first. A few new pages in Discovered just means they are queuing. Thousands of URLs is a different problem. Google’s crawl budget guide lists sites with “a large portion of their total URLs classified by Search Console as Discovered - currently not indexed” among those it is written for. For everyone else, Google considers a current sitemap and a regular look at the Page indexing report to be enough.

If most of a smaller site is stuck here, act on Splitt’s point: Google has seen enough of the site to put the rest off. Cutting pages for the sake of it is not the answer; improving the ones that matter is. The whole-site steps in our crawled guide apply here as well.

Getting indexed is the first of three stages we take every client through: indexed, then found, then named in AI answers. It is all one plan, at £1,750 a month.