URL Inspection tool: indexed data vs live test
Read the conclusion first
URL Inspection contains two different kinds of evidence: the version Google indexed and a test of the page available now. Read their timestamps and results separately. A live test passing, or an indexing request being accepted, does not establish that the latest content is already indexed.
Applicable conditions
Applicable to new pages, changed pages, and indexing issue reviews. Requires access to the target property and use of the complete canonical URL.
Before you open the report
The full URL, indexed-status fields, last crawl time and the live-test result with its rendered page.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Inspect the exact production URL
Copy the final public address, including protocol, host, path and relevant parameters, and choose a property that covers it. Save the inspection date and the reported last crawl, indexing reason, declared canonical and Google-selected canonical.
Compare last crawl with your deployment date. If the crawl predates the repair, the indexed result may describe the old version. A different selected canonical requires checking that target's content and signals; it is not automatically an unrelated indexing failure.
Use the live test to check today's delivery
Run the live test and examine page availability, crawl permission, index permission and the rendered HTML or screenshot where available. Confirm Google received the expected article rather than a login, challenge, empty JavaScript shell or soft error. Check HTTP headers as well as HTML directives.
If it fails, retain the exact error and time, then test the corresponding server, robots, resource or rendering issue. Browser access by a signed-in administrator is insufficient to prove public delivery. A passing live test does not assess every indexing selection condition.
Request processing only after a verified change
After a meaningful repair is available and live checks pass, use the native indexing request where appropriate. Record whether the request was accepted, rejected or unavailable. Repeating an unchanged request does not provide new evidence or guarantee faster indexing.
The URL Inspection API queries indexed information; it is not a normal-article indexing submission endpoint. Keep a submitted sitemap and an accepted indexing request as separate events. Neither proves a crawl, indexing or a ranking improvement.
Close with a dated state record
A useful repair record contains the URL, original fault, deployment time, live-test outcome, last indexed crawl and request outcome. Reinspect later to see whether Google processed the changed version and selected the expected canonical.
If live access is healthy but indexing is still absent, investigate duplication, page value and discovery signals. If the report simply remains older than the deployment, retain the pending state. Do not change URLs merely to make a stale report appear new.
Common mistake: Call API check success submission success
Querying and requesting indexing are different actions, and a returned status is not proof of ranking.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| Indexed version is old, live is normal | Record crawl time and observe updates | Live passing does not mean updated |
| Live test returns 404 | Fix the canonical URL or correctly remove it | Verify again with a real response |
| Request accepted but not indexed | Continue checking selection conditions | Do not repeatedly request unmodified pages |
A fixed page and an old indexed version can coexist
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: yesterday’s indexed result records noindex. You removed it today; the live test now says indexing is allowed.
- What it establishes
- The two results describe different versions. Live success confirms the tested version’s conditions, not that Google has replaced its stored version.
- What to do next
- Confirm HTML and response headers both permit indexing. Preserve the deployment time and live result, request indexing where appropriate after a real change, then recheck the stored crawl date later.
What counts as a checked result
Keep four separate states: deployed, live test, request receipt and indexed version. If Google selects another canonical, inspect that URL before calling the repair complete.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A dated record of indexed version, live delivery and any separately received indexing request.
- Stop and resolve this first
- Do not say the latest edit is indexed when Google’s last crawl predates it.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Why is it still not indexed after a successful live test?
It does not evaluate all indexing selection conditions; Google still decides whether and when to index.
Can the live test tell me Google’s final canonical?
No. Read the Google-selected canonical in the indexed result. The live test does not predict that choice.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Save the inspected index version with a dated task in AISEO Site. Google's live test and a request for indexing still take place in Search Console.
See how it works →