stillindexedStart monitoringOpen the app

Search Console Page indexing: Why pages aren't indexed

Discovered - currently not indexed: what it means

Google knows the URL but has not crawled it yet, usually to avoid overloading the site. When it clears on its own and when to act on it.

Google knows the URL exists but has not crawled it yet, typically because crawling then was expected to overload the site, so Google rescheduled. On a new site this is expected for a while. If it persists, make the server faster, cut low-value URLs, and link to the pages that matter.

What "Discovered - currently not indexed" means

Google: "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; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report." Google found the URL in a sitemap or a link and knows nothing about its content yet. Like "Crawled - currently not indexed", the report gives its source as "Google systems".

Is it a problem?

Depends on the URL

Usually a matter of time on a small or new site. Google's crawl budget guide names a large share of URLs in this status as one sign that crawl budget is worth managing. It needs action when the count keeps growing or important pages sit here for weeks.

Causes, most likely first

  1. The site is new or the URLs were just published. Google says every site starts with the same conservative crawl capacity limit, raised over time while the site stays healthy.
  2. The server was slow or returned errors. Google lowers the crawl capacity limit when response times rise or when it sees 5xx or 429 responses.
  3. Too many low-value URLs competing for the same crawl time: filter and sort parameters, session IDs, duplicate pages, soft 404s.
  4. Low crawl demand. Google crawls more popular URLs more often, so pages with few links pointing at them wait longer.

How to confirm it

  1. Inspect the URL. The live test cannot check this status, but the indexed result shows whether there is a crawl date and how Google discovered the URL.
  2. Open Property settings, Crawl stats, and check the host status and average response time.
  3. Run the sitemap validator on your sitemap to confirm it is reachable, parses and lists as many URLs as you expect.

Sitemap validatorBulk indexability checker

How to fix it

  1. Make the server answer quickly and without errors. That is what raises the crawl capacity limit.
  2. Stop generating low-value URLs, or keep Google out of them: consolidate duplicates and block endless filter and sort combinations in robots.txt.
  3. Link to the important pages from pages Google already crawls, and keep them in an up-to-date sitemap with accurate lastmod values.
  4. Request indexing in URL Inspection for a handful of key URLs. Google says there is a quota, so do not spend it on the whole list.

How long recovery takes

Google says that after a URL is known "it can take some time (up to a few weeks) before Google crawls some or all of your site", and that crawling can take "anywhere from a few days to a few weeks". The crawl capacity limit rises only while the site stays fast and healthy, so the change is gradual.

After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.

Would monitoring have caught it?

No. Nothing in this status is a change to a status code, a robots.txt rule, a noindex, a redirect or a canonical tag, which are what the monitor watches, so it would not have warned you before Google reported it. The checks above are how to investigate it.

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.