How to redesign an old company website without losing search rankings

Why redesign at all

An old site loses enquiries for three reasons. First - it doesn't work on mobile, or works poorly. More than half of people now search for services on their phones, and if a button won't click or text overlaps an image, they leave for a competitor.

Second - the design creates distrust. This isn't about beauty, it's about signals: if your site looks like it was built in 2010, clients wonder whether your company is still operating. An updated site doesn't need to be flashy, but it must look alive.

Third - technical. Old platforms load slowly, index poorly, and can't connect to modern analytics tools. Google directly factors load speed into rankings, and a slow site simply drops lower in results.

If your site brings in enquiries but you see conversion falling, time on site dropping, and bounce rate rising - that's a warning. A redesign solves all three problems, but only if you do it right.

What to preserve during a redesign

First and most important - page URLs. If an old page lived at /services/web-development, the new one must stay there. Search engines index individual pages, not whole sites, and each page has accumulated weight. Change the address and you lose the ranking.

If URL changes are unavoidable (for example, migrating from an ancient CMS to a new structure), set up 301 redirects. This is a server instruction: this page has moved here, transfer all accumulated weight. Without redirects, the search engine assumes the page was deleted and drops it from the index.

Second - text on important pages. If a Web Development page has been in the top three for a key query for years, rewriting the text entirely is risky. The search engine will re-evaluate the page and may decide it's now about something else. Keep the structure and key paragraphs, improve phrasing, add specifics - but don't start from scratch.

Third - meta tags: title and description. These are the heading and summary shown in search results. If a page ranks well, don't touch them without reason. If you do change them, check the ranking after two weeks and roll back if it dropped.

What you can and should change

Change the design freely. Search engines don't care what colour your buttons are or where the menu sits. What matters is that content remains accessible: headings, text, links. Don't hide important text in images or JavaScript widgets that search engines can't see.

Change the markup - you must, if the site isn't mobile-responsive. Google has moved to mobile-first indexing: it looks at the mobile version first, then desktop. If the site doesn't work on phones, rankings fall even for people searching from computers.

Load speed is also fair game for changes. Compress images, remove unnecessary scripts, set up caching. Check current speed through Google's free PageSpeed Insights tool - it shows what's slowing you down and gives recommendations. Speeding up by 1-2 seconds genuinely lifts rankings.

Improve navigation and menu structure if the old one was confusing. Clear navigation helps both people and search engines: if you can reach a key page in two clicks, it's indexed more readily. Just don't delete old sections without redirects.

Step-by-step redesign plan

Step one: compile a list of all pages currently in the index. You can do this through Google Search Console - there's a report on indexed URLs. Export it to a spreadsheet. This is your map: every page on the list must either stay at its old address or receive a redirect to a new one.

Step two: check which pages bring traffic. In Google Analytics, look at the Landing Pages report for the past three months. Pages with traffic are your asset; they're the riskiest to touch. Highlight the top ten and mark them in your spreadsheet.

Step three: develop the new version on a subdomain or test server, but don't publish it to the main domain yet. Verify that all URLs from your spreadsheet open, that text on key pages is preserved, that submission forms work. Run the test version through PageSpeed Insights - it should load faster than the old one.

Step four: move the site to the main domain during off-hours when traffic is minimal (night or weekend). Immediately after migration, manually check the top ten pages from step two: do they open, are texts and meta tags intact. If something broke, fix it immediately.

Step five: two days later, go into Google Search Console and request re-crawling of updated pages. This speeds up re-indexing. Monitor the Coverage report in Google - errors will show up there if any appear.

Step six: after two weeks, compare rankings. If key pages dropped - look for the cause: did the text change, did a redirect fail, did speed drop. Minor fluctuations of 2-3 positions are normal; a sharp drop of 10+ is a signal that something went wrong.

Redirects: how to set up and verify

If page addresses change, you need 301 redirects. This is a permanent redirect: when someone (human or search bot) visits the old URL, the server automatically sends them to the new one and transfers all SEO weight.

Redirects are configured either in server configuration (the .htaccess file for Apache or nginx.conf for Nginx), or in the hosting control panel if there's such a section. Ask your developer to set them up before publishing the new site - this isn't a task to do later.

Check redirects manually: open the old URL and see if it forwards to the new one. Or use a free service like httpstatus.io - paste the old address, it shows where the redirect goes and what response code the server returns. Code 301 is correct; 302 (temporary redirect) or 404 (not found) is an error.

If you have many pages (50+), checking each manually takes too long. Ask your developer to export a redirect map and run it through a script or specialised service. The key is that no indexed page leads nowhere.

Common redesign mistakes

Mistake one: completely rewrote text on main pages. The owner decides old texts don't sell, hires a copywriter, and they write new ones from scratch. A month later rankings drop. The search engine considered the page relevant to certain queries; now it's about something else. If you want to improve text, do it gradually, paragraph by paragraph, and monitor statistics.

Mistake two: didn't set up redirects or set them up wrong. For example, all old pages redirect to the homepage. This kills all accumulated weight of internal pages. Or set up 302 instead of 301 - the search engine thinks it's temporary and won't transfer weight to the new page.

Mistake three: launched the new site without testing on a test domain. The developer uploaded code, something broke, the site is down for two hours while they fix it. Google comes to check, sees errors, lowers trust in the site. Always test updates on a copy, and only move a verified version to the main domain.

Mistake four: blocked the site from indexing during development and forgot to unblock after launch. There's a ban in CMS settings or in the robots.txt file, and search engines stop visiting. Check robots.txt immediately after migration - there shouldn't be a line saying Disallow: / without qualifications.

Mistake five: didn't track results. Launched the new site and forgot about it. Six months later they look - traffic has halved. If they'd checked after a week, they could have quickly rolled back changes or fixed the error.

When not to update but build new instead

If your old site is on a builder like Wix or Squarespace and you need complex logic (user accounts, CRM integration, product filters), it's simpler to build new on a proper CMS or framework. Builders aren't designed for this, and trying to force business logic onto them creates workarounds.

If your old site was written ten years ago on an ancient CMS that no one supports anymore, updating it is throwing money away. The code is outdated, vulnerabilities aren't patched, connecting modern analytics or marketing tools is impossible. Building new is cheaper and safer.

If your current site brings no traffic at all, updating it to preserve rankings makes no sense - there are no rankings to preserve. In this case you can build a new site from scratch, focusing on usability and content rather than technical constraints of the old one.

In all other cases - when the site works, brings enquiries, but looks dated - an update is more cost-effective. You keep SEO weight, accumulated links, search reputation, and simply refresh the appearance.

How we update client sites

At EFIMOV DEV, before updating we conduct an audit: we look at which pages are indexed, where traffic comes from, where the bottlenecks are. We build a redirect map before development starts so no URL is lost. We test the new version on a separate subdomain and only move it to the main domain after verifying all key scenarios.

After launch we track rankings for two weeks and make adjustments quickly if needed. The cost of an update depends on the current state of the site and scope of changes - we calculate after a brief. More detail about services and indicative pricing is on our site efimovdev.ru.