This lesson is about reading AI-visibility data without fooling yourself. It separates the question that data answers reliably today — who is cited alongside you — from the harder one — who owns a topic — and shows how easily the second produces a confident, wrong answer.
What this lesson covers
- Two different AI-visibility questions
- The reliable scoped view
- Configuring a topic-level query
- The contamination trap
- Sanity checks before reporting
- Labelling confidence in client reports
Three topic queries on the demo site’s own subjects, run with loose matching, returned plausible lists of real domains — and all three were wrong. “Semantic SEO” returned sources about semantic HTML, “machine learning for SEO” returned job boards, and “entity SEO” returned company-formation sites, because the matcher could not tell the topic from a homonym. None of the results were empty; all of them looked healthy. The lesson explains why that failure is so easy to miss and links it to the corpus problem from Lesson 2.1: the pipeline ran perfectly and measured something other than what was asked.
It then sets out three checks — read the names, open a sample of the underlying answers, and test a query whose competitive set you already know — and a four-tier labelling convention for reports: scoped results are reported, verified topic results are reported with their method, default-configuration topic results are not reported or are clearly marked indicative, and every AI-visibility number is dated. Two practicals follow: one with the exact query settings and a script that formats and checks queries, and one on structuring an AI-visibility report.
The scoped view on the demo site is the part to trust today: seventeen AI mentions, fourteen on Google and three on ChatGPT, with Surfer SEO, learningseo.io and YouTube cited alongside it. The lesson explains why that scope constrains the answer for you, and why the topic-level view needs calibrating before it can be reported at all.
Its closing argument is that saying a number is indicative, and why, is an advantage rather than a weakness. Most AI-visibility charts in circulation come from default settings nobody checked; the consultant who labels their confidence is the one whose numbers are still standing a quarter later.
This lesson continues Module 4 of The AI-powered Entity Audit. It suits anyone buying, running or presenting AI-visibility data who wants numbers that survive a client’s questions.