GoDaddy Domain Forwarding and URL Redirect Guide

GoDaddy offers built-in domain forwarding that lets you redirect one domain to another without needing a hosting plan or web server. The feature works for simple use cases, but it has real limitations that catch people off guard. This guide walks through the setup process, explains the different forwarding types, and covers when you need a different approach. For background on how redirects work, see URL Forwarding Explained.

How GoDaddy Domain Forwarding Works

GoDaddy's forwarding feature works by pointing your domain's DNS to GoDaddy's forwarding servers. When someone visits your domain, those servers respond with an HTTP redirect to the destination URL you specified. The visitor's browser follows the redirect and loads the destination site.

This all happens at the DNS and HTTP level. You do not need a hosting plan, a web server, or any files on a server. GoDaddy handles the redirect infrastructure.

Setting Up Domain Forwarding

To set up forwarding for a domain registered with GoDaddy:

Log into your GoDaddy account and go to your domain portfolio.
Select the domain you want to forward.
Click on the "Forwarding" section (under "Additional Settings" or in the domain management panel).
Click "Add Forwarding."
Choose the subdomain to forward. Select the domain itself (the @ record) to forward the root domain, or type a specific subdomain like www or blog.
Enter the destination URL. Include the full URL with https://.
Choose the forward type: "Permanent (301)" or "Temporary (302)."
Choose whether to use "Forward only" or "Forward with masking."
Save the settings.

GoDaddy updates the DNS records automatically. The forwarding typically starts working within minutes, though full DNS propagation can take up to 48 hours if your domain was previously pointing to different nameservers.

Forward Types: Permanent vs Temporary

GoDaddy offers two redirect types, and picking the wrong one has SEO consequences.

Permanent (301)

A 301 redirect tells browsers and search engines that the domain has permanently moved to the new destination. Search engines transfer ranking signals from the old domain to the new one and eventually drop the old domain from their index.

Use a permanent redirect when you have bought a new domain and want to consolidate traffic, when you are retiring an old brand, or when the forwarding is meant to last indefinitely.

Temporary (302)

A 302 redirect tells browsers and search engines that the forwarding is temporary. Search engines keep the old domain in their index and do not transfer ranking signals.

Use a temporary redirect when you are forwarding during maintenance, when you plan to use the domain for its own content later, or when the forwarding is a short-term measure.

Most domain forwarding should be permanent. If you are just parking a domain and sending its traffic to your main site, use a 301. For a deeper comparison, see 301 vs 302 Redirects.

Forward with Masking

GoDaddy offers a "masked" forwarding option that loads the destination site inside an HTML frame while keeping the forwarded domain in the browser's address bar. The visitor sees yourforwardeddomain.com in their browser, but the actual content comes from the destination URL.

This works by serving an HTML page with an iframe that loads the destination site:

<html>
<head><title>Your Site Title</title></head>
<frameset>
  <frame src="https://destination-site.com">
</frameset>
</html>

Why Masked Forwarding Is Usually a Bad Idea

Masked forwarding creates several problems:

SEO. Search engines see the frame page, not the destination content. The forwarded domain has no real content for search engines to index. You get none of the SEO benefits of a proper 301 redirect.

HTTPS issues. If the destination site uses security headers like X-Frame-Options: DENY or Content-Security-Policy: frame-ancestors 'none' (which most modern sites do), the iframe will refuse to load. The visitor sees a blank page.

Broken functionality. JavaScript-heavy sites, single-page applications, and sites that use cookies for authentication often break inside iframes. Login forms, payment flows, and interactive features may not work correctly.

URL bar does not update. Deep links within the destination site all show the same forwarded domain URL in the browser. Visitors cannot bookmark specific pages or share links to internal content.

Use "Forward only" (the standard redirect) in almost every case. Masked forwarding is a legacy feature that predates modern web architecture.

Forwarding Subdomains

You can forward specific subdomains independently. For example, you might forward blog.example.com to your Medium page or shop.example.com to your Shopify store.

Each subdomain forwarding is set up separately in GoDaddy's forwarding panel. You can have different destinations and different redirect types for each subdomain.

To forward the www subdomain alongside the root domain, you need to set up forwarding for both. GoDaddy sometimes offers this as a single option, but verify that both the root domain and www are forwarding correctly.

Limitations of GoDaddy Forwarding

GoDaddy's built-in forwarding is basic. Here is what it cannot do.

No path forwarding. If someone visits olddomain.com/about, GoDaddy redirects them to the root of the destination URL, not to newdomain.com/about. Every path on the old domain goes to the same destination. This is a significant limitation for site migrations where you need URL-to-URL mappings.

No conditional redirects. You cannot redirect based on the visitor's location, device, time of day, or any other condition. Every visitor gets the same redirect.

No query string passing. Query parameters from the original URL are not forwarded to the destination. If someone visits olddomain.com?ref=email, the ref=email parameter is lost in the redirect.

Limited subdomain support. You can forward the root domain and specific subdomains, but you cannot set up wildcard forwarding that captures all subdomains.

No HTTPS on the source domain. GoDaddy's forwarding servers may not serve a valid SSL certificate for your domain. Visitors who type https://yourforwardeddomain.com might see a certificate warning before the redirect happens. This depends on your specific configuration and whether GoDaddy provisions a certificate for the forwarding.

Verify your forwarding with a redirect checker

After setting up forwarding, test the actual HTTP response to confirm the status code and destination URL. The GoDaddy interface does not always make it clear whether a 301 or 302 is being sent. Use Redirect Tracer to see the exact redirect chain.

When to Use Hosting Instead

If you need any of the following, GoDaddy's built-in forwarding is not sufficient:

Path-level redirects. Mapping /old-page to /new-page requires server-level redirect rules (in .htaccess, Nginx config, or your application). You need hosting for this. See htaccess Redirect Guide or Nginx Redirect Guide.

Redirect maps for site migrations. A proper site migration needs a CSV or database of old-URL-to-new-URL mappings, applied as server rules. GoDaddy forwarding cannot handle this.

Wildcard or pattern-based redirects. Redirecting all URLs that match a pattern (like all product pages or all blog posts) requires regex support in your server configuration.

HTTPS with a custom certificate. If you need the forwarded domain to serve valid HTTPS before redirecting, you need a hosting environment where you can install an SSL certificate.

For simple domain-to-domain forwarding where every URL on the old domain goes to the same destination, GoDaddy's built-in feature works fine. For anything more complex, set up even basic hosting with redirect rules.

GoDaddy Forwarding vs DNS-Level Redirects

GoDaddy's forwarding feature modifies your DNS records behind the scenes. It points your domain's A record to GoDaddy's forwarding servers and adds a forwarding configuration.

An alternative approach is to use a DNS provider that supports URL redirect records (sometimes called URL forwarding records). Some DNS providers offer this as a DNS record type. The effect is similar: the DNS provider's servers handle the redirect.

Neither approach gives you the control of a proper web server. If you are already using a hosting provider or CDN like Cloudflare, configure your redirects there instead. Cloudflare's Page Rules or redirect rules give you pattern matching, path forwarding, and HTTPS support that GoDaddy's basic forwarding lacks. See the Cloudflare Redirect Guide for setup instructions.

Troubleshooting

Forwarding is not working. DNS changes take time to propagate. Wait up to 48 hours. If it still does not work, check that your domain's nameservers are pointed to GoDaddy. Forwarding only works when GoDaddy controls the DNS.

Seeing a GoDaddy parking page instead of the redirect. This usually means the forwarding is not configured or the DNS has not propagated. Clear your browser cache and try again, or test from a different network.

Getting a certificate error on HTTPS. GoDaddy's forwarding servers may not have a valid certificate for your domain. Try accessing via HTTP instead of HTTPS, and consider switching to a hosting solution that supports HTTPS redirects.

Redirect goes to the wrong page. Double-check the destination URL in GoDaddy's forwarding settings. Make sure you included the full URL with the protocol (https://).

References

GoDaddy Help, "Forward my domain," https://www.godaddy.com/help/forward-my-domain-12123
GoDaddy Help, "What is domain forwarding and masking," https://www.godaddy.com/help/what-is-domain-forwarding-and-masking-12124
IETF, "RFC 9110 - HTTP Semantics, Section 15.4: Redirection 3xx," June 2022. https://httpwg.org/specs/rfc9110.html#status.3xx

Verify your GoDaddy domain forwarding

Check the exact redirect chain, status codes, and final destination of your forwarded domain. Catch misconfigurations before they affect your SEO.

Try Redirect Tracer