Google search redirect loop fix on Android

You tap a search result in the Google app or Chrome on Android, and instead of loading the page, it bounces you back to the search results. Or the page flickers and reloads the search over and over. This usually happens after an OS update, a Chrome update, or when your phone's clock drifts out of sync with Google's servers. It can also appear after you clear your browser data and the session token gets orphaned.

What's actually happening here

Google Search uses session tokens stored in the Android System WebView to keep you logged in and serve personalized results. When WebView's cache or session data gets corrupted (common after an app update or a security patch), the token validation fails. The search app tries to re-authenticate, but the corrupted session creates a loop — it can't verify the token, so it requests a new one, which also fails, and you're stuck.

Another common trigger is an incorrect date/time setting. Google's servers reject requests with timestamps that are too far off, which forces a redirect loop. Same thing happens if you're behind a proxy or VPN that's interfering with the HTTPS handshake.

The fix — step by step

1. Force close the Google app
   Go to Settings > Apps > Google > Force stop. Don't skip this — it clears any stuck processes.
2. Clear the Google app's cache and storage
   In the same app info screen, tap Storage & cache > Clear cache. Then tap Clear storage (or Manage space > Clear all data). This wipes the corrupted session tokens. You'll need to sign back into Google within the app after this.
3. Check your date and time
   Go to Settings > System > Date & time. Toggle Set automatically off, then on again. If it's already on, toggle it off, set the correct time manually, wait 10 seconds, then turn auto back on. This forces a fresh NTP sync with Google's servers.
4. Update Android System WebView
   Open the Play Store, search for Android System WebView. If it's not up to date, update it. A stale WebView is a classic cause of redirect loops after a Chrome update.
5. Clear Chrome's cache too
   Even if you're using the Google app, Chrome and WebView share underlying storage. Go to Chrome settings > Privacy and security > Clear browsing data. Make sure Cached images and files is checked. Don't clear passwords or cookies unless you want to log out of everything.
6. Restart your phone
   I know it sounds basic, but the OS needs to reload WebView and the Google app with fresh sessions. A restart does that cleanly.

If it still fails

If the loop persists after all that, check whether you're running a VPN or ad blocker that modifies HTTPS traffic. Apps like Blokada, AdGuard, or company VPNs can break the handshake. Disable them temporarily and test again.

Also check if Google’s servers are down for your region — sometimes it's not on your end. A quick search on downdetector or Twitter confirms that.

Last resort: uninstall updates for the Google app (Settings > Apps > Google > three-dot menu > Uninstall updates). This rolls it back to the factory version, which rarely has this bug. Then update it again from the Play Store. Pro tip: after reinstalling, wait 5 minutes before opening the app — it needs time to initialize WebView in the background.

If none of that works, you're likely dealing with a carrier-specific DNS hijack or a Samsung device with a known WebView bug (common on One UI 5.1 and 6.0). In that case, switch to a different browser entirely — Firefox or Brave avoid this because they don't rely on the system WebView.