Anchor-Browser
Anchor-Browser is a headless browser operated by Anchor. It runs full JavaScript and renders pages exactly like a real user, which makes it harder to detect and capable of every interaction a human can perform.
Use cases range from legitimate (test automation, AI agents, browser-based scraping) to abusive (credential stuffing, fake account creation, scalping). Treat each case on the merits of what it actually does on your site.
Blocking by user-agent rarely works for long, since headless browsers can spoof any string. Behavioral signals (rate, sequence of requests, IP reputation) are more reliable.
See Anchor-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
Yes
IP verification
User-Agent only
Crawl frequency
Variable
Honors robots.txt
Often ignored
Honors Crawl-delay
No
Anchor runs 3 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Task Automation
1Agentic Browser
1Headless Browser
1- Anchor-BrowserYou are here
Should I let Anchor-Browser through?
Watch your logs for a week first. Behavior varies wildly. Observe the request pattern before allow/block decisions.
Does blocking Anchor-Browser affect my Google rankings?
No. Anchor-Browser acts on behalf of one specific user at a time, not on behalf of a search index. Classical SEO is unaffected. The trade is whether you want users delegating tasks to Anchor to be able to reach your site.
How do I confirm a request is really from Anchor-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 Anchor-Browser", not "the traffic is genuinely Anchor-Browser". If you need stronger guarantees, look for a reverse-DNS check or wait for Anchor to publish IP ranges.
Can Anchor-Browser take actions on my site, like buying or signing up?
In principle yes. Agentic browsers can fill forms, click buttons, and complete transactions. That is the entire point. If your site leans on automation detection to prevent bots from acting, Anchor-Browser is a different threat model from a passive crawler and you should think about it separately.
How is Anchor-Browser different from Anchor's other bots?
Anchor 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 Anchor family above to see which ones actually matter for your site.
What's the cleanest way to control Anchor-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.