A website redesign doesn’t have to mean losing your Google rankings, provided you keep the content and addresses that bring you traffic today and redirect every changed URL to its new equivalent with a 301 redirect. Add to that carrying over meta titles and descriptions, an up-to-date sitemap, reporting the changes in Google Search Console, and careful monitoring for several weeks after launch. No process can guarantee your rankings will stay exactly the same, but drops after a refresh usually come from skipping one of these steps, not from the change in appearance itself.
Below is a checklist that walks you through the whole process, from taking inventory before launch to checks after publication.
Redesign, refresh or migration: what are you planning?
Before you start, name the scope of the changes, because the risk depends on it:
- Website refresh. A new look, with the same addresses, content and structure. The lowest SEO risk.
- Redesign with a restructured site. The menu, pages and some addresses change. Medium risk, requires redirects.
- Site migration. A change of system (for example from WordPress to a modern static site), domain or protocol. The highest risk, requires the full checklist.
A redesign often combines all three. In that case, treat each change separately and plan it carefully.
Stage 1: Before launch, take inventory
List all URLs
Export all addresses of the current site: from the sitemap, from a site crawler and from the pages report in Google Search Console. Don’t skip old blog posts, PDF files or pages that aren’t in the menu but have traffic or external links.
Check which pages bring traffic
In Google Search Console and your analytics tool, check which pages have the most impressions, clicks and visits. These are the most valuable and must not disappear or lose their content.
Record current rankings and results
Write down the key phrases the site shows up for, along with search traffic from recent months. Without a baseline you won’t be able to tell after launch whether something went wrong.
Save meta titles and descriptions
Export titles, descriptions, H1 headings and structured data from your important pages. The new site should keep them or deliberately improve them, not overwrite them by accident.
Stage 2: Plan the new structure
Keep URLs wherever possible
The safest address change is no change. If the page /services/renovations/ works and has traffic, leave it at the same address even if the look changes.
Prepare a 301 redirect map
For every address that changes or disappears, prepare a table: old URL → new URL. Rules:
- redirect to the page that best matches in content, not in bulk to the homepage,
- avoid redirect chains (A → B → C): every old address should lead directly to the final one,
- use 301 (permanent) redirects, not 302 (temporary),
- account for address variants: with and without “www,” http and https, with and without a trailing slash.
Don’t throw away content that works
A new design often tempts you to shorten texts “because they look better.” If a page ranks thanks to a detailed description of a service, trimming it may lower rankings. Content can be reworded and tidied up, but keep its scope.
Look after internal linking
A new menu and footer change how pages link to each other. Make sure important pages are still easy to reach and haven’t been “hidden” deep in the structure.
Stage 3: Before publishing, test
Prepare the new site on a staging environment blocked from indexing. Before launch, check:
- that all redirects from the map work and lead where they should,
- that meta titles, descriptions and headings are filled in on every page,
- that canonical tags point to the correct addresses,
- that structured data (for example business details, FAQ) has been carried over,
- that images have alt text,
- that the site works well on a phone,
- that contact forms send messages.
Check site speed
A redesign is a good opportunity to make the site faster than before, and a bad one if you add heavy animations, large photos and dozens of scripts. Test key pages with performance measurement tools and make sure images are compressed and external scripts are kept to a minimum.
The most common mistake: an indexing block
A staging environment usually blocks search engine robots through the robots.txt file or a “noindex” tag. If that block makes it to production, the site will start disappearing from Google. Check this first thing on launch day.
Stage 4: Launch day
- Publish the new site and deploy the redirects.
- Check that robots.txt allows indexing and that no pages carry an accidental “noindex.”
- Test a random dozen or so old addresses to see whether they redirect correctly.
- Generate a new sitemap (sitemap.xml) containing only current addresses.
- Submit the sitemap in Google Search Console.
- If the domain has changed, use the change of address tool in Search Console.
- Check that the analytics code works and is collecting data.
Stage 5: Monitoring after launch
The first weeks after a redesign are key. Fluctuations in rankings during this time are normal, as Google needs time to process the changes. What matters is telling natural fluctuations from real problems.
What to check
- The indexing report in Search Console. Is the number of 404 errors and excluded pages growing?
- Search traffic. Compare it with the data collected before launch.
- Rankings for key phrases, especially for the pages that brought the most traffic.
- 404 errors in logs and analytics. Any frequently visited address without a redirect needs fixing quickly.
- Speed and Core Web Vitals. Has the site slowed down in real-world use?
How long to monitor
Intensively for the first two to four weeks, then regularly over the following months. Keep 301 redirects permanently. Don’t remove them after a few weeks, because old external links will keep working for years.
What to do if traffic drops anyway
Don’t panic and don’t immediately roll back the whole change. First check which pages lost traffic. If it’s a few specific addresses, the cause is usually simple: a missing redirect, trimmed content, a changed title or a page accidentally excluded from indexing. Fix the problem and ask Google to reindex in Search Console.
If the drop affects the whole site, first check robots.txt, “noindex” tags, canonical tags and whether the site works correctly under one proper address (for example, https only).
The checklist at a glance
| Stage | Key tasks |
|---|---|
| Before launch | URL list, traffic analysis, recording rankings and meta data |
| Planning | Keeping addresses, 301 redirect map, keeping content |
| Testing | Redirects, meta, canonicals, mobile, speed, forms |
| Launch day | Indexing unblocked, sitemap, Search Console, analytics |
| After launch | 404 errors, traffic, rankings, performance |
If you’re still planning a budget for a new site, our article how much does a website cost will also be useful.
Refresh your website with nbits
We refresh and rebuild company websites so that they look modern, run fast and keep what they have already earned in Google as far as possible. We take care of redirects, meta data and the sitemap, and we show you the first version of the new site after just one business day. See what a website refresh looks like, or get in touch.
Frequently asked questions
Will my Google rankings drop after a website redesign?
Short-term fluctuations are normal, but lasting drops usually come from mistakes: missing 301 redirects, removed content, changed meta data or an accidental indexing block. A well-prepared migration minimizes the risk, though it can’t remove it entirely.
Do I have to change URLs when refreshing a website?
No. If your current addresses are readable and have traffic, it’s best to keep them. Change only those that truly require it, and set up a 301 redirect for every change.
How long should I keep 301 redirects after a site migration?
Ideally permanently. Old addresses can stay linked from other sites, business listings or social media for years. Removing the redirects means losing that traffic and the value of those links.