301 Redirects and SEO: When to Use Them and How To

A 301 redirect permanently sends users and search engines from an old URL to a new one, passing the large majority of the original page's ranking authority. Use it whenever a page moves or is removed for good, and reserve the 302 for temporary changes. Handled correctly, 301s protect your rankings during site changes; handled badly, they leak authority and frustrate users.

Key Takeaways

A 301 redirect signals a permanent move and passes almost all of the original page's ranking authority to the destination.
Use a 301 for permanent changes and a 302 only when the move is genuinely temporary.
Redirect chains and loops waste crawl budget and dilute authority, so always redirect to the final destination in one hop.
Redirects can be implemented at server level with Apache or Nginx, or through your CMS and plugins.
Redirecting to an irrelevant page, such as the homepage, wastes the authority you are trying to preserve.
You should monitor redirects after launch to catch errors, chains and lost traffic early.

What a 301 Redirect Is

A 301 redirect is an HTTP status code that tells browsers and search engines a page has moved permanently to a new location. The server responds to a request for the old URL by instructing the client to load the new one instead.

The user rarely notices. They click a link, the redirect fires and they land on the new page seamlessly.

The status code explained

The number 301 is the HTTP response code for a permanent move. Search engines read it as an instruction to update their index, replacing the old URL with the new one over time.

This differs from a 404, which tells search engines the page is simply gone, and from a 200, which confirms a normal working page.

Why it matters for SEO

When a page has earned backlinks and rankings, deleting it without a redirect throws that value away. A 301 preserves most of it by transferring authority to the destination page.

That preserved authority is why redirects sit at the centre of any careful site migration or restructure.

When to Use a 301 Versus a 302

Use a 301 for permanent changes and a 302 for temporary ones, because search engines treat the two codes very differently. Choosing the wrong code can cost you rankings or leave the wrong page in the index.

The table below summarises the common scenarios.

Scenario	Correct redirect	Reason
Permanently moved page	301	Passes authority and updates the index
Merged two pages into one	301	Consolidates authority permanently
Temporary promotion page	302	Original page returns later
Site under short-term maintenance	302	Change is not permanent

When a 301 is right

Reach for a 301 whenever the change is permanent:

Moving from HTTP to HTTPS.
Changing a URL structure or slug.
Merging duplicate or overlapping pages.
Migrating to a new domain.
Consolidating pages that cause keyword cannibalisation.

When a 302 is right

Use a 302 only when you intend to restore the original URL. A temporary campaign page, a short A/B test or brief maintenance all justify a 302.

A common and costly mistake is using a 302 for a permanent move. Search engines may keep the old URL indexed and delay passing authority, which stalls the new page.

How Authority Flows Through Redirects

A 301 passes the vast majority of a page's ranking authority to its destination, which is why redirects preserve rankings during site changes. Google has stated that 301s pass full PageRank in most cases, removing the small loss that older guidance assumed.

The link equity question

Backlinks pointing to the old URL still count once a 301 is in place, because the authority flows through to the new page. Without the redirect, those links point to a dead page and their value evaporates.

Where possible, update your most important inbound links to point directly at the new URL. Direct links are always cleaner than redirected ones.

Relevance still matters

Authority only transfers meaningfully when the destination is relevant to the original page. Redirecting a deleted article about brake tests to a page about tyre pressure passes little useful value, because the topics do not match.

Match content to content. A retired guide should redirect to its closest replacement, not to a generic landing page.

Common Redirect Mistakes to Avoid

The most damaging redirect errors are chains, loops and irrelevant destinations, all of which waste authority and crawl budget. Each is avoidable with a little planning.

Redirect chains

A chain occurs when URL A redirects to B, which redirects to C. Each extra hop slows the page, wastes crawl budget and risks a small authority loss at each step.

According to Google's own guidance, its crawlers follow only a limited number of redirect hops before stopping, so long chains can leave pages unindexed. Always redirect straight to the final URL in a single hop.

Redirect loops

A loop happens when A redirects to B and B redirects back to A. The browser bounces between them and eventually shows an error, breaking the page entirely.

Test every new redirect to confirm it resolves to a live page and does not point back on itself.

Redirecting everything to the homepage

Mass-redirecting deleted pages to the homepage is a classic error. Google often treats these as soft 404s and passes little authority, because the homepage rarely matches the original content.

Redirect each page to its most relevant equivalent instead. Where no equivalent exists, a clean 404 or 410 is often the honest choice.

How to Implement Redirects

You can implement 301s at server level or through your CMS, and the right method depends on your hosting and technical comfort. All produce the same 301 response when configured correctly.

Server-level methods

On an Apache server, add rules to the .htaccess file:

Redirect 301 /old-page /new-page

On Nginx, add a rule to the server block:

rewrite ^/old-page$ /new-page permanent;

Server-level redirects are fast and reliable but require care, since a syntax error can take a site down.

CMS and plugin methods

Most content management systems handle redirects without touching server files. WordPress users typically manage them through a redirect plugin or an SEO plugin, as covered in our WordPress SEO checklist.

Follow these steps whatever the method:

List every old URL and its correct destination.
Match each old page to its most relevant new page.
Implement the 301 using your chosen method.
Test each redirect resolves in one hop to a live page.
Update internal links to point directly at the new URLs.

This work sits within the wider remit covered in our technical SEO for bloggers guide.

How to Monitor Redirects After Launch

Monitoring after launch catches the errors that inevitably slip through, protecting rankings during and after a migration. A redirect you set and forget can break silently.

What to watch

Crawl errors and soft 404s in Google Search Console.
Redirect chains flagged by a site crawler.
Traffic and ranking changes on redirected pages.
Server logs for unexpected redirect behaviour.

Give it time

Search engines need time to process redirects and update their index, often several weeks for a large migration. A temporary ranking dip is normal, so avoid changing course too quickly.

Track performance in Google Search Console content strategy reporting and compare against your pre-migration baseline. Sustained losses after a month or two signal a problem worth investigating.

Frequently Asked Questions

Does a 301 redirect pass all the link authority?

Google has stated that 301 redirects pass full PageRank in most cases, so the old assumption of a small loss no longer holds. The bigger risk to authority is redirecting to an irrelevant page rather than the redirect type itself.

How long should I keep a 301 in place?

Keep permanent redirects indefinitely. As long as the old URL has any inbound links or lingering rankings, the redirect protects that value, and removing it later would create dead pages.

Will a 301 redirect slow my site down?

A single, direct 301 adds a negligible delay. Chains of multiple redirects do slow things measurably and can harm your Core Web Vitals, so keep every redirect to a single hop. See our page speed and Core Web Vitals guide for the wider picture.

Should I use a 301 or a canonical tag?

Use a 301 when a page has genuinely moved and the old URL should no longer serve content. Use a canonical tag when both URLs must stay live but you want to tell search engines which is the primary version.

What happens if I forget to redirect a deleted page?

Users hit a 404 error and any backlinks and rankings the page held are lost. If the page had no value and no inbound links, a clean 404 is fine, but any page with authority deserves a relevant 301.