Plan a redirect before renaming a page
A redirect sends a visitor from one address to another. When a page genuinely moves, an appropriate permanent redirect can help people using old links reach its replacement. Decide the destination before changing the address, rather than discovering broken links after publication.
Before you start
- Record the exact old URL and the proposed new public URL.
- Check whether your platform automatically creates redirects when a page is renamed.
What to do
Confirm that the new page replaces the old one
If /food becomes /menu with the same customer purpose, the relationship is clear. An expired recruitment page and a general homepage are not equivalent. Choose a destination that genuinely helps someone who followed the original link, not simply any page that loads.
Plan the platform-supported change
Use the documented redirect controls for your site or ask the administrator to implement the map. Preserve a record of existing rules. Permanent and temporary moves have different meanings, so explain whether the change is lasting rather than choosing a status code by guesswork.
Update current links as well
Change your own navigation and relevant content links to the final destination. A redirect supports old references; it is not a reason to keep every new link pointing through the old address. Check downloads and promotional materials you still control where practical.
Follow the complete route
Open the old address and confirm it reaches the intended new page without a loop or a chain of unnecessary stops. Check the new page directly as well. Record the outcome and ask the developer to verify response codes if the visible behaviour is unclear.
What to check
- The old and new addresses are documented accurately.
- The destination is a relevant working public page.
- New internal links and the sitemap use the final URL.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.