What Is Server-Side Redirect?
A server-side redirect is a redirect handled by the web server before any page content is sent to the browser. The server responds with an HTTP 3xx status code and a Location header, telling the browser to go to a different URL.
Why It Matters
Server-side redirects are the correct way to redirect domains and URLs. They’re faster, more reliable, and the only method that consistently passes SEO value to the destination.
When a registrar like Namecheap or GoDaddy offers “domain forwarding,” they’re setting up server-side redirects behind the scenes. The problem is they often default to 302 instead of 301, and most don’t support HTTPS.
How It Works
- Browser requests
https://old-domain.com/page - Server responds immediately with:
- Status: 301 Moved Permanently (or 302, 307, 308)
- Location: https://new-domain.com/page
- Browser follows the Location header to the new URL
- No page content is loaded from the old URL
The entire redirect happens in a single HTTP round-trip. With Domain Forward, this takes less than 5ms.
Server-side redirects can be configured via .htaccess files (Apache), Nginx config, reverse proxies, or dedicated services like Domain Forward.
Server-Side vs Client-Side
| Factor | Server-Side | Client-Side |
|---|---|---|
| Speed | Instant (no page load) | 200-500ms (page must load first) |
| SEO | Full support, passes link equity | Unreliable |
| Works without JS | Yes | JavaScript redirects require JS |
| Works without HTML | Yes | Meta refresh requires HTML |
| Server access needed | Yes (or use a service) | No |
Server-side redirects can also support advanced routing like geo redirects and device-based redirects by inspecting request headers before responding.
How Domain Forward Handles This
Domain Forward is a server-side redirect service. You point your DNS records (A record + CNAME) to our servers, and we handle the redirect at the HTTP level. Every redirect is server-side, with automatic SSL certificates and 301 status codes by default.
Related Terms
Related Features
Frequently
asked questions
A server-side redirect happens before the browser receives any content — the server sends a 3xx status code with a Location header. A client-side redirect requires the browser to load a page first, then execute JavaScript or a meta refresh tag to navigate elsewhere. Server-side is faster and more SEO-friendly.
You need access to your web server configuration — Apache (.htaccess), Nginx (config), or a redirect service like Domain Forward. If you don't have server access, Domain Forward lets you set up server-side redirects without hosting.
Yes. Search engines reliably follow server-side 301 redirects and transfer link equity. Client-side redirects (JavaScript, meta refresh) may not be followed by all search engines and can delay indexing.
Still Confused? Try It Free.
Set up your first domain forward in under 5 minutes. Free plan includes 5 domains.