How to redesign your website without losing SEO, enquiries or sales

Your website may look dated, feel difficult to update or no longer reflect the quality of your business. Perhaps it is slow on mobile, awkward to navigate or simply fails to generate the enquiries it once did.

A redesign can solve these problems—but it can also create new ones.

Changing page addresses, removing useful content or launching without adequate testing can affect search rankings, break links and make it harder for potential customers to find what they need.

A successful website redesign therefore involves much more than changing colours and rearranging a few pages. It is an opportunity to improve the design, user experience, technology and commercial effectiveness of your website while protecting everything that already works.

Here is how to approach it properly.

Start with evidence, not appearance

Most redesign projects begin with a familiar statement:

“Our website looks old.”

That may be true, but appearance is only one part of the problem.

Before deciding what the new website should look like, establish how the existing one performs. Useful questions include:

• Which pages attract the most organic traffic?
• Which landing pages generate enquiries or sales?
• Where do visitors commonly leave?
• Which pages have links from other websites?
• What do customers regularly struggle to find?
• Which devices and screen sizes do visitors use?
• Is the website slow or unstable?
• Which parts are difficult for your team to manage?

Analytics, Search Console data, customer feedback and conversations with the people who manage the website can all help build a clearer picture.

Without this research, there is a risk of removing or changing something valuable simply because nobody realised how important it was.

Define what the redesigned website needs to achieve

A redesign needs measurable objectives.

“Make it look better” is subjective. A stronger brief might include goals such as:

• Increase qualified enquiries.
• Make important services easier to find.
• Improve mobile usability.
• Reduce page-loading times.
• Simplify content management.
• Support a growing product or service range.
• Improve accessibility.
• Strengthen organic search visibility.
• Make the business appear more credible.
• Increase the percentage of visitors who complete an important action.

These goals influence the structure, content and functionality of the website. They also give you something meaningful to assess after launch.

The best-looking website is not necessarily the best-performing one. Good web design should support the user and the business at the same time.

Protect the pages that already perform well

One of the easiest redesign mistakes is to concentrate entirely on the new website and overlook the value of the old one.

Some existing pages may already rank well, attract links or introduce customers to the business. Replacing them with shorter, more generic content could reduce their relevance and visibility.

Before development begins, create an inventory of the current website. For each important page, record:

• Its URL.
• Its purpose.
• Organic traffic and rankings.
• Enquiries, sales or other conversions.
• Links from external websites.
• Important headings and content.
• The equivalent location on the new website.

This does not mean every old page must survive. Outdated or overlapping content may need to be combined, improved or removed. The important point is to make those decisions deliberately.

A redesign should preserve useful content and strengthen weaker content—not discard everything and start again without evidence.

Plan the structure around real customer journeys

Website navigation often reflects the internal structure of a business rather than the way its customers think.

Your visitors may not understand department names, industry terminology or how responsibilities are divided within your organisation. They arrive with a question, problem or objective and want to know whether you can help.

A clearer website structure usually starts with:

• The audiences you serve.
• The problems you solve.
• The services or products you provide.
• The information customers need before making contact.
• The logical next step from each page.

Important pages should be accessible through normal navigation and internal links. Visitors should not need to search repeatedly or return to the home page whenever they want to change direction.

Clear structure also helps search engines discover pages and understand their relationship to one another. Google’s SEO guidance for web developers stresses the importance of crawlable links and a technically accessible website.

Avoid changing URLs unnecessarily

A page address does not need to change just because its design has changed.

If an existing URL is concise, relevant and already performing well, keeping it is normally the simplest option. This avoids unnecessary redirects and preserves the address people may have bookmarked or linked to.

For example, there may be little benefit in changing:

/web-design

to:

/services/digital/web-design-services

If a URL genuinely needs to change, it should be mapped to the most relevant new page.

This is especially important when:

• Changing the website’s domain.
• Replacing an old content management system.
• Restructuring services or products.
• Combining several pages.
• Moving content into new sections.
• Changing URL naming conventions.

Every important old address should have a planned destination before launch.

Redirect old pages to the correct new ones

A permanent redirect tells browsers and search engines that a page has moved.

Where an old page has a close replacement, it should normally use a server-side 301 or 308 redirect to send visitors to the new location. Google recommends permanent server-side redirects for pages that have permanently moved.

Avoid redirecting every removed page to the home page. That rarely helps the visitor and may be treated as a soft 404 because the destination is not a meaningful replacement.

Instead:

• Redirect old service pages to their corresponding new service pages.
• Redirect merged articles to the most relevant consolidated guide.
• Allow genuinely removed content with no replacement to return a proper 404 or 410 response.
• Avoid redirect chains where one old URL redirects through several others.
• Update internal links so they point directly to the final address.

Google provides detailed site-migration guidance, including URL mapping, redirect testing and post-launch monitoring.

Here's a guide on how to add 301 redirects.

Improve the content instead of merely moving it

A redesign is an ideal time to improve the substance of a website.

This does not mean adding unnecessary paragraphs to every page. It means making each page more useful, specific and convincing.

A strong service page might explain:

• Who the service is for.
• The problem it solves.
• What is included.
• How the process works.
• What makes the business credible.
• Relevant experience or case studies.
• Frequently asked questions.
• The next step.

Generic claims such as “we offer high-quality solutions” say very little. Original examples, evidence, photographs, qualifications and clear explanations are far more persuasive.

The redesigned website should make it easier for a potential customer to understand what you offer and why they should choose you.

Design for action, not decoration

Visual impact matters, but every design decision should have a purpose.

Large animations, unconventional navigation and dramatic page transitions can look impressive in a presentation. They can also make a website slower, harder to use and more frustrating on mobile devices.

Effective commercial web design creates a clear visual hierarchy. Visitors should quickly understand:

1. Where they are.
2. What the page offers.
3. Why it is relevant.
4. What they should do next.

Calls to action should match the visitor’s stage of decision-making. Not everyone is ready to request a quote immediately, so useful secondary actions might include viewing a case study, downloading a guide or exploring related services.

The objective is not to cover every screen with buttons. It is to provide an obvious next step whenever the visitor is ready to take one.

Treat mobile design as a priority

A desktop design cannot simply be squeezed onto a smaller screen.

Mobile users may be browsing with one hand, using a slower connection or trying to complete a task while away from their desk. Navigation, forms, buttons, tables and interactive elements all need to work comfortably within those constraints.

During a redesign, check that:

• Text remains legible without zooming.
• Buttons and links are easy to tap.
• Menus are straightforward.
• Forms do not request unnecessary information.
• Important content is not hidden on mobile.
• Images are appropriately sized.
• Pop-ups do not block the interface.
• Telephone numbers and directions are easy to use.

Test on real devices where possible. A browser preview is useful, but it does not always reveal the practical frustrations of using a website on a phone.

Build performance into the website from the beginning

Performance is difficult to repair if a website has been designed without considering it.

Oversized images, excessive scripts, unnecessary tracking tools, poorly implemented animation and bloated third-party plugins can all make a new website slower than the one it replaces.

Performance should therefore be considered during design and development—not added to a checklist immediately before launch.

Useful areas to address include:

• Modern image formats and responsive image sizes.
• Sensible font selection and loading.
• Efficient CSS and JavaScript.
• Page and server caching.
• Reliable hosting.
• Limited use of third-party scripts.
• Stable dimensions for images and embedded content.
• Fast interaction after the page appears.

Google’s Core Web Vitals focus on loading performance, visual stability and responsiveness. The current metrics are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. The official Web Vitals guidance explains how these measurements relate to real user experience.

Performance is not only an SEO consideration. A faster website feels more professional and removes friction from the path to an enquiry or purchase.

Include accessibility throughout the project

Accessibility should influence design, content and development from the beginning.

It covers considerations such as:

• Colour contrast.
• Keyboard navigation.
• Visible focus states.
• Alternative text for meaningful images.
• Proper heading structure.
• Clear form labels and error messages.
• Captions or transcripts for media.
• Interfaces that do not depend solely on colour.
• Support for zoom and text resizing.

Addressing these points early is far easier than attempting to retrofit accessibility after the website has been completed.

The W3C recommends evaluating accessibility throughout a project because early checks reduce the risk of becoming constrained by expensive design decisions. Its accessibility planning guidance provides a useful framework.

Accessible design benefits more than users with permanent disabilities. It can also help people using a phone in bright sunlight, recovering from an injury or browsing under difficult conditions.

Do not overlook technical SEO

The visual redesign may receive the most attention, but small technical mistakes can have a significant effect after launch.

The new website should be checked for:

• Crawlable navigation and internal links.
• Unique page titles and meta descriptions.
• One clear main heading per page.
• Correct canonical tags.
• Appropriate index and noindex rules.
• A valid XML sitemap.
• A sensible robots.txt file.
• Accurate structured data.
• Descriptive image alternative text.
• Proper 404 responses.
• Secure HTTPS delivery.
• Redirects from changed URLs.

Structured data should accurately represent what visitors can see on the page. Google recommends JSON-LD where practical, but markup does not guarantee a rich result. Its structured-data guidelines explain the technical and quality requirements.

The XML sitemap should contain the canonical URLs you want search engines to discover. After launch, submit it through Google Search Console and monitor it for processing errors.

Test the website before it goes live

A redesign should be tested as a working website, not approved solely through static design images.

Testing should cover:

• Navigation and internal links.
• Contact and enquiry forms.
• Search and filtering.
• Ecommerce or payment processes.
• Account areas.
• Downloads.
• Mobile and tablet layouts.
• Common browsers.
• Keyboard navigation.
• Page speed.
• Analytics and conversion tracking.
• Cookie controls.
• Redirects.
• Error pages.
• Emails and notifications.

Ask someone who was not closely involved in the project to complete realistic tasks. They are more likely to expose unclear wording or assumptions the project team has stopped noticing.

For example:

• Find a specific service.
• Locate evidence of relevant experience.
• Submit an enquiry.
• Find a technical document.
• Complete a purchase.
• Return to a previously viewed section.

Testing real tasks is much more useful than simply asking whether somebody “likes” the website.

Plan the launch carefully

Launching a redesigned website should be treated as a controlled technical change.

Before launch:

• Create and check the final redirect list.
• Crawl the staging website for errors.
• Confirm that important content is present.
• Check canonical tags and indexation rules.
• Test analytics and form tracking.
• Take a backup of the existing website.
• Choose a lower-traffic launch period where practical.
• Make sure the necessary people are available to resolve problems.

Immediately after launch:

• Test the most important pages and forms.
• Confirm that redirects work.
• Check that search engines are not blocked.
• Submit the new sitemap.
• Inspect important URLs in Search Console.
• Monitor server errors, enquiries and sales.
• Compare traffic and conversions with the pre-launch baseline.

Some movement in search visibility can occur while Google recrawls and processes a redesigned or migrated website. Monitoring helps distinguish normal adjustment from a technical problem requiring action.

Continue improving after launch

A website is not finished simply because it has gone live.

The first few weeks provide valuable evidence about how real users respond to the new design. Monitor:

• Organic traffic.
• Search queries and landing pages.
• Enquiries and conversion rates.
• Form abandonment.
• User journeys.
• Page speed and Core Web Vitals.
• 404 errors.
• Customer feedback.
• Internal search terms.

This information can reveal opportunities that were not obvious during the project.

Small, evidence-led improvements after launch are normally more valuable than waiting several years and replacing the entire website again.

A redesign should protect value as well as create it

A successful redesign brings together strategy, content, user experience, development, accessibility and SEO.

It should make the website more attractive, but it should also make the business easier to understand, easier to trust and easier to contact.

The biggest risks arise when a redesign is treated as a purely visual exercise. Existing traffic, content and customer journeys need to be understood before anything is removed or changed.

With the right planning, a redesigned website can modernise your online presence, protect your search visibility and create a stronger platform for future growth.

Planning a website redesign?

Made Simple Media designs and develops fast, accessible and commercially focused websites for organisations that need more than a cosmetic refresh.

We can help you review your current website, preserve valuable search visibility and create a new site built around your customers and business goals.

Talk to us about your website redesign.

Article by David Reeder. LinkedIn Profile: https://www.linkedin.com/in/david-e-reeder/