Redirect SEO Guide: 301 vs 302 and How to Do It Right

You renamed a URL, merged two pages, or moved to a new domain — and now you're staring at a wall of old links pointing at pages that no longer exist. Do nothing, and every one of those links becomes a 404, along with the rankings and traffic they were sending you.

The fix is a redirect, and it's a lot less risky than most people assume. The real skill isn't writing the rule itself — it's knowing which redirect type to use, when to use it, and how to avoid the handful of mistakes that actually cost you rankings.

Quick Answer

For SEO, use a 301 (permanent) redirect any time a page has moved for good — it passes ranking signals to the new URL and updates search engines' index over time. Reserve 302 (temporary) redirects for short-lived situations, like A/B tests or maintenance pages, where the original URL needs to stay indexed. Always point redirects at the closest matching new page, never chain them, and update internal links to the new URL directly.

What is a redirect, in SEO terms?

A redirect is an instruction, sent by the server, that automatically sends a visitor (and a search engine crawler) from one URL to another. In SEO, the type of redirect you choose is a signal about intent — it tells Google whether the old URL is gone for good or just temporarily unavailable.

The practical takeaway: pick the redirect type based on whether the old URL is gone forever or just temporarily out of commission — everything else about SEO-friendly redirects follows from that one decision.

Why redirects matter for rankings and traffic

Skipping redirects, or setting them up carelessly, has consequences that compound over time:

📊 Quick stat Most redirect-related ranking drops trace back to chains, loops, or redirects pointing to an unrelated page — not to the use of a 301 itself. A single, direct, relevant redirect is one of the safest changes you can make to a URL.

Step-by-step: setting up an SEO-friendly redirect

  1. List every URL that's changing. Before touching any config, write down each old URL and the new URL it should map to — this becomes your redirect map.
  2. Match old URLs to their closest new equivalent. Redirect a page to the new page that replaces it, not to your homepage — a mismatched destination is treated as a weak or irrelevant redirect.
  3. Choose 301 for permanent moves. Use a 301 for renamed pages, merged content, and domain or URL-structure migrations — anything that isn't coming back.
  4. Generate or write the redirect rule. Use your CMS's redirect manager, an SEO plugin, or a redirect generator to produce the rule for your platform (.htaccess, Nginx, or a hosting-specific config).
  5. Update internal links to the new URL. Point navigation menus, buttons, and in-content links directly at the new address instead of relying on the redirect to catch them.
  6. Test the redirect before and after publishing. Confirm it returns the correct status code and lands on the intended page, with no extra hops in between.
  7. Monitor for errors after launch. Check Search Console for crawl errors or unexpected drops in the days and weeks after a migration, and fix any redirects that didn't behave as planned.
Try the Rebrixe Redirect Generator — free Map old URLs to new ones and get ready-to-use redirect rules. No coding required.
Generate Redirects →

Common redirect mistakes that hurt SEO

1. Redirecting everything to the homepage

It's tempting to point every removed URL at the homepage, but search engines read this as a low-relevance redirect. Visitors also land somewhere unrelated to what they clicked, which drives up bounce rate.

2. Building redirect chains

Redirecting A → B, then later B → C, leaves A chained through two hops instead of pointing straight at C. Each extra hop adds latency and can dilute the ranking signal passed along — chains should be flattened to a single, direct redirect.

3. Creating redirect loops

A loop happens when a chain eventually redirects back to its own starting point, which traps both browsers and crawlers in a cycle that never resolves — these need to be found and broken immediately.

4. Using 302s for permanent moves

A 302 tells search engines the old URL is still the "real" one, so ranking signals aren't fully transferred. Using it for a permanent page move slows down how quickly the new URL can take over in search results.

5. Leaving internal links pointed at the old URL

Even with a working redirect in place, internal links that still point at the old address add an unnecessary hop on every single click and signal to crawlers that the old URL is still actively in use.

💡 Pro tip Keep your redirect map as a simple spreadsheet — old URL, new URL, redirect type, date added — so a future migration can check for existing redirects instead of accidentally chaining a new one on top.

Real-world examples

How different situations call for different redirect strategies:

Blog cleanup
Renamed post URL
301, one hop
Old slug redirects directly to the new slug, and every internal link is updated to match — no chain left behind.
E-commerce store
Discontinued product
301 to category
Product page redirects to the closest matching category or replacement product instead of the homepage.
Marketing team
A/B test landing page
302, short-term
Temporary redirect keeps the original URL indexed while traffic is split during the test period.
Company rebrand
Full domain migration
Page-by-page 301s
Every old URL maps to its direct equivalent on the new domain, preserving rankings through the move.

In each case, the redirect type and destination were chosen based on whether the change was permanent and what the closest matching page actually was — not applied as a one-size-fits-all rule.

Redirect types compared

A quick reference for choosing the right redirect type for the situation.

Redirect type Permanence SEO signal passed Best for
301 Permanent Strong, near-full transfer Page moves, renames, domain migrations
302 Temporary Partial, original stays indexed A/B tests, maintenance pages, short campaigns
307 / 308 Temp / Permanent (method-safe) Same as 302 / 301 Redirects involving form submissions or API calls
Meta refresh / JS Varies, unreliable Weak, inconsistently followed Only when server-side redirects aren't possible

Generate your redirect rules right now — free

The Rebrixe Redirect Generator maps old URLs to new ones and produces clean, ready-to-use redirect rules for the most common platforms. No account, no watermark, and nothing to write by hand — just enter your URLs and copy the result.

Free Redirect Generator Map your URLs, pick a redirect type, copy the rule.
Open Redirect Generator →

Frequently asked questions

A single, correctly configured 301 redirect passes the vast majority of a page's ranking signals to its new URL and typically causes little to no lasting loss. Rankings usually only suffer when redirects are chained, looped, misused, or point to unrelated content.
A 301 tells search engines a page has moved permanently and transfers ranking signals to the new URL. A 302 tells search engines the move is temporary, so the original URL is kept in the index and ranking signals are not fully transferred.
Permanent 301 redirects should stay in place indefinitely, since search engines and browsers can take months to fully update, and some external links pointing to the old URL may never be updated at all.
A redirect chain is when one URL redirects to a second URL, which redirects to a third, and so on. Each extra hop adds load time and dilutes the ranking signal passed along, so chains should be flattened into a single direct redirect.
Yes. Domain-level migrations use page-by-page 301 redirects that map each old URL to its closest equivalent new URL, rather than redirecting every old page to the new homepage.
No. A redirect sends visitors and crawlers to a different URL and removes the old one from normal browsing. A canonical tag lets a page remain accessible while telling search engines which version should be indexed, which is useful when both URLs need to stay live.
Not for most cases. Most CMS platforms and SEO plugins include a redirect manager, and a redirect generator tool can produce ready-to-use rules for .htaccess, Nginx, or common hosting platforms without hand-written code.

Generate your redirect rules in seconds

The Rebrixe Redirect Generator builds clean, ready-to-use redirect rules for the most common platforms — no account, no watermark, and nothing to code, just a ready-to-paste rule.

Launch the Redirect Generator →
← Back to blogs