curl -s https://www.pathwren.workers.dev/crawler/google-inspectiontool.json   # this page, as JSON

Google-InspectionTool

Google · Tools and frameworks · json

User-agent: Google-InspectionTool
Disallow: /

What it is

The fetcher behind Search Console's URL Inspection and the Rich Results Test. It runs when a site owner clicks a button.

What blocking it costs you

Your own Search Console live tests stop working. Blocking this only hurts you.

Full user-agent string

Mozilla/5.0 (compatible; Google-InspectionTool/1.0;)

Allow it instead

User-agent: Google-InspectionTool
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=google-inspectiontool&s=client-dossiers'

• /tools/verification-methods?crawler=google-inspectiontool
  How do I prove a request really is Google-InspectionTool? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
• /tools/verify-crawler?ip=108.177.2.0&ua=Google-InspectionTool
  Is 108.177.2.0 really Google-InspectionTool? That address checked against every prefix this host mirrors. 108.177.2.0 is the first address of 108.177.2.0/27, one of the ranges listed on this page — so the link is a worked example that returns a match. Swap in an address from your own log.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers
Machine copies: json · markdown
Policies that name this crawler: allow-all · maximum-ai-visibility