Book a call Free rebuild
Home/Glossary/SEO/301 Redirect

301 Redirect

April 22, 2026 Updated November 16, 2026 4 min read

SEO glossaryA 301 redirect sends visitors and search engines from an old URL to a new one permanently, and passes the old page's ranking signals to the new address.

A 301 redirect is the server's way of saying "this page has moved for good, and here is its new address." It is the right choice whenever a URL changes permanently: a new slug, a merged article, a switch from HTTP to HTTPS, or a move to a new domain. Done well, visitors never notice, and search engines carry the old page's links and rankings over to the new one.

How it works

When a browser or crawler requests the old URL, the server answers with the status code 301 Moved Permanently and a Location HTTP header holding the new URL. The browser follows it straight away. Browsers also cache permanent redirects, sometimes for a long time, so test a redirect before you rely on it.

Google treats a 301 as a strong canonicalization signal that the new URL should be the one it indexes, and it moves the old URL's signals across. Google has said since 2016 that 3xx redirects do not lose PageRank, so a 301 passes full link equity. The old "90 to 99 percent" figure is out of date.

301 compared with other redirects

CodeMeaningUse it for
301Moved permanentlyMost permanent URL changes
308Permanent redirect, keeps the request methodPermanent moves where form posts or API calls must stay POST
302Found (temporary)Short-term moves, such as a page under maintenance
307Temporary redirect, keeps the request methodTemporary moves that must keep the method

Google treats 301 and 308 the same way, as a strong signal that the new URL should be indexed. A 302 or 307 is only a weak signal, so Google often keeps showing the original URL. Our guide to 301 vs 302 redirects covers the choice in more detail.

When to use a 301, and when not to

  • Use one when you change a URL, merge two pages into one, move to HTTPS or a new domain, or settle on one version of the site (www or not, trailing slash or not).
  • Do not use one for a temporary move, a short campaign, or an A/B test. Use a 302 instead.
  • Do not redirect a deleted page that has no close replacement. A 404 or 410 is the honest answer; Google may treat a redirect to the home page as a soft 404.

Setting up 301 redirects in WordPress

WordPress already adds a 301 when you change a published post's slug, using the old slug it stores. For everything else there are a few options:

  • A plugin such as Redirection, or the redirect manager built into some SEO plugins, which also logs 404s.
  • The server: on Apache, a line in .htaccess such as Redirect 301 /old-page/ https://example.com/new-page/ (or a mod_rewrite rule); on Nginx, return 301 https://example.com/new-page/; inside a location block.
  • The host or CDN: many managed hosts have a redirect screen, and Cloudflare offers redirect rules that run before a request reaches the server.

Server-level and CDN redirects are faster than plugin redirects, because WordPress does not have to load first. For a site with thousands of redirects, that difference adds up.

Common mistakes

  • Chains: A redirects to B, which redirects to C. Each hop adds a round trip for visitors and wastes crawl budget. Googlebot follows up to 10 hops, then gives up. Point every old URL straight at the final one.
  • Loops: A redirects to B and B back to A, so the page never loads.
  • Everything to the home page: after a redesign, map each old URL to its closest new equivalent instead.
  • Stale internal links: update menus, content, and sitemaps to the new URLs, so the redirect only catches outside links and bookmarks.
  • Removing redirects too soon: Google recommends keeping site-move redirects for at least a year, and longer is better while old links still point at them.

FAQs

What is a 301 HTTP status code?

It is the response a server sends when a URL has moved permanently. It comes with a Location header naming the new URL, which browsers and crawlers then request instead.

How do I implement 301 redirects correctly?

Redirect each old URL directly to the most relevant new page, at the server, host, or CDN where possible, or with a redirect plugin in WordPress. Then update internal links, refresh the XML sitemap, and test each redirect returns a single 301 to a page that loads.

Can a JavaScript redirect or meta refresh replace a 301 redirect?

Only when a server-side redirect is impossible. Google treats an instant meta refresh as a permanent redirect and can follow JavaScript redirects once it renders the page, but both are slower and less reliable than a 301 from the server.

How do I resolve redirect issues, such as loops or chains?

Crawl the site with an SEO crawler or check URLs in the URL Inspection tool in Google Search Console to see each hop. Then edit the rules so every old URL points straight to its final destination, and remove any rule that sends a URL back to an earlier one.

Should I update the canonical URLs when migrating to a new domain?

Yes. Each page on the new domain should carry a canonical tag pointing to its own new URL, not the old domain. Canonicals, redirects, internal links, and sitemaps should all agree on the new addresses.

Source: Google Search Central, Redirects and Google Search.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.