Discovery & crawling

Discovered — currently not indexed

Google knows this URL exists, but has not crawled it yet. Focus on discovery, crawl demand, and reliable access before diagnosing the page’s content as an indexing failure.

Troubleshooting guide · Public signals and practical next steps

What this means

The URL has been discovered but not yet crawled, according to this Search Console report. There may be no last crawl date to investigate.

When it’s normal—and when to investigate

Often expected

New URLs can wait before their first crawl. A recently submitted sitemap does not create an immediate crawl schedule.

Worth investigating

Pay attention when core pages remain untouched, an entire new section is affected, or a site produces far more parameter URLs than useful pages.

Work through these checks

  1. Confirm the exact preferred URL

    Check HTTPS, hostname, path spelling, and trailing slash behavior. Your sitemap and internal links should point to the final version, rather than sending crawlers through redirects.

  2. Find an ordinary link to the page

    Navigate from the homepage or a relevant indexed page. A URL accessible only through a search form or a button that runs JavaScript may have weak discovery paths.

  3. Review the sitemap and server response

    Confirm that the sitemap opens as XML and lists useful canonical URLs. Check the page for intermittent 5xx responses or rate limits. One successful test does not prove continuous uptime.

  4. Look for unnecessary URL growth

    Review filters, calendars, internal search, and session parameters. If these create effectively endless combinations, address the generator instead of submitting larger sitemaps.

FREE URL DIAGNOSTICOne page. Public signals.

Use a public HTTP or HTTPS URL. No login needed. Don’t submit private links or URLs containing access tokens.

HTTP & redirectsCrawl & index controlsCanonical & content

Common causes

  • A new page has not been prioritized for crawling.
  • Important pages are isolated from normal internal navigation.
  • A sitemap contains redirects, removed URLs, or excessive variants.
  • Unstable hosting or a large volume of low-value URLs complicates crawling.

Possible fixes

  • Add useful HTML links from relevant pages, using the final URL.
  • Keep sitemaps focused on the canonical pages you want discovered.
  • Repair server availability problems and unnecessary URL generation.
  • Use URL Inspection for an important URL after confirming it is ready, then allow time for another observation.

Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.

What this tool can and cannot verify

It can

Inspect current access, redirect destinations, robots rules, and a small sample of sitemap locations.

It cannot

Read Google’s crawl queue, measure crawl demand, inspect sitewide link paths, or predict the first crawl date.

Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.

A useful follow-up

Should I resubmit the same sitemap every day?

No. Keep it accurate and accessible. Repeated submission does not force Google to crawl each listed URL.

Official reference: Google: Troubleshoot crawling errors. See also the Page indexing report documentation.