WordPress redirect tutorials
301, 302, 307, 308 or 410: choose a WordPress redirect response
Choose the right response for a permanent move, temporary change or retired page. Learn how redirect methods and browser caching affect testing.
A permanent page move usually needs a 301 redirect. A temporary move usually needs a 302. The 307 and 308 responses explicitly preserve the request method; 410 means the content is gone and does not redirect anywhere. Choose the response based on the intended change, then test it before publishing widely.
Permanent and temporary moves
Use 301 when an old article has a lasting replacement, such as /old-guide/ moving to /new-guide/. Use 302 when the move is temporary and the old address is expected to return. Do not use a temporary redirect simply to avoid planning where an old page belongs.
307 is temporary and 308 is permanent. Unlike the historical method-changing behaviour permitted with 301 and 302, they preserve the method when a client follows the redirect. RedirectNest handles GET and HEAD requests only, so choosing 307 does not turn it into a tool for moving checkout POST submissions or API writes.
When 410 is a better answer
A page with no useful replacement may be left as a genuine 404 or intentionally return 410. In RedirectNest, select 410 and leave the destination empty. Do not redirect every deleted page to your homepage: a visitor searching for a removed product will usually need a relevant replacement or an honest explanation.
Test with a small example
- Create /old-guide/ with a destination of /new-guide/ on a test site where the destination exists.
- Choose the response according to whether the move is permanent or temporary.
- Open the old URL and check the network response as well as the final page.
- Repeat with a query parameter if preserving campaign links matters.
- Check that the destination does not send the visitor back to the source.
Permanent redirects can be cached by browsers and intermediaries. Changing a rule later does not automatically clear those copies. A fresh browser session and a direct HTTP check help distinguish an old cached response from a current plugin rule.
RedirectNest Free supports 301, 302, 307, 308 and 410. Follow the first redirect guide for the interface steps, or use the troubleshooting guide when the observed response differs from the rule.