How a redirect works
When a browser asks for a page, your server answers with a status code before it sends anything else. Most of the time that code is 200, meaning here is the page. A redirect is a different answer: a 3xx code plus the address to try instead. The browser follows it, usually without the visitor noticing anything beyond the address changing.
The two that matter in practice are the permanent redirect, 301, and the temporary one, 302. A 301 says this page has moved for good, so search engines transfer the old address’s standing to the new one and eventually replace it in their index. A 302 says the move is short-term, so the old address is kept. Choosing the wrong one is the most common redirect error there is, and it is invisible in a browser because both look identical to a visitor.
Why redirects matter
They are what stops a site restructure from destroying its own search visibility. Every link anyone has ever built, every bookmark, every result still sitting in Google points at the old address. A redirect turns those into a route to the new page; without one they become dead ends, and the reputation those pages earned is lost.
They also keep a site honest about having one address per page. Forcing HTTPS, settling www against the bare domain, and standardising trailing slashes are all redirects, and doing them consistently prevents the same content from existing at several addresses at once. That work sits at the centre of any website migration.
Where redirects go wrong
The worst habit is sending every retired page to the home page. It looks tidy and it destroys the point: a visitor who wanted a specific product lands on a generic page, gives up, and search engines treat the redirect as a soft error rather than a genuine equivalent. Redirect to the closest real match, or return a 404 and mean it.
The second problem is chains. Address A points to B, B was later pointed to C, and now every request pays for two hops. Chains slow pages down, and long ones can be abandoned before the destination is reached. Loops are the same fault taken further, where two rules point at each other and the page becomes unreachable. Both grow silently over years because nobody reviews old rules. A third habit worth dropping is the redirect written in JavaScript, which only works once the page has loaded and is a poor substitute for a server answer.
How to act on it
Before any restructure, list every existing URL and decide its fate one by one: keep, replace, merge or remove. Map each changed address to the single most relevant new page, and use a permanent redirect unless the move genuinely is temporary. The redirect map builder is a straightforward way to lay that mapping out and spot chains and loops before they reach the server.
After launch, crawl the old list and confirm each address resolves in one hop to a page that returns 200. Keep the rules in place long after you think they have stopped being useful, because old links keep sending people for years, and review the file periodically so that when destinations move again the chains get flattened rather than extended.
