“Discovered” vs “Crawled” in Google Search Console

These statuses describe different stages. “Discovered – currently not indexed” means Google knows the URL but has not crawled it yet; Google’s report says its last crawl date is empty. “Crawled – currently not indexed” means Google crawled the page but did not index it at that time. Start with the exact status and the indexed-view crawl date, then follow the matching checks below. Neither status alone tells you the cause or guarantees a future indexing result.

What is the difference between the two statuses?

These are report labels, not a diagnosis of a site-wide crawl budget, a content defect, or a migration problem. Google’s definition of “Discovered” mentions rescheduling to avoid overloading a site, but the status does not establish that a particular site is overloaded. “Crawled” confirms a crawl occurred; it does not disclose every reason a URL was not indexed.

What should I check for “Discovered – currently not indexed”?

1. Confirm the URL and property. Copy the exact affected URL from the Page indexing report and open URL Inspection in the matching Search Console property. Keep URL variants such as host, protocol, path, and redirects distinct while checking.
2. Read the indexed data first. Record the verdict and last crawl date if shown. An empty last crawl date is consistent with Google’s definition of this status; it is not proof that the URL is unreachable now.
3. Check the current page separately. Run a live URL test and note its time, fetch result, and crawl permission. A passing live test describes current test access; it does not mean Google has crawled or indexed the URL.
4. Check how Google can find it. Google says a page needs to be linked from a known page or included in a sitemap to be found. Confirm that the intended canonical URL is in the sitemap, linked from relevant live pages, and not accidentally isolated. This is a discoverability check, not a promise that crawling will happen immediately.
5. Recheck with dates. Keep the original status and timestamp, then inspect again later. Do not infer a cause from one empty crawl date or repeated checks close together.

What should I check for “Crawled – currently not indexed”?

1. Use the report’s latest crawl information. Inspect the exact URL’s indexed data and note the last crawl date. Compare it with the page’s publish or substantive-update date to see whether Google crawled the version you meant to review.
2. Inspect the current page and its intended URL. Check that the page returns the expected content to visitors, that internal links and sitemap entries point to the preferred URL, and that redirects, robots directives, and canonical declarations match your intent. A live test can help check current access; it cannot replace the indexed record.
3. Review the page’s purpose and distinct information. If technical checks look intentional, compare the page with other pages on your site and its cited sources. Ask whether it answers a distinct reader task and adds verifiable information. This is an editorial review prompt, not a claim that thin or duplicate content caused this specific status.
4. Make a meaningful change only when you found one. Record what changed and when. Google says the status may change in the future; repeated sitemap submissions or crawl requests do not reveal the reason for this current status. Avoid treating a request as a guarantee of indexing.

Does a status change prove the cause?

No. A November 2026 Search Central Community discussion describes one site that saw “Crawled – currently not indexed” after moving content to a subdomain. The thread records the site owner’s report and replies, but it does not establish a general migration rule or verify the cause for other sites. Use the report definition and the evidence for your own exact URL; do not generalize a single discussion.

When the status changes, save the date, exact URL, status label, indexed crawl date, and any relevant page or canonical change. Compare observations over time without treating them as a causal experiment. The local fixed-sample indexing log can record repeated URL observations and compare URLs present at both boundary dates. It does not connect to Search Console or explain why a label changed.

For a disagreement between a passing live test and indexed data, see the separate guide to URL Inspection’s live test and indexed version. For sitemap-file retrieval errors, use the sitemap “Couldn’t fetch” diagnostic; that report status is about retrieving the sitemap file, not whether every listed page is indexed.

Method and limits: This decision guide follows Google’s current Page indexing report definitions and discovery guidance, checked November 3, 2026. The community discussion is one qualitative migration report, not evidence of prevalence or a general cause. This guide does not access Search Console, inspect any site, or promise indexing.