What is Google-CloudVertexBot?
Google-CloudVertexBot is the crawler Google documents for site-owner-requested crawls used to build Vertex AI Agents. Google lists it among its common crawlers, while Cloudflare classifies it as an AI crawler and identifies Google as the operator in its operator reference.
The request starts with a Vertex AI workflow in which a site owner asks Google to crawl that owner's site. This is narrower than a crawler that discovers arbitrary domains for a public search index. A visit should correspond to content selected for a particular Vertex AI Agent project.
Cloudflare's bot directory records both mobile and desktop Chromium-style User-Agent forms. Each contains the Google-CloudVertexBot substring, and its recorded matching pattern is CloudVertexBot. Chrome version numbers can change, so log rules should match the stable bot token rather than a complete browser string.
Google says preferences for this crawler have no effect on Google Search or any other product. Content it can reach may be available to the Vertex AI Agent being built, but access does not improve organic ranking or make the page visible across public AI search services. Cloudflare describes the purpose as targeted AI training; in this bot that means a site owner supplying its own site for an agent-building task, not documented training of Google's general foundation models.
There is a source conflict about robots.txt. Google's crawler documentation places Google-CloudVertexBot in the common-crawler list, whose automatic crawls always obey robots.txt, and the page metadata records support as true. Cloudflare's bot directory marks followsRobotsTxt as false. A named rule is still the operator-documented control, but sites that require enforcement should confirm the result in logs.
The exact token offers useful classification, not authentication. No Web Bot Auth directory is recorded, and this page does not mark the bot as IP verified. If a request needs privileged access, validate it through the Vertex project or another access mechanism instead of trusting the User-Agent header.
