Website Migration SEO: How to Redesign Without Losing Your Rankings
A private clinic planned to redesign its six-year-old website. The site held hundreds of pages, including many blog posts, and had built up years of search visibility. The owner was excited about a fresh look, but nervous. Would a new design wipe out what they had earned? Keeping addresses intact, and reworking tired posts without breaking links, was the central worry.
Website migration SEO is the discipline of moving a site without losing its rankings. Here is how to approach a redesign safely.
Why redesigns put rankings at risk
A redesign can change addresses, page structure, headings, links and content, all of which Google uses to judge pages. If old pages disappear without redirects, their visitors and authority vanish. Even well-meant changes can cause drops. Planning protects the value you have built, and prevents a beautiful new site from being invisible.
Start with a full inventory
List every page on the current site, with its address, traffic, links and rankings. Include blog posts and older pages. This is the foundation of the whole project. Without it, you cannot decide what to keep, or know what you have lost. Export data from analytics and Search Console before you touch anything.
Identify your most valuable pages
A small number of pages usually bring most traffic and enquiries. Mark them clearly. These pages need the most care: keep their content, headings and internal links as close to the original as you can, and check them first after launch. Protecting the winners protects the business.
Keep the same addresses where you can
The safest approach is to keep existing page addresses unchanged. If the new design can use the same structure, do so. Every change of address needs a redirect, and each redirect carries a small risk. Fewer changes mean fewer chances for something to go wrong.
Website migration SEO depends on a redirect map
Where addresses must change, map each old address to the most relevant new one, one to one. Do not send everything to the homepage. Test the redirects before launch, and again straight afterwards. A careful redirect map is the single most important safeguard in any migration.
Decide what to do with old blog posts
Not every post deserves a place on the new site. Keep strong posts, update fixable ones, merge overlapping ones and retire the weak ones, with redirects. A redesign is a good moment to tidy a library, but do it with a plan, and never delete pages with visitors or links without a redirect.
Preserve on-page elements
Titles, headings, descriptions, image descriptions and internal links all contribute to search performance. Make sure the new templates carry them across, or improve them deliberately. A design that drops these elements can quietly weaken every page, so add them to your checklist for the build.
Test on a private copy first
Build and review the new site on a private test copy, blocked from search. Crawl it, check headings and links, test speed and mobile layouts and compare the list of pages with your inventory. Problems found in testing cost little. The same problems on a live site cost visibility.
Choose the launch date carefully
Avoid busy seasons or big campaigns. Choose a time when you can watch results closely for several weeks. Keep the team available, and have a plan to reverse quickly if something goes badly wrong. A calm, well-timed launch is far safer than a rushed one.
Check everything straight after launch
Confirm redirects work, pages are indexed, tracking is running and the sitemap is submitted. Check the key pages and forms. Watch Search Console for errors. Fix problems within hours, not days. The first few days after launch are when most mistakes can be caught cheaply.
Monitor for weeks, not days
Some fluctuation is normal while Google reassesses. Compare impressions, clicks and rankings for key pages with your baseline, weekly for the first two months. Investigate large drops promptly. Patient, structured monitoring shows whether the migration is settling, or needs correction.
Be honest about expectations
Even a well-run migration may cause a temporary dip, and nobody can guarantee outcomes. What you can do is reduce risk through planning, testing and monitoring. Explain this to the team beforehand, so that a small wobble is understood rather than feared.
Keep a rollback plan
Before launch, make sure you can restore the old site quickly if something goes badly wrong. Keep a complete backup, know who can switch back and agree in advance what would trigger that decision. A rollback plan is rarely used, but having it makes the whole team calmer and the launch safer.
Tell the right people about the change
Inform staff, referrers and partners of the new site and any address changes. Update links in directories, profiles and email signatures. Links to old addresses can then be replaced with direct links to the new pages, which is better than relying on redirects alone.
Check images, documents and forms
Redesigns often lose images, downloadable guides or forms that patients rely on. Include them in your inventory, and confirm each one works on the new site. A missing consent form or referral document can frustrate patients and referrers as much as a broken page.
A quick checklist
- Inventory every page and record traffic.
- Protect your most valuable pages.
- Keep addresses the same where possible.
- Map every changed address to a new one.
- Test on a private copy.
- Monitor weekly for two months.
Our companion article on refresh or rebuild helps you decide whether to migrate at all, and our guide to website consolidation has a related checklist. If you would like help, we are glad at Pulse Digital Health to talk.
Frequently asked questions
Will a redesign hurt my rankings?
It can if addresses, content and links change carelessly. Careful planning, redirects, testing and monitoring reduce the risk, though a temporary dip is possible and nothing can be guaranteed. A written plan and a careful launch reduce the risk substantially. A written plan that everyone has seen prevents the most common misunderstandings.
What is a redirect map?
A list matching each old page address to the most relevant new one, so visitors and search engines land in the right place after a move. Test it before and after launch. Test a sample of redirects before launch and again straight afterwards. A small number of redirect errors can lose surprising amounts of traffic if the pages are important.
Should I keep my old blog posts?
Keep strong ones, update fixable ones, merge overlapping ones and retire weak ones with redirects. Never delete pages with visitors or links without a proper redirect. Choose which posts to keep using traffic, links and quality, not just age. Keeping a record of each decision helps if anyone questions it later.
Why test on a private copy?
Because problems found before launch cost little to fix, while the same problems on a live site cost visibility. Block the copy from search and crawl it against your inventory. Block the copy from search and compare its pages with your inventory. Testing costs little compared with fixing a live problem after launch.
When should I launch a new site?
When you can watch results closely for several weeks, outside busy seasons. Keep the team available and have a plan to reverse quickly if something goes wrong. Choose a time when you can react quickly and the team is available. A launch with a rollback plan is a calmer launch for everyone.
How long should I monitor after launch?
Weekly for the first two months at least, comparing key pages with your baseline. Investigate large drops promptly and correct problems quickly. Compare against your pre-launch baseline and record what you find. Weekly comparisons show early whether the migration is settling or needs correction.
