Google Site Verifier fetch
Google-Site-Verification is the fetcher Google uses to confirm a site-ownership verification token — for example retrieving an HTML verification file or checking a meta tag — when you verify a property in Search Console or other Google services. It is documented among Google's special-case fetchers and is unrelated to ongoing search indexing.
What this means
Google-Site-Verification is the fetcher used when Google needs to confirm a verification token you placed on your site — such as an HTML file upload or a meta tag — to prove ownership in Search Console and related products.
It is a functional fetch tied to verification, not part of search indexing. If a verification check fails, ensure this fetcher can reach the token URL; blocking it can prevent ownership verification from completing.
How it identifies itself
It uses the user-agent token Google-Site-Verification and is listed among Google's crawlers and fetchers. Match on the stable token rather than a version string.
For authenticity, verify the source IP against Google's published fetcher ranges, since the user agent alone can be spoofed.
- User-agent token: Google-Site-Verification
- Purpose: confirm a site-ownership verification token
- Separate from Googlebot indexing
How it appears in analytics and logs
A request carrying the Google-Site-Verification token means Google is checking a verification token to confirm you control the property. It is a one-off-style functional fetch tied to verification, not crawl coverage.
Diagnostic use case
Recognise ownership-verification fetches during Search Console setup, and avoid mistaking them for Googlebot indexing or for human traffic.
What WebmasterID can help detect
WebmasterID classifies the Google-Site-Verification fetch as a special-case Google fetcher, so verification checks do not appear as Googlebot crawl coverage or as human visits in your analytics.
Common mistakes
- Blocking the verification fetcher and then being unable to verify the property.
- Treating a verification fetch as ongoing search-crawl activity.
- Assuming the user agent guarantees authenticity without IP verification.
Privacy and accuracy notes
Google-Site-Verification is identified only by its user-agent token. It is automation, not a visitor; WebmasterID records it as a bot event and never associates it with a person.
Related pages
- The Search Console Crawl Stats report
The Crawl Stats report is a Google Search Console feature that summarises Googlebot's crawling of your site over the last 90 days — total crawl requests, total download size, average response time, and breakdowns by response code, file type, crawl purpose (discovery vs refresh), and Googlebot type. It is the primary first-party place to understand how Google crawls a property.
- APIs-Google fetcher
APIs-Google is a Google fetcher user agent used when Google products send push notifications or other API-driven requests to a developer's server — for example a PubSubHubbub (WebSub) delivery. It is not the search crawler and is not used to build the search index. Google documents it in the list of Google crawlers and fetchers, and it is verifiable against Google's published crawler IP ranges.
- How to verify Googlebot
The Googlebot user agent is widely spoofed, so a request claiming to be Googlebot should be verified, not trusted. Google documents two methods: a reverse-DNS check that resolves into googlebot.com or google.com confirmed by a matching forward lookup, and matching the source IP against Google's published crawler IP ranges.
- Documentation
Set-up guidance for verification and traffic intelligence.
Sources and verification notes
- Google Search Central — Google crawlers and fetchers overviewGoogle-Site-Verification listed among Google's fetchers.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.