Redirects and 404s: keeping links alive through a redesign
A redesign that changes page addresses can cost years of search traffic. How Google treats 301s and 404s, and a practical plan for moving a site without losing ground.
The most expensive line in a redesign plan is often one nobody wrote: "we will tidy up the URLs". New page addresses look cleaner, but every old address has links pointing at it, bookmarks, search rankings and pages in Google's index. Change the address without telling anyone, and all of that leads to a 404.
What Google does with redirects
Google's documentation describes a permanent redirect (HTTP 301 or 308) as a strong signal that the new address should replace the old one in search results. A temporary redirect (302 or 307) is a weak signal: Google may keep showing the old address. For a page that has moved for good, use a permanent redirect.
Redirects themselves are nothing to fear; they are how the web is supposed to handle moved pages. What does cause problems:
- Chains. Old page to newer page to newest page. Google's crawler follows up to 10 hops, but each hop costs time and browsers follow them too. Point every old address straight at its final destination.
- Redirecting everything to the home page. If a hundred old pages all redirect to
/, Google tends to treat them as "soft 404s", errors pretending not to be. Redirect each old page to the most relevant new one, and let pages that truly no longer exist return a 404 or 410. - Redirect loops, where two rules send visitors back and forth until the browser gives up.
404s are normal
A site with no 404 errors at all is rare. Google's position is that 404s for addresses that should not exist do not harm the rest of the site. The 404s that matter are the ones for addresses that used to work and still get visits or links. Those are the ones to redirect.
A plan for moving a site
- Before you change anything, export a list of every address that exists today: your sitemap, plus your top pages in Search Console and analytics for the last year. Pages with external links matter most.
- Map old to new, one row per address, in a spreadsheet. Decide for each: redirect to a specific new page, or let it go.
- Put the redirects live at the same moment as the new site, not a week later.
- Submit the new sitemap in Search Console.
- Watch the 404 log for a month. Visitors and bots will find addresses your list missed; add redirects for the ones that matter.
- Keep the redirects for at least a year. Google's guidance suggests keeping them in place for a year or more; external links last far longer.
The quiet version: changing one slug
The same applies to small edits. Change a post's address from /blog/our-new-service-2024/ to /blog/our-service/ and the old address breaks. WordPress tries to guess the new address for some old post slugs, but it does not cover pages, products or anything else reliably.
In Ironhelm
Redirects and broken links sends old addresses to new ones, creates a redirect automatically when you change a page's address, catches the addresses that lead nowhere so you can redirect the ones that matter, and the SEO audit flags internal links that point at redirects instead of the final page.
Sources
- Google Search Central, Redirects and Google Search
- Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search
- Google Search Central, Site moves with URL changes
- Google Search Central Blog, 404s, soft 404s and other errors (on whether 404s hurt a site)
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.