Google: Disabled Discover Clicks Were a Bug in an Experiment
/ 6 min read
Summary
Patel was replying to Lily Ray, who had quote posted Andell's report the morning of Oct. 23. Patel wrote: Hey Lily, this was a. The practical question is what this changes for SEO, content quality, and AI search visibility.
Google says disabled source taps on Discover's AI summary cards were "a bug in a Discover experiment," and that it has turned the experiment off. Rajan Patel, VP of Engineering for Search at Google, said so in a reply on X Monday evening. This connects with Google Expands Personalization Across Search, Discover & News when the same signal needs a clearer operating decision.
Damien Andell, who researches Google Discover, had reported the issue on Oct. Before the test, Andell wrote, tapping a summary's sources opened a feed of articles from those sources, one path from an AI summary to the sites it cites.
What Google Said
Patel was replying to Lily Ray, who had quote posted Andell's report the morning of Oct. 23. Patel wrote: Hey Lily, this was a bug in a Discover experiment. We've turned off the experiment, and the experience works as intended again. The. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.
The reporting question is whether this signal changes a decision. If it only creates another number in a dashboard, it adds noise. If it helps separate profile activity, website visits, calls, bookings, and direction requests, it can make local performance easier to understand.
What Was Reported
Andell wrote on Oct. 23 that Discover was testing an AI summary change that disabled clicks on sources. He found this test through a flag called "disable_aio_sources_button_tap," and stated that this flag stopped taps on the sources at the. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path. A useful companion note is If an AI Watermark Scares You, because it looks at a nearby part of the same system.
What Andell Found After Google's Reply
On Oct. 27, he looked at this again. In a reply on X, he stated: I just checked and the experiment did indeed remove and replace it with another one called "aio tap falls through to hero". His post didn't explain how the new experiment. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.
The practical value is in connecting the idea to an observable signal. That means deciding what should be checked, what would prove the issue is real, and where the team should make the smallest useful improvement first.
Why This Matters
The Discover generative AI report from Search Console reports how many times users see links to your pages in Discover through the generative AI capabilities. Each source page is listed by URL in the Discover Generative AI Report. The only. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.
Looking Ahead
Until Google or Andell explains the replacement experiment, you can take a quick look for yourself. Tap the sources on an AI summary card in your Discover feed to see whether the article feed opens. The practical question is what this changes in the system: the page structure, the evidence presented, the measurement habit, or the way the topic is connected to related work.
What Google Said in practice
Introduction Google says disabled source taps on Discover's AI summary cards were "a bug in a Discover experiment," and that it has turned the experiment off. Rajan Patel, VP of Engineering for Search at Google, said so in a reply on X. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.
What the visibility signal actually changes
What the visibility signal actually changes: google: Disabled Discover Clicks Were a Bug in an Experiment: the Practical Angle should be treated as a visibility signal, not a standalone headline. Introduction Google says disabled source taps on Discover's AI summary cards were "a bug in a Discover experiment," and that it has turned the experiment off. Rajan Patel, VP of Engineering for Search at Google, said so in a reply on X Monday evening. Damien.
What the visibility signal actually changes: the practical question is whether the page, brand evidence, and surrounding content make the answer easier to trust. If that support is weak, search systems can still understand the topic but fail to connect it confidently to the brand.
What the visibility signal actually changes: that is why the response should begin with an audit of the evidence already on the site before creating a new asset. The fastest improvement is often a clearer page, a better internal link, or a stronger explanation of why the brand belongs in the answer.
Where the evidence needs to be tested
Where the evidence needs to be tested: a single study or ranking observation should not become a strategy by itself. It should become a diagnostic prompt: which source is being trusted, which query pattern is affected, and which part of the site would make that trust easier to earn?
Where the evidence needs to be tested: that keeps the response grounded. The goal is to improve the evidence chain around the topic rather than publish another summary that repeats what every other page already says.
Where the evidence needs to be tested: the important distinction is between a useful signal and a fashionable talking point. A useful signal changes the brief, the page structure, the linking plan, or the measurement view.
How to avoid overreacting to one data point
How to avoid overreacting to one data point: for content teams, the strongest move is to map the claim to existing assets before creating anything new. The right page may already exist, but it may need clearer headings, stronger internal links, fresher proof, or a better explanation of why the brand belongs in the answer.
How to avoid overreacting to one data point: this is also where title rewriting matters. A title should not copy the source headline; it should frame the practical implication so readers immediately know why the topic deserves attention. The same pattern also shows up in Personalization Can Help Small Publishers, where the practical question is how the signal becomes visible.
How to avoid overreacting to one data point: the same standard should apply to every section. Each heading needs to earn its place by moving the reader through the evidence, not by repeating the outline in a more polished voice.
What this means for content and authority
What this means for content and authority: authority is becoming more contextual. It is not enough to be generally known in a category if the specific answer depends on a different source, a different index, or a different retrieval pattern.
What this means for content and authority: that means the content system should show consistent entities, related pages, credible references, and useful depth around the exact questions people and AI tools are asking.
What this means for content and authority: when the context is weak, AI systems can still mention the brand but describe it in the wrong frame. The fix is not more volume; it is cleaner evidence around the specific association.
Comments
Comments are reviewed before they are published. Links are not allowed inside comments.