Search Console field guide · updated October 19, 2026
Discovered vs crawled: why pages are not indexed
A URL can appear in a sitemap, return HTTP 200 and still be missing from Google Search. The Page indexing report tells you which stage needs investigation; it cannot guarantee inclusion in results.
Identify the precise indexing status
Discovered – currently not indexed: Google knows the URL exists but has not crawled it yet, according to its report. Check whether the page is linked from relevant public pages, listed in an accurate sitemap and accessible to Googlebot. Newly published or lower-priority URLs can take time to be fetched.
Crawled – currently not indexed: Google has fetched the URL but has not selected it for indexing at the time of the report. This does not prove a technical defect. Review originality, usefulness, duplication, canonical signals and whether the page answers a distinct search need.
Other reasons: HTTP errors, redirects, noindex, robots restrictions or a different Google-selected canonical need separate investigation. An intentionally redirected URL or canonical alternate is not necessarily a problem.
A five-step diagnostic checklist
- Inspect the exact URL. Open Search Console → URL Inspection for the intended HTTPS URL. Compare Google's previously indexed view with the live test; they answer different questions.
- Check fetch access. Confirm reliable HTTP responses, useful HTML, and the absence of accidental
noindexor robots blocks. A sitemap entry cannot override access restrictions. - Check canonical consistency. Review canonical tags, redirects and internal links. Link to the preferred URL, not a mixture of HTTP/HTTPS, www/non-www and parameterized variants.
- Improve the purpose. What does the page uniquely help a visitor do? Substantial original instructions, tools or answers are more useful than duplicate, empty or mass-generated pages.
- Improve discovery. Link from a relevant guide or directory and list the preferred canonical URL in a current XML sitemap. Recheck after Google has had time to process changes.
What a sitemap does not fix
A sitemap helps Google discover important preferred URLs, but it does not force crawling, indexing or higher rankings. Include canonical public pages and truthful lastmod dates when used. The free XML sitemap validator checks pasted XML syntax and URL entries locally, but cannot confirm that URLs resolve or appear in Google.
If Search Console reports a server error or block, fix that first. If a page is accessible but not selected for indexing, improving its substance and internal context is more meaningful than repeatedly submitting the same sitemap.
Verify progress without guessing
Record the URL, inspection date, Google's reported status, canonical choice and any site changes. Revisit URL Inspection and the Page indexing report after Google has time to reprocess it. The report is not live, and a successful live test cannot guarantee indexing. Once pages appear in search, review real query impressions and clicks for relevant searches.
For specific statuses, see Excluded by noindex tag, Google chose a different canonical and soft 404 errors. You can also check canonical tags in pasted HTML.
Next, review query and page opportunities, try the Searchlight sample report, or return to all guides.
Official documentation
Google Page indexing report · URL Inspection tool · Troubleshoot crawling problems · Indexing FAQ.