How to Redesign a Website Without Losing Google Rankings
A practical website redesign SEO guide for businesses upgrading an existing site, covering what to protect, what to test and what to monitor after launch.
A website redesign should make your business easier to find, understand and contact. But if your existing website already brings enquiries from Google, replacing it can feel risky. What happens to the pages that rank? Will changing the layout affect your traffic? Could a better-looking website leave you with fewer customers?
To redesign a website without losing Google rankings, start by identifying what already performs well. Protect useful content and existing page addresses, redirect any addresses that must change, test the new website before launch and monitor search performance afterwards.
No agency can guarantee that every ranking will stay unchanged. Google explains that significant site changes can cause temporary fluctuations while pages are recrawled and reindexed. A careful migration plan helps reduce avoidable disruption. See Google’s guidance on site moves.
This guide explains how to approach a website redesign with SEO in mind, particularly if you run a small or medium-sized business and rely on your website for leads.
If you are still deciding on the scale of the project, start with whether to repair or replace your existing website.
Can redesigning a website affect SEO?
Yes. A redesign can change far more than colours, fonts and photographs. It might also change your written content, page addresses, navigation, mobile experience and the way pages are delivered to visitors.
Think about a local accountancy firm. Its existing bookkeeping page may answer questions about monthly fees, software, record keeping and support for sole traders. A replacement page containing a large photograph, a short slogan and a contact button might look cleaner, but it no longer gives potential customers the same information.
That is a content change as well as a design change.
Treat SEO as part of the project brief from the beginning. Before approving the new design, agree which pages, subjects and customer journeys it needs to preserve or improve.
1. Find out what your existing website is doing well
Start with evidence. Your favourite page is not necessarily the page bringing in your best enquiries.
Use Google Search Console to review the search queries and pages generating clicks and impressions. Its indexing reports and URL Inspection tool also help you investigate how Google sees individual pages. Google’s Search Console introduction explains the main reports.
For your redesign brief, record:
- The pages attracting organic search visitors.
- The searches bringing people to those pages.
- The pages associated with enquiries, bookings or sales.
- Useful pages that other websites link to.
- Seasonal services whose performance varies throughout the year.
Look beyond one recent week. As a practical baseline, review the last three months alongside a longer period where data is available. For seasonal businesses, compare equivalent periods from previous years too.
Measure enquiries as well as traffic
A specialist service page receiving 40 visits and five suitable enquiries may matter more commercially than a blog post attracting 2,000 visitors who never become customers.
Ask your team which services are profitable, which enquiries are valuable and which questions customers ask before buying. Combine that knowledge with your analytics.
Save the baseline before development starts. You will need it when assessing the new website, especially if the project takes several months.
2. Create a page inventory and agree what happens to each page
Make a simple inventory of the existing website. Give each page an owner or reviewer and a clear decision: keep, improve, merge or remove.
For each entry, record its address, purpose, main topic, business importance and proposed treatment. Add notes about outdated information, useful customer questions and any features that must survive the move.
A page does not become worthless simply because it has an old design. Equally, keeping everything forever is not a strategy. An obsolete service page may mislead visitors, while two overlapping guides may be clearer as one well-structured resource.
The important point is to make these decisions deliberately. Avoid allowing pages to disappear just because they were absent from the designer’s initial mock-up.
Include less visible business assets
Remember downloadable brochures, price lists, case studies and useful images. Ask colleagues whether they send customers links to specific resources in emails or proposals.
Those links are part of the customer experience too. Someone opening a six-month-old quotation should still be able to reach the relevant information after your redesign.
3. Keep existing URLs where they still make sense
A URL is a page’s web address. Changing the appearance or technology of your website does not automatically require changing its addresses.
If a useful service page already has a clear address, keep it unless there is a good reason to move it. A desire to make every address slightly shorter is rarely a strong business reason on its own.
Ask your developer early whether the replacement platform can preserve your existing URL structure. Include details such as trailing slashes and any established document addresses in that discussion.
If addresses must change, prepare an old-to-new URL map before launch. Google’s migration guidance recommends this mapping, updating internal links and keeping migration redirects for at least a year. Maintaining useful redirects longer can also help people following old links. See Google’s URL migration checklist.
4. Redirect moved pages to relevant replacements
A redirect automatically takes someone from an old address to a new one.
For a permanent page move, Google recommends a permanent server-side redirect where possible. Both 301 and 308 are permanent redirect status codes. See Google’s explanation of redirects.
The destination should fulfil the same need. An old boiler repair page should lead to its replacement boiler repair page, rather than a general homepage that makes visitors search again.
For example, your redirect plan might say:
- An old service page moves to the equivalent updated service page.
- Two overlapping guides move to one comprehensive replacement.
- An outdated brochure moves to the current equivalent brochure.
Do not redirect every deleted address to the homepage. Google warns that irrelevant mass redirects can be treated as soft 404s. Where content has genuinely gone and no suitable replacement exists, a proper 404 or 410 response is appropriate. Google’s site move guidance covers these cases.
Test the actual redirect behaviour
Opening the destination page is not enough. Ask the developer to test the old address and confirm its response code, destination and final result.
Prefer a direct route to the final page. Check for loops, unnecessary intermediate stops and destinations that return errors. Keep the test results with the launch checklist so there is a clear record of what was verified.
5. Improve the content without losing its purpose
A redesign is a useful opportunity to make content clearer. It should not automatically become an exercise in removing text.
For each important page, write down what a visitor needs to know before making contact. A commercial cleaning page, for example, might need to explain the premises served, locations covered, working hours, quotation process and arrangements for access.
You can present that information more attractively with shorter paragraphs, helpful headings and clearer sections. The objective is to improve understanding while retaining substance.
Review titles and headings individually
Avoid giving every page the same generic title, such as your company name followed by “Welcome”. Describe the specific service or subject clearly.
Review the main heading, supporting headings, SEO title and meta description together. They should describe the same page honestly, without repeating a keyword in every sentence.
For pages already generating good enquiries, consider preserving their core message for launch and testing larger editorial changes afterwards. That makes it easier to understand which changes helped and which need adjustment.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
6. Check navigation and internal links
Use the redesign to make important information easier to reach.
Try a few realistic tasks: finding the right service, checking the area you cover, reading a relevant case study and requesting a quotation. Ask someone unfamiliar with your business to try them too.
A minimalist menu is not an improvement if customers cannot find what they need. Consider links from relevant service pages and articles as well as the main navigation.
Google generally needs links built with an HTML anchor element and an href attribute to discover linked pages reliably. Ask your developer to check that key navigation does not depend solely on scripted click actions. See Google’s JavaScript SEO guidance.
7. Keep the development website out of search results
Build and review the replacement website in a separate development or staging environment. Protect it with authentication where appropriate, so unfinished pages are not publicly accessible.
If a public preview uses noindex, understand what that does: it tells supporting search engines not to include the page in search results. It does not make the page private.
Google must be able to crawl a page to see its noindex instruction. Blocking crawling in robots.txt is therefore not a reliable substitute for preventing indexing. See Google’s guidance on blocking indexing.
Include a specific launch check to remove staging restrictions from the public pages you want indexed. Check both page-level instructions and HTTP headers. A website can look completely normal in a browser while still telling Google to exclude it.
8. Check canonical URLs and mobile content
A canonical URL identifies your preferred version of a page where duplicate or very similar versions exist. Google treats canonical declarations as signals, rather than an instruction it must always follow. Google’s canonical URL documentation explains how these signals work.
During a redesign, check that public pages do not accidentally declare a staging address, an obsolete URL or the homepage as their canonical version. This is especially important when metadata is generated from a shared template.
Also review the mobile version carefully. Google uses the mobile version of a site’s content for indexing and ranking. Essential information should remain available on mobile, even if its presentation changes. See Google’s mobile-first indexing guidance.
Test more than the homepage. Check a service page, an article, a contact form and any booking or checkout journey on a phone.
9. Improve speed without assuming it guarantees rankings
Make performance part of the design brief. Large images, unnecessary scripts and elaborate effects can undermine an otherwise attractive website.
Compare representative pages before and after the redesign under similar test conditions. Include pages with forms, galleries or other features, rather than testing only the simplest page.
Core Web Vitals are used by Google’s ranking systems, but good scores do not guarantee top rankings. Performance should support useful content and a good customer experience. See Google’s explanation of Core Web Vitals.
Set practical acceptance criteria with your developer: readable content appears promptly, buttons respond reliably and elements do not jump around while someone is trying to use them.
10. Use a website redesign SEO launch checklist
Agree who will approve the launch, who can fix problems and who will review performance afterwards. Schedule the release when those people are available.
Before launch, confirm that:
- Important existing pages have been reviewed against their replacements.
- Changed addresses have tested redirects.
- Public pages have appropriate indexing and canonical settings.
- Titles, descriptions and headings describe the correct content.
- Mobile navigation, forms and contact details work.
- Analytics and enquiry tracking are configured.
- A current backup and a practical recovery plan exist.
Immediately after launch, test the live website again. A staging environment cannot reveal every production configuration problem.
Check the live sitemap and submit it through Search Console. Inspect important URLs and monitor indexing and performance reports. Search Console helps you identify access and indexing problems; submitting a sitemap does not guarantee that every page will be indexed. See Google’s Search Console guidance.
What if traffic drops after the redesign?
Investigate the pattern before deciding on the remedy.
If analytics traffic falls but Search Console clicks remain broadly stable, check whether the tracking setup or consent behaviour changed. A measurement problem can look like a marketing problem.
If only a few pages lose visibility, inspect those pages and their old addresses. Look for missing content, incorrect redirects, indexing restrictions or broken navigation links.
If the decline affects the whole website, prioritise shared settings and templates. Check site availability, indexing instructions and canonical generation before rewriting every page.
Compare equivalent weekdays and consider seasonal demand. Keep a dated record of fixes, then review the affected pages again. Avoid making several unrelated changes at once, as that makes it harder to identify the cause.
As a practical monitoring schedule, check technical problems daily during the first week and review search traffic and enquiries weekly afterwards. Continue closer monitoring if errors or unexplained losses persist.
Frequently asked questions
Can I move from WordPress to another platform without losing SEO?
It is possible to preserve search visibility during a platform change, but the platform name alone does not protect it. Include content, URLs, metadata, redirects and measurement in the migration brief. Ask for evidence that the live replacement passes the agreed checks.
Do I need Google’s Change of Address tool for a redesign?
Not for an ordinary redesign that keeps the same domain. The tool is intended for eligible domain or subdomain moves, not changes to paths within the same site. See Google’s Change of Address instructions.
How long does SEO recovery take after a redesign?
There is no reliable universal deadline. The scale of the changes, crawling and any technical problems all matter. Do not accept a fixed recovery promise without investigation. Known errors should be corrected promptly rather than dismissed as normal settling-in time.
Should I keep my old website running?
Keep a secure backup and access to the configuration needed for recovery. That does not mean maintaining two publicly indexable copies. If the domain changes, plan how the old domain will continue serving its redirects.
Plan your website upgrade around what matters
Before commissioning a redesign, ask the agency three questions: which existing pages are valuable, how will those pages be protected, and what evidence will show that the launch worked?
At Afterworks, we build a proposed replacement using your existing website as a starting point, so you can see what an upgrade could look like before committing. We also explain the improvements and how the proposed website is prepared for search engines.
If your current website feels outdated, start the conversation with your website address and the services you most want to grow. A useful redesign brief connects the new design to your customers, your existing search visibility and the enquiries your business needs.
