AAA Signal07 2802 5222Customer login
AAA SIGNAL GUIDES · 4 minute read

Discovered – currently not indexed: what to check next

Understand why a discovered page may not yet be indexed, which checks matter, and when to request indexing in Google Search Console.

Last updated 15 October 2026

What this Google status means

Google knows about the URL, but its stored report does not yet show the page as crawled and indexed. This is different from “Crawled – currently not indexed”, where Google reports having crawled the page. Discovery alone does not guarantee that a page will enter search results.

The status does not identify a single cause. A new page may be waiting for a crawl, but weak internal linking, server problems or a website with many similar URLs can also deserve investigation. Do not conclude that Google has penalised the website from this label alone.

Start with the page a customer should actually find

Open the exact URL without signing in. It should contain useful public information and return the response you intend. A service page should explain the service, where it is offered and how someone can take the next step. A contact page should provide real contact options, rather than a near-empty template.

If the URL redirects, review the destination. If it duplicates another page or is deliberately private, exclusion may be correct. There is no benefit in requesting indexing for every URL just to make a report greener.

Check discovery, access and canonical signals

Use these checks before requesting another crawl. A sitemap can help Google discover a URL, but it does not override access restrictions or guarantee indexing.

  1. Link to the page from a relevant public page, using a descriptive link. Important service pages should be reachable through normal website navigation.
  2. Keep the intended canonical URL in a working sitemap. Avoid listing redirects, private pages and URLs you deliberately exclude.
  3. Check robots.txt access, HTTP responses, meta robots and X-Robots-Tag headers. A robots.txt block and a noindex instruction have different effects; Google generally needs crawl access to see a page-level noindex.
  4. Check the canonical link and Google’s selected canonical, when reported. A canonical is a preference signal, not an instruction Google must follow.
  5. Review distinct value. If several location or service pages say almost the same thing, improve their usefulness before treating indexing requests as the fix.

Use Test live URL, then request indexing when appropriate

In Search Console, inspect the exact URL under a property you control and use Test live URL. A successful live test can show that Google can access the current page, but it does not promise that Google will index it or select it as canonical.

If the page is useful, accessible and intended for search, use Request indexing when available. Repeated requests do not guarantee faster processing. Keep the underlying issue fixed and check the stored report again later; there is no reliable fixed waiting time for every website.

Keep stored information separate from live checks

Google’s stored inspection result can lag behind a recent website change. Record the last crawl date when one is available, and compare it with when you changed the page. A normal browser opening the page does not prove Googlebot received the same response.

AAA Signal can organise stored inspections for discovered sitemap URLs and compare them with live HTML checks. The live HTML check is not a Googlebot live test and does not render every JavaScript application. Individual indexing requests remain in Search Console.

Keep your indexing checks organised

AAA Signal brings sitemap discovery, saved page checks and practical review steps into one dashboard. Google decides which pages it crawls and indexes.

Explore website monitoring · View pricing from A$19/month

Keep reading

Google’s Page indexing report documentation · Google Analytics reporting documentation

CallEmail