Home >BlogMy client bought an old domain and pointed it at their new site — how do I check that all the old links redirect properly?Published 2026/10/07Updated 2026/10/07How do you check old-domain redirects without missing a hop?An old-domain migration can look finished in a browser while a deeper URL still loops, loses its path, or lands on the wrong section. The question is not simply whether the old homepage opens; it is whether representative old URLs reach the intended new URLs with a short, visible chain.Use a redirect checker to inspect each response in order. Keep the old path, query string, status code, Location header, and final URL together so you can fix the rule rather than guess at it.Questions readers usually askShould I test the old homepage only?No. Test the homepage plus old product, article, image, and parameterised URLs. Migrations often preserve the root path while individual routes fall through to a generic homepage or a second redirect rule.What counts as a redirect chain?A chain has two or more redirect responses before the final page. One clean 301 or 308 is easier to crawl and debug than a sequence such as HTTP to HTTPS, old host to www, then path rewrite. The exact count is visible only when you inspect every hop.How can I tell whether the path was preserved?Compare the requested old path with the final new path, not just the domain. A product URL that ends at a site homepage may return HTTP 200 and still be a migration failure because the useful content was lost.What does a redirect loop look like?The same two or more URLs repeat until the checker stops. Common causes include competing HTTP-to-HTTPS rules, an old host rule that points back to itself, or an application rule that rewrites the already migrated path.Which status codes should I expect?Permanent migrations usually use 301 or 308, while 302 and 307 indicate a temporary redirect. The right choice depends on the migration plan, but the important part is that the status and Location header match the intended policy.Do redirects prove the new page is correct?No. They prove the route reaches a response. Open or fetch the final URL and check its title, canonical, status, and visible content separately. A perfect redirect chain can still point to a page that is missing or irrelevant.Try the focused workflow.Run representative old URLs through Redirect Chain Checker, then verify the final page content and canonical URL before changing every legacy rule.FAQShould I test the old homepage only?No. Test the homepage plus old product, article, image, and parameterised URLs. Migrations often preserve the root path while individual routes fall through to a generic homepage or a second redirect rule.What counts as a redirect chain?A chain has two or more redirect responses before the final page. One clean 301 or 308 is easier to crawl and debug than a sequence such as HTTP to HTTPS, old host to www, then path rewrite. The exact count is visible only when you inspect every hop.How can I tell whether the path was preserved?Compare the requested old path with the final new path, not just the domain. A product URL that ends at a site homepage may return HTTP 200 and still be a migration failure because the useful content was lost.What does a redirect loop look like?The same two or more URLs repeat until the checker stops. Common causes include competing HTTP-to-HTTPS rules, an old host rule that points back to itself, or an application rule that rewrites the already migrated path.Which status codes should I expect?Permanent migrations usually use 301 or 308, while 302 and 307 indicate a temporary redirect. The right choice depends on the migration plan, but the important part is that the status and Location header match the intended policy.Do redirects prove the new page is correct?No. They prove the route reaches a response. Open or fetch the final URL and check its title, canonical, status, and visible content separately. A perfect redirect chain can still point to a page that is missing or irrelevant.