URL Inspection: checking what Google knows about a page
URL Inspection is a Google Search Console tool for investigating what Google knows about a specific web address. It can show information from earlier processing and run a live test of current access. A successful live test does not mean the page is already indexed or guaranteed to appear in search.
Also known as: Search Console URL Inspection
At a glance
- Stored indexing information and live tests refer to different times and questions.
- Requesting indexing asks for processing; it does not guarantee inclusion.
- Google’s selected canonical can be examined in stored indexing information.
On this page

Start with one exact URL
When an important page does not appear as expected, URL Inspection narrows the investigation to that address. It does not grade the entire website.
Use the appropriate Google Search Console property and complete URL. Another hostname, protocol or path may identify a different page. Google documents stored indexing information and live testing as separate functions. URL Inspection documentation
Stored information versus a live test
The stored report describes a version Google processed earlier. A live test investigates what can be accessed now. Yesterday’s data can still show a fault corrected this morning.
Indexing does not happen simply because the owner runs a successful test. Live access evidence does not include every quality, safety or selection decision. Compare the change date with the processing date, especially after changing redirects, robots rules or noindex.
Details worth examining
Depending on the state, inspect access, fetch results, indexing directives and canonical information. Rendered content, resources or a screenshot may explain why essential text did not arrive.
The declared canonical URL and Google’s selection can differ. A live test cannot reliably predict a later canonical decision. Canonicalization guidance
The HTTP status code is another clue. A working page, error response and redirect are different explanations for “not appearing.” Response-code guidance
Example: an updated dental information page
Imagine a clinic publishing an explanatory article about a cleaning appointment. Three days later, its maintainer investigates why the page is absent from search.
Stored information shows noindex, which a developer removed the previous day. A live test now sees the complete article, a successful response and no exclusion directive. The supported conclusion is that the current technical state differs from the earlier observation.
The maintainer can request processing and check the stored information later. Removing the obstacle does not prove an immediate ranking or new patient enquiry.
What requesting indexing does
It asks Google to process the address again. It is not purchased priority, compulsory inclusion or a precise deadline. Repeated submission cannot replace fixing a problem.
For many new pages, normal internal navigation and an XML sitemap support discovery. The individual tool is particularly useful for diagnosis of important URLs, not an endless manual submission workflow.
Record a narrow, accurate conclusion
Save the URL, test time, stored observation date and substantive finding. “The live test sees complete content while stored data predates the fix” is more informative than “SEO works.”
One successful test does not establish the state of every URL, every visitor’s experience or future business results.