What Is a URL Forwarder and How Does It Work?
A URL forwarder sends visitors from one web address to another automatically. Here's how it works, when to use one, and what to look for in a forwarding service.
A URL forwarder is a service that automatically sends visitors from one web address to another by returning an HTTP redirect response. When someone visits the source URL, the server returns a 301 or 302 status code pointing to the destination, and the browser loads that destination instead. The visitor typically sees only the final URL — the forwarding is invisible.
How it works under the hood
The mechanics involve two pieces: DNS and HTTP.
First, DNS points your source domain or subdomain at the forwarding service. This is usually a CNAME record pointing at the forwarder's infrastructure. Once DNS propagates, any request to your source URL hits the forwarder's servers instead of going nowhere.
When a browser hits the forwarder, it receives an HTTP response like this:
HTTP/1.1 301 Moved Permanently
Location: https://destination.com/pageThe browser follows the Location header and loads the destination. The whole process takes milliseconds.
The critical detail: the forwarding service needs an SSL certificate for the *source* domain, not just the destination. This is why most domain registrar forwarding breaks — they serve the redirect over HTTP only, which triggers browser security warnings before the user ever reaches your destination.
301 vs 302 — when it matters
A 301 tells search engines the move is permanent. Link equity and rankings transfer to the destination URL over time. Use this when you're migrating a domain, retiring an old URL, or consolidating traffic.
A 302 tells search engines the move is temporary. Rankings stay on the source URL. Use this for campaign links, A/B test redirects, or anything where you plan to change the destination later.
Most use cases call for 301. The exception is vanity URLs and campaign links — those are often 302 because the destination changes by campaign.
When to use a URL forwarder
Domain migration — moving from an old domain to a new one. Every URL on the old domain needs a 301 to the corresponding new URL, or you lose the SEO value built up on the old domain. See our Domain Migration SEO Checklist for a step-by-step process.
Vanity URLs — yourcompany.com/podcast pointing at your podcast host, yourcompany.com/demo pointing at a booking page. Clean URLs you control, easy to update when destinations change. See how vanity URLs work for marketing campaigns for setup tips and attribution strategies.
Multiple domains to one site — you own yourcompany.net, yourcompany.org, and yourcompany.co and want all of them to forward to yourcompany.com. One forwarder rule per domain.
Campaign links — spoken URLs in ads, on business cards, in podcast show notes. The short URL stays constant; you update the destination without changing what you printed.
What to look for in a forwarding service
Automatic HTTPS on the source domain. This is non-negotiable. If the forwarder doesn't provision SSL for your domain automatically, visitors will see a security warning before the redirect fires.
Path passthrough. If someone visits old.com/products/widget, they should land on new.com/products/widget — not just new.com. Registrar forwarding almost always strips the path. A proper forwarder preserves it by default.
Click analytics. You want to know how many times each forwarded URL was clicked, where traffic came from, and whether your campaign links are working. Without analytics, a forwarder is a black box.
Instant updates. When a destination changes, the update should take effect immediately — not after a deploy or a cache flush.
Set up your first forwarder
RedirectIQ connects any domain or subdomain with a single CNAME record. SSL is provisioned automatically, path passthrough is on by default, and you get click analytics for every rule. Connect your domain and create your first redirect →