What Are Domain Redirects? How Domain Forwarding Works (and Affects SEO)
Michel Bardelmeijer is Tech Lead and Sales at redirect.pizza, where he helps DevOps and IT teams solve domain redirect challenges at scale. Michel has guided organizations like SD Worx, Zurich Airport and Harvard through complex redirect scenarios involving thousands of domains.
Have questions about bulk redirects, HTTPS migrations, or domain consolidations? Connect with Michel on LinkedIn or reach out to the redirect.pizza team.
Domain redirection is a process that involves forwarding one domain to another. Unlike a single URL redirect, a domain redirect forwards all traffic from the source domain to a destination domain. Organizations use domain redirects when renaming a website, consolidating multiple domains after a merger or acquisition, or protecting brand names by pointing unused domains to a primary site.
For a complete overview of all redirect types, see our complete guide to URL redirects.
Key Takeaways
- Domain redirects forward all traffic from one domain to another using DNS or server-level configuration
- Use 301 redirects for permanent domain moves to preserve SEO rankings and pass link equity
- DNS-based redirects work without hosting, server access, or SSL certificate management
- Proper domain redirects are critical during domain migrations, rebrands, and M&A consolidation
- Monitor redirect analytics after setup to verify traffic is flowing to the right destination
How domain redirects work
Every domain redirect has two components: a source domain (the old domain you want to redirect from) and a target domain (the new domain you want traffic to reach). In redirect.pizza, the target domain is called the "destination" domain.
There are three types of domain redirects:
- 301 redirects (permanent): Tells search engines and browsers that the source domain has permanently moved to the destination. This is the recommended type for domain migrations and rebrands because it passes link equity from backlinks pointing to the old domain. Search engines transfer ranking signals to the new domain over time.
- 302 redirects (temporary): Tells search engines the move is temporary. The old domain keeps its link equity and indexation. Use this for A/B testing, maintenance, or seasonal campaigns where you plan to revert.
- URL frame (masked redirect): Displays the destination site inside an iframe while keeping the source domain in the browser address bar. The visitor sees the original domain name, but the content comes from another domain. This approach causes problems for SEO because search engines cannot properly index framed content.
Learn more about the difference between 301 and 302 redirects and all the redirect types and forwarding options available in redirect.pizza.
How domain forwarding affects SEO
Domain redirects directly impact your search engine rankings. When done correctly, a domain redirect preserves most of the SEO value built up on the original domain. When done incorrectly, it can destroy years of ranking authority overnight.
Link equity and 301 redirects
When you set up a 301 redirect from an old domain to a new one, search engines transfer the link equity (ranking signals from backlinks) to the destination domain. This is why 301 redirects are the standard for permanent domain moves. Google has confirmed that 301 redirects pass link signals, though some ranking value may be lost in the process. The sooner you implement the redirect after a domain change, the less disruption your rankings will experience.
For a deeper explanation of how 301 redirects handle link equity, see What Are 301 Redirects?
When to use domain redirects for SEO
Domain redirects are essential in several scenarios where keeping SEO intact matters:
- Rebranding: Your company changes its name and moves to a new domain. Without a 301, every backlink to the old domain becomes worthless.
- Mergers and acquisitions: Consolidating multiple company domains into one primary domain after a merger. Each acquired domain should 301 to the appropriate page on the surviving domain.
- Domain portfolio management: Brands that own multiple TLDs (.com, .net, .org) or common misspellings should redirect all variants to the primary domain to consolidate ranking signals.
- HTTP to HTTPS migration: Redirecting the non-secure version of your domain to the secure version. This is a domain-level redirect that also requires valid SSL certificates on the source domain.
Common SEO mistakes with domain redirects
Michel Bardelmeijer, Tech Lead at redirect.pizza:
The biggest mistake we see with domain redirects is using 302s instead of 301s during permanent domain migrations. A 302 tells Google the move is temporary, so link equity stays with the old domain instead of transferring to the new one. We have seen companies lose months of ranking progress from this single misconfiguration.
Other common mistakes include:
- Creating redirect chains: Domain A redirects to Domain B, which redirects to Domain C. Each hop increases latency and risks losing link equity. Redirect directly from source to final destination.
- Forgetting subpages: Redirecting only the root domain while leaving subpages unresolved. Every URL on the old domain should redirect to the most relevant page on the new domain.
- Missing SSL certificates: If the old domain does not have a valid SSL certificate, visitors arriving on https://olddomain.com see a certificate error before the redirect even fires. DNS-based redirect services like redirect.pizza handle this automatically with automatic HTTPS.
- Not monitoring after setup: Failing to check redirect analytics in the weeks after a migration. Traffic dips or errors often go unnoticed without active monitoring.
How to set up domain redirects
There are three approaches to implementing domain redirects, each with different trade-offs:
DNS-based redirect services handle redirects at the DNS level without requiring web hosting, server access, or manual SSL certificate management. You point your domain's DNS records to the redirect service, and it handles the rest. This is the simplest approach for domain-to-domain redirects, especially when managing multiple domains. For a step-by-step DNS setup guide, see How to Set Up a Domain Redirect in 3 Minutes.
Server-level redirects (.htaccess on Apache, nginx configuration, or IIS URL Rewrite) give you granular control over redirect rules but require server access and technical expertise. This approach makes sense when you already host the source domain and need complex path-level redirect logic.
CMS plugins (such as WordPress redirect plugins) provide a user-friendly interface but are platform-dependent and only work while the CMS is actively hosted on the source domain.
Domain redirects vs URL redirects
A domain redirect forwards all traffic from one entire domain to another. A URL redirect forwards traffic from a specific URL path to a different URL. When someone says "domain forwarding" or "domain name forwarding," they typically mean redirecting an entire domain, not individual pages.
In practice, most domain redirects include path forwarding: a visitor to olddomain.com/pricing lands on newdomain.com/pricing, not just newdomain.com. This preserves the user experience and ensures deep-linked pages do not break. redirect.pizza supports path forwarding and query parameter forwarding by default through its redirect service.
Related Guides
Frequently Asked Questions
Yes. A 301 domain redirect passes link equity from the old domain to the new one, preserving most of your search engine rankings. A 302 redirect does not transfer link equity, so using the wrong redirect type during a permanent domain move can cause your rankings to drop. Always use 301 redirects for permanent domain migrations.
After updating your DNS records, most traffic redirects within 2 to 6 hours. Complete global DNS propagation can take up to 48 hours, depending on ISP caching policies and TTL settings. The redirect service itself responds instantly once DNS changes reach a resolver.
Domain forwarding redirects all traffic from an entire domain to another domain. URL forwarding redirects traffic from a specific page or path to a different URL. Domain forwarding is used for rebrands and domain consolidation, while URL forwarding is used for individual page moves or restructuring.
No. DNS-based redirect services handle domain redirects without requiring web hosting, server access, or manual SSL certificate management. You only need access to your domain registrar's DNS settings. The redirect service provisions SSL certificates automatically and manages the redirect infrastructure.
Use a 301 redirect. A 301 tells search engines the move is permanent and transfers link equity to the new domain. A 302 signals a temporary move and keeps ranking signals on the old domain. For rebrands, mergers, and any permanent domain change, 301 is the correct choice.
