Reading is not recommending in AI search
An AI assistant reading your site is not a recommendation. A crawler fetching a page simply means the assistant can see your work, not that anyone chose you. We keep AI reads and AI visits apart because reading is not recommending.
Understanding the difference
When an AI assistant fetches a page on your site, that is a read. A person arriving on your site from an assistant's answer is a visit. The two are different events, so we count them separately and never add them together.
What crawlers do
A crawler is simply a software tool that fetches pages so an engine can index them. A crawler can fetch your pages ahead of time to build an index, or during a conversation to answer a question. We can see that a page was fetched during an interaction, but we cannot see the exact prompt that triggered the fetch. A read shows an assistant can see your page; it does not mean a buyer or seller chose you.
Proof of a recommendation
True evidence of a recommendation is concrete and measurable. You need to see your name explicitly stated in an answer we recorded, or you need to track a visit that arrived directly from one of those responses. We tested responses across 4 assistants to understand how frequently names appear in real queries. Out of all the answers we read, 97.2 percent named at least one agent or team. So an assistant asked for an agent almost always answers with names; the question is whether yours is one of them.
Viewing your numbers
Your dashboard keeps your website statistics, your AI reads and your AI visits apart, beside your monthly report and where you stand on ChatGPT, Perplexity, Gemini and Google AI Overviews.
Questions
Where can I see my visits and reads?
In your dashboard: website statistics show AI reads and AI visits as separate numbers, beside your monthly report.
How often are my metrics updated?
Where you stand on the four engines is measured monthly on a solo plan and weekly on a team seat, and your monthly report shows what changed since the last one.