Tag: AI visibility tracking

This is the third piece in our series on how AI platforms decide who gets cited. The first looked at how much AI referral traffic ChatGPT controls. The second looked at how selective it is about which sources it trusts. This one asks the practical follow-up: if two of the biggest AI platforms disagree this much about sources, what does that do to the way you measure visibility?

The headline number is that only about 11% of domains are cited by both ChatGPT and Perplexity. It has been repeated in dozens of articles this year, usually with a sentence claiming that single-platform tracking leaves 89% of your visibility invisible. That last part goes further than the data supports. The 11% figure is real and worth acting on, but it is also easy to misread, and several of the studies stacked underneath it measure different things. Here is what each one actually found, and what it means for how you track your brand.

Where the 11% comes from

The figure appears in three related but distinct places, and they are not the same study repeated three times.

The first is a dataset of 680 million citations covering August 2024 to June 2025, analyzed by Profound and cited in Averi’s B2B SaaS benchmark report. Averi’s report states that only 11% of domains are cited by both ChatGPT and Perplexity. Worth noting: the 680 million analysis is Profound’s work, and Averi uses it as a supporting reference rather than presenting original research of its own. Several articles online attribute the analysis to Averi directly, which is a small but real attribution error.

The second is a Qwairy analysis of 118,000 AI responses collected between January and March 2026 across ChatGPT, Perplexity, Google AI Mode, and Claude, which Whitehat SEO cites in its own comparison. It found that only 11% of cited domains appeared across multiple platforms. That is a slightly different measurement from the first one. It looks across four platforms at once instead of comparing ChatGPT and Perplexity as a pair, so the matching 11% is a coincidence of two different methods, not one result confirmed twice.

The third is a Wellows study of 22.7 million citations across 1.15 million questions, covering January to June 2026. It approaches the same question from the opposite direction and reports that 89% of websites ChatGPT cited on a given question were never cited by Perplexity on that same question. That is essentially the mirror image of the 11% figure, measured at the website level, on identical questions.

So three datasets, three time windows, and two different definitions of overlap all point the same way: the two platforms draw on substantially different sets of sources. That agreement is the meaningful finding. The exact percentage matters less than the direction.

What the 11% does and does not mean

Now for the overreach. A low overlap between two platforms’ cited domains does not mean 89% of your potential visibility is hidden from you. Authority Tech, which curates and compares these studies, states explicitly that the figure does not imply that. There are three reasons.

First, the overlap is measured across all domains cited, not across your domain. Your brand could appear consistently on both platforms while the rest of the web fragments around you. The 11% describes the whole citation landscape, and your own footprint inside it is a separate question.

Second, Wellows itself is careful about this. Its authors describe the gap as a different candidate pool rather than a more unpredictable engine, and they point out that the number measures which sources answer a particular question, not which websites are permanently available to each platform.

Third, overlap depends heavily on how strictly you match. Wellows reports different results at website level, page level, and with different levels of address cleanup. A percentage that moves that much with the matching rule should be read as a range, not a fixed law.

The accurate version of the claim is narrower and still useful: if you only measure one platform, you are measuring a different slice of the web than the one your buyers see on the other. That alone is reason enough to change how you track.

A different 12% that gets mixed in

Ahrefs published a widely quoted 12% figure that often gets bundled into this conversation, and it deserves separating out. Ahrefs analyzed 15,000 long-tail queries in a study published on August 11, 2025, and found that only 12% of URLs cited by ChatGPT, Gemini, and Copilot also ranked in Google’s top 10 for the same prompt. The measurement compares AI citations with Google rankings. It does not compare one AI platform with another.

The Ahrefs data does contain a useful platform-level detail, though. Perplexity’s overlap with Google’s top 10 was 28.6%, far higher than ChatGPT at around 8%. So Perplexity leans on pages that also rank well in traditional search, while ChatGPT draws more heavily from pages that do not. Placed next to the 11% cross-platform figure, that goes a long way toward explaining why the two platforms disagree. They are retrieving from different places.

For anyone doing search engine optimization alongside AI visibility work, this is the important takeaway. Ranking well in Google helps you with Perplexity noticeably more than it helps you with ChatGPT. Treating them as one channel with one strategy will over-serve one and under-serve the other.

The same brand, very different results

Two more datasets show what this looks like at the brand level, and both are better evidence for multi-platform tracking than the 11% headline.

Superlines analyzed 34,234 AI responses across 10 platforms between January 14 and February 13, 2026, and reported a 615x gap in citation volume between the highest-citing platform, Grok at a 27.01% citation rate, and the lowest, Claude, at close to zero. The number is striking, but it needs context. It reflects how differently each platform handles linking out to commercial brand sites, which is partly a product design difference and not purely a measure of how much each platform likes any given brand.

Slate HQ published a 90-day study on March 30, 2026, tracking six B2B SaaS brands across ChatGPT, Perplexity, Gemini, Claude, Google AI Overview, and Google AI Mode, with more than 300,000 citation data points. Its central finding is that 76.3% of all citations went to domains that were neither the brand nor its direct competitors. Most of the visibility lives on third-party sources.

The per-platform breakdown Slate published for one email security client illustrates the spread. Brand-owned citation share was 10.2% on Google AI Mode, 10.0% on Google AI Overview, 9.1% on Claude, 6.9% on Gemini, 6.8% on Perplexity, and 4.5% on ChatGPT. Those are the numbers for one client, not an average across all six brands, and it would be wrong to say ChatGPT was the weakest platform for every company studied. But the spread within that single brand, more than double between the highest and lowest platform, makes the point clear. The same company can look strong on one platform and weak on another during the same 90 days.

Slate also found that Claude had the narrowest external source pool at 54% unidentified sources, while Perplexity cast the widest net at 67.7%. Different platforms are not just citing different pages. They are behaving differently in how broadly they search.

What to do with this

The practical response is not to panic about an invisible 89%. It is to stop treating AI visibility as a single number.

Track each platform separately. A blended score hides exactly the variation the studies above describe. At a minimum, report ChatGPT, Perplexity, Google AI Overviews, and Claude as separate lines, and watch each for movement independently. This is the foundation of any serious generative engine optimization program.

Identify which sources each platform trusts in your category. Since most citations go to third-party domains, your visibility depends on where you are mentioned as much as on what you publish. Check which review sites, directories, and community platforms each engine leans on for your topics, then look at whether you are present there.

Match your optimization to the platform. Because Perplexity correlates more strongly with Google rankings, traditional ranking work supports it. ChatGPT draws from a broader mix, so entity clarity, third-party mentions, and presence on the sources it favors carry more weight. This is where generative engine optimization and answer engine optimization diverge in practice, even though they are often discussed as one thing.

Set a baseline before changing anything. Record your citation presence per platform for a fixed set of prompts this week, then repeat monthly. Without a starting point, you cannot tell whether a change came from your work or from platform variability.

Treat every overlap statistic as a range. Different matching rules produce different percentages, and the sample sizes, time windows, and definitions vary. Use the studies to understand direction, then validate against your own prompts.

Where this leaves you

Only 11% of domains being cited by both platforms is a real signal, backed by three independent datasets using different methods. It does not mean 89% of your visibility is lost, and it is not the same as the Ahrefs 12% figure, which compares AI citations with Google rankings. What it does show is that ChatGPT and Perplexity behave like separate channels with separate source preferences, and that measurement built around one will miss what the other is doing. Track them separately, benchmark against a baseline, and treat the percentages as direction, not precision. That is the discipline answer engine optimization now demands.

Frequently Asked Questions

1. Is it true that only 11% of domains are cited by both ChatGPT and Perplexity?
Answer: Yes, that figure appears in several studies, including a 680 million citation dataset analyzed by Profound and a Qwairy analysis of 118,000 responses. Definitions differ slightly between studies, so treat 11% as an approximate indicator of low overlap, not an exact constant.

2. Does this mean 89% of my AI visibility is hidden if I only track one platform?
Answer: Not exactly. The 11% describes overlap across all cited domains, not your own brand. It does show that each platform draws on a different pool of sources, so single-platform tracking gives you an incomplete picture.

3. Is the Ahrefs 12% the same statistic?
Answer: No. Ahrefs found that only 12% of URLs cited by ChatGPT, Gemini, and Copilot also rank in Google’s top 10 for the same prompt. That compares AI citations with Google rankings, not one AI platform with another.

4. Which platform gives brands the highest citation share?
Answer: It depends on the brand and category. In Slate HQ’s example for one email security client, Google AI Mode and AI Overview were highest and ChatGPT was lowest. That is a single-client result and should not be generalized to every company.

5. What does the 615x citation gap mean?
Answer: Superlines found a 615x difference in citation volume between the highest platform, Grok, and the lowest, Claude, across 34,234 responses. It reflects how differently platforms link to commercial sites, so it shows platform behavior more than brand preference.

6. What should I track first?
Answer: Start with a fixed list of prompts your buyers actually ask, then record whether your brand is cited on ChatGPT, Perplexity, Google AI Overviews, and Claude separately. Repeat monthly and compare against that baseline.

If you want to see where your brand stands on each platform, not just one, that is exactly what we cover in a free AI Visibility Audit.

On August 26, a Google spokesperson confirmed what SEOs had already been spotting in the wild since late June. Search result links are being rewritten to route through google.com/goto before landing on the actual destination page. Google’s stated reason was procedural: it said it regularly deploys technical measures to protect its services and users from evolving abuse. This sits alongside a separate legal fight, Google’s suit against SerpAPI, first filed in July and amended in August, over how that company accesses Google’s search results.

That much is confirmed. What happens after that point, in coverage of this story, splits into two very different camps, and it is worth being precise about which claims are actually settled and which ones are not before you act on either.

What actually changed, mechanically

Instead of a result linking straight to a destination page, the link now points to google.com/goto, with the destination URL encoded using Protocol Buffers, Google’s own binary data format. A server-side redirect on Google’s end then forwards the visitor to the real page. For a person clicking a result, nothing looks different. They click, they land where they expected. What changed sits entirely underneath that click, in a URL structure that any tool reading destination links now has to parse differently than before.

Third-party tools that read destination URLs directly took the first hit, and here the evidence is solid because the vendors themselves reported it. SerpAPI confirmed impact across several of its products. Ahrefs confirmed what it called a temporary inconsistency in its data. One rank-tracking vendor documented a real six-day window, August 26 through September 2, where its Share of Voice reporting misattributed clicks because its parser was not reading the new format correctly. That has since been fixed, with the affected data being backfilled for customers.

Not every tool broke the same way, and this is worth sitting with for a moment. SE Ranking and Semrush both confirmed no impact on their own position tracking data at all. So the blanket claim that the /goto redirect broke SEO tools is not quite accurate. Some tools broke. Others, reading the exact same search results pages, did not, which suggests the difference has more to do with how each vendor’s parser was originally built than with the redirect itself being universally disruptive.

Where the coverage actually splits

Here is where a real divide appears. Several sources treat GA4 organic-to-direct misattribution as an established, active problem, describing what one piece called “massive organic attribution data loss” and sudden, unexplained spikes in Direct traffic. That framing has spread fast, because it is the scariest possible read of a genuinely technical, genuinely unresolved situation, and alarming framing tends to travel faster online than careful, hedged framing ever does.

Now look at what the more carefully sourced coverage actually says. As of late August, one detailed technical write-up stated plainly that nobody had reported confirmed organic undercounting inside GA4. A separate analysis went further and ran an actual test across ten device and browser combinations, checking whether referrer data survived the redirect chain. It found the referrer stayed intact in every case, and GA4 correctly classified those sessions as Organic Search each time. Multiple outlets, working independently of each other, land on the same conclusion. Google has not confirmed a GA4 attribution impact, and the direct evidence gathered so far does not show one either.

None of that means the concern is baseless. The mechanism Google’s own documentation describes makes an attribution gap plausible in principle. If a redirect chain ever strips referrer data before it reaches your site, GA4’s fallback logic would file that session as Direct rather than Organic Search, silently, with no alert generated anywhere in your dashboard. That is a real risk worth watching closely. It is not the same thing as a confirmed, ongoing problem, and treating it as something that has already happened is exactly the kind of overstatement that risks needing a correction once more data actually comes in, one way or the other.

Why the distinction actually matters

It would be easy to read the last two sections and conclude the difference between disputed and confirmed is mostly semantic. It is not, and the practical stakes are worth spelling out.

If a team reacts to this as a confirmed GA4 problem, the natural response is to start second-guessing every organic traffic number reported for the past month, which burns real time reconciling data against a theory that current testing does not support. Budget conversations get harder to have with confidence when the underlying numbers are being treated as suspect without evidence. Reporting to a client or a leadership team gets shakier too, since telling a room that your organic numbers might be wrong because of a redirect Google has not confirmed affects attribution is not a comfortable thing to say out loud in a review meeting.

If a team instead treats this as a plausible, unconfirmed risk worth monitoring, the response looks completely different. You set a baseline, you watch two specific ratios over the following weeks, and you keep operating normally in the meantime rather than freezing decisions around a risk that has not actually materialized in the testing done so far. That is the more defensible position given what is currently known, and it is also simply less exhausting to maintain.

A second, less-discussed layer

There is a second angle here that is easy to miss if you are only thinking about traditional search engine optimization reporting. Reports say /goto-wrapped URLs are starting to show up as cited sources inside ChatGPT, Perplexity, and Claude, wherever those systems pull from Google’s search results as part of answering a query. If a citation-tracking tool has the same blind spot rank trackers had in late August, before their parsers caught up, the same kind of silent misattribution could in theory apply to AI citation counts, not only to GA4 sessions.

Nobody has published confirmed data on this specifically yet either. It follows the same underlying mechanism, and the same caution about calling something confirmed before the evidence is actually in applies here just as much. This is precisely the kind of gap that generative engine optimization and answer engine optimization work now has to account for. Visibility inside an AI answer is only useful if you can actually measure it, and a measurement tool with an unpatched blind spot will quietly undercount exposure it should be reporting, in exactly the way several rank trackers briefly did in late August.

Setting a baseline instead of guessing

The sensible response to a disputed, plausible-but-unconfirmed risk is not to panic and it is not to ignore it. It is to set a baseline now, so that if this ever does show up in your own data, you catch it immediately instead of noticing it months later as an unexplained trend with no starting point to compare against.

Record this week’s ratio of Search Console clicks to GA4 organic sessions for your key properties, and write the number down somewhere you will actually revisit. Do the same for your current organic-to-direct traffic split. These two figures are your tripwire. If either one moves meaningfully in the weeks ahead with nothing else in your setup changing, that is your signal to look closer, rather than reacting to someone else’s alarmed blog post as though it were your own data.

Reconcile Search Console against GA4 weekly for the next month, instead of your usual monthly cadence. A real attribution gap, if one exists, would show up as a widening divergence between the two figures over time, not as a single dramatic jump you would notice immediately anyway.

Check your GA4 referral exclusion list for any new entries appearing as google.com/goto. If Google’s own redirect domain starts showing up there as a distinct referral source, rather than resolving cleanly through to Organic Search, add it to your exclusions so it does not fragment your organic channel into two separate, harder-to-reconcile pieces.

Hold off on reacting to a rank-tracker alert this week unless you have confirmed that specific tool already adjusted its parser to read the new /goto format correctly. Given that SE Ranking and Semrush reported no impact while SerpAPI and Ahrefs did, an alert from a tool that has not caught up yet is more likely a parsing problem on their end than an actual ranking change on your site.

And if you are already doing any AI visibility tracking, apply the same caution to what you see there. A cited source appearing as a raw /goto link rather than a resolved domain in your reporting is a sign your tool needs to catch up, not evidence that your underlying citation count has actually changed.

Where this leaves you

Google confirmed the redirect itself on August 26. It has not been confirmed, and the direct testing done so far does not support a GA4 attribution problem. Some SEO tools broke, others did not, and the ones that did have mostly already fixed their parsers by now. The plausible risk to your own analytics is real enough to baseline and monitor closely. It is not, as of this writing, a confirmed, active problem serious enough to justify the level of alarm some coverage is giving it, and treating an unconfirmed risk as settled fact is its own kind of mistake, one that tends to send teams chasing a problem that is not actually there yet while a genuinely useful baselining exercise gets skipped entirely.

Frequently Asked Questions

1. Is Google’s /goto redirect confirmed?
Answer: Yes. A Google spokesperson confirmed the rollout on August 26 and described it as a technical measure to protect Google’s services and users from evolving abuse. The rollout itself is not in dispute anywhere in the coverage. What remains unsettled is how far its effects reach.

2. Is my GA4 organic traffic being misattributed because of it?
Answer: Not as far as anyone has confirmed. Google has not acknowledged a GA4 attribution impact, and one technical test across ten device and browser combinations found referrer data stayed intact, with sessions classified as Organic Search. The risk is plausible in principle, so it is worth monitoring, but it is not a confirmed problem.

3. Why is my rank tracker showing odd data?
Answer: It depends on the tool. SerpAPI and Ahrefs confirmed some impact, with Ahrefs calling it a temporary inconsistency, while SE Ranking and Semrush confirmed none. Check whether your vendor has published a statement or a fix before assuming your rankings actually moved.

4. Does this affect AI citation tracking?
Answer: Possibly, but nothing is confirmed. /goto-wrapped links are reportedly appearing as cited sources in ChatGPT, Perplexity, and Claude. A tool that cannot parse them could undercount your citations. Treat any sudden citation drop as a possible tracking issue first, and verify it manually.

5. What should I check first?
Answer: Record this week’s ratio of Search Console clicks to GA4 organic sessions, plus your organic-to-direct traffic split. These two numbers are your baseline. If either shifts meaningfully with nothing else changing, investigate then.

6. How often should I reconcile Search Console and GA4?
Answer: Weekly for the next month, instead of monthly. A genuine attribution gap would show up as a widening divergence between the two over several weeks, not as a single sudden jump.

7. Should I change my SEO strategy because of this?
Answer: No. Nothing about the redirect changes how rankings are earned. Keep your strategy as it is, baseline your data, and update only if a confirmed impact emerges.

If you want a second set of eyes on whether your own reporting, or your AI visibility specifically, is being affected, that is exactly what we check in a free AI Visibility Audit.

In August 2025, Google’s own John Mueller warned the SEO industry about something specific. Speaking about the growing pile of new acronyms, GEO, AIO, AEO, he warned that pushing new terminology too aggressively was often a signal of low quality tactics rather than genuine innovation. A month later, in September 2025, when a fake screenshot claimed Google had built a dedicated AI Overview filter inside Search Console, Mueller shut that down too, calling the screenshot fake and confirming no such feature existed.

Eleven months later, on 31 August 2026, Google built exactly that feature, for real, and rolled it out to every website on earth.

I want to walk through what actually changed, why the timing and the backstory matter more than the feature itself, and exactly how to check this on your own site.

The rumour that turned out to be a preview of the future

The story is worth telling properly, because it says something about how much pent up demand existed for this.

On 15 September 2025, a user holding Platinum Product Expert status in Google’s own Search Console help forums, Adrian Coutin, posted that Google had integrated data for AI-generated search features directly into Search Console’s Performance reports. The post included a fabricated screenshot showing a new Search Appearance filter specifically for AI Overview data. It spread fast, because it was exactly what site owners had been asking for.

Mueller responded on LinkedIn within hours. “There’s no filter like this in Search Console, and the screenshot itself is fake,” he wrote. Coutin deleted his original post and apologised for the error.

For the following year, Google’s official position stayed consistent, AI Overview and AI Mode data was folded into the standard performance numbers, with no way to separate it out, and no committed timeline to change that. Multiple SEO guides published through late 2025 and into early 2026 describe workarounds involving third party tools precisely because Google offered nothing native.

Then, in June 2026, Google quietly began testing a real version of exactly the feature Coutin had faked, on a limited subset of properties. On 31 August, that testing phase ended, and the feature went live everywhere.

What actually shipped

Google confirmed the global rollout on its own Search Central blog, describing the new reports as dedicated views of impressions specifically within generative AI features on Search, covering AI Overviews and AI Mode, as well as the generative AI features that now appear inside Discover.

Search Engine Journal’s coverage of the global launch adds a detail worth knowing before you go looking for it. Not every property has access yet, and sites with a low volume of AI impressions may not show meaningful data in the report even where it is available. If you check and see very little, that is not necessarily a sign the report is broken. It may simply reflect where your content currently sits in AI systems.

The report breaks impressions down by page, by country, and by date. What it does not include, and this is the detail every source I checked agrees on without exception, is clicks, click through rate, or the specific queries that triggered an appearance. You can see that a page from your site showed up inside an AI generated answer. You cannot see what someone typed to get that answer, and you cannot see whether they clicked through to you afterward.

The report is best understood as a record of where you showed up, not a measure of what that appearance actually earned you in traffic or business.

Google also shipped an opt out control alongside the reporting, letting site owners remove themselves from these AI features entirely. Google has stated that using this toggle does not affect a site’s ranking anywhere else in standard Search results, which matters, because it means the choice to opt out is a genuine preference rather than a trade-off against traditional visibility.

Why the backstory matters more than the button

I keep returning to the Mueller timeline because it tells you something the feature announcement alone does not.

In August 2025, Google’s own search advocate was publicly wary of the entire AI visibility conversation, treating the proliferation of GEO and AEO terminology as a likely signal of low quality hype rather than a legitimate new discipline. A month later, Google was actively denying it had built any tooling to support that conversation.

Less than a year on, Google built the tooling anyway, at a global scale, unprompted by any specific competitive pressure that forced its hand. That sequence is a stronger signal than the launch blog post itself. It suggests the internal case for treating AI visibility as a distinct, measurable category became undeniable even to a company that was publicly skeptical of the framing not long before.

For anyone running SEO or GEO work for a client, that timeline is useful ammunition. The scepticism you may have encountered from more traditional stakeholders, the idea that AI visibility is a marketing buzzword rather than something worth the budget, gets harder to sustain once the platform itself has built a dedicated reporting surface for exactly that.

The data that explains why Google finally built this

Two independent data points, unrelated to this launch, explain the pressure Google was likely responding to.

Semrush’s AI Visibility Index, tracking brand mentions across Google’s AI Mode over several thousand prompts, found a 4 percent drop in mention share between August and October last year, while the diversity of sources being cited across the same period rose 13 percent. Visibility was getting harder to hold onto and more competitive at the same time, with no native way for an affected business to even confirm it was happening.

BrightEdge’s industry wide data adds the commercial pressure point. Search impressions are up 49 percent year over year, while click through rate on those impressions is down 30 percent over the same period. Businesses have been watching their visibility numbers climb while their actual traffic stalls or falls, with no first party data source able to explain why. That is precisely the gap this report is built to close, even if only partially.

How to actually find and use this on your own site

Coverage of exactly where this sits inside the Search Console interface is not fully consistent across sources I checked, some describe it as a dedicated left navigation item, others as a filter within the existing Performance report. Rather than send you hunting for one specific click path that may not match what you see, the reliable approach is this. Open your Performance report inside Search Console for the property in question, and look for a Generative AI or AI features option, either as a separate section or as a filter on your existing search appearance data. If it is not visible yet, that is consistent with Google’s own rollout note that access is expanding property by property rather than appearing identically for everyone on day one.

Once you find it, compare the AI impression volume against your total Web impressions for the same period. If AI generated impressions represent a meaningful share of your total visibility, and your click through rate has been falling without a ranking drop to explain it, that gap is very likely hiding inside exactly this data. This is the same pattern the BrightEdge numbers describe industry wide, positions can hold while clicks fall, because an increasing share of answers are being delivered before anyone reaches your listing.

If the number is small or close to zero, treat that as informative in a different way. It likely means your content is not currently being retrieved for the kinds of questions that trigger these AI features in your category, which is a different and in some ways more urgent problem than a visibility measurement gap.

What not to do with this data yet

Do not draw conclusions from a single week. This is newly global infrastructure, and Google’s own historical pattern with new reporting features is that data takes time to stabilise as more properties gain access and reporting pipelines mature.

The useful read is a trend over four to eight weeks, not a snapshot. Is your share of AI impressions climbing, flat, or falling relative to your total visibility over that window. That trajectory tells you far more than any single day’s number, particularly while the feature is still rolling out unevenly across different sites.

Frequently asked questions

1. Does this show me if ChatGPT or Perplexity cite my site?
Answer: No. This report is scoped entirely to Google’s own AI features, AI Overviews, AI Mode, and Discover’s generative surfaces. It has no visibility into any AI platform outside Google’s own products. Measuring citation inside ChatGPT, Claude, Gemini, or Perplexity still requires testing those platforms directly, since none of them currently offer a first party reporting tool of their own.

2. Does a high AI impression count mean I am getting more traffic?
Answer: Not necessarily, and this is the central limitation to keep in mind. The report measures impressions only. BrightEdge’s industry data shows click through rate falling even as impressions rise broadly, so a strong impression number does not guarantee a proportional lift in actual visits.

3. Can I see which search queries triggered my AI impressions?
Answer: No, and every source covering this launch agrees on that point. Query level detail is one of the more consistently requested features Google has not shipped, alongside click data.

4. Should I use the opt out toggle?
Answer: For most businesses, no. Google has confirmed opting out does not improve or protect your standing in standard Search results, so opting out only removes a visibility channel without gaining you anything in return. It exists mainly for edge cases such as publishers protecting content behind a specific business model, not for typical service or B2B businesses trying to be found.

5. Why did it take Google so long to build this, given the September 2025 rumour showed clear demand?
Answer: Google’s public position throughout that period was that AI Overview data belonged inside standard performance reporting rather than a separate view. The shift to building a dedicated report suggests the internal case changed, likely under the same pressure reflected in the Semrush and BrightEdge data, impressions climbing, clicks falling, and no way for site owners to see why.

If you want visibility that goes further than what Google’s own tools can show, including whether ChatGPT, Claude, Gemini, and Perplexity are actually citing you, that is exactly what we check in a free AI Visibility Audit.