Why does my browser keep redirecting?
Investigate unwanted browser redirects by checking when navigation changes, comparing its scope, inspecting settings and extensions, and choosing the next action.
What a redirect tells you
A redirect takes browsing from one address to another. The useful question is what triggered that navigation and whether you intended it. One website opening an advertisement, address-bar searches passing through an unwanted provider, and a browser reopening yesterday’s tab can look similar while having different causes.
Redirection is also an ordinary web feature. MDN explains its legitimate uses, including moving an old address to a new page and sending an HTTP address to its HTTPS version. A changed address therefore cannot establish malware by itself. This article covers desktop investigation on Windows and Mac, with Chrome and Edge examples; it does not identify a culprit from a destination alone.
If a destination demands a support call, payment, installation, or pasted command, close it through normal browser controls. Do not explore it to see what happens next. If you already ran its instructions or gave it credentials, use the infection diagnostic and account-recovery guidance rather than treating this as a settings problem alone.
Record when navigation changes
Describe the event before changing the browser. Record the browser and profile, approximate time, original address if known, displayed destination, and what you did immediately before it. Keep a screenshot only if it can be collected without revisiting the suspect page, and protect private information in the record.
Distinguish these triggers:
- A page changes address after you follow a particular link or visit one website.
- A new tab or window opens while the original page stays visible.
- A search typed into the address bar uses an unexpected provider.
- Launching the browser or selecting Home opens an unwanted destination.
- A desktop notification opens a site after you select it.
The last case starts with a notification permission, not necessarily a changed search provider. Use random-pop-up investigation to identify that source. A browser’s back button returning you to the unwanted destination may reflect the navigation sequence; it is not evidence that a specific installed program caused it.
Compare the observed scope
Use ordinary trusted browsing for comparisons. Do not repeat the suspect navigation, log into sensitive accounts on an unresolved device, or switch off browser warnings to continue a test. If there is active theft or damage, stop comparisons and follow the diagnostic’s containment path.
| Pattern you observed | First question to investigate | What remains uncertain |
|---|---|---|
| Only one website causes the change | Does that page or its advertising initiate navigation? | Whether the site or an installed component is responsible |
| Address-bar searches use an unwanted provider | Which search entry or extension controls the choice? | Whether the change was authorized |
| Only startup or Home opens the page | Which launch, session, or Home setting applies? | Why that setting was established |
| One profile is affected; another behaves normally | What differs in settings, extensions, and management? | Whether the rest of the device is trustworthy |
| Several browsers or devices are affected | What shared application, account, or environment needs investigation? | The cause; broad scope does not prove a router compromise |
A comparison narrows what you observed. It does not certify a clean computer or tell you to delete every component unique to the affected profile. Preserve the observation so support can reproduce the circumstances using safe checks.
Inspect settings and who controls them
Use the controls for the affected browser: Chrome, Edge, Firefox or Safari on Mac. Search, homepage, startup and new-tab choices can be separate. Record which action redirects before changing them.
If an unwanted browser add-on is involved, use the extension removal guide for supported controls, managed installations, recurrence and any exposed account access.
Open settings through the browser menu. In Chrome, inspect Settings > Search engine and Settings > On startup, using Google’s search instructions and startup documentation. Check the Home destination separately if that button is the trigger. Restoring a previous session can reopen an old tab without a new installation.
Review the affected browser’s extension manager and record extensions associated with the changed setting. Chrome’s extension guidance explains supported controls and notes that Windows or Mac applications can also install extensions. A name you recognize does not prove trust, and a name you do not recognize is not sufficient evidence for removal.
Check whether a setting names an extension or is enforced. Google’s managed-browser instructions describe Chrome’s management notice and inspection pages. On work or school equipment, ask IT about policy. If management is unexpected on a personal device, preserve the details for investigation; do not run a policy-deletion script to make the label disappear.
When an unwanted controller or persistent setting is identified, use the browser-hijacker removal workflow. It provides the Chrome and Edge corrections, software checks, reset consequences, and verification steps. This symptom article helps establish which part of that procedure is warranted.
Understand the pop-up blocker’s limits
Chrome’s Settings > Privacy and security > Site settings > Pop-ups and redirects lets you inspect allowed-site exceptions. Google documents these permissions, including legitimate uses of pop-up windows. Correct an unwanted exception without allowing all sites to open pop-ups.
A pop-up blocker is one browser control, not a verdict about navigation or installed software. Closing an ad window does not correct a changed search provider, and a blocked pop-up does not show that an extension was removed. Keep the original trigger in view instead of changing unrelated settings until the behavior seems quieter.
Choose the next action
If the behavior occurs only on a particular site, avoid it and retain the observation. Contact that site’s established support through a trusted route if a legitimate service is affected. If search, startup, or Home remains unwanted, follow the browser-hijacker workflow. If advertising or an installed application is implicated, use adware source checks.
Google’s unwanted-software guidance identifies persistent redirects and changing browser settings as reasons to inspect further. Scan when execution, recorded findings, or unexplained software involvement warrants it; use the Windows scan guide or the installed Mac product’s procedure. Read the completed action and scope rather than treating one clean result as an explanation for the redirect.
If redirects affect multiple devices or the controlling component remains unknown, give qualified support the trigger, destinations, affected profiles, recent changes, and existing logs. Avoid random DNS, proxy, certificate, or router edits. Those changes can disrupt normal access while obscuring the original problem.
If you entered credentials or approved access on an unexpected page, use a trusted device and the affected provider’s recovery process. Microsoft’s scam guidance explains impersonated destinations; the infostealer article explains why account exposure may require work even after browsing returns to normal.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.
- MDN Web Docs: HTTP redirections and legitimate uses
- Google Chrome: Remove unwanted ads, pop-ups and malware
- Google Chrome Help: Pop-up and redirect permissions
- Google Chrome Help: Install, manage, and remove extensions
- Google Chrome Help: Browser management and policies
- Google Chrome Help: Default search engine and site search
- Google Chrome Help: Homepage and startup pages
- Microsoft Support: Protect yourself from online scams and attacks