A temporary HTTP redirect indicating that a resource is available at another address for now.
A 302 redirect tells a client that a resource is available at a different address temporarily. Like other HTTP redirects, it supplies a destination that a browser can follow. The distinction from a permanent redirect concerns the intended relationship between the original URL and the temporary destination, not whether the visitor sees a visible warning.
Google follows a 302, but its indexing process does not treat that temporary redirect as a reason to select the destination as canonical. Other signals can still lead Google to index the destination. The redirect therefore does not guarantee that a particular URL will remain in search results; choose it to reflect the actual temporary arrangement.
Temporary arrangements need an owner and an end condition. A campaign or short-lived page substitution can otherwise remain in place long after the business intended to restore the original. The useful question is whether the original destination is expected to return, and what the visitor should receive in the meantime.
Takeaway: Choose a temporary redirect for a genuinely temporary routing decision, and record when it should be reviewed. Do not use a 302 simply because it happens to be a plugin’s default.
Example
A training provider temporarily routes a course-information URL to an alternative booking-information page during a short booking-system change. It expects the original route to return. The team records the intended destination and removal date instead of allowing the temporary routing to become an undocumented permanent change.
What to check
Test the destination and revisit the rule when the temporary arrangement ends. For server outages or maintenance, ask your developer which response fits the situation; a temporary redirect is not a universal replacement for an appropriate availability response.
For more detail, see MDN 302 reference.