What Is a 301 Redirect? How It Works + SEO Impact

Simply put, a 301 redirect is a way to permanently redirect one URL to another. The "301" is a response code given by a server, indicating that the URL has changed permanently.

When a browser or search engine crawler requests the old URL, the server responds with a 301 status code and a new destination address. The visitor lands on the new page without noticing. Search engines update their index, transferring ranking signals from the old URL to the new one. This makes 301 redirects the standard tool for domain migrations, rebrands, URL consolidation, and any scenario where an old address will never serve content again.

For the full technical picture of how redirects work across different types and use cases, see our complete guide to URL redirects.

In this article, you'll find:

1. How a 301 redirect works
2. When to use a 301 redirect
3. SEO impact of 301 redirects
4. 301 vs 302: which should you use?
5. Common 301 redirect mistakes
6. How to set up a 301 redirect
7. How to verify your 301 redirect

Key Takeaways

• A 301 redirect permanently moves one URL to another and tells search engines to transfer ranking value to the new address.
• The server returns a 301 status code with a Location header pointing to the destination. Browsers and crawlers follow it automatically.
• Use 301 redirects for domain migrations, rebrands, HTTPS upgrades, and URL restructuring. Use a 302 redirect for temporary changes.
• Search engines pass link equity through 301 redirects, but expect short-term ranking fluctuations during reprocessing.
• DNS-based redirect services handle SSL certificates automatically, avoiding the HTTPS errors that break traditional redirect setups at scale.

How a 301 Redirect Works

A 301 redirect is a server-side response. When someone visits the old URL, the server does not return page content. Instead, it returns a 301 status code along with a Location header that contains the new URL. The browser sees this response and immediately requests the new address.

Here is what the HTTP response looks like:

HTTP/1.1 301 Moved Permanently
Location: https://www.example.com/new-page

That is the entire mechanism. The "301" tells the client this move is permanent. The Location header tells it where to go next. Every major browser and every search engine crawler understands this response and follows it without user interaction.

This is different from client-side redirects like HTML meta refresh tags or JavaScript redirects. Those methods load the original page first, then redirect the visitor. Server-side 301 redirects happen before any page content loads, which is faster and more reliable for both users and search engines. For a closer look at client-side alternatives and their trade-offs, see our article on HTML redirects.

When to Use a 301 Redirect

The rule is simple: if the old URL will never serve content again, use a 301. Here are the most common scenarios.

Domain migration or rebrand. You are moving your entire website from oldbrand.com to newbrand.com. Every page on the old domain needs a 301 redirect to its equivalent on the new domain. This preserves your search rankings and ensures existing links from other websites still work. For a step-by-step walkthrough, see our domain redirects guide.

URL restructuring. You have changed your site's URL structure, for example from /blog/post-title to /resources/redirects/post-title. A 301 redirect from the old path to the new one prevents 404 errors and preserves any backlink value the old URL had accumulated.

HTTPS migration. Moving from HTTP to HTTPS requires redirecting every HTTP URL to its HTTPS equivalent. Without this, visitors on the old HTTP URLs see security warnings or broken pages. DNS-based redirect services like redirect.pizza handle this automatically by provisioning SSL certificates for your domains before any redirect fires. For more detail on why HTTPS redirects break and how to fix them, see Why HTTPS Redirects Break.

Domain consolidation. After a merger or acquisition, you may have multiple domains that should all point to a single website. 301 redirects from the acquired domains to the primary domain consolidate your online presence and combine the ranking value of all domains.

When NOT to use a 301. If the change is temporary, use a 302 redirect instead. This applies to A/B tests, seasonal campaigns, maintenance pages, and any situation where you plan to restore the original URL. A 301 tells search engines the move is final, and browsers cache it aggressively, making it hard to reverse. See our 301 vs 302 comparison for the full decision framework.

SEO Impact of 301 Redirects

301 redirects are the only redirect type that explicitly signals permanence to search engines. That signal triggers several important behaviors in how search engines process your pages.

Link equity transfer. When another website links to your old URL, that link carries ranking value (sometimes called "link juice"). A 301 redirect passes that value to the new URL. Google has confirmed that 301 redirects do not lose PageRank in the transfer. This is the primary reason to use 301s during migrations: your backlink portfolio follows you to the new address.

Index replacement. After encountering a 301, Google removes the old URL from its index and replaces it with the new one. This process is not instant. Depending on how frequently Google crawls your site, it can take anywhere from a few days to several weeks for the swap to complete.

Crawl budget. Every 301 redirect costs a small amount of crawl budget because the crawler has to make two requests instead of one (the old URL, then the new one). For most websites, this is negligible. For large sites with thousands of redirects, it becomes a factor worth managing. Updating your internal links to point directly to the new URLs reduces this overhead.

Short-term fluctuations are normal. Even a perfectly implemented 301 redirect can cause temporary ranking drops. Search engines need time to reprocess the page, evaluate the new URL, and confirm that the content and context remain equivalent. These fluctuations typically resolve within 2 to 4 weeks. If your rankings have not recovered after a month, something else may be wrong, and our redirect troubleshooting guide can help you diagnose the issue.

301 vs 302: Which Should You Use?

The decision comes down to one question: will the old URL ever serve content again?

If the answer is no, use a 301. The old URL is gone for good, and you want search engines to transfer all ranking value to the new address. This is the right choice for rebrands, domain migrations, URL restructuring, and domain consolidation after an acquisition.

If the answer is yes (or maybe), use a 302. You are parking the URL temporarily and plan to bring it back. This applies to seasonal landing pages, A/B tests, and maintenance periods. Search engines keep the original URL in their index and do not transfer ranking signals.

One common mistake is using a 302 for what is actually a permanent change. Google may eventually treat a long-running 302 as a 301, but "eventually" is not a strategy. If you know the move is permanent, commit to a 301 from the start. For the full comparison, including a decision table and edge cases, see 301 vs 302 Redirects: Which Should You Use?

Common 301 Redirect Mistakes

301 redirects are straightforward in theory, but small mistakes can quietly cost you traffic and rankings. Here are the five most common ones.

How to Set Up a 301 Redirect

There are several ways to implement a 301 redirect. The right method depends on your infrastructure, the number of domains involved, and whether you have access to a web server.

DNS-based redirect service. You point your domain's DNS records to the redirect service, which handles everything from there: SSL certificate provisioning, redirect rules, and traffic routing. No web server or hosting required. This is the fastest option for domain-to-domain redirects, especially when managing multiple domains. redirect.pizza uses this approach, with automatic Let's Encrypt certificates and an edge network that processes redirects in milliseconds.

Apache .htaccess. If your site runs on Apache, you can add redirect rules to your .htaccess file:

RewriteEngine On
RewriteRule ^old-page$ /new-page [R=301,L]

Nginx config. For Nginx servers, redirects go in the server block:

server {
    listen 80;
    server_name olddomain.com;
    return 301 https://newdomain.com$request_uri;
}

Cloudflare Page Rules. If your DNS runs through Cloudflare, you can set up redirects using Page Rules or Bulk Redirects without touching your server configuration.

"Most teams underestimate how much time they will spend managing SSL certificates across redirect domains," says Michel Bardelmeijer, Tech Lead at redirect.pizza. "A single certificate expiration can silently break hundreds of redirects overnight. That is why we built redirect.pizza to provision and renew certificates automatically at the DNS layer, before traffic ever reaches a server."

For a step-by-step walkthrough of setting up your first redirect without server access, see How to Set Up a Domain Redirect in 3 Minutes.

How to Verify Your 301 Redirect

After setting up a redirect, verify that it works correctly before moving on.

Browser DevTools. Open your browser's developer tools (F12), go to the Network tab, and visit the old URL. Look for a response with status code 301 and a Location header pointing to the correct destination.

Redirect checker tool. Use our free Redirect Tester to check any URL instantly. It shows the full redirect chain, every status code in the chain, and the final destination.

Google Search Console. Use the URL Inspection tool to check how Google sees the old URL. After processing the 301, Google should report that the URL is "not indexed" because it redirects to another page. If Google still shows the old URL as indexed weeks after the redirect, there may be a configuration issue.

For bulk redirects during large migrations, test a sample of URLs across different paths and subdomains before going live. Catching errors in a sample of 20 URLs is much cheaper than discovering them after 2,000 redirects are live. Our guide on bulk domain redirects covers the full testing workflow.

Frequently Asked Questions

Related Guides