Domain Redirect
DomainsDomain Redirect is a DNS- and web-server level method that sends visitors from one domain or URL to another destination automatically. It is commonly used to point alternate domains, old addresses, or misspellings to a primary website. Redirects can be temporary or permanent, can preserve or change the path, and help maintain usability and search engine signals during changes.
How It Works
A domain redirect works by returning an instruction that tells a browser (and often search engines) to request a different URL. This instruction can be issued at several layers: via HTTP response codes from a web server (such as Nginx or Apache), via application rules (for example in WordPress), or via a DNS provider feature that pairs DNS records with a forwarding service. Pure DNS cannot perform an HTTP redirect by itself; it can only map names to IP addresses or other names, so most practical redirects rely on an HTTP-capable endpoint.
The most common redirect types are 301 (permanent) and 302 (temporary). A 301 signals that the old URL has moved and is typically used when consolidating domains or changing site structure, while a 302 is used for short-term moves like testing or maintenance. Redirects can be configured to forward only the root domain, or to forward all paths (for example, /products to /products) and optionally preserve query strings. Correct configuration also includes choosing whether to redirect between www and non-www, and between HTTP and HTTPS, to avoid duplicate versions of the same site.
Why It Matters for Web Hosting
Redirect support affects how smoothly you can rebrand, switch domains, or standardize your site address without breaking links. When comparing hosting plans and domain/DNS management tools, look for easy 301/302 management, wildcard or path-based forwarding, HTTPS-capable forwarding (so visitors do not see certificate warnings), and clear control over canonical versions (www vs non-www). Poor redirect handling can cause downtime, SEO confusion, redirect loops, or mixed-content and HTTPS issues.
Common Use Cases
- Forwarding an old domain to a new brand domain after a rebrand
- Redirecting non-www to www (or the reverse) to enforce a single canonical hostname
- Sending HTTP traffic to HTTPS to improve security and avoid duplicate pages
- Pointing typo domains or alternate TLDs to the primary site
- Redirecting specific legacy URLs to new page locations after a site rebuild
Domain Redirect vs Domain Alias
A domain redirect sends users to a different URL, changing what appears in the browser address bar and guiding search engines to treat the destination as the primary location (especially with a 301). A domain alias (sometimes called a parked or addon domain depending on the control panel) typically serves the same website content under another hostname without forcing the browser to change URLs. Redirects are preferred for consolidation and SEO clarity; aliases are used when you intentionally want multiple hostnames to resolve to the same site without forwarding.