What BotVisibility does
You enter a URL; we fetch that public website and analyze how visible and usable it is to AI agents, then show you a report. There are no accounts and no sign-up to scan.
Part 1: The website (botvisibility.com)
Analytics
The website uses Google Analytics to understand how many people visit, which pages they view, and where traffic comes from — standard business measurement.
What Google Analytics collects:
- Pages visited and time spent on the site
- General geographic region (country or city level, not precise location)
- Referral source (how you found us)
- Device type and browser (e.g. “Chrome on Windows”)
- Anonymous, aggregated usage patterns
What it does NOT do:
- No advertising or remarketing profiles are built from your visit
- No personal identification (we don’t know your name, email, or identity)
- No cross-site tracking or behavioral targeting
- No data is sold to third parties or used to target you with ads anywhere
The URLs you scan
When you run a scan, we process the URL you submit so we can fetch and analyze that public website. We may cache a scan’s results by URL so the same site loads faster next time — that cache is keyed to the website address, not to you. We don’t build a history of what you personally scanned.
Keeping the free tier fair (rate limiting)
The scan API is free up to a daily allowance. To enforce that, we keep a simple per-day counter tied to a value derived from your network (IP) address — a count (“this caller has run N scans today”), not a profile. It resets daily and isn’t used to identify or track you across the web.
Cookies
Google Analytics sets standard analytics cookies to tell unique visitors and sessions apart. They don’t identify you personally and aren’t used for advertising. You can opt out across all websites with the Google Analytics Opt-out Browser Add-on.
Part 2: Paid scans for agents (x402)
Autonomous agents can pay per scan in USDC on the Solana blockchain via the open x402 protocol (through pay.sh). We don’t collect names, emails, or card details for this — payment is a blockchain transaction. Note that blockchain transactions are public by nature: the payment amount and wallet addresses are recorded on a public ledger we don’t control. On our side, we only see that a valid payment arrived for a given scan.
Third parties we rely on
To run the service we use a small set of providers, each for one job:
- Google Analytics — website traffic measurement
- Netlify / Fly.io — hosting
- Turso — the per-day scan counter
- thum.io — website screenshots shown in reports
- pay.sh / Solana — agent payments
We don’t sell your data to anyone, and we don’t share it beyond what these providers need to do their job.
The CLI, WordPress plugin, and MCP server
- The CLI runs on your own machine and scans the URL or local repo you point it at; it doesn’t send us your code.
- The WordPress plugin runs on your own site.
- The MCP server answers tool calls about scans and requires no account.
Changes
If we change this policy, we’ll update this page and the date above. Our basic approach — no accounts, no selling data, minimal collection — is foundational and unlikely to change.
Contact
Questions about privacy? Reach us through our contact page.