---
language: en
title: "Google-Agent"
description: "Google-Agent identifies visits by agents hosted by Google that browse and act at the user's request. Learn how to verify their origin and define permissions."
canonical: "https://tropk.ai/en/resources/glossary/google-agent"
last_modified: "2026-10-12T16:11:20.487Z"
---

# Google-Agent

Reviewed on 2026-10-06.

## What it means

Google-Agent is an identifier used by agents hosted on Google's infrastructure to browse the web and take actions at users' request. The documentation lists desktop and mobile User-Agent versions and publishes a specific list of source addresses. The token describes this delegated access without identifying, by itself, which task was requested.

## Why it matters for marketing

A marketing team needs to distinguish a delegated request from [crawling](/en/resources/glossary/crawling) to build an index. The purpose changes how logs are interpreted and how site barriers are assessed. Since visits in this category generally ignore [robots.txt](/en/resources/glossary/robots-txt), a rule in that file should not be treated as an authentication control or authorization to perform operations.

## Example in practice

In a hypothetical test, someone asks an agent hosted by Google to check the visiting hours published by a museum. The log shows Google-Agent accessing the hours page shortly after the request. The team links the visit to the delegated request and avoids counting it as evidence that the page was added to the [Search index](/en/resources/glossary/search-index).

## How to apply or verify

To verify the request for the visiting hours, associate the test request with the URL, the time of access, and the HTTP response received. The technical team should compare the source against the official user-triggered-agents.json list or the verification method indicated by Google. The User-Agent declares an identity but does not authenticate the source. If there is a restricted area, review its controls separately; the token does not grant an authenticated session.

## Important distinctions

Google-Agent is not an alternate name for [Googlebot](/en/resources/glossary/googlebot) or a universal specification for agents. The cited documentation describes browsing and actions at a user's request, but does not list every task or permission for each product. A confirmed visit verifies that request; it does not prove the task was completed, a purchase was authorized, a public [citation](/en/resources/glossary/ai-citation) was made, or the search index was updated.

## Sources and references

- [List of Google user-triggered fetchers](<https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers>) — Google
- [Verify requests from Google crawlers and fetchers](<https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests>) — Google

## Continue a leitura

- [Googlebot](</en/resources/glossary/googlebot>)
- [User agent](</en/resources/glossary/user-agent>)
- [robots.txt](</en/resources/glossary/robots-txt>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)