A sign-in loop is a repeated return to an earlier screen without reaching the account. It is different from an explicit wrong-password message, a required verification challenge, or a notice that the account is disabled.
Record where the loop occurs
Note whether the loop happens on Google itself or after returning to another app. Record the visible error text and the browser involved, but do not share passwords, verification codes, or complete authentication URLs containing private parameters.
If you are trying to recover a locked account, preserve your familiar browser and device. Google’s recovery guidance favors those signals; clearing their data or starting in a private window is not the first step for proving ownership.
Test the ordinary sign-in path
- Save work in the affected app.
- Open Google’s sign-in page directly in an updated, supported browser.
- Check the selected account and complete any legitimate verification prompt.
- If direct sign-in works, return to the app through its normal login button and inspect the result.
A failure only inside an app’s embedded browser points to a different problem from a failure on Google’s own sign-in page. Use the app’s supported external-browser login where available.
Inspect cookies and JavaScript
Check whether the browser allows the site data needed for the Google session and whether an exception blocks it. Confirm that JavaScript is available. Review a recently installed extension if the problem began immediately afterward.
On a managed device, collect the symptom for the administrator instead of overriding security policies. Do not disable antivirus, bypass certificate warnings, or enable unknown extensions to make a login proceed.
Use a controlled comparison
For an ordinary browser-session problem, a separate supported browser or a temporary clean profile can help identify whether the issue is specific to the existing profile. Change one variable at a time and keep the original session intact until you know you can return.
If narrowly clearing site data becomes necessary, save local work and confirm your sign-in methods first. Repeated password resets are not a general cure for a loop. If the screen instead reports that Google cannot verify ownership, switch to the official account-recovery process and its instructions.
Official references
Reviewed against Google’s official guidance on October 27, 2026. Available options and screen labels can vary by account, device, region, and organization policy.