Google Web Guide currently has an awkward exit problem. In a reproducible but inconsistent bug, clicking the “Classic search” control can leave the user inside Web Guide, with the AI-organized results reloading instead of the expected standard search experience.
The behavior was documented on September 20 by Search Engine Roundtable in tests and screenshots of the Web Guide issue. The report also shows other signs of interface breakage, including elements appearing in unexpected positions and links resolving to the malformed destination null://null.
There is an important qualification: Google has not officially confirmed the bug, and the behavior is not consistent. It should therefore be treated as a reproduced interface failure affecting some Web Guide sessions, not as evidence that Google has intentionally removed the ability to return to classic results.
“Classic search” can lead straight back to Web Guide
The clearest failure concerns the control that is supposed to move a user out of the AI-organized interface. Search Engine Roundtable reports that selecting “Classic search” sometimes refreshes or reloads the Web Guide experience rather than taking the user to standard results.
That creates a loop in the interface. The user explicitly chooses the non-Web-Guide option, yet the next state can remain the AI-organized page they were attempting to leave.
The bug is particularly noticeable because the control communicates a clear expectation. “Classic search” is not an ambiguous label for another AI presentation; it signals a route back to Google's familiar results experience.
Google originally said Web Guide users could switch back easily
The observed behavior conflicts with the intended design Google described when it launched Web Guide. In the official July 2025 announcement, Google said the experiment would initially be accessible from the Web tab for opted-in Search Labs users, where people could easily switch back to standard Web tab results at any time.
That makes the current problem best understood as a broken navigation path rather than a documented product change. Google's public description still presents Web Guide as an experimental AI-organized search experience with a route back to standard web results.
No official Google source located for this report says that “Classic search” is supposed to reload Web Guide or that users are intentionally being prevented from leaving the experiment.
Web Guide is an AI-organized layer over web search
Web Guide is not simply another visual skin for the conventional results page. Google describes it as a Search Labs experiment that uses a custom version of Gemini to understand both the query and web content, then organizes links into groups related to different aspects of the search.
Like AI Mode, it uses query fan-out: the system can issue multiple related searches concurrently and use the results to build a more structured response. The aim is to help users explore open-ended or detailed questions while still surfacing links to websites.
This architecture makes the distinction between Web Guide and standard results meaningful. A user switching to classic search is choosing a different presentation and retrieval experience, not merely collapsing a decorative panel.
The bug also produces malformed null://null links
The failed exit is not the only symptom captured in the report. Screenshots show a link whose destination is rendered as null://null, a malformed value that strongly suggests a missing or incorrectly populated URL in the interface state.
That does not establish the underlying engineering cause. Without confirmation from Google, it would be speculative to say whether the problem comes from client-side state, routing, an experiment flag, result rendering or another component.
What can be said from the visible behavior is narrower: at least one Web Guide session produced a link destination that was not a valid normal web URL, alongside the navigation problem.
Other interface elements can appear out of position
The tests also show UI components appearing in places where they do not normally belong. Combined with the broken Classic Search transition and malformed link, this suggests the observed issue is broader than a single mislabeled button.
Again, that does not justify diagnosing the internal cause. Experimental search interfaces can involve multiple active tests, layouts and account states, and the report explicitly notes that the behavior is inconsistent.
The useful conclusion is that Web Guide can currently enter a visibly broken state in which navigation and result-page elements do not behave as expected.
The behavior is reproducible, but not stable
Intermittency matters when evaluating this type of report. A bug that appears in one session and disappears in another can be difficult for users, publishers and independent testers to characterize.
It may depend on account state, Labs enrollment, query, browser session, experiment configuration or other variables that are not publicly visible. Search Engine Roundtable was able to reproduce the Classic Search issue, but the report also notes that it does not happen every time.
That is why the strongest accurate description is “reproduced but inconsistent,” rather than “all Web Guide users are trapped.”
This is not evidence that Google intentionally removed classic results
The visual effect of the bug is provocative: a user asks to leave an AI search interface and is returned to it. But product intent should not be inferred from a malfunction.
Google's original Web Guide documentation says users can switch back to standard results. The feature also remains framed as an experimental Search Labs experience. Until Google says otherwise, there is no factual basis for interpreting the loop as a deliberate attempt to prevent access to classic search.
This distinction is especially important because Google's search interface is undergoing rapid AI-driven changes. A broken control can look like a strategic product decision when, in reality, it may simply be a temporary implementation problem.
Web Guide itself has been moving deeper into the SERP
The bug appears while Google continues experimenting with where Web Guide appears in Search. NetContentSEO recently covered tests in which Web Guide was appearing at the top of the SERP, a more prominent position than its original introduction inside the Web tab suggested.
Google's launch announcement anticipated some of this evolution. The company said it planned to experiment with AI-organized results in other parts of Search, including the All tab, as it learned where the format was useful.
That broader experimentation makes reliable navigation between AI-organized and standard result formats increasingly important. The more visible Web Guide becomes, the more consequential a broken exit control becomes for ordinary search behavior.
The user-control issue matters more than the visual glitch
A misplaced interface component or malformed link is inconvenient, but the Classic Search problem touches a more fundamental usability expectation: when a user selects a different search mode, the interface should respect that choice.
AI search interfaces increasingly reorganize the web rather than presenting a familiar ranked list. Users may prefer that experience for some queries and conventional results for others. Easy movement between the two is therefore part of the product's usability, not a minor cosmetic feature.
Google itself emphasized that ability when Web Guide launched. A bug that interrupts it is worth tracking even if it affects only a subset of sessions.
Publishers should not infer ranking changes from the broken interface
For SEO teams, the screenshots may be tempting to interpret as evidence of a deeper search-ranking change. There is currently no basis for that conclusion.
The observed problem concerns interface behavior and navigation. It does not demonstrate that a page's underlying ranking changed, that Google altered Web Guide's retrieval logic or that standard results have been removed for the affected queries.
Likewise, the null://null link should not automatically be interpreted as an indexing or canonicalization issue on the publisher's site. The malformed value appears in Google's interface and, based on the available evidence, should be treated as a search-product rendering or routing symptom unless further information emerges.
Web Guide remains experimental
Google launched Web Guide through Search Labs, where experimental features are tested and refined using user feedback. That context does not make broken navigation unimportant, but it does make transient behavior more plausible than it would be in a long-established search interface.
Google has repeatedly described its generative search products as evolving experiments, with features changing as the company learns how users interact with them. Web Guide has followed that pattern from its initial Web-tab placement toward tests in more prominent areas of Search.
The current exit problem is another reminder that the interface layer around AI-organized search is still being actively developed.
For now, this is a bug to monitor, not a new Google policy
The September 20 tests establish a concrete problem: in some Web Guide sessions, clicking “Classic search” can reload Web Guide instead of returning to standard results. The same testing has surfaced misplaced interface components and at least one malformed null://null destination.
What the evidence does not establish is equally important. Google has not confirmed the issue, has not announced a change to the Classic Search control and has not said that Web Guide users are intentionally being kept inside AI-organized results.
For now, Google Web Guide has an exit bug, not a documented no-exit policy. If the behavior persists or Google comments on it, the distinction between an unstable experiment and a deliberate change to how users move between AI and classic search will become much clearer.