What is a 301 redirect and when to use one

If you have been reading about domains for a while, you have probably seen the term 301 redirect come up more than once. The basics are straightforward. A 301 redirect permanently sends visitors and search engines from one URL to another. The server responds with a status code of 301, the browser follows it, and the visitor lands on the new address without seeing an error. That is the technical side. What matters more in practice is knowing when to set one up and when not to.

When should you use a 301 redirect to new domain?

The most common reason to use a 301 redirect is a domain change. You are rebranding, you found a better domain name, or your old name no longer fits what your brand does. When that happens, every URL on the old domain needs a 301 redirect pointing to its matching URL on the new one.

This is not just a homepage redirect. If someone bookmarked your pricing page on the old domain, that bookmark needs to land on the pricing page of the new domain. If a blog post on your old site earned backlinks from other websites, those links need to reach the same content on the new domain. A 301 redirect to new domain means mapping every old URL to its new equivalent, page by page.

Without it, you lose everything you built. The traffic, the backlinks, the search rankings. They all reset to zero on the old domain and do not transfer to the new one. The redirect is what carries them over.

Should you use a 301 when merging two websites?

Yes. Merging two sites into one is one of the clearest cases for a 301 redirect. Maybe you ran two brands that now operate under one name. Maybe you had a separate blog on its own domain and want to bring it under your main site. Whatever the reason, every page on the site being retired needs a 301 redirect to the closest matching page on the site that is staying.

If both sites have a page about the same topic, the redirect should point to the page you are keeping. If a page on the old site has no match on the new site, redirect it to the most relevant category or section page. Sending orphaned pages to the homepage is a last resort. It works, but you lose the topical relevance of that specific redirect. Search engines pass more value when the old page and new page are about the same subject.

Do you need a 301 when switching from HTTP to HTTPS?

You do. When you install an SSL certificate and activate HTTPS, the HTTP version and the HTTPS version of every URL are technically two different addresses. Without a 301 redirect from every HTTP URL to its HTTPS match, you end up with two copies of your entire site in the eyes of search engines.

That split means your domain authority gets divided between two versions instead of concentrated on one. The 301 redirect fixes this by telling search engines that the HTTPS version is the permanent home. Most website platforms handle this automatically when SSL is turned on, but it is worth checking that the redirect is in place on every page, not just the homepage.

What about changing your URL structure?

If you reorganize the URLs on your site, for example moving /services/web-design to /web-design, every old URL needs a 301 redirect to the new one. This applies whether you are shortening URLs, adding categories, removing date-based paths from blog posts, or renaming slugs.

The risk here is the same as with a domain change, just on a smaller scale. Any link pointing to the old URL, whether it is an internal link on your own site or a backlink from somewhere else, breaks the moment the URL changes. The 301 redirect keeps every link working and preserves the search value attached to those pages.

Should you redirect pages you are removing?

If the page earned any backlinks or search traffic, yes. Redirect it to the most relevant page that still exists on your site. If no relevant match exists, the next best option is the parent category page. Only let a page return a 404 error when it has no links pointing to it and no meaningful traffic.

A common mistake is deleting old pages without checking whether they have value. Before removing any page, look at two things. First, does it have backlinks from other websites? Second, does it get any organic search traffic? If the answer to either is yes, set up a 301 redirect before deleting it.

How does a 301 redirect affect your SEO?

A 301 redirect passes most of the link value from the old URL to the new one. Google has confirmed that a single, properly set up 301 redirect transfers essentially full PageRank. This means the authority, the backlinks, and the ranking signals you built on the old address move to the new address over time.

There are a few things to keep in mind.

• The transfer is not instant. Search engines need to crawl the redirect, reprocess the URLs, and update their index. This can take anywhere from a few days to a few weeks depending on how often your site gets crawled.
• Redirect chains reduce the value passed. If URL A redirects to URL B, which redirects to URL C, each hop loses a small amount of value and adds load time. Always point directly from the old URL to the final destination.
• Rankings may dip temporarily. Even with a perfect 301 setup, it is normal to see a short-term fluctuation in rankings while search engines process the change. This usually stabilizes within a few weeks.
• Page-level redirects pass more value than blanket redirects. Redirecting /old-page to /matching-new-page preserves more relevance than redirecting everything to the homepage.

The bottom line is that a 301 redirect is the best tool available for preserving SEO value during any permanent URL or domain change. It is not perfect, and the transition takes time, but it is far better than the alternative of losing everything.

When is a 301 the wrong choice?

Not every redirect should be a 301. Because a 301 signals a permanent move, using one in a temporary situation sends the wrong message to search engines.

Use a 302 redirect instead when any of the following apply.

• You are running an A/B test and sending some visitors to a different version of a page temporarily.
• You are redirecting to a seasonal or promotional page that will be taken down later.
• You are showing a maintenance page while making updates and plan to bring the original page back.
• The content at the old URL will return once you finish making changes.

If the original URL is coming back, a 302 tells search engines to keep the old address in their index. A 301 in this situation would cause search engines to drop the old URL from their index entirely, which means you would need to rebuild its rankings from scratch when it comes back.

Does domain forwarding pass SEO value the same way?

Domain forwarding through your registrar and a server-level 301 redirect do the same fundamental thing. They send visitors from one address to another. But the domain forwarding SEO impact depends on how your registrar handles it.

Some registrars implement domain forwarding as a proper 301 redirect. In that case, it works the same way for SEO as any other 301. Search engines see the permanent redirect, follow it, and transfer the ranking value.

Other registrars use methods that do not pass SEO value cleanly. Some use a 302 redirect instead of a 301. Some use an HTML frame that loads the destination site inside a wrapper while keeping the old domain in the browser's address bar. Framed forwarding does not pass any SEO value because search engines see the frame, not the destination content.

If domain forwarding SEO matters to you (and it should if the forwarded domain has any backlinks or authority), verify that your registrar uses a 301 redirect for forwarding. If it does not, set up the redirect at the server or platform level instead. For the full process, see how to redirect a domain.

How does WEMASY handle redirects?

WEMASY includes a redirect manager built into the platform. You can add 301 redirects directly from your project settings without editing server files or writing code. When you connect a custom domain and activate SSL, the HTTP-to-HTTPS redirect is set up automatically.

For domain changes or URL restructuring, the redirect manager lets you map old URLs to new ones individually. This means you can handle a full domain migration or a simple slug change from the same interface. See what is included in each plan at WEMASY pricing.

Frequently asked questions

The next chapter covers managing multiple domains, including how to organize several domain names under one brand and when to use redirects versus separate sites for each one.