Search Console URL Inspection Tool: A Marketer's Guide

#01What does each section show?

From Google's URL Inspection help:

#02When should marketers use it?

#03Why does rendering matter for AI search?

Content that Googlebot can't render can't be indexed, and so can't ground AI Overviews or AI Mode. Other AI crawlers often render less JavaScript than Google. See JavaScript rendering for AI crawlers.

Our view: add "inspect and request indexing" to every launch checklist for key pages. It takes a minute and catches template problems early.

#04Reading the result

#05Troubleshooting

#06A launch checklist using URL Inspection

Use this for any page that matters: pricing, product, major campaign landing pages.

1. Before launch: on staging, check there's no noindex and that the canonical points to the production URL. (URL Inspection can't test staging unless it's public and verified.)
2. On launch: inspect the live URL, run Test live URL and check View tested page shows the main content and headings in the screenshot.
3. Check the HTML tab for the title, meta description, canonical and structured data.
4. Check More info > Page resources for blocked resources that matter, such as CSS or JavaScript needed for content.
5. Request indexing once.
6. One week later: inspect again, check "URL is on Google" and the Google-selected canonical.
7. Two weeks later: check the page in the Performance report for first impressions.

#07Edge cases

• Personalised or geo-redirected pages. Google-InspectionTool usually crawls from the US. If your site redirects by location, the live test may show a different version.
• Cookie walls and consent banners. If the banner covers content in the screenshot, check the HTML still contains the content.
• Login-only pages. They can't be indexed. URL Inspection will show the login page.
• Request indexing for many URLs. The daily quota is low. For many URLs, update the sitemap and rely on normal crawling.
• "Crawled as" differences. Google mostly crawls with a smartphone user agent. Content missing on mobile templates won't be indexed even if it's on desktop.

#08Reading the canonical mismatch

When "User-declared canonical" and "Google-selected canonical" differ, compare the two pages: content, internal links, redirects and sitemap entries. Google weighs all of them. Make the signals agree, then request indexing on the page you want.

#09Questions practitioners ask

Why does the indexed result show an old title? It reflects the last crawl. Request indexing after updating, then check again later.

The live test passes but the page isn't indexed. Why? Passing means it can be indexed, not that Google will choose to. Work on quality, duplication and internal links.

Can I see how Google renders a competitor's page? No, only URLs in your verified properties. Use public tools for others.

Is the screenshot the full page? It shows the top of the rendered page; use the HTML tab to confirm content further down.

#10Troubleshooting URL Inspection results

#11A habit worth keeping

Before any launch announcement, inspect the new page live, confirm it is indexable, and request indexing. It takes two minutes and avoids announcing a page Google can't fetch.

#12Where this fits in the monthly routine

Use URL Inspection reactively: on launches, after fixes, and when the indexing check flags a key page. Record the date of each Request indexing in your annotations.

#13Quick checks before you move on

• You can tell the indexed version from the live test.
• You know which canonical Google chose for each key page.
• Launch pages were tested live before announcement.

#14Worked example: Ledgerline's canonical surprise

Ledgerline is a fictional accounts-payable software company. Details and numbers are illustrative.

Ledgerline's new pricing page wasn't appearing in Search. URL Inspection showed it indexed, but with a Google-selected canonical pointing to an older pricing URL that still existed and had more internal links. The team redirected the old URL, updated navigation links, and requested indexing. The inspection later showed the new page as canonical.

Walkthrough

1. Paste a full URL into the inspection bar at the top of Search Console.
2. Read the indexed result: whether the URL is on Google, and the Page indexing details.
3. Expand Page indexing and note the Google-selected canonical.
4. Click Test live URL to check the current version.
5. Click View tested page to see the rendered screenshot and HTML.
6. Open More info to check page resources and JavaScript messages.
7. If the page is new or changed and the live test passes, click Request indexing.

#15Try it yourself

Inspect your five most important pages. For each, record: indexed or not, Google-selected canonical (matches yours or not), last crawl date, and whether the live screenshot shows your main content.

#16Quick quiz

1. Where do you see the Google-selected canonical?

Answer: In the indexed result under Page indexing; it isn't shown in the live test.

2. What does Request indexing do?

Answer: Asks Google to crawl the URL; it doesn't guarantee indexing.

3. Which crawler performs live tests?

Answer: Google-InspectionTool.

4. Is URL Inspection good for checking thousands of URLs?

Answer: No. Use Page indexing, or the URL Inspection API within its quota.

#17What should you check before the next lesson?

• You inspected your five key pages.
• Your canonicals match Google's, or you know why not.
• Request indexing is on your launch checklist.
• Read Canonicals and duplicates in AI answers.

Next: Core Web Vitals report. Or return to the Search Console for Marketers track.

#18Common questions

How long does Request indexing take? Google doesn't give a time. It can be days. Don't request repeatedly.

Can I inspect URLs outside my property? No. You can only inspect URLs in properties you have access to.

Is there a URL Inspection API? Yes, with its own per-site and per-project quotas.