FIX · INSPECT URL
Inspect any URL and see every signal in one place.
Paste a page from your site and see what every module knows about it: Google’s inspection result, Search Console performance, organic visits, crawler history, technical signals, robots.txt rules and AI citations, on one timeline.
- Google, server and analytics views
- One timeline
- robots.txt per crawler
- GoogleIndexed · last crawl 5 days agoCanonical matches yours
- Search9,120 impressions · 412 clicksAvg. position 4.2
- CrawlersGooglebot, OAI-SearchBot, Bingbot200 OK, 310 ms
- AICited in 2 tracked answers18 AI referral visits
index status, canonical and last crawl
Search
Search Console clicks and impressions
Logs
verified crawler history
AI
citations and AI referrals
INSIDE THE PRODUCT
One page. Every source. One answer.
Stop switching between tools to understand a single URL.
Google’s view
See what Google recorded for the page
Index status, last crawl, crawled-as device, Google’s chosen canonical against yours, whether indexing is allowed, page fetch and rich-result messages, beside the page’s Search Console clicks and impressions.
- Google’s canonical vs yours
- Indexing allowed and page fetch
- Rich results
| Signal | Value | Status |
|---|---|---|
| Index status | Indexed | Good |
| Google’s canonical | Same as yours | Good |
| Crawled as | Smartphone | — |
| Rich results | Product snippet | 1 warning |
Your server
See which crawlers requested it
Which verified crawlers requested the URL, how it answered and when, together with what robots.txt allows each key crawler to do.
- Crawler history from your logs
- Status and response time
- robots.txt for key crawlers
- AllowedGooglebot14 requests · 200 OK
- AllowedOAI-SearchBot3 requests · 200 OK
- AllowedBingbot6 requests · 200 OK
- BlockedCCBotDisallowed in robots.txt
Visits & AI
See the visits and AI answers that point to it
Organic visits from GA4, plus Prompt Tracking answers and AI referrals that point to the page, on the same timeline as crawls and changes.
- Organic visits from GA4
- AI citations from Prompt Tracking
- AI referrals
One timeline
Every source on one timeline
Crawls, index status changes, clicks, visits and AI answers for the URL appear in date order, so you can see what happened first.
- Crawler requests and inspections
- Search and analytics changes
- AI answers that cite the page
- 28 OctGooglebotRequested, 200
- 27 OctPrice changeIndexNow notified
- 24 OctInspectionIndexed, canonical = self
- 21 OctAI answerCited by a tracked prompt
Robots & access
See what each crawler may do
For the URL, see what robots.txt allows for each key crawler, and how your server answered the crawlers that requested it.
- robots.txt per crawler
- Server responses by crawler
- Verified, not user-agent guesses
| Crawler | robots.txt | Last response |
|---|---|---|
| Googlebot | Allowed | 200 |
| Bingbot | Allowed | 200 |
| OAI-SearchBot | Allowed | 200 |
| GPTBot | Disallowed | — |
WHAT IT MEASURES
What one URL brings together.
What each metric tells you, and where it comes from.
| Metric | What it tells you | Source |
|---|---|---|
| Index status and canonical | Google’s verdict and chosen canonical. | URL Inspection API |
| Clicks and impressions | Search performance for the page. | Google Search Console |
| Organic sessions | Visits from search to the page. | Google Analytics 4 |
| Crawler requests | Verified crawlers that requested the URL, and the response. | Crawl Analytics logs |
| robots.txt rules | What each key crawler is allowed to fetch. | Your robots.txt |
| AI citations and referrals | Tracked AI answers citing the page, and AI referral visits. | Prompt Tracking + GA4 |
| Audit findings | Issues the latest audit found on the page. | Ndovu site audit |
UNDER THE HOOD
How Inspect URL gathers the evidence.
How the numbers are produced, so you can judge them for yourself.
One URL, every module
Inspect URL asks each module what it knows about the URL: Search Console clicks and queries, GA4 sessions, URL Inspection, the latest audit, robots.txt verdicts, crawler logs and AI citations.
A dated timeline
Every dated event is placed on one timeline, so you can see whether the canonical changed before the clicks fell or after.
Never invents a date
If no source records when Google indexed a page, no date is shown. Each panel keeps its own source and date.
Free to read
Inspect URL reads data your project already has, so it uses no credits.
HOW IT WORKS
From a URL to the cause.
Four steps from connecting your data to a decision you can stand behind.
Paste or open a URL
Paste it, or open it from any table in the project.
Compare the views
Read Google’s, your server’s and your analytics’ view side by side.
Find the first change
Use the timeline to see what changed first.
Fix and re-inspect
Fix the cause, then inspect again.
WITH YOUR AI AGENT
Ask about one URL, get every module’s answer.
Your agent pulls one URL’s evidence from every source in the project.
- Uses the same data as the web app
- Paid tools estimate their cost first
- Saves the report to the project
YouWhy did /phones/phone-a/ lose clicks this week?
get_url_intelligenceinspect_urls
AgentClicks fell 38% from Tuesday. Google still reports it indexed, but the canonical changed to a filtered URL on Monday, and Googlebot has requested the filtered URL 40 times since.
YouIs anything else wrong on the page?
AgentThe last audit found no other P0 or P1 issues. Fix the canonical, then inspect again after Googlebot’s next visit.
Illustration · sample data
USE CASES
Built for the way you work.
How teams put it to work.
Answer “what happened to this page?”
See indexing, crawling, traffic and AI evidence for one URL in seconds.
Check a page after a release
Confirm the page returns 200, keeps its canonical and is still crawled.
Answer “what happened to this page?”
Bring one URL’s crawl, index, click and visit evidence to the meeting.
Confirm a fix reached Google
See the next Googlebot request and inspection after a deploy.
DATA & LIMITS
Know what the numbers can and cannot tell you.
Where the data comes from, how fresh it is, and the questions it cannot answer on its own.
| Source | What it provides | Freshness & limits |
|---|---|---|
| URL Inspection API | Index status, last crawl, canonical, rich results. | Quota-limited by Google. |
| Search Console and GA4 | Clicks and visits. | Each with its own delay. |
| Crawl Analytics | Verified crawler requests. | Depends on your log source. |
| Prompt Tracking | AI answers citing the page. | Only tracked prompts. |
Empty can mean not connected
A blank panel usually means that source is not connected.
Not an indexing request
Inspecting reads Google’s status; it does not ask Google to index.
Each panel keeps its date
Sources update at different times; dates are shown on every panel.
Tracked prompts only
AI citations come from prompts you track, not every AI answer.
WORKS WITH
Connected to the tools you already use.
The sources and clients this feature reads from or works alongside.
CHOOSE THE RIGHT VIEW
Which view answers which question.
Start where the question points. Each view keeps its own source.
| Your question | Start with | Why |
|---|---|---|
| Everything about one URL? | Inspect URL | All modules for one page. |
| Index status across many URLs? | Indexing intelligence | Inventory and history. |
| Every request by crawlers? | Crawl Analytics | Activity and issues. |
LEARN & TRY
Guides and free tools for the same job.
Read how the evidence works, or try a free check before you connect a project.
Robots.txt URL tester
Check whether a crawler may fetch a URL.
FAQ
Inspect URL: common questions.
Straight answers about what it does, what it costs and where its limits are.
Does inspecting a URL request indexing?
No. It reads Google’s recorded status. URL Inspection is quota-limited by Google and is not an indexing request.
Which URLs can I inspect?
Pages on the website connected to the project’s Search Console property.
Why is a panel empty?
Each panel needs its source: Search Console, GA4, a log source or Prompt Tracking. An empty panel usually means that source is not connected.
Can my AI agent inspect URLs?
Yes. Connected agents can inspect URLs for your projects through MCP.
Does Inspect URL cost credits?
Reading your own Search Console, GA4 and log data does not. AI citations come from tracking you already run.
Can I inspect any website?
Inspect URL is for URLs on your own project’s site, where your sources are connected.
Can my agent use it?
Yes. Agents can pull the same URL evidence and inspect URLs through MCP.
Why is a panel empty?
Usually because that source is not connected to the project, or has no data for the URL yet.
Does it show robots.txt for AI crawlers?
Yes. It shows what robots.txt allows for key search and AI crawlers on that URL.
What are the limits of the data?
URL Inspection is quota-limited by Google and is not an indexing request. Each panel keeps its own source and date; an empty panel usually means that source is not connected.
How do I get access?
Platform access is reviewed. Request access with your website and the data sources you use, and the team will help you connect them.
See it with your own data.
Tell us about your website. We will review access and help you connect the right sources.