Why isn't the site on Google? Indexing diagnostics

Discovering the address is just the beginning

Google separates content retrieval, indexing, and results display. Finding a link does not mean that the address has already been indexed, and indexing does not provide visibility to the selected query.

Source: Google: how the search engine works ↗

First check the exact address: protocol, host, trailing slash and parameters. The site owner may be viewing a different version than the one reported in the sitemap. Listing these variants helps you avoid diagnosing the wrong URL.

Check the server response and content

Open the website without logging in, check the response code and the final address after redirection. An error page displayed with a status of 200 does not become a valid offer just because the server did not return a 404. Also check the X-Robots-Tag, robots, and canonical headers.

If the content only appears after JavaScript is executed, compare the HTML with the rendered view. Watch for unavailable resources, API errors, and data that requires user interaction.

Source: Google: JavaScript and SEO ↗

Confirm the status in the owner tool

In Search Console's address inspection, compare the index information with the active address test. They concern different moments. Note the reason for exclusion and the canonical address chosen by the search engine. Reading a public page by an external scanner does not replace this data.

Remove the cause and check again

After changing a rule or template, verify representative addresses, improve internal links and sitemap. Record the implementation day. There is no safe promise that indexing will occur within a certain number of hours. If the problem affects the entire group, look for a common configuration item.