AGI Agent
AGI Agent is a live-fetch agent with no publicly identified operator. It does not crawl the web on a schedule. It hits your site only when an end-user asks the underlying AI a question that requires fresh information from a specific page.
Traffic is bursty and unpredictable. A single trending topic can send hundreds of AGI Agent requests in an hour, then nothing for days. Each request typically reads one or two pages, not your whole site.
Allowing this agent typically improves the chance your content is cited inside AI answers; blocking it means users get answers built from competitors' content.
See AGI Agent on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
Sometimes
IP verification
User-Agent only
Crawl frequency
Burst, user-driven
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Should I let AGI Agent through?
In most cases, yes. Live-fetch agents drive citations inside AI answers. Allowing keeps your content in the conversation. If volume gets noisy, rate-limit it before you block it outright.
Does blocking AGI Agent affect my Google rankings?
No. AGI Agent fetches a page only when a user is actively asking the assistant a question. It has nothing to do with how Google or Bing rank you. The cost of blocking is that the operator can't quote your content in its answer.
How do I confirm a request is really from AGI Agent?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be AGI Agent", not "the traffic is genuinely AGI Agent". If you need stronger guarantees, look for a reverse-DNS check or wait for the operator to publish IP ranges.
Does a AGI Agent visit count as a real user visit?
Sort of. There is a human asking the assistant a question on the other end, but they never load your page in their own browser. They see whatever the assistant quotes back, usually a snippet plus a citation link. Count it as upstream attention rather than as a session.
Why can't I tell who operates AGI Agent?
Some bots run under generic User-Agent strings or are operated by smaller, less-documented companies. The pragmatic default is to treat unverified operators as untrusted traffic. If volume climbs, log the source IPs and check whether they cluster around a single network or ASN. That'll usually surface who's actually behind it.
What's the cleanest way to control AGI Agent?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.