| Clean |
No redirect issue found |
This page resolved cleanly. There is no redirect chain and no immediate protocol or loop problem to fix. |
Copy summary · Export chain |
| Needs attention |
This chain resolves, but it is inefficient |
The request eventually lands on a valid page, but the chain uses mixed protocol, includes a temporary redirect, and takes more hops than it should. |
Copy summary · Export chain · Run a deeper site check in Semrush |
| Broken |
Redirect loop blocks the request |
The browser keeps bouncing between URLs and never reaches a stable final page. |
Copy summary · Export chain · Audit redirect issues in Semrush |
| Empty |
Open any page to start monitoring |
This extension watches main page loads automatically and shows redirect chains, loops, and status changes for the current tab. |
No CTA |
| Loading |
Waiting for the final destination |
This request is still resolving. The extension will update automatically when the chain finishes. |
No CTA |
| Error |
Could not load redirect data |
The extension could not retrieve the current tab's redirect data. Reload the page or navigate again, then reopen the extension. |
Retry |
| Mixed protocol card |
Mixed HTTP and HTTPS |
Part of the chain still starts on HTTP, which can create avoidable redirect overhead and trust issues. |
Read: How to Redirect HTTP to HTTPS |
| Temporary redirect card |
Temporary redirect in permanent flow |
A 302 appears inside a path that looks permanent. That can send mixed signals to crawlers and site owners. |
Read: 301 vs. 302 Redirect |
| Long chain card |
Long redirect chain |
Three hops add unnecessary latency and crawl overhead before users reach the final page. |
Read: Redirects: What They Are & How to Use Them |
| Loop card |
Redirect loop detected |
The same request path keeps routing users back into the chain, so the page cannot load. |
Read: What Is the Too Many Redirects Error? |