AI search visibility has become the new vanity metric, and most teams are measuring the wrong number. The AI visibility tools multiplying across the market count how often a model mentions you, or cites you, when someone types a prompt. That number feels like progress because it looks like the rank tracking we have done for 20 years. It is not the same thing, and the gap between what these tools count and what actually moves your business keeps widening. This is a guide to the metrics that matter in AI search, the ones that only look like they matter, and how to tell them apart, built from six No Hacks podcast conversations with people who do this for a living and the data that landed this month.<\/p>\n
The dominant way to measure AI search right now is prompt tracking, and as most teams use it, it is the wrong instrument. The pitch is familiar: a tool types a set of prompts into ChatGPT, Perplexity, and Google\u2019s AI Overviews<\/a>, and reports how often your brand shows up. It looks like rank tracking, so it sells. I get more pitches every week from companies that built one and want to come on the podcast. There are far more of them than the market needs, and the attention is rushing toward the most visible, most obvious thing to count, whether or not it is the thing that matters.<\/p>\n Jono Alderson, a technical SEO<\/a> consultant, put the objection this way when he came on the show. \u201cWe need to instead try and influence how the machine perceives us. And that\u2019s not prompt tracking, which is what everyone is doing at the moment,\u201d he said. \u201cThere is a place for that, but it\u2019s far smaller than I think.\u201d His diagnosis of why these dashboards feel off is sharper still: \u201cIt\u2019s copy-paste the current modality of rank tracking into a new thing. It doesn\u2019t really fit, but it\u2019s better than nothing.\u201d<\/p>\n Prompt tracking also rests on a guess about user behavior that mostly is not grounded. You invent a list of prompts you hope your customers type, then measure yourself against them. For most brands, that list has little to do with what real people are actually asking, and an AI prompt is not a keyword. Ground those prompts in real search data instead, and you hit a second problem: AI is corrupting that data faster than you can read it.<\/p>\n I have a first-hand reason. Last year, I helped investigate a strange leak: real users\u2019 ChatGPT prompts were turning up inside Google Search Console<\/a>, the report website owners use to track search traffic. I worked on it with the analytics consultant Jason Packer, who published the findings on Quantable, and Ars Technica, and a long list of outlets covered it. We traced it to a bugged prompt box that made ChatGPT search almost every time, with a ChatGPT URL leading the queries that Google<\/a> then tokenized, so websites ranking for those terms saw strangers\u2019 private prompts in their dashboards. My own concern at the time, which Ars Technica quoted, was that the leak was contributing to \u201ccrocodile mouth\u201d in Search Console, the pattern where impressions spike while clicks dip.<\/p>\n The leak was the visible version of a problem that is now everywhere and impossible to see. AI systems hit Google constantly to ground their answers, fanning a single prompt out into several parallel queries and reading results no human ever lays eyes on. Every one of those searches lands as an impression on the pages that rank for it. So when your impressions climb while your clicks do not, that is not rising human demand.<\/p>\n","protected":false},"excerpt":{"rendered":" AI search visibility has become the new vanity metric, and most teams are measuring the wrong number. The AI visibility tools multiplying across the market count how often a model mentions you, or cites you, when someone types a prompt. That number feels like progress because it looks like the rank tracking we have done […]<\/p>\n","protected":false},"author":7,"featured_media":83816,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/64032.png","fifu_image_alt":"AI Search Visibility: Citations Are Not Recommendations","footnotes":""},"categories":[31],"tags":[],"class_list":["post-64032","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/64032.png","fifu_image_alt":"AI Search Visibility: Citations Are Not Recommendations","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/64032","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=64032"}],"version-history":[{"count":0,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/64032\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/83816"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=64032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=64032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=64032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}