TL;DR Summary:
Stuck in Web Guide: Google’s beta Web Guide has a bug where the “Classic search” button reloads the same interface instead of returning users to normal search results.Broken Page Details: Testers also spotted extra glitches, including a “null://null” link and stray interface text, which suggests the feature is still unstable.Inconsistent Behavior: The problem does not happen every time, and different searches can produce different results, making the bug harder to predict.Workaround and Risk: Refreshing the page or starting a new search may help for now, but there is no confirmed Google fix yet.Why won’t the “Classic search” button in Google Web Guide take you back to normal search results? Google’s beta Web Guide feature has a bug that traps some users inside its interface, and clicking the exit button reloads the same results instead of switching you out. The Google Web Guide Classic Search Button Bug surfaced on September 20, 2026, and it matters now because anyone testing this new feature may find themselves stuck with no clear way out.
What The Google Web Guide Classic Search Button Bug Actually Does
Web Guide is a beta opt-in feature from Google. It blends the AI search results view with the standard web search interface into one experience. The button labeled “Classic search” is supposed to take you out of Web Guide and back to normal search results. Instead, it just reloads the same Web Guide page. You click the button, you wait, and you land right back where you started.
Who Spotted The Bug First
Damien Andell found the issue and posted about it on X. He described it directly: “Google search bug: impossible to return to ‘classic search,’ it always redirects to Web Guide.” Andell also flagged a second, separate error on the same page. A link that should show a site name instead displays “null://null,” which is broken code showing up where a real name belongs. Barry Schwartz tried to recreate the problem and confirmed it happens. He posted a GIF showing the page reload instead of exit.
Confirmation From Glenn Gabe Adds Weight To The Report
Glenn Gabe, who tracks Google Web Guide closely, backed up the report on X. He said he got stuck in Web Guide himself and could not get out at first. On a later attempt, he reached standard search results normally. Gabe called it “a weird one,” which suggests the bug does not happen every single time. This inconsistency matters because it means the Google Web Guide Classic Search Button Bug may be tied to specific searches or sessions rather than a total breakdown of the feature.
Visual Glitches Beyond The Button Itself
Andell pointed out additional display problems tied to the same bug. Leftover Web Guide text appeared below the knowledge panel, which is the info box Google shows on the right side of some search results. A stray label reading “Access” also showed up where it should not. Schwartz tested the same search and got a similar but not identical result, involving a LinkedIn page, a Google Search profile, and a Wix site built by Mordy Oberstein. The fact that two testers saw different outcomes on similar searches shows the bug does not behave the same way every time.
What This Means For Most Searchers
Most people do not use Web Guide at all, since it remains an opt-in beta feature. That limits how many people run into this problem right now. However, the bug still points to real instability in a tool Google may push to more users later. Google has not announced a fix, and every report on this issue so far comes from discussion on X, not from an official Google statement. Bugs like this are also a reminder that site owners shouldn’t rely purely on Google’s own interfaces to understand how their pages are actually being crawled and shown. Independent platforms such as Screpy give site owners a way to verify crawlability and technical visibility separately, so a glitch on Google’s end doesn’t leave them guessing about their site’s real standing.
If you opted into Web Guide and hit this problem, try refreshing the page or running a new search rather than clicking “Classic search” again. Watch for an official response from Google, since no fix has been confirmed yet. Until Google addresses the Google Web Guide Classic Search Button Bug directly, treat the feature as unstable and expect inconsistent results. While Google works through issues like this one, it’s worth remembering the value of checking your site’s crawl and indexing status independently rather than relying solely on Google’s shifting search experiments—a tool like Screpy’s monitoring platform can help confirm bot activity and technical health regardless of what’s happening on Google’s end.
