Google Search Indexing Checklist: Inspect, Diagnose and Retest a URL

1. Record the exact URL and distinguish the two inspection results

Open URL Inspection and enter the complete public address, including HTTPS, hostname and path. Record the inspection date, last crawl, reported exclusion and Google-selected canonical. The indexed result describes the version Google previously processed. The live test checks the version available now. If a server error was recorded last week but the live fetch succeeds today, those results describe different moments; they are not contradictory. Inspect the final article URL rather than a login page or a tracking-link variant.

2. Check the response, indexing directives and canonical signals

Check the HTTP response and any redirects before editing the article. A valid public article should return its content at the preferred URL. Read both the HTML robots meta tag and the X-Robots-Tag response header for noindex. Also inspect robots.txt: blocking a crawler there can prevent it from reading a noindex directive. Preserve deliberate exclusions for private account and administration pages. Then compare the page canonical, sitemap entry and internal links. Use a consistent preferred URL for duplicate versions. For translated articles, inspect the English and Chinese addresses separately; a live test cannot tell you which canonical Google will ultimately select.

3. Match the repair to the evidence and inspect the article

Choose a specific change from the inspection evidence. An accidental noindex on a public article calls for correcting that directive. A redirect chain calls for checking the final target and links. A soft 404 calls for inspecting the actual page that Google receives, even when the server returns 200. Open the rendered HTML and screenshot: look for the article heading, useful main text and working resources. Confirm that the page is a complete guide or article rather than an empty shell, an access prompt or an error message. Keep a copy of the prior result and the deployed revision so that a later comparison refers to a known change.

4. Retest the same URL and record what actually changed

After publishing, run the live test on the same article address and open its rendered view again. Compare the fetch, indexing permission and main content with your earlier record. If the relevant problem has been repaired, you can request indexing through URL Inspection. Record the request separately from the outcome: submitting a request does not establish that the article is indexed. Revisit the indexed result after Google processes the page and compare its last crawl and selected canonical.

For example, suppose the recorded result reports an accidental noindex and the current live result allows indexing after that directive is removed. The verified change is that the live page is eligible for processing. The recorded exclusion may still describe the older crawl. If the live result instead continues to report soft 404, inspect the returned article and its rendering before submitting again. Treat this as a diagnostic example, not a claim about a completed test on your site. Search results and site: queries can help with spot checks, but they are not a complete index inventory. Technical eligibility and sitemap inclusion do not guarantee indexing.