Google Disables Discover AI Source-Tap Test After Confirming a Bug

Google disabled a Discover experiment after confirming a bug that blocked users from tapping the source area of AI-generated summary cards, engineer Rajan Patel confirmed on October 27, 2026, following identification of the configuration flag disable_aio_sources_button_tap by Damien Andell. Google said the behavior was a bug in an experiment rather than an intentional removal of source access, and the source interaction was reported to be working again. A follow-up trace by Andell found the disabled test replaced by a configuration described as "aio tap falls through to hero," which Google has not publicly explained.

Google has disabled an experiment in Discover after confirming that it incorrectly prevented users from tapping the source area of AI-generated summary cards. For publishers, the episode matters because a visible source citation is not necessarily a usable route to their content, and Search Console does not directly report clicks made inside Discover’s AI surface. The issue became public after Damien Andell identified a configuration flag, disable aio sources button tap , that blocked users from opening the source mini-view associated with an AI summary. On October 27, 2026, Google engineer Rajan Patel confirmed that the behavior was a bug in an experiment and said the experiment had been disabled. Search Engine Journal's reporting on Patel's confirmation https://www.searchenginejournal.com/rajan-patel-disabled-discover-source-clicks-bug/594579/ documents the sequence. The change does not establish a new publisher-linking policy for Discover. It does, however, show how an interface experiment can change the path from an AI-generated summary to the publishers cited within it. The affected Discover experience used AI-generated summaries with a source area intended to lead users to related publisher content. During the experiment, taps on that source area did not open the expected article-feed mini-view. Patel described the behavior as a bug, rather than an intentional permanent removal of source access. Google turned off the experiment, and the source interaction was reported to be working as intended again. That distinction is important. The confirmed development is the disabling of a faulty experiment, not a confirmed broad withdrawal of publisher links from Discover AI summaries. The public information also does not quantify how many users, queries, publishers, devices, or markets were affected, or how long the faulty behavior was live. AI summaries can change the way audiences encounter publisher content. A URL may be surfaced as a source, yet the interface determines whether the user can easily inspect that source or continue to the publisher's page. In this case, the bug affected a specific interaction point: the source area of an AI summary card. If users cannot open it, a publisher can retain on-screen exposure while losing a potential route toward referral traffic. That is why impression data alone cannot fully describe the value of an AI citation or source appearance. The incident is especially relevant for publishers that rely on Discover as a traffic channel. Discover is not a conventional ranked-results page, and audience journeys can be shaped by feed design, card interactions, and experiments as well as by whether Google selects a URL for display. Google Search Console's Discover Generative AI Report reports impressions for publisher links surfaced through Discover's AI features. It does not report direct clicks occurring within the AI surface. That creates a practical limitation when a Discover interface changes. A publisher may still see impressions attributed to its URLs in the report, but the data alone cannot confirm that source taps remained available or that users were reaching the site through the same journey. This is not evidence that every change in Discover AI source behavior will reduce traffic. Referral outcomes depend on the audience, the summary, competing links, the specific UI, and the destination experience. The point is narrower: a persistent impression count should not be treated as proof that the publisher's access path is unchanged. In a follow-up trace, Andell reported that the disabled test was replaced by another configuration described as “aio tap falls through to hero.” Google has not publicly explained how that variant behaves. It would be premature to conclude that this configuration removes source access, restores it in a different form, or changes where taps lead. The phrase suggests that the interaction flow may differ from the earlier source mini-view, but its effect on user journeys has not been publicly detailed. Publishers and SEO teams should separate the confirmed bug fix from the unresolved behavior of any subsequent test. Interface labels and technical flags can be useful monitoring clues, but they are not a substitute for documented product behavior or traffic evidence. The useful response is not to assume that Discover AI exposure has either disappeared or returned to a fixed state. Instead, monitor both visibility and outcomes over time. For agencies and in-house teams https://blog.geosearchleads.com/geo-lead-generation-tool-seo-agencies/ , this is also a reporting issue. AI visibility reporting should distinguish between a link being displayed, a source being actionable, and a visit arriving at the site. Those are related signals, but they are not interchangeable. If Discover AI citations are part of your organic visibility picture, create a GEO Search Leads account https://app.geosearchleads.com/pages/register to begin assessing your website's GEO readiness https://blog.geosearchleads.com/ai-visibility-tool-seo-agencies/ and identify optimization opportunities. A structured review can help your team separate where content is eligible to be discovered from how changing AI interfaces may affect the path users take to reach it. What was the Google Discover source-tap bug? A Discover experiment prevented users from tapping the sources area of certain AI-generated summary cards to open the expected article-feed mini-view. Google engineer Rajan Patel confirmed it was a bug and said the experiment was disabled. Did Google permanently remove publisher source links from Discover AI summaries? No. Google confirmed that the blocked source-tap behavior was a bug in an experiment, not a confirmed permanent product change. Google disabled that experiment. Does the Discover Generative AI Report show clicks from AI summaries? No. The report provides impressions for publisher links surfaced through Discover's AI features, but it does not report direct clicks within the AI surface. What does “aio tap falls through to hero” mean? It is the name of a follow-up configuration identified by Damien Andell. Google has not publicly explained how it works, so its effect on source access or publisher traffic remains uncertain. Google's response resolved the confirmed source-tap bug, but it also underscores a broader reality for publisher visibility in AI-driven discovery: being cited and being reachable are different things. Monitor Discover AI impressions alongside referral trends and observed interface behavior, especially while Google continues to test how users interact with AI summary cards.