Redirecting a Domain Without Losing SEO

Changing a website’s domain can put years of search visibility at risk if you handle the move poorly. Existing pages, rankings, backlinks, and organic traffic are tied to URLs search engines already recognise, so simply pointing an old site to a new one isn’t enough. The safer approach is to redirect each important URL to its relevant replacement and give search engines clear signals about the move. 

This guide explains how to plan and implement those redirects, verify that they work correctly, avoid common SEO problems, and keep the old URLs active long enough for the move to be processed.

Can You Redirect a Domain Without Losing SEO?

Yes. A properly implemented permanent redirect can preserve the SEO signals associated with URLs on the old site when they move to a new one. Google states that 301 and other permanent redirects do not cause a loss of PageRank, so changing the site’s address does not mean starting its search visibility from scratch.

However, a redirect does not guarantee that rankings and traffic will remain unchanged immediately. Google may temporarily fluctuate rankings while it recrawls and indexes the new URLs, and it does so URL by URL. The key is to send each important old URL to its relevant new destination and maintain consistent signals throughout the move.

The Right Way to Redirect an Old Domain to a New Domain

A successful move is not about sending every visitor from the old site to the new homepage. The important part is preserving the connection between individual old URLs and their relevant replacements. Before switching over, map the URLs that matter, then implement direct permanent redirects and update the new site’s signals so Google can process the move consistently.

Map the Old URLs to Their New Equivalents

Start by identifying the important URLs on the old site and deciding where each one should go on the new site. A simple URL map can show the relationship:

The destination should be the closest relevant replacement, not simply the homepage. This matters when the site’s URL structure changes during the move. Google recommends mapping old URLs to their corresponding new URLs so users and search engines can reach the appropriate content at its new location.

Use a Permanent Redirect for the Move

Once the URL map is ready, implement a server-side permanent redirect from each old URL to its new equivalent. A 301 redirect is the most common option, while a 308 redirect can also be used for a permanent move.

Temporary redirects such as 302 are intended for situations where the original URL is expected to return. They are therefore not the normal choice when a site has permanently moved to another address. Google recommends permanent server-side redirects for permanent URL changes.

Keep Each Redirect Direct

Whenever possible, send the old URL straight to its final destination:

Old URL → New URL

Avoid setups such as:

Old URL → Intermediate URL → New URL

Multiple redirects make the path longer for both visitors and crawlers and can create unnecessary problems during a migration. Google recommends avoiding redirect chains and sending users directly to the final destination.

Update the New Site’s URLs

The new site should use its new URLs directly rather than relying on redirects for its own navigation. Update internal links, canonical URLs, and the XML sitemap so they consistently reference the new locations.

This gives Google a clearer picture of the new site and reduces unnecessary requests through the old URLs. The sitemap should include the new URLs you want Google to crawl and index, while canonical tags should point to the corresponding new versions.

Tell Google About the Domain Change

After the redirects and new site are ready, use Google Search Console’s Change of Address tool to notify Google that the site has moved from one domain to another. The tool does not replace the redirects. Make sure the redirects are working before you submit the change.

Also verify the relevant versions of both sites in Search Console and submit the new XML sitemap. Google recommends using Change of Address for domain-to-domain moves and keeping the redirects in place while Google processes the change.

How to Check That the Domain Redirect Is Working

A redirect is only useful if it sends the right old URL to the right new destination. After the change goes live, test a representative set of important URLs rather than assuming the rules work as intended. Google recommends testing redirects with the URL Inspection tool for individual URLs, or with scripts and command-line tools for larger sets.

Check that:

• The old URL redirects to the intended new URL.
• The redirect uses a permanent status code.
• The request does not pass through another redirect first.
• The destination page loads normally and is not a 404.
• Important pages are not blocked from crawling or indexing.
• The new sitemap contains the corresponding new URLs.

Also check Search Console after the move. Google recommends monitoring both the old and new sites for changes in traffic, indexing, and unexpected crawl errors. As the migration progresses, indexing of the old URLs should decline while the new URLs become indexed.

For larger sites, don’t rely on manually checking a handful of pages. Crawl the redirect set in bulk so you can identify incorrect destinations, unexpected status codes, and other migration errors before they affect more of the site.

What Can Cause SEO Loss After a Domain Redirect?

A domain change doesn’t automatically erase a site’s search visibility. Problems usually arise when important URLs redirect incorrectly, the new site sends mixed signals, or search engines remove old URLs before they’ve processed the move. The most common issues include:

Redirecting Every Old URL to the Homepage

Sending every old URL to the new homepage may seem convenient, but it doesn’t preserve the relationship between individual pages. A product page, service page, or article should normally redirect to its relevant replacement, not a generic destination.

If no suitable replacement exists for an old page, forcing an unrelated redirect is unlikely to provide the same value as directing users to a genuinely relevant page.

Using a Temporary Redirect for a Permanent Move

For a permanent change, use a permanent server-side redirect, such as a 301 or 308. Using a temporary redirect for a permanent move can send a different signal about the relationship between the old and new URLs.

Creating Redirect Chains or Loops

A redirect should ideally take the old URL directly to its final destination. Chains add unnecessary steps, while loops can prevent the destination from loading at all. Both are worth catching during testing before the migration is fully processed.

Leaving Old URLs Throughout the New Site

After the move, internal links, canonical tags, and the XML sitemap should reference the new URLs. Leaving these elements pointed at the old site creates unnecessary redirects and makes it less clear which URLs should be crawled and indexed.

Blocking the New Site From Crawling

A migration can fail even when the redirects themselves are correct if the new site is accidentally blocked by robots.txt, a noindex directive, authentication, or another access restriction. Google needs to crawl the new URLs to process the move.

Removing the Redirects Too Soon

The old URLs still matter after the new site goes live. Users may have bookmarks, and other websites may still link to the previous addresses. Google also needs time to crawl the redirects and process the new URLs. Keeping the redirects active gives both users and search engines a path from the old locations to the new ones.

How Long Should You Keep the Old Domain Redirect?

Don’t remove redirects as soon as the new site starts appearing in search results. Google recommends keeping redirects in place for at least 180 days, and longer if Google Search traffic is still reaching the old URLs. This gives search engines time to crawl the redirects and users time to follow links that still point to the previous addresses.

Google also recommends keeping the old domain registered for at least one year after the move. This helps prevent someone else from registering the previous addresses while old links and references to the site are still in circulation.

Treat the 180-day period as a minimum, not an automatic expiration date. If important pages still receive organic traffic, backlinks, or referrals through the old URLs, keeping the redirects active longer can help maintain a reliable path to the new site.

Conclusion

Changing a domain does not mean starting your SEO from scratch. The key is to maintain a clear connection between the old URLs and their relevant new destinations, use permanent redirects, and keep the new site consistent with its own URLs. Testing the redirects and monitoring Search Console after the move can also catch problems before they affect more pages. With a structured approach, you can handle a domain change without unnecessarily sacrificing the search visibility and signals the site has already built.