Home >BlogMy client bought an old domain and pointed it at their new site — howPublished 2026/10/22Updated 2026/10/22The symptom: old pages redirect somewhere, nobody knows whereA client buys an old domain, points it at a new site, and weeks later search traffic is still falling. The usual cause is not missing redirects, it is redirects that lead somewhere wrong: old URLs hitting the homepage, chains that bounce through three hops, or destinations returning 404. This guide walks through auditing the whole redirect setup before anything else gets changed.Why this keeps happeningOne wildcard rule. A single catch-all redirect sends every legacy URL to the homepage, which looks fine in a browser and fails in search.Domain-level instead of path-level mapping. The old blog, products, and contact pages all deserve separate destinations.Redirect chains. A rule added on top of another rule produces 301 → 302 → 200 paths that waste crawl budget.No re-test after deployment. Rules are written, never verified, so 404s ship silently.Step 1: build the complete list of legacy URLsYou cannot audit what you have not listed. Gather candidates from four places:XML sitemaps and the Wayback Machine for pages that still get requests.Google Search Console crawl and coverage reports for indexed URLs.Backlink reports (Ahrefs, Semrush, or your own export) for URLs other sites still link to.CMS exports and analytics top pages for the URLs that actually earn traffic.Write them down with a note of what each one should point to, for example /blog/old-guide/ → the new guide page, /products/widget.html → the new product page. URLs with links, traffic, or rankings get priority.Step 2: test every URL's status and destinationCheck the HTTP status code and the final Location after all hops. A healthy permanent move is 301 to the most relevant new page, not just the homepage. A 404 means the destination does not exist yet. curl -sI -L -o /dev/null -w "%{http_code} %{url_effective}\n" https://oldsite.com/blog/old-guide/ Batch-test the whole list, then look at the pattern of failures rather than single rows.Step 3: audit chains, loops, and broken destinationsRead the full hop path, not just the final code:301 → 200: healthy permanent redirect to a working page.301 → 302 → 200: a chain worth simplifying to one rule.301 → 404: broken destination, highest priority to fix.A → B → A: a loop; fix before touching anything else.Redirect Chain Checker (https://redirectchainchecker.com/) inspects each hop and the final status, so you can spot intermediate hops and loops without clicking through manually. Test single URLs or batches where supported, then review the final destination and status for every entry.Step 4: fix, then verify after deploymentMap each legacy URL to its closest relevant new page, correct the rules at the server or CMS level, and retest the failures. Watch for these mistakes while fixing:Redirecting everything to the homepage instead of the matching page.Using 302 for permanent moves; search engines treat it as temporary.Adding conflicting rules that override each other.Assuming a redirect test alone guarantees SEO recovery; monitor Search Console for crawl errors afterward.Close the loop with a checklist: export the results, resolve every error, retest, then watch Google Search Console for crawl errors and indexing changes over the next few weeks.FAQShould every old URL redirect to the new homepage?No. Redirect each URL to the most relevant new page. Homepage redirects lose the page-level signals and the user lands somewhere irrelevant.Is a 302 ever the right answer for a domain move?Only for genuinely temporary situations. A permanent domain move should use 301 so search engines transfer the signals.How long do redirects need to stay in place?Keep them as long as the old domain exists and links point at it, typically years. Removing a 301 early lets legacy links start 404ing again.Why does my redirect work in the browser but not in search?Browsers follow chains quietly; crawlers record every hop and may give up on long or looping chains. Simplify the path until one rule reaches the final page.