Skip to content
SEOReseller

SEO concepts compared

301 redirect vs 302 redirect

What each one is, how they differ, when to use which, and how they should appear in a client report.

301 redirect

Use when: A site migration, domain change or HTTPS move where old URLs won't return.

302 redirect

Use when: Sending visitors to a temporary page while the original is briefly unavailable.

Short answer

Use a 301 (or 308) when a URL has moved permanently, such as in a redesign, migration or URL clean-up; search engines then treat the new URL as the main one. Use a 302 (or 307) only when the move is genuinely temporary and the original URL will come back, such as a short maintenance page. Using a temporary redirect for a permanent move can keep the old URL showing in search for longer.

Reviewed October 30, 2026 against search engine documentation.

Definitions

301 redirect

A permanent redirect: the content has moved for good, and search engines should treat the new URL as the one to show. A 308 is the permanent equivalent that keeps the request method.

302 redirect

A temporary redirect: the content is elsewhere for now and the original URL is expected to return. A 307 is the temporary equivalent that keeps the request method.

Side by side

Aspect301 redirect302 redirect
SignalMoved permanentlyMoved temporarily
Which URL search engines tend to showThe destinationUsually the original, for a while
Typical useMigrations, redesigns, merged pagesShort-term promotions or maintenance
Method-preserving equivalent308307
Risk if misusedHard to undo once establishedOld URL lingers in search for a permanent move

When to use each

Use 301 redirect when

  • A site migration, domain change or HTTPS move where old URLs won't return.
  • Merging two similar pages into one, or retiring a page in favour of its closest replacement.

Use 302 redirect when

  • Sending visitors to a temporary page while the original is briefly unavailable.
  • Short-lived routing, such as a seasonal page, where the original URL will be used again soon.

Common mistakes

  • Using 302s throughout a migration because they were the default in a plugin or server config.
  • Redirecting every old URL to the homepage instead of the closest equivalent page.
  • Leaving chains of several redirects in a row instead of pointing straight to the final URL.

How it should appear in a client report

A launch or migration audit should show a sample of old URLs, their status codes and final destinations, and flag temporary redirects used for permanent moves, chains and redirects to irrelevant pages. That gives the client's developers a precise list to fix.

See sample reports

Frequently asked questions

Do redirects lose ranking signals?
Google has said redirects don't lose signals in the way older advice claimed. What matters is choosing the right type and sending each old URL to its closest equivalent.
How long should redirects stay in place after a migration?
As long as possible, and at least a year. Old links and bookmarks keep arriving long after search engines have updated.

Tell us what your clients need

Share the service, rough scope and market. You'll get a written scope and quote to review. Nothing starts until you agree to it.

  • You keep the client relationship
  • Unbranded deliverables
  • Written scope before work starts