Domain Forwarding SEO

I start by deciding whether the move is permanent. If it is, I use a 301 redirect and nothing else. A 302 or 307 is for temporary moves, and masked forwarding is for people who want a pretty URL without the work — it does not pass signals. When I migrated a client from old-brand.com to new-brand.com, I mapped every old URL to its new equivalent. That meant 47 product pages, 12 category pages, and the blog archive. I used a spreadsheet to match them one-to-one. I then set up the redirects at the server level (Apache .htaccess in that case) and tested each one with a browser and a tool like Redirect Path. The result: within two months, Google had transferred roughly 90% of the ranking equity from the old domain to the new one. The only drop was short-lived, and it recovered. I also updated the [301 redirect](/301-redirect/) mapping in the [sitemap](/what-is-a-sitemap/) to point to the new domain, so Google had a clear signal of the new structure. I submitted a change of address in Search Console, which accelerated the process. That is the path I take every time now: permanent redirect, full URL mapping, and a submission to Google. I also keep the old domain live for at least six months to catch any residual traffic or bookmarks. The key is to avoid shortcuts — every missing redirect is a lost visitor and a missed signal. I also check for [duplicate content](/duplicate-content/) issues by ensuring that the old domain does not accidentally serve content alongside the new one. A [canonical tag](/canonical-tag/) on the old domain pointing to the new one adds an extra layer of safety, but I prefer the redirect because it is definitive.

The biggest trap is masked forwarding. Some registrars offer it as a free option: you point domain A to domain B, and the browser shows domain A in the address bar while the content comes from domain B. That is a disaster for SEO. Google sees the content at domain B but the URL is domain A, so it treats domain A as the canonical source. You end up with two URLs competing for the same content, and the redirect never passes link equity. I have seen sites lose 40% of their organic traffic because of this. Another watch-out is redirect chains. When you set up a redirect, make sure it goes directly to the final URL. If you redirect old.com to new.com, and then later redirect new.com to newer.com, you create a chain that wastes crawl budget and can lose equity along the way. I once found a client with a chain of four redirects — the final page loaded in 2.5 seconds instead of 1.2 because of the extra hops. That is a penalty you can avoid by testing with a tool like Screaming Frog and consolidating. Also, do not assume that a newly registered domain with no history will gain value by forwarding to an established site. I have seen people buy a keyword-rich domain and forward it to their main site, hoping for a boost. It rarely works. Search engines treat that as a redirect of a domain with no authority, and you get little to no lift. Spend your money on content or backlinks instead. Finally, watch the timing. Google can take weeks to process a domain change. During that window, you might see a dip in rankings. That is normal, but you can soften it by keeping the old domain live and not deleting it. I also run a [seo audit](/seo-audit/) after the move to check for broken links, orphaned pages, and indexing gaps. A domain migration is not a one-day task; you need to monitor for at least three months.

I used to think that masked forwarding was a neat way to keep the old domain visible while pointing to the new site. I set it up for a personal project, forwarding my old blog domain to a new one. The content appeared fine, the URL bar showed the old domain, and I thought I was clever. Six months later, I noticed that the new domain had almost no rankings. The old domain had the content, but it had no backlinks of its own. The masked forwarding meant that search engines indexed the old domain as the canonical URL, but the old domain had no authority. I had essentially created a duplicate content situation where neither domain performed well. I switched to a 301 redirect, and within three months the new domain started ranking. That mistake cost me half a year of growth. Another error: I set up a domain redirect and forgot to update the internal links on the new site. The pages still linked to the old domain, which redirected to the new one. That created a redirect chain for every click. I found it when I ran a [website structure](/website-structure/) audit and saw 30 internal redirects. I fixed them by updating the links directly, which cut page load time by 200ms. I also learned that you should never forward a domain that you plan to use again. If you think you might want the old domain back, use a 302 instead of 301, because a 301 is permanent and Google will de-index the old domain. I once helped a friend who wanted to forward a domain temporarily while a site was under construction, then switch back. I used a 301, and when he tried to switch back, the old domain had lost all its rankings. That was a hard lesson. Now I always ask: 'Is this permanent? If yes, 301. If not, 302 or leave it.'