Most Google URL Inspection tool SEO advice stops at “click Request indexing”. That skips the useful part. The tool returns a verdict, a set of fields and, if you ask, a live test, and each of those can say something reassuring that is not quite true. Read correctly, it tells you exactly which stage a page is stuck at. Read loosely, it sends you chasing the wrong fix.
Everything below comes from Google’s own Search Console Help article, URL Inspection tool, quoted where the wording matters. If you are new to the wider product, start with our guide to using Google Search Console and come back here for the detail.
Two modes: the indexed view and the live test
Google describes the tool as providing “information about Google’s indexed version of a specific page”, while also letting you “test whether a URL might be indexable”. You reach it by typing “the fully-qualified URL to inspect in the inspection search bar at the top of any Search Console screen”, or by clicking an Inspect link next to a URL in most reports. The URL must belong to the property you have open. For a site you don’t own, Google points you to non-owner tests such as the Rich Results test.
The first screen you see is not live. In Google’s words: “The results shown are from most recently indexed version of a page, not the live version on the web.” If you fixed something yesterday, this view may still show the old problem. To check the page as it stands, you press Live Test, and “the tool fetches and examines the URL in real time.”
That split is the key to every result. The indexed view is history. The live test is a fetch. Neither is a prediction of what Google will do next.
Every URL Inspection tool verdict, decoded
Here are the verdicts as Google’s help page defines them, with the sensible next step for each. The next steps are our reading; the definitions are Google’s.
| Verdict | Mode | What Google says it means | What to do next |
|---|---|---|---|
| URL is on Google | Indexed | Indexed, can appear in results, no enhancement problems found | Nothing for indexing; look at rankings and content instead |
| URL is on Google, but has issues | Indexed | Indexed, but problems might prevent some enhancements | Fix the flagged structured data or enhancement |
| URL is not on Google | Indexed | “This URL won’t appear in Google Search results.” | Read the fields below to find the blocking stage |
| URL is an alternate version | Indexed | An AMP alternate of a canonical non-AMP page | Inspect the canonical URL instead |
| URL is unknown to Google | Indexed | “Google hasn’t seen this URL before.” | Add it to a sitemap and link to it internally |
| URL is available to Google | Live | Google-InspectionTool can access the page now | Request indexing if the indexed view is out of date |
| URL is available to Google, but has issues | Live | Accessible, with problems to look at | Fix the listed issues, then retest |
| URL is not available to Google | Live | Google can’t access the page for indexing | Check login walls, robots.txt and server responses |
“URL is unknown to Google” deserves a separate note. It is a discovery problem, not a quality one. Our posts on Discovered, currently not indexed and Crawled, currently not indexed cover the two statuses that usually follow once Google does find the page.
The fields that change the diagnosis
Under the verdict sit the fields that explain it. Four matter most.
- Crawl allowed? Whether robots.txt lets Google crawl the URL.
- Page fetch. Whether Google could retrieve the page. Google warns that “Fetching can be successful even if the page is not indexed for another reason.”
- Indexing allowed? Whether a noindex directive blocks indexing.
- User-declared and Google-selected canonical. The URL you named and the one Google picked. “Google might select the user-declared canonical, but sometimes Google might choose another URL.”
The robots.txt trap
This one catches experienced people. Google states: “If your page is blocked by robots.txt (see Crawl allowed?), then Indexing allowed? will always be ‘Yes’ because Google can’t see and respect any noindex directives.” A “Yes” there proves nothing if crawling is blocked. Fix the robots.txt rule first; our post on Blocked by robots.txt walks through it. If the canonical fields disagree, see Google chose a different canonical.
Why “URL is on Google” is not “ranking”
The green verdict is the most misread result in Search Console. Google is blunt about it: “‘URL is on Google’ doesn’t guarantee that your page is appearing in Search results. The URL Inspection tool doesn’t take into account all requirements for appearing on Google.” Its own suggestion for a definitive check is to search for the URL on Google. Our guide on checking whether a page is indexed covers that and the other methods.
The live test has the same ceiling. Google says it “only confirms if Google-InspectionTool can access your page for indexing. There is no definitive test that can guarantee whether your page will be included in the Google index.” The live test also:
- “does not check for the presence of the URL in any sitemaps or any referring pages”;
- does not test whether the page is a duplicate or alternate;
- “cannot predict whether or not the tested version will be considered canonical”;
- does not show that it followed a redirect, nor the final URL tested.
That redirect point matters during migrations. A clean live test on an old URL may be a test of wherever it redirects, and the tool will not say so. The page also needs to be reachable “without any login requirements”, so staging sites behind a password will always fail. One upside of the live test: “A screenshot of the rendered page is available only in a live test”, which helps when JavaScript rendering is in doubt.
Request indexing: a nudge with a cap
Request indexing asks Google to recrawl a URL. It is not a fast lane. Google says “Indexing typically takes only a day or so, but can take much longer in some cases”, and elsewhere that it “can take up to a week or two”. More importantly: “Submitting a request does not guarantee that the page will appear in the Google Index.” And “You cannot request indexing if the page is considered to be non-indexable in the live test.”
There are also limits Google does not quantify. “There is a daily limit to how many index requests you can submit”, plus a daily limit of inspection requests and a per-property daily limit of live inspections. The help page gives no figures for any of them, so ignore anyone who quotes one as fact. For more than a handful of URLs, Google’s advice is to “submit a sitemap, with the updated pages marked by <lastmod>.” Our post on getting indexed by Google covers the wider process.
The limitation is worth stating plainly. The URL Inspection tool reports on one URL at a time and only on indexing mechanics. Google lists manual actions, security issues and content quality among the things it does not test, so a clean result says nothing about whether the page deserves to rank.
Frequently asked questions
What is the purpose of the URL Inspection tool?
It shows information about Google’s indexed version of a specific page, including structured data, video, linked AMP and indexing details, and lets you live-test whether a URL might be indexable.
Does “URL is on Google” mean my page ranks?
No. Google says the verdict doesn’t guarantee the page appears in Search results, because the tool doesn’t consider every requirement. Search for the URL on Google for a definitive check.
How many URLs can I inspect or submit per day?
Google confirms daily limits on inspections, live tests and indexing requests, but its help page publishes no numbers. For many URLs, submit a sitemap with lastmod dates instead.
Why does the result show an old version of my page?
The default view is not live; it shows the most recently indexed version. Run the Live Test to see the page as Google can fetch it now.
The takeaway Separate the indexed view from the live test, check Crawl allowed? before trusting Indexing allowed?, and treat every green result as “accessible”, not “ranking”.
