Key takeaways:
- A redirect automatically sends visitors and search engines from an old URL or original URL to a new URL when content has moved, changed, or been removed.
- The main types of redirects include permanent redirects (301 and 308) and temporary redirects (302, 303, and 307).
- The right redirect type protects traffic, supports search indexing, helps preserve ranking signals, and keeps users on the correct page instead of a 404.
The internet never sits still. URLs change when you rebrand, remove outdated content, or rebuild your site. Over time, links can break, frustrating your visitors and hurting your traffic, rankings, and conversions.
Redirects help you prevent that. A URL redirect sends users and search engines to a different URL than the one they initially requested. If you click a link on one page and eventually land on another, you have experienced a redirect.
In this guide, we’ll thoroughly explain everything you need to understand about redirects, their comprehensive definition, types, and best practices for your website.
What is a redirect?
A redirect automatically sends visitors and search engines from one web address to another when something changes on your website.
You may have renamed a page, moved a blog post into a new category, or changed domains. It makes sure that users and search engines are directed to the correct content, even if the original page’s URL changes.
Put simply, you can use redirects to move a web page to a new address so both visitors and search engines automatically reach the correct page.
Redirects matter because they:
- Prevent broken links and 404 errors
- Protect traffic and conversions
- Preserve SEO value from backlinks and rankings
- Help search engines understand which URL is current and preferred
How a redirect works behind the scenes
The jump from one URL to another happens really fast; most of your visitors do not notice it. Behind the scenes, the process looks like this:
- Browser requests URL A.
- Server responds with a 3xx status code, such as 301 Moved Permanently.
- Browser loads URL B, which becomes the redirect target.
Browsers may also remember some redirects. It will cache a 301 redirect and immediately perform it again next time, without needing to fetch the original URL again until the cache is cleared. That can speed up repeat visits, but it also means permanent moves should be tested carefully before launch.
Redirects vs domain forwarding
Redirects and domain forwarding are related, but they solve different problems.
Domain forwarding works at the domain level. It sends all traffic from one domain to another and is best for brand variations or multiple domain names.
For example, oldsite.com can forward entirely to newsite.com, or a misspelled domain can lead to the correct one (e.g., appl.com > apple.com). Use domain forwarding when an entire domain should point to a single main site.
Page‑level redirects are more precise. They move individual pages or sections, such as redirecting /old‑page to /new‑page. These are used when URLs change due to content updates, site restructuring, or the replacement of outdated pages.
For example, if /pricing changes to /plans, a page‑level redirect ensures visitors and search engines reach the right page.
In short, domain forwarding manages full‑site or brand‑level changes, while page‑level redirects handle focused URL updates within a site.
Why redirects matter for SEO and user experience
A redirect protects continuity. Websites change constantly, but many users still click old links, save bookmarks, and arrive on pages published months or years ago. If those visits don’t yield anything useful, both your user experience and SEO efforts can take a hit.
Here are some more reasons redirects are important:
- Prevent broken links and lost traffic
- Preserve your SEO value
- Help search engines index your new pages
Prevent broken links and lost traffic
When a URL changes without a redirect, visitors can land on a 404 error page. Search engines remove 404 pages from the index.
Your users can get confused and drop off, which means wasted clicks or weaker engagement. A redirect prevents this by routing an old URL to the most relevant live page.
Instead of landing on an error, your visitors reach a new page, a replacement product page, or a consolidated resource. They land on a functional page when an original resource has been moved, renamed, or deleted.
Preserve your SEO value
Permanent redirects also help preserve your SEO authority. It preserves link equity and other long-term signals.
A permanent (301) redirect passes ranking signals (e.g., backlinks) to search engines from the original URL to the new one, so SEO value isn’t lost.
A temporary redirect, on the other hand, signals that the original page may return, so long‑term signals usually stay with the source. Hence, using the right redirect ensures your search visibility doesn’t reset when URLs change.
Help search engines index your page
Redirects tell search engines which URL is the current version and should be treated as the canonical URL. Permanent redirects are strong signals that a page has been replaced, helping new URLs get indexed faster.
Tools like Google Search Console (GSC) make it easier to confirm that redirects are working properly and that search engines are indexing the right pages after a site update or migration.
When should you use a redirect?
A redirect is the right move whenever content or a domain has changed location, and there’s still a reason for users or crawlers to reach the old address.
Redirects can guide users from outdated to updated content. When content has moved to a new address, a redirect keeps them on the right path.
Other common situations you can use a redirect include:
- Moving a site to a new domain
- Migrating from HTTP to HTTPS
- Changing URL folders, categories, or slugs during a restructure
- Deleting outdated content but wanting to preserve traffic with a relevant replacement
- Merging similar articles or duplicate pages into one stronger page
- Running limited-time promotions or A/B tests with a temporary redirect
- Managing multiple domain names and sending them to one main site
Types of redirects (permanent vs temporary)
There are many types of redirects, but most decisions come down to permanence (permanent or temporary) and where the redirect happens (on the server or in the browser).
A few types of redirects include:
- Permanent redirects (301 and 308)
- Temporary redirects (302, 303, 307)
- Server vs client side redirects
Permanent redirects (301 and 308)
A 301 is the most common permanent redirect. It tells browsers and search engines that the page has been permanently moved to a new location. It can be used for domain migrations, HTTPS migrations, and permanent page changes.
A 308 is also permanent, but it’s more precise for technical cases because it keeps the method and body unchanged. 308 ensures the same HTTP request method is used in a permanent redirect for more technical precision.
There’s a very small chance you’ll need a 308 redirect, because if you’re not dealing with forms or special request types, a 301 redirect is usually simpler and perfectly fine.
Temporary redirects (302, 303, 307)
A 302 is the standard temporary redirect, where the page is redirected to somewhere else “for now.” 302 Found indicates a temporary move and should be used for A/B testing, limited-time promotions, or brief maintenance.
A 303 is commonly used after a form submission. It sends users to a separate confirmation page, and the follow-up request is always made with GET. It’s especially useful after a post request from a form.
A 307 is also temporary, but it keeps the request method the same. 307 Temporary Redirect preserves the original HTTP method and should be used for temporary redirects that require the same request method.
Server vs client side redirects
Server-side redirects are handled before the page loads in the browser. They include 301, 302, 303, 307, and 308. Many prefer these redirects because they are most likely to be interpreted correctly.
A client-side redirect happens in the browser after the page starts loading. Client-side redirects are triggered by code running in the browser that redirects the browser to another URL. They are more fragile, can be slower, and fail if the browser does not fully process the page.
The main browser-based options are meta refresh, redirect, and JavaScript redirect:
- An instant meta refresh happens immediately and is usually treated as permanent.
- A delayed meta refresh redirect waits a few seconds before moving the user and is usually treated as temporary.
- A JavaScript redirect redirects the browser to another page via code and should be used only when server-side options are unavailable.
Meta refresh redirects occur at the page level and are less effective for SEO than server-side redirects. JavaScript redirects are another type of client-side redirect, but aren’t recommended for SEO unless other options aren’t possible.
Among all side redirects, server-handled methods are usually the strongest, with browser-based methods as fallback tools.
Comparison table of redirect types
Redirect type | Status code | Permanent/Temporary | Server/Client | SEO impact |
|---|---|---|---|---|
301 Redirect | 301 | Permanent | Server-side redirect | Passes most SEO value |
302 Redirect | 302 | Temporary | Server-side redirect | SEO value is retained in the original URL that stays in the search index |
303 Redirect | 303 | Temporary | Server-side redirect | Minimal SEO impact |
307 Redirect | 307 | Temporary | Server-side redirect | Same as 302, preserves HTTP method |
308 Redirect | 308 | Permanent | Server-side redirect | Passes SEO value, preserves HTTP method |
Meta refresh | N/A | Temporary | Client-side redirect | Weak SEO value |
JavaScript redirect | N/A | Temporary | Client-side redirect | Unreliable for SEO |
Deep dive: 301 vs 302 redirects
What is a 301 redirect?
A 301 is a permanent move. It tells browsers and search engines that the resource has been moved permanently to a new URL and that the destination should replace the source over time. It’s the classic choice when a page or site has been permanently replaced.
When to choose a 301
Use a 301 when the move is lasting, such as:
- The site is moving to a new domain
- Content has been permanently moved to a new page
- Several overlapping pages are being merged
- A cleaner structure is replacing messy legacy URLs
- HTTP is being replaced with HTTPS
What is a 302 redirect?
A 302 is a temporary redirect. It says the content is somewhere else for now, but the original URL is still expected to return. 302 is for short-term changes.
When to choose a 302
Use a 302 when the move is temporary. For example:
- Limited-time promotions
- A/B testing. Google specifically recommends 302 for redirected experiments
- Short maintenance periods during which the source page will return
Does 301 vs 302 affect SEO?
Yes. A 301 tells Google the move is permanent, so long-term signals should shift to the destination. A 302 says the move is temporary, so the source usually remains the canonical version for longer.
How to implement redirects (without breaking your site)
A redirect is simple in principle, but the setup still needs planning. Here is an overview of the process:
- Before you set up redirects
- Implementing redirects on your server
- Implementing redirects in your CMS
- Domain-level redirects and DNS
Before you set up redirects
Start with a mapping. List every old URL, the correct destination, and whether the move is permanent or temporary.
Use this checklist:
- Map each old URL to the closest relevant destination
- Decide whether each change requires a 301 or a 302 redirect
- Send the source directly to the final URL
- Keep a spreadsheet of affected URLs and planned redirect rules
Implementing redirects on your server
The best place to implement redirects is usually at the server level. They can be set in server configuration files, such as the .htaccess file on Apache servers, or in server-side scripts.
Implementing redirects in your CMS
Many CMS platforms already include redirect tools or plugins. Some platforms have built-in redirect solutions. Most processes are simple: enter the source URL, enter the destination URL, choose the redirect type, and save.
Domain-level redirects and DNS
At the domain level, forwarding is usually set where the domain is managed. With domain forwarding, you can:
- Route multiple domains to one main website
- Protect brand variations
- Keep traffic flowing during a rebrand
Redirect best practices (and common mistakes to avoid)
The best redirect setup is direct, relevant, and easy to follow. Follow these best practices to maximize your use of redirects:
- Redirect to a relevant page
- Avoid redirect chains and loops
- Update internal links after redirecting
- Fix broken pages with backlinks
- Prefer server-side redirects
- Test and monitor your redirects
Redirect to a relevant page
Sending every retired URL to the homepage is a poor experience. Google warns against redirecting many old URLs to a single irrelevant destination, as this can confuse users and may be treated as a soft 404. The destination should match the same intent as closely as possible.
For example, if a product page is retired and a very similar product exists, send traffic to that product page. If nothing comparable exists, a clean 404 may be better than a misleading redirected page that doesn’t satisfy the same need. Redirects aren’t inherently bad for SEO if they lead users to relevant content.
Avoid redirect chains and loops
A redirect chain occurs when URL A points to URL B, which then points to another URL. A longer version looks like A → B → C. A redirect loop is worse. It happens when A sends users to B, and B sends them back to A. The page never loads.
Avoid redirect chains and keep chains low if they can’t be avoided. Redirect chains can increase load time and should be avoided by redirecting to the final URL directly.
Update internal links after redirecting
Once a redirect is live, internal links should be updated to point directly to the destination instead of relying on the redirect forever. Google can identify the correct URL more quickly and avoid building silent redirect chains into the site structure.
Fix broken pages with backlinks
If a page has backlinks and now returns 404, that’s a missed opportunity. Redirecting that old URL can recover useful visits and preserve continuity if a relevant replacement exists. The new page should closely match what the source page previously offered.
Prefer server-side redirects
3xx server-side redirects are preferred over client-side redirects for better SEO performance. A client-side redirect or a delayed meta refresh redirect should be used only when server-side methods are not possible.
Test and monitor your redirects
Every redirect should be tested after launch. Make sure it returns the expected code, goes to the correct URL, and lands on the intended page.
You can test redirects by copying the old URL, pasting it into your browser, and checking whether it redirects to the new URL. Regular audits using tools like Google Search Console can help identify redirect loops or broken 404 pages.
Site security and redirects
When you switch from HTTP to HTTPS, a 301 helps ensure every visitor reaches the secure version, every time. It also helps search engines index the secure version and avoid duplicate pages.
If your site suddenly sends users to strange destinations, treat it as a red flag. This can happen after compromised plugins, outdated software, or stolen logins.
Keep your site protected with basics like:
- SSL (so your site runs on HTTPS)
- Backups (so you can restore quickly)
- Security monitoring (to catch issues early)
We offer SSL and site protection options that help you maintain trust while keeping your site moving.
How Network Solutions can help you manage redirects
Domain transfer and forwarding
If you’re moving domains or consolidating brand domains, we can help you transfer and forward them from a single dashboard. We’ll help you:
- Move from an old brand domain to a new one
- Route typo domains to your main site
- Keep customers from getting lost during a rebrand
Security and expert support
When redirects go wrong, you can lose traffic fast. Our support team can help you troubleshoot:
- A misconfigured redirect type
- Unexpected loops
- Chains that slow down your site
- Domain forwarding setup
Frequently asked questions
A redirect sends people and search engines from one URL to another automatically when the source address is no longer the right place to land.
A browser requests one address, receives a 3xx response and a location header, and then loads the destination URL. In simple terms, the browser is automatically sent to the new location.
Use a redirect when content or domains change location, including site moves, HTTPS migrations, page merges, removed content with a clear replacement, and short-term tests or promotions.
Use a 301 for permanent changes and a 302 for temporary ones. That is the shortest accurate rule.
A temporary redirect sends users to another URL for now while signaling that the original URL may return. Common examples include 302 and 307.
No. A well-matched permanent move is usually good for SEO because it helps preserve ranking signals and signals to Google that the content has been moved to a new destination.
A redirect chain happens when more than one hop exists between the source and the final URL. Fix it by sending the source directly to the destination instead of routing it through extra steps.
Google says it can follow chains, but it recommends keeping them low and redirecting directly to the destination whenever possible. In practice, one direct move is best.
Yes. Domain redirects and domain forwarding are commonly used to send traffic from alternate, typo, and retired domains to a single main site.
It varies by site size and crawl speed, but Google says a medium-sized site often takes a few weeks for most pages to move and recommends keeping redirects in place for at least one year so signals can fully transfer.
A redirect moves users and crawlers to another URL. A canonical tag does not move anything. It only tells Google which URL should be treated as the preferred version among similar pages.
Start using redirects correctly
A redirect keeps your website usable, searchable, and consistent even when things change. With the right setup, you’re sure your visitors and search engine crawlers still land where they should.
Always match the redirect type to the situation. Use a permanent redirect when a change is final. Use a temporary redirect when the original page comes back. And keep every redirect direct, relevant, and easy to follow.
For domain changes, domain forwarding needs, HTTPS rollouts, and hosting-related setup, we can support the process while keeping your website traffic pointed to the right destination.
