Google Search Console’s URL Inspection tool shows information Google has about a specific URL and can test the page as it is available now. It is useful for diagnosing indexing questions, but a live test is not the same as an indexing decision, and requesting indexing does not guarantee inclusion in search results.
Inspect the indexed version first
Enter the exact URL, including protocol, host, and path. Review whether Google has an indexed version, the last crawl information, the declared and selected canonical when available, and any reported indexing reason. Make sure the inspected URL matches the version you intend to serve; HTTP/HTTPS and trailing-slash variants may be treated separately.
Use the live test for current problems
If the indexed report looks outdated or a page changed, run a live test to inspect what Google can fetch now. Check availability, robots access, rendered content, and detected resources. Compare the live result with the indexed result: a page can be accessible today while the stored index still reflects an earlier crawl or a different canonical choice.
- Inspect the canonical URL and the actual page URL separately when they differ.
- Check internal links, sitemap inclusion, response status, and robots or noindex directives outside the tool as needed.
- Fix the cause before requesting another crawl.
- Use URL Inspection for representative diagnosis; use aggregate reports for site-wide patterns.
Avoid common misreads
“URL is available to Google” does not mean the page will rank or remain indexed. A successful live test does not prove that the indexed version will update immediately. The tool also has request limits and does not replace a crawl audit, server log review, or analytics diagnosis.
A quick diagnostic sequence
If the indexed report says a page is excluded, check whether the exclusion matches intent: a deliberate noindex is different from an accidental block. If the live test fails, investigate the current response and rendering. If the live test passes but the indexed canonical differs, review duplicates, canonical tags, redirects, and internal links. Fix the cause first, then use the appropriate report to confirm whether Google’s stored state changes.
Record the inspected URL, date, indexed state, live-test findings, and change made. After correcting a clear technical or content issue, a single indexing request can signal that the page is ready to be recrawled. Then monitor for a change rather than repeatedly submitting the same unchanged URL.
How did this article land?
Choose one reaction. You can change it anytime.