Google URL Inspection Live Test: how to read it and troubleshoot indexing

Google Search Console URL Inspection has two important views: information about Google’s indexed version and a Live Test of the current URL. They can disagree, and that disagreement is often the fastest clue to an indexing problem.

What the Live Test actually tells you

The Live Test fetches the current URL with Google’s inspection system and evaluates whether the page appears accessible and potentially indexable. It does not prove that the URL is currently in Google’s index and it does not guarantee future inclusion.

Step-by-step: run a Live Test

1. Open the correct Search Console property.
2. Inspect the complete URL you want to diagnose.
3. Review the indexed information first so you have a baseline.
4. Select Test Live URL.
5. Open the availability/indexability details.
6. Review the tested page, response information, rendered screenshot, and resources when available.
7. Compare the Live Test with the indexed information.

Live Test vs indexed result

Indexed result says there is a problem, Live Test is clean

This often means you fixed the page after Google’s last stored crawl. Verify the deployed fix, then request indexing if appropriate and wait for Google to revisit the URL.

Live Test fails, indexed result was previously clean

The current page may have developed a new fetch, robots, rendering, server, or access problem. Fix the live problem before requesting another crawl.

Both are accessible, but the page still is not indexed

Move beyond basic access. Review canonical selection, duplicate content, usefulness, internal discovery, and whether the page provides enough value to remain indexed.

What to inspect in the tested page

• Final HTTP response and fetch status.
• Whether crawling is allowed.
• Rendered title, H1, main body, and important links.
• Canonical and robots directives.
• Loaded resources and JavaScript errors when shown.
• The screenshot, especially for client-rendered applications.

A simple troubleshooting decision tree

1. Live Test cannot fetch → fix server/access/redirect issues.
2. Crawl blocked → fix robots/WAF rules if indexing is intended.
3. noindex present → remove it if the page should be searchable.
4. Canonical points elsewhere → reconcile duplicate/canonical signals.
5. Rendered content is missing → fix SSR/rendering/hydration.
6. Everything is technically valid → review quality, intent, discovery, and authority.

Request indexing only after the URL is healthy

Request Indexing is useful after a new page is published or a meaningful issue is fixed. It is not a repair mechanism. Submission, crawling, indexing, and ranking are separate states, and Google makes the final indexing decision.

For larger URL sets, use a bulk status workflow to find the URLs that need individual Search Console diagnosis instead of manually inspecting every URL first.