What the assistants did with our pages.
Two of the files are our own companies, measured from the day they went live, so you see the method on a site with no history, no backlinks and no paid links. The third is a London firm whose own analytics we show with its name removed. Every number carries its date and source. Index builders and live fetchers are reported separately and never mixed.
Week two up 300% on week one. Read by Amazon Alexa (100%), Meta AI (97%) and Bing (84%). First visitors from ChatGPT on 14 October.
Anthropic 94%, OpenAI 91%. ChatGPT answered from 12 different pages in the first week, once from five pages at a time.
8 tapped the phone number, 3 sent the form, one became a £3,300 instruction. Shown redacted.
An answer served is a person asking an assistant and the assistant fetching our page, right then, to reply: the user agents ChatGPT-User, Perplexity-User, Claude-User, Meta-ExternalFetcher, DuckAssistBot and MistralAI-User in the server log, with fetches by the same assistant from the same address within two minutes counted as one answer. The page it fetched is the topic it used us for. The question text itself is only visible in Bing Webmaster's AI Performance report and Search Console's AI report, so the questions we show are marked likely. Index builders (OAI-SearchBot, GPTBot, ClaudeBot, PerplexityBot, Bingbot, Googlebot and the rest) are counted separately as pages fetched, because a fetch shows a crawl, not index membership.