how to redesign your website without losing Google rankings

When rankings fall after a website redesign, the new design is rarely the cause. More often the URLs, titles and content Google knew on the old site quietly disappeared in the move. Here is what to check before the redesign, on launch day and in the four weeks after.

Record the current state before you redesign

Before design work starts, open the Performance report in Search Console, widen the date range (up to 16 months of data) and export the list under the Pages tab. Traffic tends to sit on a handful of pages, and those need the most care.

What to record:

• Pages that receive clicks and their main queries
• Every URL on the site: the sitemap plus a crawler export, PDFs included
• Every page's title tag, meta description and H1
• Pages with links from other websites (the Links report in Search Console)
• Pages that produce conversions in Google Analytics 4: forms, phone calls, sales
• Mobile speed measurements for the main page templates

Keep it all in one spreadsheet; once the old site is off, its titles and copy are hard to recover.

URL mapping and 301 redirects

Rankings are most often lost because URLs change and the old ones are not redirected. To Google, a new URL is a new page; the old URL's history and links pass on only through a permanent redirect (301).

The safest option is not to change URLs at all. If they must change, map every old URL to a destination:

Points to watch:

• Send each old URL to the new page closest in content. Google often treats a blanket redirect to the homepage as a missing page.
• Redirect in one hop. Chains slow the page down and invite errors.
• Use a permanent redirect (301), not a temporary one (302).
• Resolve http and https, www and non-www to a single version.
• If the domain is changing too, use the Change of Address tool in Search Console.
• Keep redirects for at least a year.

Carry over titles, descriptions and content

Copy tends to get shortened in a redesign, yet that copy is usually what earned the page its ranking. On pages that bring traffic, move the title tag, H1 and main text across intact. Improve them after launch, one page at a time. Change the URL, title and content together and you cannot tell which one caused a drop.

Check on the new site:

• Have title tags and meta descriptions been migrated? They often arrive empty after a platform change. Google truncates titles after roughly 60 characters, so review their length too.
• Have image alt texts been carried over?
• Do menu, footer and in-text links point straight to the new URLs?
• Do canonical tags point to the new URL? On a multilingual site, are hreflang tags in place?
• Is structured data for products, the business and FAQs present in the new templates?

Deleting a page is a decision too. Base it on the traffic and link data in your inventory, not on how dated the page looks. In our web design and e-commerce projects we build the mapping table alongside the page structure; left to the end, it stays incomplete.

Sitemap, crawlability and speed

A new site is normally built on a staging address closed to search engines. The classic launch-day accident is that this block goes live too: a Disallow: / line forgotten in robots.txt, or a noindex tag left on the pages. In WordPress it is the search engine visibility box under Settings, Reading.

The XML sitemap should list only working URLs you want indexed, never redirected or noindexed ones.

New designs often bring larger images, more fonts and animation. Before launch, measure the main templates on mobile with PageSpeed Insights and compare them with your earlier figures. Watch three values: load time of the largest element (LCP), response to interaction (INP) and layout shift (CLS). Fix any template that scores worse than the old one.

Verify tracking as well. If Google Analytics 4 and Google Tag Manager tags do not fire on the new site, reports show a fall in traffic that never happened. Checking that conversion events fire on the new buttons and forms is the key part of measurement setup in a redesign.

Launch day and the first four weeks

Launch-day checklist

Launch when the team will be reachable the next day. A Friday evening launch means finding the problem on Monday.

1. Take a full backup of the old site and write down the rollback steps.
2. Check on the live site that the robots.txt and noindex blocks are gone.
3. Crawl every old URL in the mapping table: one hop, 301, right page?
4. Open the 20 highest-traffic pages by hand: title, H1, content and canonical correct?
5. Try a URL that does not exist: does it return a real 404 status?
6. Submit the sitemap to Search Console and request indexing for key pages with the URL Inspection tool.
7. Test forms, call buttons, basket and checkout with a real transaction.
8. Confirm visits and conversion events in the Google Analytics 4 real-time report.

Let the launch be the only change on launch day. If the domain, server, design and content all change at once, tracing a problem back to its source can take days.

What to watch in the first four weeks

Some fluctuation after launch is normal while Google crawls the new URLs and matches them to the old ones. The task is to tell temporary movement from lasting loss.

• Week one: check the Pages (indexing) report in Search Console every day. The Not found (404) list reveals URLs you missed in the mapping; redirect them straight away.
• Week two: compare before and after in the Performance report, page by page. Look past the total to the pages you marked at the start.
• Week three: the Core Web Vitals report begins to fill with real user data. Compare the conversion rate too; if rankings held but enquiries fell, the problem lies in the design.
• Week four: if a page is still slipping, ask why: shorter content, a changed title, fewer internal links?

With no technical fault in sight, the quickest fix is often to restore the old title and content. That is why the inventory comes first.

Where to start

Before design is discussed, do three things: export page-level performance data from Search Console, list every URL, and mark the pages that bring traffic. Then make the mapping table a separate deliverable in the project plan.

If you have no Search Console account, set one up first; data only accumulates once it exists. A redesign is also a chance to fix existing problems: SEO work brings missing titles and weak pages to light, and a UI/UX analysis shows where visitors get stuck.

These steps reduce the risk considerably but do not remove it; Google decides rankings, and no migration comes with a guaranteed outcome. If you are planning a redesign and want to discuss protecting your rankings before launch, write to us through the contact page.