You publish a new page, wait a few days, and it still does not appear in Google. You check your content, your title, your keywords, and everything looks fine. So what is going wrong? The fastest way to find out is Google Search Console URL Inspection, a free diagnostic tool that shows you exactly how Google sees one specific page on your website.
Think of Google Search Console URL Inspection as an X-ray for a single URL. It tells you whether Google has found the page, whether it was crawled, whether it was indexed, which canonical Google picked, and whether any structured data or technical problem stands in the way. Few features in Search Console answer so many questions in so little time.
In this complete guide, you will learn what Google Search Console URL Inspection is, how to open it, how to read every section of the report, how to test a live URL, how to request indexing properly, and how to fix the most common errors. Whether you manage a small business site or a large WordPress blog, this guide gives you a repeatable workflow you can use every week.
What Is Google Search Console URL Inspection?
Google Search Console URL Inspection is a tool inside Google Search Console that provides detailed crawling, indexing and serving information about a single page, taken directly from Google’s index. You enter a full URL, and the tool returns the status of that page as Google last recorded it.
Google Search Console URL Inspection answers four practical questions:
- Is this page in Google’s index right now?
- When did Googlebot last visit it, and what did it find?
- Which URL did Google choose as the canonical version?
- Is the page eligible for enhancements such as rich results?
Unlike broad reports that group thousands of pages together, Google Search Console URL Inspection focuses on one URL at a time. That makes it the best starting point whenever a single page misbehaves. If you are new to the platform, our complete guide on how to use Google Search Console explains the full dashboard before you dive into this specific tool.
Why Google Search Console URL Inspection Matters for SEO
A page that is not indexed cannot rank. It is that simple. Before you spend time on backlinks, content updates or design changes, you must confirm that Google can actually find and store the page. Google Search Console URL Inspection gives you that confirmation in seconds.
Here is why the tool deserves a place in your regular SEO routine:
- It confirms indexing. You see whether the page is on Google or not, with a clear explanation.
- It speeds up new content. You can ask Google to crawl a fresh or updated page.
- It reveals technical blockers. Robots rules, noindex tags and redirects all show up in the report.
- It exposes canonical conflicts. You learn whether Google agrees with the canonical you declared.
- It validates fixes. After you repair a problem, you can test the live page before waiting for a recrawl.
Because of these benefits, professional SEOs treat Google Search Console URL Inspection as a first-response tool, not a last resort.
How Google Finds, Crawls and Indexes a Page
To use Google Search Console URL Inspection well, you need a basic picture of the pipeline behind it. Google works in three broad stages: discovery, crawling and indexing. Our guide on how Google search works covers the full process, but here is the short version.
Discovery. Google learns that a URL exists through sitemaps, internal links, external links or earlier crawls.
Crawling. Googlebot requests the page, reads the HTML, and may render JavaScript to see the final content.
Indexing. Google analyzes the content, chooses a canonical version, and stores the page so it can appear in search results.
A page can fail at any of these stages. Google Search Console URL Inspection tells you which stage broke, and that is why it is so valuable. Instead of guessing, you can see whether the page was never discovered, discovered but not crawled, crawled but not indexed, or indexed with problems.
How to Open Google Search Console URL Inspection
There are two simple ways to start a Google Search Console URL Inspection.
Method 1: The search bar. Open your property in Search Console. At the top of the screen, you will see a search bar that says “Inspect any URL in your property.” Paste the full URL, including https://, and press Enter.
Method 2: The left menu. Click “URL inspection” in the left navigation. A similar input box appears. Paste the URL and press Enter.
Some important rules apply:
- The URL must belong to the property you currently have selected. A URL from another domain, or from a different protocol or subdomain than your property, will be rejected.
- You need at least restricted access to the property. Owners, full users and restricted users can all view inspection data.
- If you use a Domain property, you can inspect any URL on any subdomain under that domain. A URL-prefix property only covers URLs that start with that exact prefix.
If you have not verified your website yet, set that up first. Without a verified property, Google Search Console URL Inspection is not available.
Understanding the Google Search Console URL Inspection Report
After you submit a URL, Google Search Console URL Inspection loads a report built from the last indexed version of the page. The report is divided into several expandable sections. Let us walk through each one.
The Main Status Banner
The top of the report shows a headline verdict. You will usually see one of four messages:
- URL is on Google. The page is indexed and can appear in search results. This does not guarantee any specific ranking, only that it is eligible.
- URL is on Google, but has issues. The page is indexed, but something related to an enhancement, such as structured data, needs attention.
- URL is not on Google. The page is not indexed. The report explains why, for example because of a noindex tag or a crawl problem.
- URL is unknown to Google. Google has no record of the URL. It may be brand new, or Google may never have found a path to it.
Read this banner first in every Google Search Console URL Inspection. It sets the direction of your entire investigation.
The Page Indexing Section
This is the most important block in Google Search Console URL Inspection. It explains in detail how the page moved through discovery, crawling and indexing.
Discovery shows which sitemaps listed the URL and which referring pages linked to it. If a page has no sitemap and no internal links, Google may struggle to find it. Adding it to your XML sitemap and linking to it from related posts solves this quickly. For deeper strategies, read our guide on how to improve website indexing.
Crawl reveals the date of the last crawl, the user agent used (smartphone or desktop Googlebot), whether crawling was allowed by robots.txt, and whether the page fetch succeeded. If the fetch failed, you will see a reason such as a server error, a not found response or a redirect error.
Indexing shows whether indexing is allowed, which canonical you declared, and which canonical Google selected. A mismatch here is a major clue. If Google picks a different URL than you intended, it may consider your page a duplicate.
The Enhancements Section
Below the indexing information, Google Search Console URL Inspection lists any detected enhancements. Depending on the page, you may see breadcrumbs, FAQs, videos, review snippets, products or other structured data types. Each item shows whether the markup is valid, valid with warnings, or invalid.
Errors in this section can block rich result eligibility. Warnings are less serious but still worth reviewing. For local businesses, accurate markup is especially valuable, and the guide on local business schema from Trade Scale Hub explains how to implement it correctly.
Test Live URL: The Most Powerful Feature
By default, Google Search Console URL Inspection shows the indexed version of a page, which may be days or weeks old. If you just fixed a problem, that stored version will not reflect your changes. This is where the “Test Live URL” button becomes essential.
When you click it, Google fetches the page in real time and shows what Googlebot would see right now. The result does not change the index. It only gives you a live diagnostic.
What the Live Test Shows
After the live test finishes, you can open “View tested page” to inspect three things:
- Screenshot. A rendered image of how Googlebot sees the page. If the screenshot is blank or missing key elements, rendering may be failing.
- HTML. The rendered HTML after JavaScript runs. Use it to confirm your main content, title tag, canonical and meta robots tag are present.
- More info. Page resources that could not load, plus JavaScript console messages and errors.
This is extremely helpful for JavaScript-heavy sites. If your content only appears after scripts run, the live test shows whether Google can actually see it.
Indexed Version vs Live Version
A common point of confusion is the difference between the two views. The indexed version reflects the last time Google crawled and processed the page. The live version reflects the page today. When you compare them, you can spot useful differences:
| Situation | What it means |
|---|---|
| Indexed shows error, live shows OK | Your fix worked. Request indexing. |
| Indexed shows OK, live shows error | A new problem appeared. Fix it fast. |
| Both show the same error | The problem still exists. Keep debugging. |
| Both show OK but page not indexed | A quality or duplication issue may be involved. |
Using both views together is one of the best habits you can build with Google Search Console URL Inspection.
How to Request Indexing With Google Search Console URL Inspection
After you publish a new page or make a major update, you can ask Google to prioritize crawling it. Here is the process:
- Open Google Search Console URL Inspection and paste the URL.
- Review the report. If the page is not indexed, click “Test Live URL” to make sure it is accessible.
- If the live test shows the page is available to Google, click “Request Indexing.”
- Wait while Google runs a quick check. A confirmation message appears when the request is queued.
What Request Indexing Actually Does
Many beginners misunderstand this button. Requesting indexing does not force Google to index the page. It adds the URL to a priority crawl queue. Google still decides whether the page deserves a spot in the index based on quality, uniqueness and technical eligibility.
You should also know that there is a daily quota. Google limits how many indexing requests you can submit, so use them on pages that matter. Submitting the same URL repeatedly will not speed things up. One request is enough; extra requests do not improve your chances.
When You Should Request Indexing
Use Google Search Console URL Inspection to request indexing in these situations:
- You published a brand new post or landing page.
- You significantly updated an important page.
- You fixed a technical error and want Google to re-evaluate it.
- You changed a URL and set up a redirect.
Avoid using it for minor edits, such as fixing a single typo. Google will recrawl the page naturally. For large sites with many new URLs, rely on your XML sitemap and strong internal linking instead of manual requests. The Search Console indexing guide from Trade Scale Hub offers a complementary look at this workflow.
Common Google Search Console URL Inspection Statuses and How to Fix Them
One of the best uses of Google Search Console URL Inspection is decoding the exact reason a page is not indexed. Below are the statuses you will meet most often, with practical fixes.
Crawled – Currently Not Indexed
Google visited the page, read it, and decided not to index it for now. This usually points to a quality signal rather than a technical block. The content may be thin, repetitive, or too similar to other pages.
How to fix it:
- Add original information, examples, data or expert detail.
- Improve internal links so the page looks important within your site.
- Remove or merge near-duplicate pages.
- Wait and monitor. Sometimes Google indexes the page later.
Discovered – Currently Not Indexed
Google knows the URL exists but has not crawled it yet. This often happens on sites with weak crawl signals or limited server capacity.
How to fix it:
- Link to the page from your homepage or high-authority posts.
- Make sure your server responds quickly and reliably.
- Reduce low-value URLs that waste crawl attention.
If speed is part of the problem, run a website speed test and fix the biggest bottlenecks.
Excluded by “noindex” Tag
The page carries a noindex directive in the meta robots tag or the X-Robots-Tag header. Google respects it and keeps the page out of the index.
How to fix it: If the page should rank, remove the noindex directive. On WordPress, check the SEO plugin setting for that page and any global setting that applies noindex to a post type. After the change, use Google Search Console URL Inspection to run a live test and then request indexing.
Blocked by robots.txt
Your robots.txt file tells Googlebot not to crawl the URL. Note that this is different from noindex. A blocked page can still be indexed without content if other pages link to it.
How to fix it: Edit your robots.txt file and remove the disallow rule that matches the page. Our guide on robots.txt for SEO shows how to write rules safely so you do not block important sections by accident.
Duplicate Without User-Selected Canonical
Google considers the page a duplicate of another URL, and you did not declare a canonical to say otherwise. Google chose its own canonical, which may not be the one you want.
How to fix it: Add a self-referencing canonical tag to the page you want indexed, and point duplicate versions to it. To understand how to use these tags correctly, read the canonical tags guide from Trade Scale Hub.
Soft 404
The page returns a normal response but looks empty or like an error page to Google. This happens with thin pages, empty category pages and expired content.
How to fix it: Add useful content, return a proper 404 or 410 status for pages that no longer exist, or redirect them to a relevant replacement.
Server Error (5xx) or Not Found (404)
These errors appear in the crawl section when Googlebot cannot fetch the page. Check your hosting logs, plugins and server limits. After repairs, run Google Search Console URL Inspection again with a live test to confirm that the page loads correctly.
Step-by-Step Workflow: Troubleshooting a Page With Google Search Console URL Inspection
If you want a repeatable process, follow this simple routine whenever a page fails to appear in Google:
- Paste the URL into Google Search Console URL Inspection. Read the main status banner first.
- Open the Page indexing section. Note the discovery, crawl and indexing details.
- Check crawl allowed and indexing allowed. These two fields reveal robots and noindex problems immediately.
- Compare user-declared and Google-selected canonicals. A mismatch means a duplication issue.
- Run Test Live URL. Confirm that the page is accessible and renders properly.
- View the tested page. Check the screenshot, HTML and resource errors.
- Fix the issue. Update content, tags, redirects or robots rules.
- Request indexing. Ask Google to recrawl once the page passes the live test.
- Monitor. Check again after several days and watch the Search Console reports.
Following these nine steps with Google Search Console URL Inspection turns a vague problem into a clear action plan. You can also pair this process with the Search Console coverage report to find patterns across many pages at once.
Using Google Search Console URL Inspection for Different Situations
Google Search Console URL Inspection is flexible. Here are the most common real-world cases where it saves time.
Checking a New Blog Post
Right after publishing, paste the URL into Google Search Console URL Inspection. If it says the URL is unknown to Google, confirm it appears in your sitemap and has internal links from related posts. Then run a live test and request indexing. This simple routine often gets a new post crawled within a short time, though results vary.
Debugging Structured Data
If you added schema markup, use Google Search Console URL Inspection to confirm that Google detects it. The enhancements section lists each type and flags errors. Fix the markup, run a live test, and request indexing again.
Investigating a Traffic Drop
If a page suddenly loses traffic, inspect it. You may discover that a plugin added a noindex tag, that a redirect broke, or that Google now selects a different canonical. Cross-check the result with your performance report to see exactly when impressions and clicks changed.
Google Search Console URL Inspection for WordPress Sites
WordPress powers a large share of the web, and it has some common indexing traps that Google Search Console URL Inspection can reveal quickly.
- “Discourage search engines” setting. If this box is ticked under Settings → Reading, your entire site may carry a noindex directive. Inspect any page and look at the indexing allowed field.
- SEO plugin settings. Plugins can noindex categories, tags, author archives or entire post types. Check each setting against what you want indexed.
- Plugin conflicts. A caching or security plugin can block Googlebot or serve error pages. A live test will expose this.
- Staging leftovers. Sites moved from staging often keep noindex tags or blocked robots rules.
If you run WordPress, our WordPress SEO guide and WordPress plugins guide will help you choose and configure tools that support indexing instead of hurting it.
The URL Inspection API: Scaling Google Search Console URL Inspection
If you manage many pages, checking them one by one in the interface becomes slow. Google offers the URL Inspection API, which lets developers retrieve inspection data programmatically. It returns much of the same information you see in the interface, including index status, canonical details and last crawl time.
There are important limits to remember. The API is subject to daily and per-minute quotas for each property, so you should prioritize your most important URLs. The API is for reading inspection data. It does not request indexing for you. For that, you still need the manual button in the interface.
Best Practices for Google Search Console URL Inspection
To get consistent value, follow these best practices.
Inspect the exact URL. Use the full canonical version, including the correct protocol and trailing slash, so you do not analyze a different variant.
Fix the cause before requesting indexing. If a noindex tag or a block remains, requesting indexing will not help.
Strengthen internal linking. Pages that receive links from important, related pages are discovered and valued faster. Our on-page SEO checklist includes a step for internal links.
Keep your sitemap clean. List only indexable, canonical URLs. Remove redirected, noindexed or deleted pages.
Run a full audit too. Our technical SEO checklist and the SEO pagination guide help you catch problems that affect many pages at once.
Improve page quality. If a page is crawled but not indexed, the answer is often better content, not another request. Add depth, originality and usefulness.
Pull keyword data from the right place. The Search Console keywords guide from Trade Scale Hub explains where to find query data, since this tool does not show rankings.
Watch speed and usability. Slow, unstable pages can reduce crawl efficiency and user satisfaction. The Core Web Vitals guide from Trade Scale Hub explains the key metrics to improve.
Earn quality links. External links help Google discover and trust your pages. Review our guides on how to get backlinks and link building strategies to support your indexing efforts.
Frequently Asked Questions About Google Search Console URL Inspection
Why does Google Search Console URL Inspection say my page is not on Google?
Common causes include a noindex tag, a robots.txt block, a crawl error, thin or duplicate content, or a page that Google has not discovered yet. Open the Page indexing section to see the specific reason.
How often should I use Google Search Console URL Inspection?
Use it whenever you publish an important page, update key content, fix a technical issue or notice a sudden traffic change. For routine monitoring of many pages, rely on the indexing reports and sitemaps.
Final Thoughts
Google Search Console URL Inspection is one of the most practical tools in an SEO’s toolkit. It removes the guesswork from indexing problems by showing exactly how Google discovered, crawled and stored a page. With it, you can confirm that new content is eligible, find technical blockers, check canonicals, validate structured data and test fixes before waiting for a recrawl.
The key is to build a habit. Inspect every important page after you publish it. Use the live test after every fix. Request indexing sparingly and only when it makes sense. Combine the results with your sitemap, internal links and reports for the full picture of your site’s health.
Remember that Google Search Console URL Inspection tells you whether a page is eligible to appear in search, not whether it will rank. Great ranking still needs helpful content, strong links, fast pages and a clear site structure. But without indexing, none of that work matters, and that is exactly why Google Search Console URL Inspection belongs in your weekly routine.
Start today. Pick your five most important pages, run Google Search Console URL Inspection on each one, and fix anything the report flags. A few minutes of inspection can unlock traffic that has been waiting for Google to notice your work.
