# Search Console URL Inspection Tool: A Marketer's Guide

> How to use Search Console URL Inspection: indexed vs live test, Google-selected canonical, rendered page, and when to request indexing.

Source: https://mentionx.ai/learn/search-console/search-console-url-inspection  
Author: Dipuck Jones, founder of MentionX  
Updated: 4 November 2026  
Level: Practitioner

**URL Inspection tells you what Google knows about one URL: whether it's indexed, which canonical Google chose, when it was last crawled and how the page renders for Google today.** It's the tool to use before and after you publish anything important.

*Checked 4 November 2026 (CET) against Search Console Help and Google Search Central documentation. Search Console reports and rollouts change often, and some features only appear for eligible properties, so confirm in your own property. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

> **Key takeaways**
>
> - The indexed result shows Google's last known version; the live test checks the page now.
> - The Google-selected canonical is shown only in indexed data.
> - View tested page shows the rendered screenshot and HTML, from Google-InspectionTool.
> - Request indexing asks for a crawl but doesn't guarantee indexing, and has a daily quota.
> - Use it for single URLs; use reports and the API for scale.

## What does each section show?

From Google's [URL Inspection help](https://support.google.com/webmasters/answer/9012289):

| Section | Shows |
|---|---|
| Presence on Google | Whether the URL is on Google |
| Page indexing | Discovery (sitemaps, referring page), crawl (last crawl, crawler, allowed), indexing (user-declared and Google-selected canonical) |
| Enhancements | Structured data and other features detected |
| Test live URL | Whether the current version could be indexed |
| View crawled / tested page | HTML, screenshot (live test), and **More info**: page resources, JavaScript console messages, HTTP response |

## When should marketers use it?

| Moment | Why |
|---|---|
| Launching a key page | Live test, then Request indexing |
| After a page update | Request indexing so changes are picked up sooner |
| A page disappeared from results | Check indexed status and canonical |
| A redesign or JavaScript change | Check the rendered screenshot shows your content |
| Duplicates suspected | Compare your canonical with Google's |

## Why 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](https://mentionx.ai/learn/technical/javascript-rendering-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.

> **Pro move:** when Google picks a different canonical, check which page it chose. It often reveals a duplicate you didn't know existed, like a print version or a tracking-parameter URL linked internally.

## Reading the result

| Result | Meaning | What to do |
|---|---|---|
| URL is on Google | Indexed and eligible to appear | Check enhancements if relevant |
| URL is on Google, but has issues | Indexed, with enhancement problems | Fix the listed issues |
| URL is not on Google | Not indexed; reason shown | Read Page indexing section |
| URL is not on Google: not in index (but not an error) | E.g. alternate or duplicate | Check the Google-selected canonical |
| Live test: URL is available to Google | Could be indexed if submitted | Request indexing if needed |
| Live test fails | Crawl or render problem now | Fix before requesting indexing |

## Troubleshooting

| Problem | Cause | Fix |
|---|---|---|
| Google-selected canonical is another URL | Duplicate content or conflicting signals | Strengthen canonical signals: tags, internal links, sitemap |
| Rendered screenshot is blank | JavaScript fails for Google-InspectionTool | Review JavaScript rendering; check resources blocked by robots.txt |
| Request indexing quota reached | Daily limit | Prioritise; rely on sitemaps for bulk |
| Indexed result differs from live test | Indexed data is from the last crawl | Expected after changes; request indexing |
| "URL is unknown to Google" | Never discovered | Add internal links and include it in a sitemap |

## A 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.

## Edge 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.

## Reading 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.

## Questions 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.

## Troubleshooting URL Inspection results

| Result | What it usually means | Next step |
|---|---|---|
| URL is not on Google, Discovered | Google knows it but hasn't crawled | Add internal links, check sitemap |
| Excluded by noindex | A noindex tag or header | Remove it if the page should rank, then test live |
| Blocked by robots.txt | A disallow rule matches | Fix the rule; test live |
| Google chose different canonical | Duplicate or near-duplicate page | Consolidate, or make the content distinct |
| Page fetch failed | Server error, timeout or redirect issue | Check server logs and the live test |

## A 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.

## Where 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.

## Quick 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.

## Worked 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**.

## Try 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.

## Quick 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.

## What 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](https://mentionx.ai/learn/technical/canonicals-duplicates-ai-answers).

Next: [Core Web Vitals report](https://mentionx.ai/learn/search-console/search-console-core-web-vitals). Or return to the [Search Console for Marketers track](https://mentionx.ai/learn/search-console/search-console-for-marketers).

## Common 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.

## Sources

- Search Console Help, [URL Inspection tool](https://support.google.com/webmasters/answer/9012289)
- Google for Developers, [Google's common crawlers](https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers)
- Google for Developers, [Search Console API: Usage limits](https://developers.google.com/webmaster-tools/limits)
- All accessed 4 Nov 2026.

## Frequently asked 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.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/search-console/search-console-url-inspection