301 Redirect Checker: Trace Every Hop and Fix Redirect Chains
A 301 redirect checker shows you exactly what happens when a browser or search engine requests a URL: every hop in the redirect chain, the HTTP status code of each one, where it points next, how long it took and what the final page returns. Our free redirect checker follows up to 10 redirects one step at a time, so you can spot redirect chains, loops, temporary redirects that should be permanent and HTTPS problems in seconds, then fix them with copy-ready code.
This guide explains the different redirect types, how they affect SEO, how to read your results and how to set up redirects correctly on Apache, Nginx, WordPress and Cloudflare.
Key takeaways
- Use a 301 (or 308) for permanent moves so search engines transfer signals to the new URL.
- Each redirect should go straight to the final URL: chains slow pages down and waste crawl time.
- Update internal links to the final URL instead of relying on redirects.
- Redirect loops and chains that end in 404s are urgent; fix them first.
What is a 301 redirect checker?
A 301 redirect checker requests a URL without automatically following redirects, records the response, then requests the next URL in the chain, and repeats until it reaches a page that doesn’t redirect. Browsers hide this process; you only see the final address. The checker reveals every step so you can see what search engines actually experience.
Why redirects need checking
Redirects pile up over time: an HTTP-to-HTTPS rule, a www rule, a trailing-slash rule, an old page moved twice. Each makes sense on its own, but together they create chains that slow pages down and dilute signals. Migrations, rebrands, CMS changes and CDN settings can also introduce loops that make pages unreachable.
Who uses a redirect checker
- SEO specialists auditing migrations and old backlinks.
- Developers verifying server rules before and after deployment.
- Marketers checking that campaign and short links land on the right page.
- Site owners confirming that HTTP and www versions point to the main site.
How to use our redirect checker
- Enter the URL you want to trace. To test HTTPS redirects, enter the
http://version. - Choose a user agent: desktop browser, mobile browser, Googlebot smartphone or Bingbot. Some sites redirect differently for mobile users or bots.
- Click Trace redirects and read the summary: number of redirects, final status and total time.
- Review the chain. Each hop shows its status code, response time, URL and Location header.
- Expand the response headers of the final URL to check caching, security headers and more.
- Follow the fix suggestions, which include ready-to-paste .htaccess and Nginx rules.
http://example.com, http://www.example.com, https://example.com and https://www.example.com. All should reach the same final URL in one hop.Redirect status codes explained
| Code | Name | Permanent? | When to use it |
|---|---|---|---|
| 301 | Moved Permanently | Yes | A page or site has moved for good |
| 308 | Permanent Redirect | Yes | Like 301, but keeps the request method (useful for forms and APIs) |
| 302 | Found | No | Short-term moves, such as a temporary promotion |
| 307 | Temporary Redirect | No | Like 302, but keeps the request method |
| 303 | See Other | No | After a form submission, to a confirmation page |
Google explains how it treats each type in its documentation on redirects and Google Search.
301 vs 302 for SEO
A 301 tells search engines the move is permanent, so they replace the old URL with the new one in their index and consolidate signals onto it. A 302 suggests the old URL will come back, so search engines may keep showing the old address. Google treats long-lasting 302s as permanent eventually, but using the right code from the start avoids delays and confusion.
Meta refresh and JavaScript redirects
These happen inside the page rather than at the server. They’re slower, less reliable for passing signals and can look suspicious when they send users somewhere unexpected. Our checker detects meta refresh redirects and recommends a server-side 301 instead.
Other status codes you’ll see
- 200 OK: the final page loaded successfully.
- 404 / 410: the chain ends on a missing page.
- 403 / 429: the server refused the request, often a firewall or rate limit.
- 5xx: the server failed.
See all codes in Google’s guide to HTTP status codes and network errors or MDN’s HTTP status reference.
Understanding your redirect checker results
No redirects
The URL loads directly. That’s ideal for your main URLs.
One redirect
A single 301 from an old or alternative URL to the final page is perfectly fine.
Redirect chain
Two or more hops before the final page. Each hop adds a round trip, typically tens to hundreds of milliseconds, and Google stops following after about 10 hops.
How to fix a chain
- Find the first URL in the chain and the final destination.
- Change the first redirect to point directly to the final URL.
- Update internal links, menus, canonical tags and your sitemap to use the final URL.
Example
http://example.com/old/ → https://example.com/old/ → https://www.example.com/old/ → https://www.example.com/new/ should become a single 301 from each old version straight to https://www.example.com/new/.
Redirect loop
The chain points back to a URL it already visited, so the page never loads and browsers show “too many redirects”. This is urgent.
Temporary redirects
302 or 307 hops on permanent moves. Change them to 301 or 308.
HTTPS downgrade
A hop from https:// to http:// lowers security and can trigger loops. Point it at the HTTPS URL.
Final URL returns an error
The chain ends on a 404 or 5xx. Redirect to the most relevant live page or restore the page. Don’t automatically send everything to the home page; Google may treat irrelevant redirects as soft 404s.
No HSTS header
Strict-Transport-Security tells browsers to always use HTTPS, skipping the HTTP redirect on repeat visits. It’s a good security practice once every subdomain works over HTTPS.
The most common redirect problems and fixes
Cloudflare Flexible SSL loops
With Cloudflare’s SSL/TLS mode set to Flexible, Cloudflare connects to your server over HTTP. If your server redirects HTTP to HTTPS, every request loops. Set the mode to Full (strict) after installing a certificate on your server.
WordPress address mismatch
If Settings → General uses http:// or a different www version from your server rules, WordPress and the server can redirect back and forth. Make both match the final URL.
Conflicting plugins and server rules
Redirect plugins, SEO plugins, security plugins and .htaccess can all add redirects. Keep redirects in one place where possible and document them.
Redirecting deleted pages to the home page
Map each removed page to its closest equivalent: a discontinued product to its category, an old article to its updated version. If there’s no relevant replacement, a 404 or 410 is the honest answer.
How to set up 301 redirects
Apache and LiteSpeed (.htaccess)
# Single page
Redirect 301 /old-page/ https://example.com/new-page/
# Force HTTPS
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]Nginx
location = /old-page/ { return 301 https://example.com/new-page/; }
server {
listen 80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
}WordPress
Use a redirect plugin such as Redirection, or the redirect manager in Yoast SEO Premium or Rank Math. Choose 301 as the type. Some SEO plugins also create redirects automatically when you change a slug.
Shopify
Go to Online Store → Navigation → URL Redirects and add the old path and the new path. Shopify creates 301 redirects.
Cloudflare
Use Redirect Rules (or bulk redirects for many URLs). Make sure the status code is 301 and that rules don’t conflict with redirects on your server.
Redirects during site migrations
Migrations are where redirects matter most. Changing domain, moving to HTTPS, switching CMS or restructuring URLs without a redirect map can wipe out years of search visibility.
Build a redirect map
- Export every URL that has traffic, rankings or backlinks.
- Match each old URL to its new equivalent in a spreadsheet.
- Implement one-to-one 301 redirects, not blanket redirects to the home page.
- Test a sample of old URLs with a 301 redirect checker, including high-value pages.
After launch
- Crawl the new site and update internal links to final URLs.
- Submit the new sitemap in Search Console; validate it first with our sitemap validator.
- Use Search Console’s Change of Address tool for domain moves.
- Run our broken link checker online on key pages to catch links that now redirect or break.
How redirects affect speed and Core Web Vitals
Every redirect adds a full request before the page can start loading. On mobile networks, one extra hop can add a noticeable delay to Largest Contentful Paint. Linking directly to final URLs, removing chains and enabling HSTS so returning visitors skip the HTTP hop all help. Measure the overall effect with PageSpeed Insights and our website page size checker.
Do 301 redirects pass SEO value?
Yes. Google has confirmed that 301, 302 and other server-side redirects don’t lose PageRank. A permanent redirect is a strong signal that the target should become the canonical URL, so links, relevance and history pointing at the old address consolidate onto the new one. That’s why redirects are essential whenever a URL changes.
Why rankings can still dip after redirects
Signals don’t transfer instantly. Google has to recrawl the old URLs, discover the redirects and process the new pages, which can take weeks for less-visited URLs. Rankings can also change because the new page is different: a thinner page, a different topic or a weaker title. Redirect to genuinely equivalent content and keep the on-page elements strong.
Irrelevant redirects
Redirecting many old pages to an unrelated page, such as the home page, doesn’t carry their value. Google may treat these as soft 404s, so each old URL should point to the closest relevant replacement.
When to run a 301 redirect checker
After changing URLs or slugs
Whenever you rename a page, change a category structure or tidy up slugs with our URL slug generator, check that the old URL lands on the new one in a single hop.
When reviewing backlinks
Links from other websites often point to old URLs. Trace those URLs to make sure they reach a live, relevant page rather than a chain or a 404.
When ad or email links misbehave
Tracking parameters can be lost in some redirects. If campaign data looks wrong in analytics, trace the landing URL, including its parameters, created with our UTM builder for GA4.
When pages are slow to start loading
A slow first byte is sometimes a redirect chain in disguise. The total time in the checker shows how much each hop costs.
Keep a simple redirect map, a spreadsheet of old URL, new URL and the date added, and re-check it after every major change. It makes migrations safer, helps you spot chains as they form and means anyone on your team can understand why a redirect exists before they remove it. Review the map once a year and update any internal links that still point at old URLs, so visitors and crawlers go straight to the final page without a hop.
Redirect checklist
- All versions of your domain reach one final URL in a single hop.
- Permanent moves use 301 or 308.
- No chains, loops or HTTPS-to-HTTP redirects.
- No redirects ending on 404 or 5xx pages.
- Removed pages redirect to their closest relevant replacement.
- Internal links, canonicals and sitemaps point to final URLs.
- HSTS enabled once HTTPS works everywhere.
Related free SEO tools
- Broken link checker online: find links that redirect or break.
- Google index checker: see whether a redirect is stopping a page being indexed.
- Sitemap validator: find redirected URLs listed in your sitemap.
- Free SEO checker: full on-page audit including redirects and canonicals.
- Who is hosting this website: check the server and CDN behind a domain.
Ready to see where your URLs really go? Run the 301 redirect checker above.