It means Google has found the address of the page but hasn’t visited it yet. Google says this usually happens because crawling the URL right then was expected to overload your site, so it rescheduled the visit. On a small website, a handful of new pages sitting in this status for a few days is normal. It’s worth acting when important pages stay there for weeks, or when the list is long and keeps growing. The usual causes are a slow or struggling server, or a site that creates far more URLs than it has real pages.

What Google says this status means

In Search Console’s Page indexing report help (checked 14 November 2026), Google defines it in three short points:

  • The page was found by Google, but not crawled yet.
  • Typically, Google wanted to crawl it, but expected that doing so would overload the site, so it rescheduled the crawl.
  • That’s why the last crawl date is empty.

The key word is discovered. Google hasn’t read the page, so it hasn’t judged the content at all. That makes this status different from its better-known neighbour.

How it differs from “Crawled – currently not indexed”

Status Has Google read the page? Usually points to
Discovered – currently not indexed No Crawling: server capacity, too many URLs, weak internal links
Crawled – currently not indexed Yes The page itself: value, duplication, purpose

If your pages are in the second group, our guide to “Crawled – currently not indexed” covers that problem.

Step 1: Decide whether it matters

Google’s help page says that if your site has fewer than 500 pages, you probably don’t need the Page indexing report at all. So start by sorting the list into two piles.

Usually fine to leave:

  • Pages you published in the last week or so. Google’s help says it can take about a week for a new page to be crawled and indexed.
  • URLs with sorting, filter or tracking parameters, such as ?sort=price or ?colour=blue
  • Tag pages, empty archives, internal search results

Worth investigating:

  • Main service or product pages that have been in this status for several weeks
  • Important guides you linked from your menu or homepage
  • A list that’s growing much faster than you’re publishing

If only the first pile is on your list, you can stop here and check again next month.

Step 2: Check whether your server is telling Google to slow down

Because this status is about Google holding back to avoid overloading your site, the first suspect is the server.

Google’s crawl budget guide (last updated 22 July 2026, checked 14 November 2026) explains that Google crawls less when a site slows down, or responds with server errors (5xx) or “slow down” signals (429). It crawls more when responses stay quick and stable.

Three quick checks:

  1. Crawl Stats report. In Search Console, go to Settings, then Crawl stats, and look at Host status. Google’s Crawl Stats help says sites under 1,000 pages normally needn’t worry about this report, but it’s the right place to look if many pages are stuck. A recent availability issue, rising average response time or a run of server errors is a clue.
  2. URL Inspection live test. Test one stuck page. If the live test can fetch it quickly and without errors, the server may be fine now, and the problem may have been temporary.
  3. Ask your host about blocking. Google’s Page indexing help notes that firewalls and bot-protection tools can block Googlebot because it makes more requests than a person does. Cheap shared hosting and aggressive security plugins are common culprits on small sites.

If the server is the problem, the fix sits with your hosting: a faster plan, better caching, or a firewall rule that stops blocking verified Google crawlers.

Step 3: Check whether your site is creating too many URLs

The second suspect is what Google calls perceived inventory: all the URLs it knows about on your site. Google’s crawl budget guide says that if many of those URLs are duplicates or unimportant, crawling time is wasted, and this is the factor you can control most.

The same guide lists “a large portion of URLs classified as Discovered – currently not indexed” as one of the signs that crawl budget is worth your attention, even for sites smaller than the million-page sites it mainly addresses.

On small business sites, the extra URLs usually come from:

  • shop filters and sort options that create a new URL for every combination
  • calendar or booking pages with a URL for every date
  • tag pages for every small topic
  • old pages that now show an empty template instead of a proper 404

What Google recommends in that guide:

  • Consolidate duplicates so one page carries each piece of content.
  • Return 404 or 410 for pages that are gone for good.
  • Block truly useless URL patterns in robots.txt, such as endless filter combinations, if you can’t consolidate them. Don’t use robots.txt as a trick to push Google towards other pages; Google says it won’t shift that crawling elsewhere unless your site is already hitting its capacity limit.
  • Don’t rely on noindex to save crawling. Google still has to fetch a noindexed page to see the tag.
  • Avoid long redirect chains.

Step 4: Make your important pages easy to find and prioritise

Once the server and URL clutter are under control, help Google see which pages matter.

  • Link to them from pages Google already crawls, such as your homepage, main menu and related guides.
  • Keep your XML sitemap up to date, listing only the pages you want indexed, with honest lastmod dates when content changes.
  • Request indexing for a few key pages in URL Inspection, once. Google’s help is clear that indexing is never instant, even after a request, so repeating it every day doesn’t help.

Quick guide: what you found and what to do

What you found What to do
A few new pages, published recently Wait a week or two, then check again
Host status shows recent problems Talk to your host about speed, errors or blocking
Thousands of filter or date URLs Consolidate or block the useless patterns
Old deleted pages showing a blank template Return a proper 404 or 410
Important pages with no internal links Link to them from your menu and related pages
Everything looks healthy, pages still stuck after weeks Recheck the sitemap, then ask for a second opinion

A hypothetical example

This is an invented example. A small furniture shop has about 120 products. Its online shop lets visitors filter by colour, size and material, and each combination creates a new URL. Search Console shows more than 4,000 URLs as “Discovered – currently not indexed”, including six new sofa pages that have been stuck for a month.

Requesting indexing for the sofas over and over wouldn’t fix the cause. The shop’s developer makes the filter combinations stop generating separate crawlable URLs, links the new sofas from the main “Sofas” category page and confirms they’re in the sitemap. The Crawl Stats report also shows slow responses at night, so the shop moves to a faster hosting plan. Nothing here guarantees the pages will be indexed by a certain date. It removes the reasons Google had to hold back.

What’s in your control, and what isn’t

In your control: how fast and reliable your server is, how many URLs your site generates, whether removed pages return the right status, how well important pages are linked, and whether your sitemap is accurate.

Not in your control: when Google crawls a page, and whether it indexes it afterwards. Google says plainly that crawling and indexing aren’t guaranteed. If your site has a lot of thin or duplicate pages, our guide to crawl budget on small sites explains the wider picture.