Make every redirect land where you meant it to
A redirect sends a request for one URL on to another. Explaining that takes one sentence. Getting it right takes more: the right status code, a stack of old domains pointed somewhere new, or a browser that keeps bouncing between two addresses.
The sections below sort the articles by that work, so start with the job in front of you. If you'd rather see the mechanics first, from status codes to DNS and HTTPS, read how URL redirects work.

From status codes to troubleshooting
- 301 vs 302 Redirects
- Are Redirects Bad for SEO?
- Best Domain Redirect Tools
- DNS-Level vs Server-Side Redirects
- Do 404 Errors Hurt SEO?
- Domain Forwarding Explained
- How to Bulk Import Domain Redirects
- How to Redirect a Subdomain
- How to Redirect non-www. to www.
- How to Set Up a Domain Redirect
- HTTP Redirect Status Codes
- Redirect Analytics: What to Monitor?
- Redirect Chains and Loops
- URL Redirects: Troubleshooting
- What Are 301 Redirects?
- What Is An HTML Redirect?
- Why HTTPS Redirects Break
- Wildcard Redirects: When and How

Choosing a status code
Most choices come down to permanent or temporary. A 301 or 308 tells browsers and search engines the move is final, and the new URL takes the old one's place in search results. A 302 or 307 says the original URL will be back, so it stays indexed. The 307 and 308 variants also keep the request method and body intact. That matters for forms and APIs, not for someone clicking a link.
Status codes aren't the only types of redirects. A meta refresh tag or a script on the old page can send visitors on too. Both run in the browser, and Google recommends a server-side redirect wherever you can set one.
301 vs 302 redirects puts the two most common codes side by side. What are 301 redirects covers the permanent move on its own, and HTTP redirect status codes goes through every 3xx code, the rare ones included. What is an HTML redirect explains the browser-side kind, and are redirects bad for SEO deals with what a redirect does to your rankings.
Setting up a redirect
Every domain redirect has two parts. DNS points the old domain at the server or service that answers with the redirect, and a rule says where requests should go. How to set up a domain redirect takes you through both. Domain forwarding explained covers the forwarding option most registrars offer.
Some setups need their own approach. Read how to redirect a subdomain or how to redirect non-www to www. When one rule should cover every subdomain of a domain, read wildcard redirects. With dozens or hundreds of domains, how to bulk import domain redirects saves you from adding them one by one.
Still deciding where the redirect should run? DNS-level vs server-side redirects compares the two approaches, and best domain redirect tools lines up the services.
When a redirect misbehaves
Most redirect problems come from a short list of causes. Two rules that point at each other create a loop. A redirect that points at another redirect adds a hop, and enough hops make a chain. A source domain without a valid certificate stops HTTPS visitors before the redirect even runs.
URL redirects troubleshooting goes through the most common ones. Redirect chains and loops shows how to find and remove both, and why HTTPS redirects break covers the certificate side. For a page that's gone for good, do 404 errors hurt SEO helps you choose between a redirect and a plain 404. Once everything works, redirect analytics shows what to keep watching.
redirect.pizza serves the redirect and the certificate for every hostname you add, so the old domain needs no server or hosting of its own.