URL Redirect Checker
Follow a public URL through its HTTP redirects. See each response code, spot unnecessary hops and check where the journey stops.
FOLLOW THE DESTINATION
A moved page should still lead somewhere useful.
Check the response, the route and the final page before calling a redirect fixed.
HIMANSHU'S APPROACH
A redirect is a decision about the visitor's next step
When I review a website migration, I do not stop at finding a 301 response. I check whether the old URL leads to the closest relevant replacement. A working redirect to an unrelated homepage can still leave a customer without the product, service or answer they came for.
Start with one old address here. Read each response in order, then open the final page yourself. For a larger move, keep an old-to-new URL map and test it alongside your internal links, canonicals and sitemap.
Read the response before changing the rule
301 / 308
Permanent move
These responses indicate a permanent destination change. Use them when the replacement is intended to stay. A redirect does not promise unchanged rankings or traffic.
302 / 307
Temporary route
Check whether a temporary rule has been left behind after a redesign, campaign or maintenance period.
303
See another resource
Often used after a form submission. This checker starts with GET requests; it does not reproduce checkout or login submissions.
200
Page returned
The request succeeded at HTTP level. Inspect the content: an irrelevant destination or soft error page can also return 200.
404 / 410
No available page
Choose a relevant replacement where one exists. Do not send every retired URL to the homepage.
5xx
Server problem
Check hosting, proxy and application logs before adding another redirect rule.
Three checks after a URL change
- Remove avoidable hops. Point old addresses directly to their intended replacement where you control the rules.
- Update links you own. Navigation, products and articles should link to the final address. Redirects protect old references; they do not replace internal-link maintenance.
- Inspect the destination. Check content, indexability and canonical with the Meta Tags Checker, then review the page in Search Console.
Explore ecommerce SEO for product moves, or multilingual SEO and international SEO for language and country structures.
What this trace covers
This tool makes public HTTP GET requests and reads response headers. It follows 301, 302, 303, 307 and 308 responses, resolves relative Location values and stops at repeated URLs. It checks up to 10 URLs with a 30-second request budget; DNS resolution and network conditions can add delay.
It does not execute JavaScript, follow HTML meta refreshes, sign in, keep session cookies between hops or reproduce a visitor's location. Anti-bot controls can change responses. Private addresses, nonstandard ports and IPv6-only hosts are unsupported. A stopped trace does not prove that a destination is broken for every visitor.
Redirects, search and AI discovery
A moved page should not leave existing references pointing at a dead end. Clear routes help visitors and crawlers reach the current resource, but this check cannot confirm indexing or AI citations. Keep the replacement accurate, accessible and internally linked. See AI search services for the wider work, or discuss a migration through SEO consulting.
Redirect checker questions
Should every old URL redirect to my homepage?
No. Map useful URLs to their closest relevant replacement. Where none exists, a genuine not-found or gone response may be appropriate. Review the content and intent first.
What is the difference between a chain and a loop?
A chain passes through several destinations before stopping. A loop returns to an address already visited. The checker preserves completed steps when it stops.
Can I test HTTPS and www redirects?
Yes. Enter each version separately, including its protocol. Compare whether the addresses reach the version you intend to use.
Why does my browser show a different destination?
Your browser may cache redirects, retain login cookies, upgrade HTTP or execute JavaScript. Geography and bot protection can also affect responses. This is a server-side check, not a full browser session.
Will a 301 recover lost rankings?
A relevant redirect can help handle a move, but recovery depends on the wider migration and replacement content. I review URL mapping, indexing, internal links and performance together.
Can you implement the fixes?
Yes. Share your website and what changed. I can review the redirect map and agree implementation with you or your developer. This checker itself does not change your website.
Further reading
Google's redirects and Google Search documentation explains permanent and temporary redirects.