--- title: "Measure AI Search Visibility | Dealership AI Tracking" description: "A practical method for tracking whether ChatGPT, AI Overviews, Perplexity and Copilot mention your store — and what the results mean." canonical: "https://carbidedigital.io/insights/measure-ai-search-visibility" published: "2026-09-01" updated: "2026-09-01" category: "AI SEARCH" author: "Carbide Digital" type: "article" --- # How to tell whether AI systems actually recommend your dealership. AI answers are not rankings. There is no position one, the same question can produce different sources on different days, and a screenshot proves nothing. That does not make it unmeasurable — it makes it measurable differently. Here is a method that produces something you can actually track over time. ## Key takeaways - One screenshot is a single sample from a distribution. A fixed prompt list re-run on a schedule is a measurement. - Record which sources the answer did cite. That is more actionable than whether you appeared. - Definitional questions move first. Commercial recommendations move last, and only after the entity is trusted. ## Why the usual approach tells you nothing Someone asks ChatGPT 'best car dealer in [city]', the store appears, and it goes in a slide. Next week it does not appear and nobody mentions it. Both results are noise, because a single query is one draw from a non-deterministic system. The answer also changes with phrasing, with whether the user is logged in, with location, and with which model version is serving that day. None of that is under your control and all of it moves the result. So the unit of measurement cannot be a query. It has to be a fixed set of queries, run the same way, repeatedly. ## Build a prompt set and freeze it Write thirty to forty questions a real buyer might ask, spread across four types: commercial ('who should I use for…'), definitional ('what is…'), problem-shaped ('why is my… not working'), and brand ('what is [your store]'). Freeze them. The moment you edit a prompt you have started a new time series and lost the comparison. Add new prompts at the bottom instead — the numbering is the contract. Run them across the systems that matter: ChatGPT with search, Google AI Overviews, Perplexity, Copilot, Claude, Gemini. Fresh session, logged out where you can, no memory, and record which location you used because it affects local answers. ## Record four things, not one Whether your store was named. The obvious one, and the least useful on its own. Whether your site was cited or linked. Being mentioned without a citation is worth less — it does not send anyone anywhere. Which sources were cited instead. This is the most actionable column by a wide margin. If three directories own every answer in your market, you now know exactly which corroboration you are missing. Whether anything said about you was wrong. Log it verbatim. Incorrect hours, wrong departments or an invented claim are a business problem, and finding them is half the value of doing this at all. ## Reading the results Expect definitional prompts to move first. A clean definition on a crawlable page is the cheapest thing for a system to quote, and it clears no trust threshold to do so. Brand prompts move next, and they are the entity check. If a system cannot say what your store is, or gets it confused with a similarly named business, the fix is external corroboration — a complete Google Business Profile, consistent listings, a company page that exists — not more content on your site. Commercial prompts move last and slowest. Being named next to a buying recommendation requires enough confidence in the entity to put it there. It follows the other two; it does not lead. ## What to pair it with Branded search volume in Search Console. Most AI referrals arrive with no referrer, so a rise in people searching your name is often the only visible trace. Referral traffic from the assistant domains, where it exists. It undercounts badly, but the direction is informative. Direct traffic to deep pages. Nobody types a URL for a specific service page from memory — that traffic came from somewhere you cannot see. And server logs. Filter for the AI crawler user agents. If they are not fetching your pages at all, no amount of content strategy is the problem — retrieval is. ## What the log looks like in practice A row per prompt, per system, per month. Six columns: date, system, prompt number, named yes or no, cited yes or no, and which sources were cited instead. A spreadsheet is entirely adequate — the discipline matters more than the tooling. Add a seventh column for anything inaccurate, recorded word for word. This is the column that produces immediate business value: a system stating wrong hours, or a service you do not offer, is a problem you can act on this week regardless of any visibility goal. After three months the sources column becomes the most valuable thing you have. It is a ranked list of who currently owns the answers in your market, which tells you precisely which directories, publications and profiles are worth the effort rather than leaving you to guess. ## Direct answers ### How often should we run the prompt set? Monthly. Weekly is noise at this sample size and creates busywork. Establish a baseline before any major change, then measure direction over quarters rather than weeks. ### Can we pay a tool to do this? Several tools track AI mentions and they save time on collection. Check what they actually query and how often before trusting the trend line — a tool using different prompts from yours is measuring a different thing, and switching tools resets your history. ### What if we never appear for commercial prompts? That is the normal starting position and it is usually an entity problem, not a content problem. Check the brand prompts first: if a system cannot describe your business confidently, it will not recommend it. Fix corroboration before writing more pages. ## Primary sources - [Google: AI features and your website](https://developers.google.com/search/docs/appearance/ai-features) - [OpenAI: Publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) ## Related services - [Car Dealer GEO](https://carbidedigital.io/car-dealer-geo) - [Dealership AEO](https://carbidedigital.io/dealership-aeo) - [Dealer AI SEO, GEO & AEO](https://carbidedigital.io/car-dealer-ai-seo) --- Source: [https://carbidedigital.io/insights/measure-ai-search-visibility](https://carbidedigital.io/insights/measure-ai-search-visibility) Publisher: Carbide Digital — team@carbidedigital.io Editorial standards: https://carbidedigital.io/editorial-standards Research methodology: https://carbidedigital.io/research-methodology