AI crawler · registry

Google-CloudVertexBot

Google · Live retrieval · robots.txt token google-cloudvertexbot

honors robots.txtMeasured across 3,958 sites with a robots.txt policy record for this agent, out of 7,068 on record.
3%
of measured sites block it
114
sites blocking
3,844
sites allowing
yes
honors robots.txt

What it is definition

Crawls sites at a site owner's request to build Vertex AI agents; no effect on Google Search.

Google-CloudVertexBot is operated by Google and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.

Disallowing google-cloudvertexbot stops the fetch that happens when a user asks Vertex AI agents about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

robots.txt token
google-cloudvertexbot
Operator
Google
Purpose
Live retrieval
Honors robots.txt
yes
Documentation
https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers

Identity on the wire exact string

User-agent string
Mozilla/5.0 (compatible; Google-CloudVertexBot; +https://cloud.google.com/vertex-ai-bot)
Verify your own edge is not refusing it
curl -A 'Mozilla/5.0 (compatible; Google-CloudVertexBot; +https://cloud.google.com/vertex-ai-bot)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

How to allow it, how to block it robots.txt

Allow it
User-agent: google-cloudvertexbot
Allow: /

Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.

Block it
User-agent: google-cloudvertexbot
Disallow: /

Disallowing google-cloudvertexbot stops the fetch that happens when a user asks Vertex AI agents about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

Sites that block it 60 shown

DomainAI access scoreRank
amazon.com 33 26
msn.com 34 62
amazonvideo.com 55 121
nytimes.com 67 157
theguardian.com 60 193
bbc.com 69 207
bbc.co.uk 70 226
launchpad.net 49 260
amazon.co.uk 33 318
bloomberg.com 53 358
amazon.de 33 377
amazon.co.jp 33 494
wired.com 74 533
patreon.com 60 543
usatoday.com 55 552
tripadvisor.com 50 564
telegraph.co.uk 45 580
amazon.fr 33 609
amazon.co.za 33 623
dailymail.co.uk 63 627
amazon.ca 33 635
amazon.in 34 659
lemonde.fr 72 671
dailymail.com 63 681
primevideo.com 55 682
amazon.it 33 706
amazon.es 33 725
people.com 38 801
amazon.com.au 33 812
theverge.com 68 815
amazon.com.br 33 833
lefigaro.fr 74 834
investopedia.com 38 913
corriere.it 83 955
theconversation.com 52 1,019
amazon.com.mx 33 1,032
bfmtv.com 71 1,073
vnexpress.net 81 1,196
furaffinity.net 41 1,223
gazzetta.it 79 1,231
vietnam.vn 77 1,272
f95zone.to 49 1,300
iltalehti.fi 50 1,409
newyorker.com 71 1,793
arstechnica.com 74 1,847
themoviedb.org 61 1,984
amazon.eg 34 2,006
vox.com 66 2,189
congress.gov 33 2,293
guardian.co.uk 60 2,299
nrk.no 61 2,325
glassdoor.com 51 2,501
smh.com.au 71 2,530
technologyreview.com 70 2,561
zeit.de 79 2,562
thehill.com 45 2,593
tmdb.org 61 2,656
theglobeandmail.com 59 2,659
newscientist.com 68 2,691
realtor.com 51 2,821

Compare Google

Google runs 5 agents in this registry, and they do different jobs. Blocking one says nothing about the others.

Common questions answered

Does blocking Google-CloudVertexBot remove me from Vertex AI agents?

Partly. Google-CloudVertexBot fetches a page only when a user asks about it, so disallowing it does not delist you from Vertex AI agents. It does mean the answer is composed without your live page, from a stale copy or a third-party summary.

How do I verify Google-CloudVertexBot requests are genuine?

Run a reverse DNS lookup on the source address. It must resolve to a host under googlebot.com or google.com, and a forward lookup of that host must return the same address. Google also publishes its crawler ranges as JSON, so an address match works when reverse DNS is unavailable.

Check your own site free

See whether your robots.txt admits Google-CloudVertexBot today, and whether your edge agrees with it.