Check my connection

AI & bot directory · Other

Google user-triggered fetchers: what it is, how to verify it and how to block it

Google user-triggered fetchers is run by Google. Fetch a page because a person asked a Google product to, for example a feed reader or a site verification.

Key facts

Key facts
Operator
Google
Category
Other
robots.txt name
It has no single robots.txt name; Google lists several user agents in its documentation.
Follows robots.txt
Problem: Generally no
Can it be verified?
OK: Yes, by IP ranges and reverse DNS
Official documentation
Registry checked
Nov 11, 2026

User agent

It has no single robots.txt name; Google lists several user agents in its documentation.

Google doesn't publish a full user-agent string; look for Google user-triggered fetchers in the user agent.

Can you verify Google user-triggered fetchers?

Yes Google publishes the IP addresses Google user-triggered fetchers uses. We download that list every 6 hours: our copy is from Nov 20, 2026 and has 1612 entries; Google dated it Nov 20, 2026.

Its addresses also have reverse-DNS names under gae.googleusercontent.com, google.com; a name only counts if it points back to the same address.

Check an address from your logs

Does Google user-triggered fetchers follow robots.txt?

Generally no Google says Google user-triggered fetchers generally ignores robots.txt, because a person asked for the page. To keep it out, you need a firewall rule.

“generally ignore robots.txt rules”

How to block or allow Google user-triggered fetchers

It has no robots.txt name of its own; Google's documentation explains which user agents it uses.

robots.txt is a request, not a lock. To enforce a block, add a firewall or CDN rule. Because Google publishes Google user-triggered fetchers's addresses, a rule can match them exactly, so a fake Google user-triggered fetchers can't slip through as the real one.

How often does Google user-triggered fetchers visit?

Google doesn't publish how often Google user-triggered fetchers visits a site, and iplover doesn't see your traffic. Your own access log is the only reliable count: paste it into the log checker, which counts each crawler's visits and flags fakes, in your browser.

Official documentation

developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers

Registry checked Nov 11, 2026. The address lists are downloaded every 6 hours.