The HTTP status 302 is called Found and indicates a temporary relocation. The response supplies the other address in its Location header. It differs from a 301 permanent move, so the choice should reflect what is intended for the original page rather than simply whether the alternative page opens. Source: MDN: 302 Found

Record why the change is temporary

If a page needs a temporary alternative, write down the reason, owner and review date before changing the route. For example, identify when a campaign page should return. This gives the team a clear decision to revisit instead of leaving a temporary arrangement unexplained.

Test the original address again

Check both the temporary destination and the return to the original page when the arrangement ends. Review any links shared during the change. Keeping those checks together helps the team confirm that the intended visitor journey has been restored.

Written and updated by Travelgenix. Sources checked on 19 October 2026. Practical advice and examples are Travelgenix editorial guidance.