HTTP Redirect Status Codes Cheat Sheet for Marketers and Developers

Overview

If you only want the short version, start here: use a permanent redirect when a URL has moved for good, and use a temporary redirect when the move is short-lived or conditional. The part that trips people up is that not all permanent or temporary redirects behave the same way. Some are better at preserving the original request method, some are more familiar in older setups, and some are chosen more from habit than from intent.

For a bookmarkable decision guide, think of the main HTTP redirect status codes like this:

• 301 Moved Permanently: The standard choice when a page or asset has moved for good.
• 302 Found: A temporary redirect commonly used for short-term destination changes.
• 303 See Other: Used when you want the client to retrieve a different resource with a GET request, often after form submissions.
• 307 Temporary Redirect: A temporary redirect that is meant to preserve the original HTTP method.
• 308 Permanent Redirect: A permanent redirect that is meant to preserve the original HTTP method.

For many marketing and content workflows, the practical decision is usually 301 vs 302. For development-heavy workflows, API traffic, forms, or stricter method handling, 307 and 308 matter more. That makes this topic useful across both content teams and engineering teams, especially when a single url redirect service or redirect management platform is being used by both.

Here is the working cheat sheet in plain language:

• Use 301 for site migrations, renamed URLs, content consolidation, broken link recovery, and permanent domain changes.
• Use 302 for temporary campaign swaps, limited-time promotions, tests, or maintenance detours that will end soon.
• Use 307 when the redirect is temporary and you need request behavior preserved more strictly.
• Use 308 when the redirect is permanent and you need request behavior preserved more strictly.
• Use 303 after an action, such as a form submit, when the next step should be a safe retrieval rather than a repeat of the original request.

One useful rule: do not choose a code based on what you have always used. Choose it based on intent. Is the move permanent or temporary? Do you need the request method preserved? Is this redirect for a browser visit, a campaign link, a QR code, an API endpoint, or a site migration? Once you answer those questions, the right code is usually clearer.

Marketers often meet redirects through branded short links, campaign links, QR campaigns, affiliate links, and landing page routing. Developers usually meet them through server rules, applications, APIs, and infrastructure. A good link redirect tool should make those choices visible rather than hiding them behind a generic “redirect” label.

Quick reference table

Use this simple memory aid:

• 301: permanent move, common default for SEO-safe long-term URL changes
• 302: temporary move, common default for short-lived changes
• 303: redirect after an action, usually toward a GET page
• 307: temporary move with method preservation
• 308: permanent move with method preservation

If you are handling duplicate content questions rather than true URL changes, a redirect may not be the right answer. In that case, it helps to compare redirect logic with canonicals in Canonical Tags vs Redirects: Which One Should You Use for Duplicate Content?.

Maintenance cycle

This section gives you a simple review process so your redirect code choices stay accurate over time. Redirect status codes are not a set-and-forget topic. They sit at the intersection of infrastructure, SEO, analytics, campaign operations, and user journeys. Even if the HTTP standards themselves are stable, the way teams implement redirects changes as sites grow.

A practical maintenance cycle is quarterly for most teams, with faster reviews during migrations, seasonal campaigns, product launches, or major tracking changes. The goal is not to re-learn HTTP every month. The goal is to confirm that your current redirect habits still match your real use cases.

What to review on a regular schedule

• Permanent redirects that may no longer be needed: Look for old migrations, outdated product pages, or retired campaign paths that still route through unnecessary hops.
• Temporary redirects that became permanent: A common drift problem is leaving 302 rules in place for months after a page has fully moved.
• Redirect chains: If URL A redirects to B and B redirects to C, review whether A can go directly to C. For a deeper workflow, see Redirect Chains and Page Speed: How Many Hops Are Too Many?.
• Rule-based redirects: Recheck geo, device, and campaign rules to make sure they still map to the right destinations and do not conflict.
• Link tracking assumptions: Confirm that your redirect analytics and attribution flows still align with your redirect logic.
• Destination health: Verify that redirected URLs resolve properly and do not land on 404s, expired pages, or blocked resources.

A practical workflow for teams

1. Export your redirect inventory. Gather redirects from your CMS, server config, CDN, app, and any dedicated redirect management platform.
2. Label each redirect by purpose. Examples: migration, campaign, QR code, affiliate, geo routing, device routing, domain forwarding, broken link recovery.
3. Review status code fit. Ask whether each rule is truly permanent or temporary. If needed, decide whether 307 or 308 is more appropriate than 302 or 301.
4. Test destination and response. Use a redirect checker or command-line tool to confirm code, hop count, and final destination.
5. Document owner and expiry. Every temporary redirect should have a review date or end date.
6. Monitor performance. Use uptime and analytics monitoring so you catch failed destinations quickly. See How to Monitor Redirect Uptime and Catch Broken Destinations Before Campaigns Fail.

For campaign-heavy teams, this process is especially useful because a temporary redirect tool often becomes an accidental permanent architecture layer. That is not always wrong, but it should be intentional. The maintenance cycle is what keeps “temporary” from becoming undocumented infrastructure.

If your team manages lots of campaign links, naming conventions also matter. Clean naming makes redirect review much faster, especially when dozens or hundreds of URLs are active at once. A useful companion resource is How to Build a Redirect Naming System Your Team Can Scale.

Signals that require updates

This section helps you spot when your redirect code reference, internal documentation, or live rules need a refresh before problems spread. A redirect guide goes stale less because the status codes changed and more because your implementation context changed.

1. Search intent shifts from basic definitions to implementation questions

If your team already understands what a 301 or 302 is, the next update should focus on use cases: migrations, QR code redirects, analytics, device rules, and domain changes. In other words, move from “what is this code?” to “which code should we use in this scenario?”

2. Your redirect inventory grows across different systems

Once redirects exist in multiple places, such as your app, DNS provider, CDN, CMS, and a link tracking software platform, code consistency becomes harder. This is a good trigger to update your cheat sheet with examples that match your stack and approval process.

3. Temporary redirects stay live longer than expected

A 302 or 307 that remains in place well beyond its intended lifespan should trigger a review. The question is not whether temporary redirects are bad. It is whether the “temporary” label still matches reality.

4. Campaign tracking or QR code behavior becomes harder to explain

When teams use dynamic qr code redirect flows, short links, UTM builders, and device- or country-based rules together, confusion rises quickly. If your analytics are difficult to interpret, or link owners are unsure which status code the platform returns, your documentation likely needs updating.

Related reading can help clarify adjacent redirect scenarios:

• Device-Based Redirects: When to Route by Mobile, Desktop, or App Deep Link
• Geo Redirects: Best Practices for Country Routing Without Hurting SEO or UX
• Domain Forwarding vs URL Redirects: What Website Owners Need to Know

5. You are planning a migration or URL cleanup

Any site migration redirects project is a clear update trigger. Your team should revisit redirect status code guidance before launch, not after rankings or user journeys are disrupted. Review map coverage, one-to-one destination logic, and whether each redirect should be permanent from day one. A useful planning resource is Site Migration Redirect Map: How to Plan URL Changes Without Losing Rankings.

6. Broken links or 404s begin to surface

If support tickets, crawl reports, or analytics show broken destinations, revisit not only which pages need redirects but also which response type makes sense. Repair work often starts with How to Fix 404 Errors With Redirects Without Creating SEO Problems.

Common issues

This section covers the mistakes that repeatedly cause confusion in redirect implementation. Most of them are not deep protocol problems. They are workflow problems.

Using 302 when you mean 301

This is probably the most common issue in day-to-day marketing operations. A page moves, a campaign landing page is replaced, or a slug is cleaned up, and a temporary redirect is added because it is easy or familiar. Months later, nobody revisits it. The fix is simple: if the destination change is final, use a permanent redirect and document it as such.

Using 301 for short-term testing or promotions

The reverse mistake also happens. Teams use 301s during promotions, launch periods, or temporary traffic routing because they want a fast redirect and do not stop to define duration. If the destination will change back, a temporary status is usually a better fit.

Not understanding 307 and 308

In many browser-based marketing cases, 301 and 302 cover the practical decision. But if your redirects touch forms, programmatic requests, or method-sensitive workflows, 307 and 308 deserve attention. If your system supports them, add examples to your internal redirect code reference so they are not ignored by default.

Creating redirect chains during routine edits

A page moves, then moves again, then gets merged into another page. Instead of updating the original source to point to the latest destination, teams stack redirects. This slows resolution, complicates analytics, and makes troubleshooting harder. Periodic cleanup is worth the effort.

Breaking attribution with inconsistent link behavior

Redirects are often part of campaign link management, affiliate routing, or QR tracking. If the redirect logic changes but naming, UTMs, or destination rules do not, attribution can become messy. This is especially true when one team owns the destination and another team owns the short link or redirect layer.

Assuming domain forwarding and URL redirects are interchangeable

They solve related but different problems. If your team is changing domains, forwarding root traffic, or handling branded short domains, make sure the setup choice and status code choice match the actual requirement rather than a generic registrar default.

Forgetting to assign review dates

The easiest way to create redirect debt is to launch rules without expiry or ownership. Every temporary redirect should have a reason, owner, and revisit date. Every permanent redirect should still be checked occasionally to confirm the destination remains the best target.

Overusing redirects where a direct link update would be cleaner

Not every outdated link should live forever behind a redirect. Sometimes the right move is to update the source wherever possible, especially for internal links, navigation, campaign assets you still control, and active templates. Redirects are useful, but they should not become a substitute for basic link hygiene.

When to revisit

Use this final section as the action plan. If you want this article to stay useful, revisit your redirect status code choices on a schedule and at key moments of change.

Revisit on a scheduled review cycle

A quarterly review is a practical baseline for most sites. Monthly may make sense for campaign-heavy teams using smart redirects, short links, QR routing, or product launch rules. During the review, ask:

• Which temporary redirects are still temporary?
• Which permanent redirects can be simplified?
• Are any redirect chains or loops present?
• Do our analytics and redirect logs still tell a clear story?
• Are our destination pages healthy and current?

Revisit before and after major changes

Bring this cheat sheet back into view when you are doing any of the following:

• site migrations or structural URL changes
• domain changes or domain forwarding updates
• product launches and limited-time promotions
• QR code rollouts for printed materials
• affiliate link changes
• geo or device routing expansions
• analytics or attribution setup changes

For launch-specific work, Redirect Rules Checklist for Product Launches, Sales, and Limited-Time Promotions is a useful companion.

Revisit when ownership changes

If a new developer, SEO lead, or marketing operations manager takes over redirects, update the cheat sheet to reflect the actual current system. Good redirect governance is less about theory and more about clarity: who can create rules, who approves them, how they are named, and when they expire.

A simple closing checklist

• Use 301 for permanent URL changes.
• Use 302 for temporary URL changes.
• Use 307 and 308 when method preservation matters.
• Use 303 for post-action redirects that should resolve as GET.
• Review temporary redirects on a fixed schedule.
• Remove chains where a direct route is possible.
• Test redirects with a checker before and after launch.
• Document owner, purpose, and review date for every rule.

That is the simplest way to keep an HTTP redirect status code guide useful: treat it as a living operational reference, not a one-time glossary. The status codes themselves are stable, but the situations around them keep changing. When your links, campaigns, domains, and destinations change, your redirect decisions should be reviewed with the same discipline.