Redirection and the Impact on SEO Rankings

Why Redirects Matter for SEO

A redirect tells browsers and search engines that the URL they asked for has moved. Done right, redirects are invisible: users land on the new page, Google updates its index, and your accumulated link equity follows the content to its new home. Done wrong — with the wrong status code, a chain of hops, or a redirect to an unrelated page — they can waste crawl budget, confuse rankings, or even trigger soft 404s.

You will need redirects when you change a URL slug, move to HTTPS, consolidate duplicate pages, restructure a site, retire stale content, or migrate to a new domain. The choice of redirect type — 301, 302, 307, or 308 — determines how search engines treat the move.

The Redirect Types You Need to Know

Four HTTP redirect codes cover almost every real-world case. The split you care about is permanent vs temporary and whether the HTTP method is preserved.

301 Redirect (Permanent)

A 301 says “this resource has permanently moved.” Search engines update their index to point to the new URL, the old page drops out, and PageRank passes to the target. This is the right choice for changed URL slugs, HTTPS migrations, site consolidations, and any move you do not plan to reverse. Historically, browsers changed POST requests to GET when following a 301, which is why form endpoints sometimes need 308 instead.

302 Redirect (Temporary)

A 302 says “this resource has moved for now.” Search engines keep the original URL in their index and treat the target as a temporary detour. Use 302 when the original URL will come back — A/B tests, seasonal pages, regional redirects, or short-term maintenance pages. Google has confirmed that a long-standing 302 will eventually be treated like a 301, but do not rely on that. Use the code that matches your intent.

307 Redirect (Temporary, Method-Preserving)

A 307 is a temporary redirect that preserves the HTTP method. If a browser sends a POST to the original URL, the 307 forwards that POST to the target instead of downgrading it to GET. Use 307 for form submissions, API endpoints, or anything where the request method matters. For routine temporary moves of a content page, plain 302 is fine.

308 Redirect (Permanent, Method-Preserving)

A 308 is the permanent equivalent of 307 — a permanent move that keeps the HTTP method intact. Google treats 308 the same way it treats 301 for indexing purposes. Choose 308 over 301 when the URL you are redirecting accepts POSTs that must continue working after the move. For static content pages, 301 and 308 behave identically from an SEO standpoint.

Meta Refresh, 404, and 410: What They Actually Do

A few related tools often get grouped with redirects. They are not the same thing.

Meta refresh is a page-level tag that reloads or sends the browser to another URL after a delay (or instantly). Google can follow meta refresh, but it is slower, not cache-friendly, and harder to debug than a server-level 301. Avoid it for anything SEO-relevant — use a proper 301 at the server level instead.

404 is an error status code, not a redirect. It tells browsers and crawlers the page was not found at this URL, but does not indicate whether it has moved. A good 404 page helps users find their way back into the site; a bad one dead-ends them. If a page has moved and you know the new URL, 301 to it — do not leave a 404.

410 is also an error code, specifically “gone.” It tells Google the page was intentionally removed and is not coming back. Google drops 410 URLs from its index faster than it drops 404s. Use 410 for retired product pages, discontinued services, or any content you want de-indexed quickly without replacement.

How to Set Up a Redirect (the Right Way)

Skip advice that tells you to “paste some PHP into your hosting folder.” Redirects belong at the server or application level, not in random PHP files. Pick the option that matches your stack:

• Apache: add a RedirectPermanent or RewriteRule directive to your .htaccess file or virtual host config.
• Nginx: use a return 301 https://new-url directive in the relevant server block.
• WordPress: use a plugin like Redirection, Rank Math Redirections, or Yoast Premium. These store redirects in the database and handle them before WordPress renders the page.
• Cloudflare or CDN: use Bulk Redirects or Page Rules for edge-level redirects that never hit your origin.
• Framework-level (Next.js, Nuxt, etc.): use the built-in redirects config so the rule ships with your deployment.

Whatever the platform, verify the response with curl -I or a browser dev-tools network tab. You want to see a single HTTP/1.1 301 Moved Permanently line followed by a Location: header — not a chain of three hops.

Redirects and PageRank: What Google Actually Says

The old SEO myth was that every 301 “loses some link juice.” Google has publicly disputed this. In 2016, Gary Illyes said that 30x redirects of any kind do not cause PageRank loss. John Mueller has reaffirmed the point several times since, including on the specific question of HTTP-to-HTTPS migrations. For modern SEO, Google’s redirect documentation confirms that permanent redirects consolidate signals onto the new URL.

The important caveat: redirecting to an irrelevant page can be treated as a soft 404. If you retire “/blog/best-hiking-boots/” and 301 it to your homepage, Google may decide the redirect does not serve user intent and treat the original URL as if it returned a 404. Always redirect to the closest-matching live page — a related article, the parent category, or a content-equivalent replacement. For related context on how Google handles near-duplicate pages and canonical signals, see our guide on duplicate content issues.

Avoid Redirect Chains and Loops

A redirect chain is A → B → C → D, where each hop is its own request. Each hop adds latency, consumes crawl budget, and gives more places for something to break. Google recommends keeping chains to no more than three hops; at four or more, Googlebot may give up before reaching the final URL. A redirect loop is worse — A → B → A — and will return an infinite redirect error in the browser.

The fix is boring but critical: after you set up a new redirect, update every source that still points to the old URL. That means internal links within your own content, sitemaps, navigation menus, canonical tags, and any marketing or email content you control. A single redirect from an external source is fine and unavoidable; a chain of your own redirects is a self-inflicted crawl tax. Quality backlink checker tools and SEO crawlers will flag chains for you.

How to Check Your Redirects

Verify before you publish and audit periodically:

• Browser dev tools: Network tab shows the full chain of status codes, headers, and timings for any URL you load.
• curl -I: curl -I -L https://example.com/old-url shows each hop and its status code in plain text. The cleanest way to verify a single redirect.
• Link Redirect Trace: Chrome extension that visualizes the full redirect path, including meta refreshes and JavaScript redirects.
• Google Search Console: the Pages report flags redirected URLs, soft 404s, and crawl errors across your whole site.
• Site crawlers (Screaming Frog, Sitebulb, Ahrefs Site Audit): surface redirect chains, loops, and internal links still pointing at old URLs.

Redirects for Site Migrations

Moving to a new domain, restructuring a site, or cutting over to HTTPS is where redirect discipline pays off. The short version of Google’s site-migration guidance:

• Map every URL: build a spreadsheet mapping each old URL to its final destination. Do not bulk-redirect to the homepage or category pages — that is the soft-404 trap.
• Use 301s, not 302s. The move is permanent; tell Google that.
• Keep redirects in place for at least a year. Longer if the URLs have meaningful backlink profiles. High-value pages often warrant indefinite redirects.
• Submit a Change of Address in Google Search Console for domain moves. This speeds up re-crawl and re-association of signals.
• Update internal links in bulk. Relying on redirects for your own content is lazy and wastes crawl budget.
• Expect a recovery window. Small sites usually stabilize in six to twelve weeks; larger sites can take four to six months. As we covered in why SEO takes so long, ranking signals need time to re-associate after a move.

Frequently Asked Questions

Do 301 redirects lose PageRank?

No. Google has publicly confirmed (Gary Illyes 2016, John Mueller 2019) that 301, 302, and other 3xx redirects do not cause PageRank dilution. The only real exception is when you redirect a URL to an unrelated page — Google may treat that as a soft 404 and drop the original URL from its index.

Should I use a 301 or a 302 redirect?

Use 301 (or 308) for permanent moves — changed URLs, HTTPS migrations, site consolidations. Use 302 (or 307) for temporary moves — A/B tests, maintenance pages, seasonal redirects. Picking the wrong one usually works but can slow re-indexing and send the wrong signal to search engines. For related context on how links pass authority, see our guide to nofollow links.

What is the difference between 301 and 308?

Both are permanent redirects that Google treats identically for indexing. The only difference is that 308 preserves the HTTP method — if the original request was a POST, the target receives a POST. 301 historically downgrades POST to GET in many clients. For static content pages, use whichever your server makes easier. For endpoints that accept POST, use 308.

How long should I keep a redirect in place?

At least a year for any URL that matters. High-value URLs with external backlinks should stay redirected indefinitely. Removing a redirect that other sites still point to turns those inbound links into 404s and loses the equity they carry.

Bottom Line

Redirects are not dangerous when you use them correctly. Use 301 for permanent moves, 302 for temporary ones, 307 and 308 when HTTP method preservation matters. Keep chains short, redirect to the most relevant live page, update internal links after migrations, and verify with dev tools before you ship. Get those basics right and you will not lose rankings when URLs change — no matter what the old “301s lose link juice” myth still insists.