Supported redirect types cheatsheet
A fast lookup for the four redirect types Redirect Supply supports. For the full explanation of when to use each, see Redirect Types.
At a glance
Type | Status | Permanent | Method preserved |
|---|---|---|---|
301 | 301 Moved Permanently | Yes | No |
302 | 302 Found | No | No |
307 | 307 Temporary Redirect | No | Yes |
308 | 308 Permanent Redirect | Yes | Yes |
Typical use cases:
301: Default choice, permanent moves, rebrands, consolidations
302: Temporary redirects, maintenance pages, campaigns
307: Temporary, non-GET requests (forms, API calls)
308: Permanent, non-GET requests (forms, API calls)
Permanent vs. temporary
301 and 308 tell browsers and search engines the move is permanent, SEO value transfers and browsers cache the redirect. 302 and 307 signal a temporary change, nothing is cached long-term and the original URL stays canonical.
Method preservation
307 and 308 guarantee the original request method (like POST) is preserved on the redirect. 301 and 302 don't make that guarantee, some clients may convert a POST to a GET. This mostly matters for API endpoints and form submissions, not standard page redirects.
Quick decision guide
Permanent page or domain move: 301. Temporary campaign or maintenance page: 302. Redirecting a non-GET request permanently: 308. Redirecting a non-GET request temporarily: 307.
Matching & priority quick reference
Pattern | Example | Matches | Priority |
|---|---|---|---|
Exact path | /about | Only | 1. |
Prefix wildcard | /blog/* |
| 2. |
Global catch-all | * | Everything on the domain | 3. |
Wildcard destinations: pair a prefix rule with a wildcard destination to carry the path over automatically, /blog/* → https://newsite.com/* sends /blog/post-1 to https://newsite.com/post-1.
Worth remembering: matching is case-sensitive, query strings count as part of the match (/page won't catch /page?utm=x), and trailing slashes aren't normalized (/page and /page/ are different).
Full detail: Path Redirects.