Skip to content

[00] Subset Redirects, User guide

Status codes

What 301, 302, 307, 308 and 410 each mean, which ones Subset Redirects offers, and how to pick.

This page explains the five HTTP status codes used for redirects and how to choose between them. Most of it is about HTTP, so it applies whichever plugin you use.

Subset Redirects offers three of them: 301, 302 and 410. It doesn’t offer 307 or 308. When you import from Redirection, Yoast SEO Premium or Rank Math, a 307 becomes a 302 and a 308 becomes a 301.

The five that matter

CodeNamePermanentMethod preservedCached by browsersIn Subset Redirects
301Moved PermanentlyYesNo (may become GET)AggressivelyYes
302FoundNoNo (may become GET)Only if told toYes
307Temporary RedirectNoYesOnly if told toNo
308Permanent RedirectYesYesAggressivelyNo
410Gonen/an/aYesYes

Each redirect code answers two separate questions: is the move permanent, and does the request method survive it?

A wrong 301 is hard to undo

A 301 tells the browser the page has moved for good, and browsers cache it. Older browsers cached it with no expiry, and several still keep it for the life of the browser profile. A visitor who gets a wrong 301 once may never reach the right page again without clearing their cache. You can’t fix it from the server, because the browser stops asking.

Why 307 and 308 exist

The specification for 301 and 302 let clients change the request method, and in practice every client turned POST into GET. That’s usually fine for a moved page. It’s wrong for an API endpoint or a form submission.

307 and 308 keep the method. 307 is temporary and 308 is permanent:

POST /api/v1/orders   →  308  →  POST /api/v2/orders   ✓ still a POST
POST /api/v1/orders   →  301  →  GET  /api/v2/orders   ✗ body discarded

For redirects between content pages, the difference doesn’t show, because browsers fetch pages with GET either way. That’s why Subset Redirects converts them on import. For anything a machine calls, use 307 or 308 in your web server or application instead.

Subset Redirects never redirects REST API requests (/wp-json/…), so WordPress’s own API endpoints aren’t affected.

410 isn’t a redirect

410 Gone says the page existed and you removed it on purpose. Use it for a discontinued product with no replacement, a finished campaign page or a retracted post.

The common alternative is redirecting to the homepage, which is worse for everyone. A visitor who wanted a specific page lands somewhere unrelated with no explanation. Search engines treat many unrelated redirects to the homepage as soft 404s, so you get none of the ranking benefit either.

404 or 410?

404 means there’s nothing at this address. It might be a typo, or the page might never have existed. 410 means the page was here and you removed it on purpose.

Google treats every 4xx code except 429 the same way and drops the URL from its index, so for Google a 410 and a 404 end the same (Google’s documentation (opens in a new tab)). A 410 still tells browsers, other crawlers and anyone checking the URL that you removed the page on purpose.

Choosing a code

  • The page has moved for good: 301. If anything sends POST requests to it, use a 308 in your server configuration.
  • The page has moved, but you might move it back: 302.
  • You’re not sure the redirect is right: 302 until you are.
  • The content is gone and nothing replaces it: 410.
  • You’re about to redirect to the homepage: use 410 instead.