The URL Inspection tool in Google Search Console shows what Google knows about one page on your site: whether it’s indexed, how Google found it, when it was last crawled, and which URL Google treats as the main copy. You open it by pasting a full URL into the search bar at the top of Search Console, and you can then run a live test or ask Google to index the page.
The tool is simple to start and easy to misread. The result you see first is Google’s stored copy from the last crawl, not your page as it is now, and a green “URL is on Google” doesn’t mean the page ranks for anything. This guide walks through running an inspection, then explains each field so you know which ones matter. Field names and rules come from Google’s URL Inspection help page, checked in November 2026.
Before you start
You need three things in place, or the tool will refuse the URL or hide the button you want.
- A verified property that contains the URL. The tool only inspects URLs inside the property you have open. If your property is
https://www.example.com/(URL prefix) and you pastehttps://example.com/page/, it won’t work. A Domain property covers every version. For pages on a site you don’t own, Google points you to public tools such as the Rich Results Test instead. - The full URL. Include
https://and the exact path, with or without the trailing slash as your site uses it. A page and its slash version can be two different URLs to Google. - Owner or full user access if you want to request indexing. Google’s recrawl guide says only owners and full users can do it. A restricted user can still inspect. If you need to upgrade someone, see how to add a user to Google Search Console.
How to inspect a URL, step by step
- Open the right property in Search Console, using the property picker at the top left.
- Paste the full URL into the search bar at the top of any screen (“Inspect any URL in…”) and press Enter. You can also click the inspect icon that appears when you hover over a URL in most reports, such as Page indexing or Performance.
- Read the top status. This is Google’s verdict from the last time it crawled and indexed the page.
- Open the Page indexing section to see why, field by field (discovery, crawl, indexing allowed, canonical).
- Click Test live URL if you’ve changed the page since the last crawl, or if you want to check that Googlebot can fetch it right now.
- Click View tested page after the live test to see the HTML Google rendered, a screenshot and any blocked resources under More info.
- Click Request indexing only once the live test passes and the page is ready. Do it once per URL.
Step 5 is the one people skip. If you fixed a noindex tag yesterday and inspect the page today, the main result can still say “Indexing allowed? No” because it describes the old crawl. The live test is what tells you whether the fix works.
What the top status means
Google uses four headline statuses for the indexed result:
- URL is on Google. The page is indexed and can appear in Search, with no problems found in its enhancements (structured data and similar).
- URL is on Google, but has issues. Indexed, but something such as a structured data error may stop it getting rich features. The page can still show as a normal result.
- URL is not on Google. The page can’t appear in Search. The Page indexing section tells you why.
- URL is an alternate version. An AMP page that points to a normal page as its main copy. Most small business sites won’t see this.
Google is clear that “URL is on Google” means eligible, not guaranteed. A page can be indexed and still get no impressions because it doesn’t rank for anything people search. That’s a content and relevance question, not an indexing one, and the tool won’t help with it.
What each field in Page indexing means
Open the Page indexing section and you get a block of fields. Here’s what each one tells you and when to care.
- Indexing status. “The page is indexed”, “The page is not indexed” with a reason, or “URL is unknown to Google”, which means Google has never seen the address.
- Discovery: Sitemaps. Which of your sitemaps list the URL. “No referring sitemap” on a page you want found is worth fixing. If your sitemap itself errors, see sitemap couldn’t fetch.
- Discovery: Referring page. A page that may have led Google here. Google says a blank value doesn’t prove no page links to it, but a new page with no internal links is a common reason it sits undiscovered.
- Last crawl. When Googlebot last fetched the page, in your local time. Everything else in the indexed result comes from this crawl, so check the date before trusting any other field.
- Crawled as. Desktop or smartphone crawler. For most sites this is smartphone.
- Crawl allowed? Whether robots.txt let Googlebot in. “No” here means a rule in robots.txt blocks the page.
- Page fetch. “Successful” or “Failed” with a reason (for example a 404 or a server error). If you see 404s here, how to fix 404 errors in Google Search Console covers which ones matter.
- Indexing allowed? Whether a noindex tag or header blocked indexing. One trap: if robots.txt blocks the page, this shows “Yes” because Google can’t read the page to see a noindex.
- User-declared canonical. The main URL your page asks Google to use, from a canonical tag, header or sitemap. “None” is fine on a normal page.
- Google-selected canonical. The URL Google actually chose. If it differs from yours, Google is treating another page as the main copy. Canonical tag in SEO explains why that happens and how to fix it.
Below Page indexing you may also see Enhancements, which lists structured data Google found and any errors. Google notes the tool doesn’t report every rich result type, so for a full check use the tools in schema markup testing tool.
In that made-up example, nothing is broken on the page itself. The fix is to add it to the sitemap, link to it from the services menu and the home page, then run a live test and request indexing.
Live test vs the indexed result
The two views answer different questions. The indexed result asks “what did Google store last time?” The live test asks “if Google fetched this page now, could it index it?”
The live test has its own statuses: “URL is available to Google”, “URL is available to Google, but has issues” and “URL is not available to Google”. It follows redirects and tests the final address without telling you a redirect happened, so if the result looks like a different page, check whether your URL redirects.
It also checks less than people assume. Google’s help page lists what the live test skips: sitemaps and referring pages, duplicate and canonical decisions, manual actions, security issues, removals, and statuses such as “Crawled - currently not indexed” and “Discovered - currently not indexed”. A passing live test means the page can be fetched and has no noindex. It doesn’t mean Google will index it.
The screenshot is the part worth opening on any page built with JavaScript or a page builder. If the screenshot shows a blank area where your services or prices should be, Google may not be seeing that content. More info lists resources Googlebot couldn’t load, which usually points to a script or stylesheet blocked in robots.txt.
What Request indexing can and can’t do
Request indexing asks Google to crawl the URL again. Before it accepts the request it runs a quick live check, and if that check finds the page can’t be indexed (a noindex, a 404, a robots.txt block), you can’t submit it.
Set your expectations from Google’s own wording:
- Timing. The recrawl guide says crawling “can take anywhere from a few days to a few weeks”.
- Repeats don’t help. The same guide says asking “multiple times for the same URL won’t get it crawled any faster”.
- There’s a daily quota. Google confirms a limit on individual requests per property but doesn’t publish the number, so save requests for pages that matter.
- No guarantee. Google can crawl the page and still decide not to index it, usually because it adds little that other pages don’t already cover.
For more than a handful of pages, submit or resubmit your sitemap with accurate <lastmod> dates instead. That’s the route Google recommends for large numbers of URLs.
If you want to check many URLs at once, the Search Console URL Inspection API returns the same indexed data in bulk, with a limit of 2,000 inspections per day and 600 per minute for each site. It reports status only. It can’t request indexing.
What can go wrong
- “URL not in property”. You pasted a URL from another version of the site (
httpvshttps,wwwvs nowww) or another domain. Switch to the matching property or set up a Domain property. - Request indexing is greyed out or fails. The live test found a blocker. Fix that first, then test again.
- The result contradicts what you see in your browser. Check Last crawl. If the date is older than your change, run the live test. If the live test still disagrees, your site may be serving Googlebot something different, such as a cached or geo-redirected page.
- “Indexing allowed? Yes” but the page still isn’t indexed. Check Crawl allowed. A robots.txt block hides any noindex, so the “Yes” means nothing until crawling is allowed.
- Indexed, but no traffic. The tool has done its job. Look at the page in the Performance report instead, and see technical SEO issues if you suspect a wider problem.
- You need a page gone, not indexed. URL Inspection can’t remove anything. Use the removals tool for a quick temporary hide, and a noindex or 404 for the permanent fix.
FAQ
How do I check if my website is indexed by Google?
Inspect your home page and two or three key pages with URL Inspection. “URL is on Google” means that page is indexed. For the whole site, open the Page indexing report under Indexing, which counts indexed and not indexed pages.
How often can I request indexing for the same page?
Once per change is enough. Google says repeat requests for the same URL don’t speed up crawling, and each one uses part of your daily quota for the property.
Can I use URL Inspection on a competitor's site?
No. It only works for URLs inside a property you have access to. For another site, Google points you to public tools such as the Rich Results Test, which can fetch any public URL.
Inspect your newest page first
Pick the last page you published, paste it into URL Inspection, and read three fields: Last crawl, Indexing allowed and Google-selected canonical. If the page is unknown to Google, add it to your sitemap and link to it from a page that’s already indexed, then run the live test and request indexing once. Check back in a week, not every day.
