Find out why a page is not indexed

Start with the exact URL

First decide whether this page should appear in search. A public service page may need indexing; an account page, temporary preview or duplicate address may correctly be excluded. Do not remove a deliberate restriction just to improve an audit score.

In a verified Google Search Console property, inspect the complete URL. Record the reported indexing reason, last crawl date and Google-selected canonical when available. The indexed result describes Google’s stored information; the live test checks the current page and cannot predict which canonical Google will choose. See Google’s URL Inspection instructions.

AEO test checks signals in fetched responses. It does not read your Search Console account or prove that a URL is indexed. An unavailable check means there was not enough evidence, not that Google rejected the page. Keep the report’s requested and analyzed URLs with your notes so you do not compare different addresses by accident.

Check whether the crawler can reach the page

Open the published URL without signing in. If it redirects, confirm that the destination is the page you intended. Ask your website manager to investigate an error response, login screen or bot challenge before changing the page’s content. A successful browser visit alone does not establish that a crawler can fetch it.

A robots.txt rule controls crawling for crawlers that follow it. It does not reliably keep a URL out of Google’s index, and it does not protect private information. If the page should be public and searchable, review the rule for that specific path and crawler. If the information is private, use actual access controls. Read Google’s explanation of robots.txt limits and our crawler troubleshooting guide.

Check noindex instructions in both places

A noindex instruction can be in the page’s HTML or an X-Robots-Tag response header. Ask your website manager to inspect both, including crawler-specific instructions. Removing a setting in your page editor will not fix a separate header added by your hosting configuration.

For a page you want indexed, remove only unintended exclusions. For a page you want excluded, remember that Google must be able to crawl it to read noindex. Blocking it in robots.txt can prevent that. Noindex also does not stop people with the address from opening a public page. See Google’s noindex guidance.

Check which URL should represent the content

A canonical declaration identifies a preferred version of duplicate or very similar content. It is a signal, not a guarantee that Google will select that URL. An alternate address being excluded can be the intended outcome when the preferred page represents the same content.

Compare the page’s declared canonical with the preferred address you actually want. Open that destination and inspect it separately in Search Console. Ask your manager to resolve conflicting declarations, redirects or sitemap entries. Do not point unrelated pages at the homepage to make a warning disappear. Follow Google’s canonical URL guidance.

Make the intended page discoverable

Give readers a useful link to the page from a relevant part of your site. If you use a sitemap, check that the published file opens and lists the intended preferred URL. Use Search Console to check whether Google could retrieve the submitted sitemap; a URL written in a file is not evidence that a search engine has processed it.

A sitemap helps with discovery but does not guarantee crawling or indexing. It does not override robots.txt or noindex instructions. A small, well-linked site may be discovered without one. See Google’s sitemap overview. AEO test inspects a bounded sitemap response, not every listed page or the search engine’s sitemap-processing history.

Verify the published change, then allow time

After a fix is published, check the exact URL again. Use Search Console’s live test to inspect the current response and rendered content. A successful live test is not confirmation that the page is indexed. Compare its result with the stored indexing information and crawl date. The URL Inspection documentation explains what each view can establish.

If appropriate, request indexing for a page you manage. Repeated requests do not speed up crawling. Google says crawling can take days to weeks, and a request does not guarantee inclusion. Monitor the result instead of treating a waiting period as proof that your fix failed. Read Google’s recrawl guidance.

What to send your website manager

• The exact URL and whether you want it to appear in search.
• The indexing reason and crawl date shown in Search Console.
• The intended preferred URL and any unexpected redirect.
• The AEO test finding, its evidence and the scan date.
• What changed, when it was published and the live-test result.

This gives the person investigating a specific question to answer. After a change, you can run a fresh page check or compare saved reports. A higher readiness score alone does not prove an indexing or ranking improvement.