Redesigning a website without losing rankings rests on three jobs: redirect every old page whose address changes to its counterpart with a permanent (301/308) redirect, keep the content and headings of important pages, and monitor after launch in Search Console. According to Google, permanent redirects do not cost PageRank; the loss usually comes from forgotten redirects and a noindex tag that travelled to production.
Why can a redesign hurt rankings?
Google knows pages by their addresses (URLs). If an address changes and the old one is not redirected, Google cannot find the old address and discovers the new one from scratch; meanwhile incoming links and history are wasted. The same happens when content is largely deleted or headings are rewritten from scratch: the page that was ranking is no longer that page.
Google's site move guide says such a change can cause temporary ranking fluctuation and that for a medium-sized site it can take a few weeks or more before the new URLs are gradually shown. So the goal is not zero fluctuation; it is that fluctuation does not turn into permanent loss.
What should you check before redesigning a website?
Start by taking a snapshot of the old site. List the important addresses: your sitemap, the pages with the most visits in analytics, and the pages bringing clicks in Search Console. For each address record the title, main heading (H1), meta description and target keyword. In the new design these should stay the same unless you change them on purpose.
The second job is the URL map: old address, new address, status (moved, merged, removed). Google's advice for removed or merged content is to return 404 or 410 on the new site, not to redirect everything to an unrelated page. Send each old address to the closest page that actually matches it; if there is no match, be honest and return a 404.
| Old address | New address | Action |
|---|---|---|
| /services.php?id=3 | /services/web-design | 301/308 redirect |
| /about.html | /about | 301/308 redirect |
| /old-campaign | no counterpart | 404 or 410 |
Which pages should you keep, merge or delete?
A redesign is a good chance to review content, but rebuilding everything is risky. Use a simple split. Keep pages that bring traffic and clicks exactly as they are, with the same address and heading; only the design changes. Merge pages that cover the same topic and are both weak, and redirect the old address to the stronger one. Delete pages that get no traffic and have gone out of date, and return 404 or 410.
When deciding, look not only at traffic but at the value the page carries for the business: a service page that people reach before asking for a quote is valuable even if few visit it. Add this decision as a column next to the URL map; on launch day nobody has to ask why a page was deleted.
301 or 308, and how do you set the redirect up?
Both are permanent redirects. Google's redirects documentation lists 301 and 308 as permanent; use them when you are sure the redirect will not be reverted. Set them up server-side where possible; use JavaScript redirects only when you cannot reach the server.
Avoid chains: /old → /middle → /new should be /old → /new. Google says to keep chains short, ideally no more than three. We hit this ourselves when moving our English URLs: one rule added an extra path to the target on an empty match and produced a second redirect; a separate rule for the root brought it down to one hop.
