Google has published a help page on how website owners can let Google-Agent traffic through their security tools. If your website sits behind Cloudflare, a hosting firewall or a security plugin, here is what Google-Agent is, what Google’s page says, and what to ask the person who manages your website.

Key takeaways

First, three quick definitions

User agent: the name a browser or bot gives your website when it asks for a page.

CDN: a content delivery network, a service that sits in front of your website to speed it up and often to filter traffic.

Firewall or bot filter: a security layer (from your host, your CDN or a plugin) that blocks or challenges visitors it thinks are automated, for example with a CAPTCHA.

What Google-Agent is

Google describes Google-Agent as the name used by agents hosted on Google infrastructure to “navigate the web and perform actions upon user request.” In plain terms, a person asks a Google AI agent to do something, and the agent visits websites to get it done.

Google lists Google-Agent among its user-triggered fetchers: tools that fetch pages because a user asked, not because Google is crawling the web. That same list says user-triggered fetchers generally ignore robots.txt rules, because a user requested the fetch. So the setting that matters here is usually your firewall or bot filter, not your robots.txt file.

Google’s page does not say which Google products use Google-Agent, and it does not connect Google-Agent to search rankings.

Does this affect your business?

It may, if your site uses a security layer that challenges or blocks automated visitors. Google’s page lists the kinds of steps an agent may take on a site: on-site search, filtering, opening detail pages, add-to-cart and booking, plus the behind-the-scenes requests those features make. For a local service business, the parts that matter most are usually your booking tool, your contact or quote form and your service pages.

Google’s troubleshooting list also names common causes of blocks: broad blocks on cloud or data center networks, managed bot rules, and policies that block a whole category of AI agents. Google says these can override a verified bot setting.

Google’s page is written for sites that run one of these security tools. If your site has none, there may be nothing to change. Either way, this is technical housekeeping that sits next to the basics in our small business SEO guide, not a ranking factor.

How Google says to recognize Google-Agent

Google gives three checks:

Google also cautions that a user agent string can be faked, which is why the name alone is not enough.

What Google says to do in your firewall or bot filter

Google says some bot-detection services, CDNs and firewalls already offer a way to verify Google-Agent requests and allow them, and it points you to your provider for the exact steps. If your service does not verify them automatically, Google lists these rules:

  1. Check the name. Confirm the User-Agent header contains Google-Agent.
  2. Check the address. Confirm the IP address is in user-triggered-agents.json.
  3. Check the signature if there is one. Verify the signature headers the way Google’s Web Bot Auth page describes.
  4. Skip bot challenges for requests that pass. Everything else your security tool blocks stays blocked.

If Google-Agent is still blocked

Google’s troubleshooting section lists six things to check. In plain words:

What to ask whoever manages your website

Frequently asked questions

What is Google-Agent?

Google says it is the name used by agents hosted on Google infrastructure that browse the web and take actions when a user asks them to. Google lists it among its user-triggered fetchers.

Does Google-Agent affect my search rankings?

Google’s page does not say so. It is about letting agents that act for a user reach your site, not about crawling for Search.

How do I know a visit really comes from Google-Agent?

Google says to confirm the User-Agent header contains Google-Agent and the IP address is in its user-triggered-agents.json file. Some requests are also signed through Web Bot Auth.

Should I turn off my firewall or bot protection?

No. Google’s advice is to verify Google-Agent requests and skip bot challenges for those verified requests only, while keeping your other security controls in place.

Related reading: our note on the Google tag becoming a Tag Manager container, another Google change to check with your web person this month. Sources: Google’s help page on allowing Google-Agent traffic (last updated November 17, 2026, per the page), its list of user-triggered fetchers and its page on Web Bot Auth, all read on November 18, 2026.

Not sure whether your firewall or security plugin lets Google-Agent through? Bright Marketing Solutions, with offices in Brooklyn, NY and Dumont, NJ, can review your site’s setup with your web person.


About the author

Paul Taramona is the founder of Bright Marketing Solutions, a Brooklyn-based digital marketing agency he started in 2015 to give small businesses across New York and New Jersey the kind of marketing programs that actually move the needle on revenue. Over the past decade, Paul and his team have built and run campaigns for HVAC companies, dental practices, plumbers, contractors, law firms, accountants, and real estate agents - combining technical SEO, web design, email and SMS automation, direct mail, social media, content marketing, and AI-driven personalization into integrated programs that produce measurable lead flow.

Paul writes about what is actually working in small-business marketing in 2026: practical playbooks tested on real client accounts, not theory pulled from a textbook. He focuses on what each industry actually needs - HVAC marketing looks nothing like dental marketing, and a contractor's funnel looks nothing like a law firm's. If you run a small business in NY or NJ and want a marketing program built around how your buyers actually buy, reach him at paul@brightmarketingsolutions.com or schedule a free discovery call.