Can the inspection request load more than the submitted page?

It may request resources required to render that page. Google says the crawler otherwise mimics Googlebot, so blocked scripts or styles can affect the test result.

Does a robots block for this token affect Search indexing?

No. Google says preferences addressed to Google-InspectionTool affect the testing tools and have no effect on Google Search or other products.

How should I authenticate a Google-InspectionTool request?

Match its source against Google's published crawler ranges or perform the documented reverse and forward DNS checks. Do not authorize a request from the user-agent text alone.

Does Google-InspectionTool feed Google's AI models?

Google documents it for Search inspection and testing, not AI training or answer retrieval. Blocking this token is therefore not an AI opt-out.

Google-InspectionTool Bot Guide

What is Google-InspectionTool?

Google-InspectionTool retrieves a page when someone uses a Google Search testing feature such as the Rich Results Test or live URL inspection in Search Console. The fetch lets the tool examine what Google can load and render for that requested URL.

Its browser-style user agent contains Google-InspectionTool/1.0. Google says that, apart from the user agent and token, this crawler mimics Googlebot. A test may therefore request scripts, stylesheets, images, or other resources needed to render the page, even though the original action concerned a single URL.

Google's crawler documentation gives Google-InspectionTool as the product token and says crawling preferences addressed to it affect the Search testing tools. Requests should still be verified through Google's published crawler IP data or a forward-confirmed reverse DNS check because the header can be copied.

This identity is limited to inspection and testing. Blocking it can prevent a live test from loading a page, but Google states that the preference has no effect on Google Search or other products. Google does not assign this crawler a role in AI answer retrieval or model training.

Not relevant for AI search

Is Google-InspectionTool relevant for AI search?

No. Google-InspectionTool is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Google-InspectionTool runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle Google-InspectionTool

Leave the requested page and its rendering resources available when developers depend on live inspection results. If a test fails, check robots.txt and application access logs before changing Googlebot's indexing controls, since this identity has its own documented token.

A site-wide testing block is written as:

User-agent: Google-InspectionTool
Disallow: /

Google specifically documents that preferences addressed to this token affect its Search testing tools. That is product-specific compliance, not a general access barrier. Keep authentication on private content and verify Google origin before adding a firewall exception.

Examples

A developer submits a product page to the Rich Results Test. Google-InspectionTool loads the page and its rendering assets so the test can inspect the structured result.
Live URL inspection reports a blocked stylesheet. The owner finds a rule for Google-InspectionTool, allows that resource for testing, and reruns the inspection without changing the site's Googlebot policy.

Frequently asked questions about Google-InspectionTool

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Google names Search testing tools such as the Rich Results Test and URL inspection in Search Console. A user action in one of those tools causes the page fetch.