How web redirects work when a page address changes
What happens when a page address changes
Change a page's address and old links, bookmarks and search results still point at the old one. These notes explain redirects in plain words. They cover what the codes mean, how to plan the move, and how to find and fix a loop.
All the notes
What a Redirect Is and Why Pages Need ThemA redirect sends visitors and links from an old page address to a new one. Here's what happens when you change an address and skip it.
301, 302, 307 and 308 Redirects: What the Codes MeanWhich redirect code to use when a page moves for good or for a while, and how each of the four codes differs.
Making a List of Old Addresses and Their New OnesHow to gather your old page addresses, pair each with a new one and plan your redirect list before you rename or move pages.
What Search Engines Say About RedirectsWhat Google's own documentation says happens in search results when a page address changes and a redirect is put in place.
Redirect Chains and Loops: Spotting and Fixing ThemWhat 'too many redirects' means, how a loop differs from a chain, and how to find the rule that causes it and fix it.
How to Check Where an Address RedirectsHow to see which status code and destination an old web address really returns, using a browser or the curl command.
Where Redirects Are Set Up: Server Files, Plugins and Site SettingsWhere a redirect rule actually lives on Apache, Nginx and hosted site builders, and how to find out which one your site uses.