Ahrefs Brand Radar gets found because the page names the category, explains the data asset, and is surrounded by supporting documentation. Its weaker spot is that the strongest methodology detail lives off the product page.
The page and what it is trying to rank for
The target page is Ahrefs' Brand Radar product page at https://ahrefs.com/brand-radar. The page is trying to own queries around AI visibility tracking, brand visibility in AI search, AI citations, and prompt-based monitoring.
The opening message is direct: Brand Radar helps users see how a brand shows up in AI search. The page also makes the dataset the hook, with hundreds of millions of prompts across AI Overviews, AI Mode, ChatGPT, Copilot, Gemini, Perplexity, and Grok.
That is good AEO structure. The entity is clear, the category is clear, and the measurable object is clear: mentions, citations, prompts, and visibility across AI answers.
What are answer surfaces doing right now?
This run used accessible web search results as a proxy because direct logged-in answer-engine querying was not available. The raw data is stored at experiments/2026-05-07-teardown-raw.json.
For branded queries such as "Ahrefs Brand Radar AI visibility," the target page surfaced strongly. For explanatory queries such as "what is Ahrefs Brand Radar AI visibility tool," Ahrefs' help-center page and methodology page also appeared. That is healthy because answer systems often prefer explanatory documentation over product pages.
For broader tool-list queries, the product page still appeared, but competitors such as AnswerRadar and CiteRadar also showed up. That means Ahrefs has clear branded retrieval, but the broader category remains contested.
What does the page do well?
The page states the product category in plain language. "See how your brand shows up in AI search" is a citable proposition because it names both the user goal and the search surface.
It also gives concrete platform coverage. Listing AI Overviews, AI Mode, ChatGPT, Copilot, Gemini, Perplexity, and Grok helps retrieval systems connect the page to platform-specific queries.
The supporting ecosystem is strong. The help-center page defines Brand Radar, the methodology page explains how prompt data is collected and modeled, and the Octopus Energy case study shows a practical use case. That creates a cluster of retrievable pages rather than a lonely product page.
What is holding it back?
The product page could bring more methodology detail above the fold. The most citation-worthy claims about prompt construction, People Also Ask inputs, semantic fanout, and response storage live mainly in the methodology article.
That is not fatal. It may even be intentional. But for answer engines, the best product page would include a short "How the data is built" section with links to the full methodology.
The page also uses large numeric claims. Those are useful, but they need nearby explanations. When a page says it tracks hundreds of millions of prompts, an answer engine needs to know whether those are live prompts, modeled prompts, monthly prompts, stored responses, or query variants.
What should Ahrefs change?
Ahrefs should add a compact methodology block on the product page. The block should answer four questions: where prompts come from, which engines are checked, how often data is refreshed, and what the metrics do not mean.
It should also add a comparison table for the three terms users are likely to confuse: mention, citation, and impression. Those are the units AEO teams need to explain internally.
Finally, it should add one example workflow on the product page itself: "Find competitor citations, inspect cited pages, identify missing third-party sources, assign a content or PR action." That would make the page more useful for non-branded category prompts.
What readers can copy
Use one canonical product page, one methodology page, one help page, and one case study. That cluster gives answer systems multiple ways to understand the same product.
Do not put all proof on the product page. Do make sure the product page summarizes the proof and links to it.
Define your metrics in visible text. If your AEO product uses "share of voice," "mentions," "citations," or "impressions," explain each term in one sentence.
What to do Monday morning
1. Add a "How our data is built" section to any AEO product page. 2. Define the metrics in plain language near the first mention. 3. Link from the product page to methodology, help docs, API docs, and customer examples. 4. Add a comparison table for your product versus manual prompt testing. 5. Run branded, category, and competitor prompts separately when auditing visibility.