Google-Site-Verification (Google): what it is and how to allow or block it
Updated · checked against the operator's documentation on
Google-Site-Verification is Google's fetcher that reads Search Console verification tokens. Verify it by Google's reverse DNS; allow it, because robots.txt generally does not apply to it. Google documents no robots.txt token for it; the name in its user agent is Google-Site-Verification.
Facts
- Operator
- Category
- Special-purpose crawler
- robots.txt token
Google-Site-VerificationGoogle documents no robots.txt token for it; this is the name in its user agent.
- Honors robots.txt?
- Generally ignored (user-triggered), per Google. Google says its user-triggered fetchers generally ignore robots.txt rules, and lists no robots.txt token for Google Site Verifier.
- User-agent example
Mozilla/5.0 (compatible; Google-Site-Verification/1.0)
- Official source
- Google: List of user-triggered fetchers
- Compared with the source
What it is used for
Per Google, Google Site Verifier fetches Search Console verification tokens. Google uses it as its example of a fetcher that acts on a user's request.
Not the crawler behind a search index. What blocking it changes is specific to its tool, so read the next section.
What happens if you block it
Per Google, user-triggered fetchers generally ignore robots.txt, so a robots.txt rule may not stop it. If your server or firewall refuses it, Search Console cannot read the verification token (our reading, not a Google statement).
Is it really Google-Site-Verification?
Anyone can send Google-Site-Verification as a user agent, so a log line proves nothing by itself. The way to tell is the requesting IP address.
- Compare the IP address with the Google: Verify Google requests (links the user-triggered fetcher IP files). A request from outside those ranges is not the operator's crawler.
- Google documents reverse DNS names of the form ***-***-***-***.gae.googleusercontent.com (Google-owned fetchers) or google-proxy-***-***-***-***.google.com (user-owned fetchers) for its user-triggered fetchers, to be confirmed by a forward lookup.
- Guide: Googlebot and robots.txt: the token, the rules, and how to verify a request.
- Guide: Fake Googlebots and PHP scanners: what hit our new server in 48 hours.
- Guide: Why Google isn't crawling your site: causes and how to check each.
- Paste any user agent from your logs into the user-agent lookup, or follow the scripts in Fake Googlebots and PHP scanners.
How to allow or block Google-Site-Verification
Add one of these groups to the robots.txt at the root of your domain. A group that names the bot overrides a general User-agent: * group.
Google names no robots.txt token for Google-Site-Verification, so these groups use the name from its user agent and may have no effect. Google says its user-triggered fetchers generally ignore robots.txt rules, and lists no robots.txt token for Google Site Verifier.
User-agent: Google-Site-Verification Allow: /
User-agent: Google-Site-Verification Disallow: /
Does your site allow Google-Site-Verification today? The checker evaluates your robots.txt for this and every other bot.Check my site
What we see on this site
No request identifying as Google-Site-Verification has been recorded since 19 Oct, so there is nothing to show yet. We never fill this in with estimates.
Counts come from this site's own server; they hold no IP addresses or URLs, and a user agent is only a claim. See the bot traffic data and the methodology.
Questions about Google-Site-Verification
What is Google-Site-Verification?
Google's fetcher that reads the verification token when someone verifies a site in Search Console. Google uses it as its example of a fetcher that acts on a user's request.
Is Google-Site-Verification safe and legitimate?
The real Google-Site-Verification is a special-purpose crawler run by Google. A user-agent string is only a claim, though, so anyone can send it. Compare the requesting IP address with the published IP ranges. Google documents reverse DNS names of the form ***-***-***-***.gae.googleusercontent.com (Google-owned fetchers) or google-proxy-***-***-***-***.google.com (user-owned fetchers) for its user-triggered fetchers, to be confirmed by a forward lookup.
Does Google-Site-Verification obey robots.txt?
Generally ignored (user-triggered), per Google. Google says its user-triggered fetchers generally ignore robots.txt rules, and lists no robots.txt token for Google Site Verifier.
How do I block Google-Site-Verification?
Robots.txt may not stop it. Google says its user-triggered fetchers generally ignore robots.txt rules, and lists no robots.txt token for Google Site Verifier. If you add a group anyway, use User-agent: Google-Site-Verification followed by Disallow: /.
Will blocking Google-Site-Verification hurt my Google rankings or AI visibility?
No ranking crawler: per Google, it only fetches Search Console verification tokens. Refusing it can stop a site verification in Search Console (our reading).
Related bots
More from Google
- Google-Extended AI control tokenA robots.txt token that lets you manage whether Google may use crawled content for Gemini training and grounding.
- Googlebot Search engine crawlerGoogle's main crawler for Google Search, whose index Google's AI features in Search also draw on.
- Googlebot-Image Search engine crawlerGoogle's crawler for the images that appear in Google Search and related surfaces.
- GoogleOther Special-purpose crawlerGoogle's generic crawler that product teams can use for their own purposes.
Other Special-purpose crawlers
- archive.org_bot Internet ArchiveReported to be the crawler the Internet Archive uses for Wayback Machine and Archive-It captures.
- WebMCPIndexBot WebMCP ShieldA survey crawler that measures how widely websites adopt WebMCP.
- AgentTrustBot agenttru.stA crawler that looks for published AI agent discovery documents on newly seen hostnames.
- OAI-AdsBot OpenAIOpenAI's fetcher that checks web pages submitted as ads on ChatGPT.
All Special-Purpose Crawlers · Bot directory · Bots from Google · Which bots to allow or block · robots.txt generator · See a page as a bot