Domain Forwarding and SEO: What You Need to Know

Domain forwarding is one of the simplest features offered by domain registrars, and one of the most misunderstood when it comes to SEO. Point one domain at another with a few clicks, and traffic flows. But the way that forwarding is implemented determines whether your search rankings transfer cleanly or disappear entirely.

This article covers what domain forwarding actually does at the technical level, how different forwarding methods affect SEO, and when you should skip the registrar's forwarding tool and use proper hosting instead. For the full technical background on redirects, see the HTTP Redirect Guide.

What Domain Forwarding Is

Domain forwarding is a feature provided by domain registrars (GoDaddy, Namecheap, Google Domains, Cloudflare, etc.) that redirects all traffic from one domain to another. If you own oldbrand.com and want visitors to end up at newbrand.com, domain forwarding handles that without requiring you to set up a web server on the old domain.

Behind the scenes, the registrar configures DNS records for the forwarded domain to point to their own servers. When a request arrives, those servers issue an HTTP redirect to the destination domain. The visitor's browser follows the redirect and lands on the target site.

The critical detail is how that redirect is implemented. There are two fundamentally different approaches, and they have opposite effects on SEO.

301 Forwarding (Permanent Redirect)

Most registrars offer a "permanent" forwarding option that uses a 301 redirect. This is the SEO-friendly method.

When a visitor (or Googlebot) requests oldbrand.com/some-page, the registrar's server responds with:

HTTP/1.1 301 Moved Permanently
Location: https://newbrand.com/some-page

The browser follows the redirect, and the visitor sees newbrand.com/some-page in their address bar. From an SEO perspective, this is exactly what you want.

SEO Impact of 301 Forwarding

Link equity transfers. Any backlinks pointing to oldbrand.com pass their full PageRank to newbrand.com. Google confirmed in 2016 that 301 redirects pass full link equity with no dampening factor. For the detailed breakdown, see Do 301 Redirects Hurt SEO?.

Indexing shifts to the new domain. Google will eventually remove the old domain's URLs from its index and replace them with the new domain's URLs. This process typically takes a few weeks to a few months, depending on how frequently Google crawls the old domain.

Search rankings transfer. The rankings you built on the old domain should carry over to the new one, assuming the content at the destination URLs is equivalent to what was on the old URLs. If you redirect oldbrand.com/pricing to newbrand.com/about instead of newbrand.com/pricing, the topical mismatch will hurt.

Limitations of 301 Forwarding at the Registrar Level

Most registrars only forward the root domain and do not preserve path information. If someone visits oldbrand.com/blog/great-article, the registrar may redirect them to newbrand.com (the homepage) rather than newbrand.com/blog/great-article. This is a significant SEO problem because it means every page on the old domain redirects to a single page on the new domain, which Google treats as a soft 404 for the specific pages.

Check your registrar's documentation to see if they support path forwarding. Some do (Cloudflare, Namecheap with certain plans), some do not, and some only forward the root domain by default but offer path forwarding as a separate option.

If your registrar does not support path forwarding, you will need a more robust solution. More on that below.

Masked Forwarding (Frame Forwarding)

Masked forwarding, also called domain masking or frame forwarding, loads the destination site's content inside an HTML iframe while keeping the original domain in the browser's address bar. The visitor sees oldbrand.com in the URL bar but is actually viewing content served from newbrand.com.

How Masked Forwarding Works

When a visitor requests oldbrand.com, the registrar's server returns an HTML page containing an iframe that loads newbrand.com:

<html>
  <frameset>
    <frame src="https://newbrand.com">
  </frameset>
</html>

The visitor sees the content from newbrand.com but the address bar still shows oldbrand.com.

Why Masked Forwarding Is Bad for SEO

Masked forwarding is one of the worst things you can do for SEO. Here is why.

No redirect signal. There is no HTTP redirect happening. Google sees the old domain serving a frameset page, not a redirect to the new domain. No link equity is transferred.

Thin content. The actual HTML content that Google indexes on the old domain is an empty frameset. This is the definition of thin content. Google may penalize the old domain or simply ignore it.

Duplicate content risk. Both domains serve the same content. Google has to decide which one is the original. Without a redirect or canonical signal, it may choose the wrong one, or it may dilute ranking signals between both.

Broken user experience. The URL in the address bar never changes as the user navigates the site inside the iframe. Bookmarks, sharing, and back-button behavior all break. Users who share a link share the framed URL, which may not resolve correctly for others.

No HTTPS consistency. If the framing page is HTTP but the framed content is HTTPS (or vice versa), browsers may block the content entirely due to mixed content policies.

The only legitimate use for masked forwarding is when you specifically want two domains to appear to serve the same content without any SEO benefit. In practice, this is almost never what you want. Avoid masked forwarding for any domain where search visibility matters.

When to Use Domain Forwarding

Domain forwarding through your registrar is appropriate in a few specific situations.

You own a typo domain. If you registered newbrand.co or newbrand.net to catch misspellings and typos, forwarding them to your primary domain with a 301 is the right move. These domains likely have no SEO value of their own, and forwarding prevents confusion.

You acquired a competitor or related domain. If you purchased a domain that has existing backlinks and you want those links to benefit your primary site, a 301 forward transfers the equity. Make sure path forwarding is supported if the old domain had indexed pages.

You rebranded. Moving from oldbrand.com to newbrand.com is a classic use case. A 301 forward from the old domain to the new one signals the change to search engines and transfers rankings.

You consolidated multiple domains. If you operated the same business on multiple domains and want to consolidate, 301 forwarding each secondary domain to the primary one is correct.

In all these cases, make sure the registrar is using a 301 (not a 302 or masked forward), and verify with curl or Redirect Tracer that the redirect is working as expected.

When to Use Proper Hosting Instead

Registrar-level forwarding has limitations that matter for complex setups. Here is when you need more than your registrar's forwarding tool.

You need path-level redirects. If oldbrand.com/pricing should go to newbrand.com/plans (different path), most registrar forwarding cannot handle that. You need a web server (Nginx, Apache, Cloudflare Workers, or a CDN with redirect rules) to map old URLs to new ones.

You need a large redirect map. Site migrations with hundreds or thousands of URL-to-URL mappings require server-side redirect rules, not registrar forwarding.

You need conditional redirects. If different pages should redirect to different destinations based on geography, device, or other criteria, you need server-side logic.

You need HTTPS on the old domain. Some registrars do not provision SSL certificates for forwarded domains. If the old domain has backlinks using HTTPS URLs and the forwarding server cannot serve HTTPS, the redirect chain breaks. Browsers show a certificate error before the redirect even happens.

For these situations, set up the old domain on a web server or CDN (Cloudflare Pages, Netlify, Vercel, or even a basic Nginx instance) and configure your redirect rules there. This gives you full control over paths, status codes, and HTTPS.

Setting Up Domain Forwarding at Popular Registrars

Cloudflare

Cloudflare offers URL forwarding through Page Rules or Bulk Redirects. Add the domain to Cloudflare, set up a Page Rule with a URL pattern, and choose "Forwarding URL" with a 301 status code. Cloudflare supports path forwarding and wildcards, making it one of the most flexible registrar-level options.

Namecheap

In the Namecheap dashboard, go to Domain List, select the domain, and find the "Redirect Domain" section under the hosting tab. Choose "Permanent (301)" and enter the destination URL. Namecheap supports basic path forwarding.

GoDaddy

In the GoDaddy DNS management panel, look for "Forwarding" under the domain settings. Choose "Permanent (301)" and set the destination. GoDaddy's forwarding is straightforward but has limited path-level control. Verify with curl that the redirect type is actually 301.

Google Domains (now Squarespace Domains)

Google Domains supported domain forwarding with path preservation and 301 redirects. Since the transition to Squarespace Domains, the forwarding features are available in the Squarespace Domains dashboard under DNS settings. Check Squarespace's current documentation for the latest setup steps.

Verifying Your Domain Forwarding

After setting up domain forwarding, always verify that it works correctly.

curl -I -L https://oldbrand.com

Look for the HTTP/1.1 301 Moved Permanently status code and verify the Location header points to the correct destination. If you see a 302 instead of a 301, reconfigure the forwarding. If you see no redirect at all (a 200 response with frameset content), you have masked forwarding enabled and need to switch to proper 301 forwarding.

Test multiple paths if path forwarding is important:

curl -I https://oldbrand.com/blog/some-post

The Location header should include the path, not just the root domain. If it redirects everything to the homepage, your registrar does not support path forwarding for your configuration.

For a comprehensive look at how all redirect types affect rankings, see How Redirects Affect SEO Rankings. And for more on the difference between 301 and 302, see 301 vs 302 Redirects.

If you are managing multiple domains, you might also find it useful to monitor their expiration dates. Domain Expiry Watcher maintains a comparison of domain registrars that covers forwarding capabilities alongside pricing and renewal policies.

References

1. Google, "Redirects and Google Search," Google Search Central, 2024. https://developers.google.com/search/docs/crawling-indexing/301-redirects
2. Google, "Change a page URL with a redirect," Google Search Central. https://developers.google.com/search/docs/crawling-indexing/301-redirects