Known Agents Browser
Known Agents Browser is a general-purpose automated agent operated by Known Agents. The behavior depends entirely on what it is configured to do, so the right response depends on the request pattern, not the user-agent string alone.
Watch what it actually does on your site for a few hours before deciding whether to allow, rate-limit, or block.
If you cannot identify the operator and the traffic is meaningful, treat it as you would any unknown bot: rate-limit, observe, and only block if it misbehaves.
See Known Agents Browser 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
No
IP verification
User-Agent only
Crawl frequency
Variable
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Known Agents runs 3 bots in total. Each one is a separate user-agent so you can allow or block them independently.
DevOps & Monitoring
1Task Automation
1- Known Agents BrowserYou are here
Live-Fetch AI
1Should I let Known Agents Browser through?
Watch your logs for a week first. Behavior varies wildly. Observe the request pattern before allow/block decisions.
Does blocking Known Agents Browser affect my Google rankings?
No. Known Agents Browser is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from Known Agents Browser?
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 Known Agents Browser", not "the traffic is genuinely Known Agents Browser". If you need stronger guarantees, look for a reverse-DNS check or wait for Known Agents to publish IP ranges.
What's the best way to understand what Known Agents Browser is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
How is Known Agents Browser different from Known Agents's other bots?
Known Agents splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Known Agents family above to see which ones actually matter for your site.
What's the cleanest way to control Known Agents Browser?
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.