301 vs 302 Redirects: Which Status Code Should You Use for SEO and Website Changes?
301 redirects302 redirectstechnical SEOHTTP status codeswebsite management

301 vs 302 Redirects: Which Status Code Should You Use for SEO and Website Changes?

PPortal Redirect Editorial Team
2026-11-04
6 min read

A practical 301 vs 302 checklist covering 307 and 308, migrations, campaigns, testing, chains and redirect review dates.

Choosing the right redirect status code protects user journeys, analytics and SEO signals. This practical checklist explains when to use 301, 302, 307 or 308 redirects, how to test the result and when to review a rule that was intended to be temporary.

Overview

A redirect tells a browser, crawler or other client that a requested URL should be fetched somewhere else. The status code adds an important instruction about whether that change is permanent and, for some codes, how the original request method should be handled.

A 301 redirect means that a resource has moved permanently. It is normally the appropriate SEO redirect when an old page, domain or URL pattern has been replaced and the change is intended to remain in place. A 302 redirect indicates a temporary move. It is useful when the original URL is expected to return or when you are running a short-lived campaign, test or operational change.

307 Temporary Redirect and 308 Permanent Redirect communicate temporary and permanent moves while explicitly preserving the HTTP request method. That distinction matters for requests such as POST, where changing the method could affect the outcome. For a straightforward browser request for an HTML page, the practical choice is often between 301 and 302, but developers should consider 307 or 308 for method-sensitive routes.

The simplest decision is: will the original URL come back? If the answer is no, start with 301 or 308. If the answer is yes, use 302 or 307. Then confirm that the destination is relevant, accessible and not part of a redirect chain.

Checklist by scenario

Permanent page replacement

  • Use a 301 when an old article, product page or service URL has a clear replacement.
  • Map the old URL to the closest relevant destination, rather than sending every retired page to the homepage.
  • Update internal links, XML sitemaps and campaign links so they point directly to the new URL.
  • Check that the destination has the intended canonical URL and returns a successful response.

For larger changes, create a documented website redirect mapping plan before publishing rules.

Domain, protocol or hostname change

  • Use permanent redirects when moving from HTTP to HTTPS, changing domains or choosing a single www or non-www version.
  • Make sure only one canonical route is selected. For example, avoid sending HTTP to a www URL and then sending that URL to HTTPS through separate hops.
  • Preserve relevant paths and query parameters where they are still valid.
  • Test representative URLs, including deep pages, files and URLs with tracking parameters.

A migration should include a bulk redirect map, not just a single homepage rule. The website migration redirect checklist can be used to organise pre-launch and post-launch checks.

Promotion, seasonal page or short campaign

  • Use a 302 when a campaign destination is temporary and the original landing page should remain the long-term URL.
  • Set a clear end date or review date for the rule.
  • Keep UTM parameters and other tracking information intact where appropriate, and verify that the destination accepts them.
  • Remove or disable the redirect when the campaign ends rather than leaving temporary routing indefinitely.

For campaign links, separate the redirect decision from the tracking decision. A temporary redirect does not replace a considered UTM link structure.

Testing, maintenance and application routes

  • Use a 302 or 307 for a controlled test when the original route may need to be restored.
  • Use 307 or 308 where preserving the original request method is important to the application.
  • Do not use a permanent redirect simply because it is convenient during a temporary deployment.
  • Record the rule owner, purpose, source pattern, destination and review date.

What to double-check

Before publishing any URL redirect, request the source URL with a redirect checker or command-line tool and record the complete response path. Confirm the status code, Location header, final status and number of hops. A clean rule normally reaches the intended destination directly.

  • Destination relevance: the new page should satisfy the same or a closely related user need.
  • Redirect chains: change old URL to final URL rather than old URL to intermediate URL to final URL wherever possible.
  • Redirect loops: check for rules that point a URL back to itself or create a cycle between hostnames, protocols or paths. See the redirect chain and loop troubleshooting guide.
  • Query strings: decide whether parameters should be retained, removed or transformed. Test tracking links separately.
  • Canonicalisation: a canonical tag suggests a preferred version to crawlers; it does not replace a redirect when users should no longer access the old URL.
  • Implementation layer: verify whether the rule is configured in Apache, Nginx, Cloudflare, a content management system or the hosting panel. Duplicate rules in multiple layers can produce unexpected results.
  • Method handling: test forms, APIs and authenticated routes with the request methods they actually use.

Test from more than one environment if the rule depends on DNS, caching, geolocation or edge configuration. Also check that the final page is not blocked, redirected again or returning an unexpected error.

Common mistakes

Using 302 for a permanent migration: this leaves the intent unclear and can weaken the consistency of a long-term migration plan. If the old URL will not return, use a permanent redirect and update references.

Using 301 for a temporary campaign: this can make a short-term experiment harder to reverse and may cause browsers, crawlers or other systems to retain the permanent interpretation longer than intended.

Redirecting everything to the homepage: this creates a poor experience when a specific replacement exists. Map pages by topic, product or function, and leave genuinely obsolete URLs to an appropriate final response where necessary.

Stacking rules over time: migrations often leave behind several layers of redirects. Periodically replace chains with direct source-to-destination rules and keep a record of retired patterns.

Forgetting non-HTML assets: PDFs, images, downloads and feed URLs may have different users and request behaviour. Include them in the audit rather than assuming the page rules cover every path.

When to revisit

Review redirect rules before a domain change, redesign, platform migration, seasonal planning cycle or campaign launch. Revisit temporary 302 and 307 rules on their stated review date, and remove rules whose original purpose has ended. A quarterly review can also identify chains created by several small URL changes, although the right frequency depends on how often the site changes.

Keep a simple redirect register with the source, destination, status code, reason, owner, date added and next review date. After each major release, sample important URLs, run a crawl or redirect checker, inspect analytics for unexpected drops and confirm that internal links use final destinations. If a workflow or hosting tool changes, repeat the tests: the same rule can behave differently when moved between an application, web server and edge platform.

Final action checklist: decide whether the move is permanent, choose the status code that matches that decision, map the most relevant destination, test the full response path, check tracking and query parameters, remove avoidable chains, document the rule and schedule a review.

Related Topics

#301 redirects#302 redirects#technical SEO#HTTP status codes#website management
P

Portal Redirect Editorial Team

Technical SEO Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.