Every website eventually moves something. A product gets renamed, a blog is reorganised, a company switches domain after a rebrand. Each of those changes leaves old addresses behind, and those addresses may still be bookmarked, shared in emails or linked from other sites. A redirect is the instruction that tells browsers and search engines where the content went.
The status codes that matter
Redirects are communicated through HTTP status codes. Only a handful come up in everyday site work:
| Code | Meaning | Typical use |
|---|---|---|
| 301 | Moved permanently | Domain changes, merged articles, retired product pages |
| 308 | Permanent, request method kept | Permanent moves where forms or APIs post data |
| 302 | Found, temporary | Short promotions, maintenance pages, A/B tests |
| 307 | Temporary, request method kept | Temporary moves that must not change POST to GET |
The practical rule is simple: if the old URL is never coming back, treat the move as permanent. Search engines then consolidate signals such as links onto the new address. A temporary code tells them to keep the old URL in mind, which is right for a weekend sale but wrong for a permanent restructure.
Common ways redirects go wrong
Chains
A chain happens when page A points to B, which points to C. Each hop adds a little delay for visitors and asks crawlers to do extra work. After a few redesigns, chains can grow surprisingly long. Pointing every legacy URL straight at its final destination fixes this.
Loops
A loop sends A to B and B back to A. Browsers give up with an error and the page effectively disappears. Loops usually come from conflicting rules, for example one plugin forcing a trailing slash while the server removes it.
Lazy blanket redirects
Sending every old page to the homepage looks tidy but rarely helps anyone. Visitors land somewhere unrelated, and search engines may treat these as soft errors. Match each old page to the closest equivalent; if nothing comparable exists, an honest 404 or 410 can be the better answer.
A routine for site moves
- Export a full list of current URLs from your sitemap, analytics and backlink reports.
- Map each one to its new address in a spreadsheet before anything goes live.
- Implement the rules at server or CDN level where possible, rather than through scattered plugins.
- Crawl the old list after launch and confirm every line returns a single hop to a working page.
- Update internal links, canonical tags and the XML sitemap so they point to final URLs directly.
Teams that would rather hand the migration to specialists sometimes work with a top SEO agency in Montreal, where experienced consultants can map large URL sets, test the rules and monitor rankings in the weeks after a launch.
Keeping things tidy afterwards
Redirects are not a one-off job. Keep the mapping file somewhere the whole team can find it, review it whenever pages are retired, and check server logs occasionally for old URLs that still receive traffic. A small amount of housekeeping keeps the site fast, preserves the value of earned links and spares visitors from dead ends.
Desk habits
Small routines that save time later
Picked up while writing the notes on this site.
Photograph the meter
A dated photo settles most arguments about estimated readings.
Name files by date
Year, month, day at the start of a filename keeps invoices and letters in order.
Sketch before you measure
A rough floor plan stops you missing an alcove or counting a strip twice.
Update the router
Check for firmware updates whenever you change your Wi-Fi password.
Put terms in writing
A short email confirming price and due date beats any verbal promise.
