# Google-Agent

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

## What is Google-Agent?

Navigates websites for user-requested actions on Google infrastructure.

## How to identify it

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

## How to check identity

Match the source IP with Google’s user-triggered-agents.json, rather than the common crawler list. Google also documents experimental Web Bot Auth under agent.bot.goog.

## 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 navigation sequence can include several pages within one delegated task.

## Useful measures

Requested URLs; Response codes; Redirect chains.

## What to check next

Review the sequence and completed actions separately from raw request counts.

## 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)