What is Anchor Browser?
Direct Answer: The Anchor Browser is a web browser for AI agents, operated by Anchor, used for automating workflows and web interactions.
The Anchor Browser is a platform for AI agentic browser automation, designed to solve the challenge of automating workflows for web applications with limited or no API coverage. It enables the creation, deployment, and management of browser-based automations, transforming complex web interactions into simple API endpoints.
User-Agent Identification
The following user-agent strings identify Anchor Browser in your live traffic data:
Anchor Browser
robots.txt Rules for Anchor Browser
Respects robots.txt: No
This bot does not commit to following robots.txt
Anchor Browser does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.
Need continuous verification across 500+ bots? Can AI See It automates this.
Crawl Behavior
Frequency:Not Documented
Request Pattern:Not Documented
JavaScript Rendering:Yes — this bot can execute JavaScript and render pages.
Crawl Activity Index
Relative crawl activity for Anchor Browser over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.
View recent activity data (last 7 days)
| Date | Activity Index |
|---|---|
| Mar 26, 2026 | 88.0 |
| Mar 27, 2026 | 82.7 |
| Mar 28, 2026 | 83.1 |
| Mar 29, 2026 | 81.8 |
| Mar 30, 2026 | 87.3 |
| Mar 31, 2026 | 90.2 |
| Apr 1, 2026 | 88.9 |
Source: Cloudflare Radar
Why track Anchor Browser traffic?
Measure what Anchor gives back. Anchor Browser takes your content for AI training — but does Anchor send any traffic in return through other products? Track whether the trade-off is worth it before deciding to block.
Understand what content is being collected for AI training. Anchor Browser crawls your site to gather data that may train AI models. Tracking its activity reveals which pages are selected — and which are skipped.
Make an informed block-or-allow decision. Blocking Anchor Browser prevents your content from being used in future model training. But first, measure the volume: how many pages does it fetch, how often, and does Anchor send any referral traffic through other products?
Detect content harvesting patterns. If Anchor Browser is systematically crawling your highest-value content (product pages, proprietary research, premium articles), you may want to restrict access using robots.txt or server-side rules.
What does Anchor Browser crawling actually cost you?
AI training bots like Anchor Browser collect your content to improve future AI models. Unlike AI search bots, there's no direct referral pipeline — Anchor Browser doesn't cite sources or send traffic back to your site.
What you give
- Server resources for every crawl request
- Your content, expertise, and original research
- Data that improves a competing AI product
What you get back
- No direct referral traffic from Anchor Browser
- No attribution in AI model outputs
- No revenue share from model usage
This doesn't automatically mean you should block Anchor Browser. But you need to measure the real cost before deciding. Anchor may send traffic through other products (Anchor's AI products) — blocking the training bot might not affect referrals at all, or it might. Only log data tells you.
What Can AI See It measures for AI training bots
How many pages Anchor Browser fetches from your site
Which pages and sections Anchor Browser prioritizes
Do Anchor's OTHER products send you traffic?
Does Anchor Browser actually respect your robots.txt?
How is this different from prompt testing tools? Prompt testing checks if AI mentions your brand in simulated queries. Can AI See It measures what actually happens: real crawls, real referrals, real conversions — from your live traffic data.
Read: Why live traffic monitoring beats prompt testing →Log Verification
To verify Anchor Browser traffic in your live traffic data:
- Search access logs for the user-agent strings listed above
- Check if the IP addresses match documented ranges (if provided by Anchor)
- Verify the crawl pattern matches documented behavior
- Use reverse DNS lookup for additional verification if available
Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.
Undocumented Information
The following information is not officially documented for Anchor Browser:
- crawl frequency
- request pattern
- IP verification
- JavaScript rendering details
Measure your Crawl-to-Referral Ratio for Anchor Browser
See how much traffic Anchor actually sends back to your site relative to how much content Anchor Browser takes.
- Connect Anchor Browser crawls in your logs with referral sessions in analytics
- Calculate your CRR — the metric prompt testing tools can't provide
- Make data-driven block/allow decisions for every AI bot
Measure business impact from Anchor Browser
The question isn't just whether to block Anchor Browser — it's what you lose or gain from its crawling activity.
- Crawl volume: how many pages Anchor Browser collects from your site
- Content value: which content categories are targeted most
- Cross-platform CRR: does Anchor send traffic through other products?
- Referral tracking: Anchor Browser takes — measure what Anchor gives back. Track actual visits arriving from Anchor's products to your site.
Based on your live traffic data and analytics — not synthetic prompt tests.
Official Documentation
View Official Anchor Browser Documentation →
Information sourced from official documentation. Content generated with AI assistance.