# Google-Site-Verification

Operator: Google
Purpose: User-requested fetch
Reviewed: 2026-09-14
HTTP identifier: Google-Site-Verification
robots.txt token: Google-Site-Verification

## What is Google-Site-Verification?

Fetches Search Console ownership-verification tokens.

## How to identify it

Look for the Google-Site-Verification identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

## How to check identity

Use Google’s published IP ranges for this crawler class and its forward-confirmed reverse DNS procedure.

## Access and robots.txt

This user-triggered fetcher may ignore robots.txt. Use server access controls for private content.

## What it means in your analytics

A verification-file request may come from a site owner setting up Search Console.

## Useful measures

Requested URLs; Response codes; Redirect chains.

## What to check next

Confirm that the verification file remains available at the expected path.

## Sources

- [developers.google.com](https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers)

Operator facts are source-backed; interpretation and actions are Apostl guidance.

## Related profiles

- [Googlebot](https://apostl.dev/bots/googlebot)
- [Google-Extended](https://apostl.dev/bots/google-extended)
- [Googlebot-Image](https://apostl.dev/bots/googlebot-image)

[Start measuring agent traffic](https://apostl.dev/start/agent-analytics)
