Website redesign without losing your Google rankings: the checklist we use

Google does not rank websites. It ranks addresses: specific URLs with specific content that earned specific positions. A redesign changes the look of a website, and that is fine. The trouble starts when it also changes the addresses, removes pages, rewrites the words Google matched, or ships with a technical setting left over from staging. Then the rankings leave with the old site, and it takes months to earn them back.

Here is the checklist we use on every redesign, in the order it happens.

Why redesigns lose traffic

Six things cause almost every drop we have seen:

1. URLs changed without redirects. The new site has a page about the same service at a new address, and the old address returns a 404. Google sees a dead page and a brand new one.
2. Pages removed. "We consolidated those into one page" is a reasonable design decision and a common way to lose ten rankings.
3. Titles and headings rewritten into slogans. "Emergency plumber in Woodside" became "We fix what others can't". The customer understands. Google no longer matches.
4. Content trimmed. The new design is cleaner because the words are gone. The words were what ranked.
5. Internal links lost. A new navigation drops the links that told Google which pages mattered.
6. Technical leftovers. A noindex tag from the staging site, a robots file that blocks crawling, a canonical tag still pointing at the preview domain, or a slower site.

None of these is hard to avoid. All of them are hard to fix after launch.

Before you start: inventory the old site

• List every indexed URL. Search Console's Pages report covers the last sixteen months; add the sitemap and a crawl of the live site, because the three lists never quite match.
• Record what each page has. Title, meta description, H1, clicks and impressions from Search Console, and any links from other websites.
• Mark the pages that earn. The top twenty by clicks, and every page that produces enquiries. These get individual attention; the rest get rules.
• Check the old site has rankings worth keeping at all. When we rebuilt this very site in August 2026, Search Console showed the previous pages had earned a handful of impressions in sixteen months, so there was nothing to preserve and we started clean. Your site may be different. Look before you assume.

During the build

• Keep URLs identical where the content survives. Change an address only with a reason. Trailing slashes, capital letters and file extensions count as changes.
• Build the 301 map, one to one. Every old address points to its exact new equivalent, not to the home page and not to a category. Pages that genuinely have no equivalent go to the closest useful page, and you accept that those rankings will fade.
• Preserve the meaning of titles and H1s. Improve them; do not replace what they say. If "Emergency plumber in Woodside" ranked, the new page still says it.
• Content parity. Nothing that ranked gets shorter. Reformat, restructure, add, but do not cut the paragraphs that answered the searcher's question.
• Carry the structured data across, and upgrade it. Organization, services, FAQs, breadcrumbs.
• Rebuild the internal links. Every page that mattered is reachable from the navigation or the footer, with descriptive link text.
• Measure speed before and after. A redesign that is slower than the old site has gone backwards, whatever it looks like.
• Keep staging blocked, and write down how. The preview site should be noindex and password-protected. The launch checklist below undoes exactly that.

Launch day

• Test every redirect in the map with a script, not by clicking a few.
• Remove the noindex tag and the staging password. Confirm on the live site, not in the build files.
• Check robots.txt allows crawling and points to the sitemap.
• Check canonical tags point at the live domain.
• Generate the new XML sitemap and submit it in Search Console.
• Request indexing for the top twenty pages in Search Console.
• Confirm analytics and the contact form work on the live domain.
• Turn on 404 monitoring, whether in Search Console, the server logs or a plugin.

The four weeks after

• Coverage. New URLs should appear as indexed; old ones as "page with redirect". Old URLs reported as "not found" mean a missing rule.
• Performance by page. Impressions on old URLs should fall as the new ones rise. Both falling at once is the signal to act.
• The 404 report. Fix stragglers with redirects the same day you see them.
• The top twenty. Positions wobble for two to six weeks. A persistent drop on one page almost always traces to its redirect target or its shortened content.

How we do redesigns

A redesign follows the same packages and prices as a new site. We inventory the old site, migrate the content, build the redirect map, rebuild the site properly with the full SEO and GEO foundation, and watch Search Console with you for the weeks that follow. If you are considering a rebuild, send us the address of the current site and we will tell you what is worth keeping before anything is quoted.