Google says Google Site Verifier fetches Search Console verification tokens. The user-triggered fetchers section says these fetchers generally ignore robots.txt rules because a user requested the fetch. The page does not print a separate robots.txt User-agent line. This check matches the whole token and still reports the RFC 9309 decision.
robots.txt token
Google-Site-Verification
Operator
Google
Kind
user_fetch
robots.txt
generally_ignores. The vendor says this fetcher generally ignores robots.txt, because a person requested the fetch.
HTTP user-agent
Mozilla/5.0 (compatible; Google-Site-Verification/1.0) The page prints this string as the HTTP user agent and does not print a separate robots.txt User-agent line.
IP list
None on the cited page. The user-triggered fetchers section names https://developers.google.com/static/crawling/ipranges/user-triggered-fetchers.json (creationTime 2026-10-16T14:46:09.000000), https://developers.google.com/static/crawling/ipranges/user-triggered-fetchers-google.json (creationTime 2026-10-16T14:46:08.000000), and https://developers.google.com/static/crawling/ipranges/user-triggered-agents.json (creationTime 2026-10-16T14:46:09.000000), and does not say which file this fetcher uses. Each URL returned HTTP 200 on 2026-10-18. Botcard does not copy the prefixes. The page says the reverse DNS mask matches ***-***-***-***.gae.googleusercontent.com when Google owns the fetcher, or google-proxy-***-***-***-***.google.com when a user owns it. A user-agent string can be spoofed.
Source
List of Google user-triggered fetchers. Retrieved 2026-10-18, page says updated 2026-08-19. CC BY 4.0 (Google Developers page, except as that page notes).
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Google-Site-Verification on /docs and allows *. The call does not fetch a host.