Using Search Console's URL Inspection tool after a change
Short answer: Open the URL Inspection tool in Search Console, paste the full address of the page you changed, and read the indexed result first: it shows what Google last stored, not what's live. Then click "Test live URL" to check the current page can be fetched and indexed, look at the screenshot and HTML to confirm Google sees your new content, and use "Request indexing" once if the page is important. It can't tell you about rankings, and asking repeatedly won't speed anything up.
You've rewritten your services page, fixed a broken template or launched a new product page. The natural next question is whether Google has noticed. URL Inspection answers that for one page at a time, but its two views (the indexed result and the live test) mean different things, and misreading them is the most common reason people think something is wrong when it isn't.
Before you start
- You need access to the Search Console property that contains the page. Google's documentation says the URL must be in the currently opened property, and to request indexing you must be an owner or full user.
- Use the complete URL exactly as it appears in the browser, including
https://and any trailing slash. - The live test needs the page to be publicly reachable without a login.
Step 1: Open the tool
There are two ways in, per Google's help page (as of November 2026): type the URL into the inspection bar at the top of any Search Console screen, or click the Inspect link next to a URL in most reports (you may need to hover to see it).
Step 2: Read the indexed result
The first screen you see is not a live test. Google's help page is explicit that it shows the most recently indexed version of the page. If you changed the page this morning, this screen probably still describes the old one.
At the top is the overall status:
- URL is on Google: the page is eligible to appear in search results. Google stresses it's not a guarantee; for a definitive check, search for the URL on Google.
- URL is on Google, but has issues: indexed, but something such as structured data has problems that might stop enhancements showing.
- URL is not on Google: the page can't currently appear in results. The reason is usually in the details below.
Expand Page indexing to see:
- Discovery: how Google found the URL (sitemaps, referring pages).
- Crawl: whether and when Google crawled it, and any obstacles.
- Indexing: including the Google-selected canonical, the URL Google treats as the main version.
The canonical check
This is one of the most useful fields in the tool. If you have similar pages (filtered category URLs, a page reachable with and without a trailing slash, old and new versions), the Google-selected canonical tells you which one Google picked. Google notes you can see the canonical only in the indexed data; the live test can't predict whether the tested version will be chosen.
Step 3: Run the live test
Click Test live URL. Google fetches the page in real time and reports whether it might be indexable now. Use this after you've fixed something, to see whether Google thinks the problem is gone.
Then open View tested page:
- Screenshot: Google's help says a screenshot of the rendered page is available only in a live test. Check that your new content actually appears, not a cookie banner, a blank area or an error.
- HTML: search the rendered HTML for a sentence you've just added. If it's missing, content may depend on JavaScript that didn't run, or a cache may be serving the old page.
- More info: page resources that couldn't load, JavaScript console messages and the HTTP response.
You can switch between Google Index and Live Test views at the top.
What the live test doesn't check
Google's documentation lists several things outside the live test: whether the URL is in your sitemaps or linked from other pages, every possible indexing issue (including whether it's a duplicate), quality and security guidelines, manual actions, removals and temporarily blocked URLs. A clean live test means "fetchable and indexable in principle", nothing more.
Step 4: Request indexing (once)
If the live test looks right and the page matters, click Request indexing. Google says the page gets a quick check for immediate indexing errors and, if it passes, joins the indexing queue. You can't request indexing for a page the live test considers non-indexable.
Three things to know:
- There's a quota. Google mentions a daily limit of inspections per property, and its recrawl guide says there's a quota for individual URL submissions.
- Repeating doesn't help. The same guide says requesting a recrawl multiple times for the same URL won't get it crawled any faster.
- It takes time and isn't guaranteed. Crawling can take from a few days to a few weeks, and a request doesn't guarantee inclusion in results.
For many changed pages at once, Google points to a sitemap with updated lastmod dates instead.
What you see → what it means
| What you see | What it means | What to do |
|---|---|---|
| Indexed result shows old content or old date | Google hasn't recrawled since your change | Run the live test; request indexing if important |
| "URL is on Google" but you can't find it in results | Eligible, not guaranteed; the tool doesn't check everything | Search for the exact URL; check Manual actions and Security issues reports |
| Google-selected canonical is a different URL | Google treats another page as the main version | Check your canonical tags, internal links and redirects point to the URL you prefer |
| Live test: page not indexable, with a "noindex" reason | Your page tells Google not to index it | Remove the noindex directive if the page should appear |
| Live test screenshot shows a blank or error page | Rendering problem, blocked resources or server error | Open More info for failed resources and the HTTP response |
| Live test OK, indexed result says not on Google | You've fixed the issue, but Google hasn't recrawled | Request indexing once and check back in a week or two |
| "Request indexing" greyed out or refused | Quota reached, page non-indexable, or you lack full permissions | Wait a day, fix the live test errors, or ask the owner for access |
When to use it
- After launching a page you want found quickly, such as a new service or seasonal offer.
- After fixing an error Search Console reported, to confirm the fix.
- After a template change that affects many pages: inspect two or three examples rather than every URL, and rely on your sitemap for the rest.
- When a page disappears from results, to see whether Google still has it indexed and which canonical it chose.
What it can't do
It doesn't show rankings, traffic or keywords (use the Performance report), it doesn't make a page rank higher, and it doesn't check content quality. It answers one question well: can Google fetch, render and index this exact URL, and what did it store last time?
FAQ
How long after requesting indexing will my change show in Google?
Google says crawling can take from a few days to a few weeks. Check the indexed result again after a week.
Why does the live test pass but the page still isn't indexed?
The live test doesn't check everything, including duplicates and quality. If Google selected a different canonical, your page may be treated as a duplicate.
Can I inspect a competitor's page?
No. The URL must be in a property you have access to. Google suggests public tools such as the Rich Results Test for pages you don't own.
Should I request indexing for every page after a redesign?
No. Submit or update your sitemap and inspect a handful of key pages to confirm they render correctly.
Checking a launch page by page is tedious, and we can run that post-launch check for you and tell you what Google actually sees.