Skip to content
SiteGuys / Guide 03

Complete Business Website Redesign Guide

A practical guide to deciding what to keep, improve or rebuild in a business website, including content, enquiries and search-sensitive URLs.

Direct answer
Start a redesign by identifying what the current website does well, what customers struggle to find and what the business needs next. Keep useful content and working search paths. Change the design, structure or platform only where the expected benefit justifies the work and migration risk.
01 / GUIDE

Find the actual problem before choosing a new look

Check the questions customers ask, the services they cannot find, the pages they use, mobile navigation and whether calls or forms work. A dated appearance can be a reason to refresh, but a clear offer and functioning enquiry path matter more than a visual trend. Ask what should improve after launch.

02 / GUIDE

Decide what should stay

Inventory the current pages, URLs, content, images, forms, analytics and integrations. Keep strong explanations and proof where they still serve customers. Retire duplicate or outdated pages deliberately. If a page attracts relevant search visits, plan what its replacement will answer before removing it.

03 / GUIDE

Choose redesign or rebuild by constraints

A redesign within the current platform can be faster when editing, performance and integrations are sound. A rebuild may be justified when the site is difficult to maintain, cannot support necessary features or is constrained by its architecture. Compare costs, disruption, ownership and the work your team must supply, rather than assuming a new platform is automatically better.

04 / GUIDE

Launch without losing the basics

Map changed URLs to relevant new pages, test redirects, forms and mobile layouts, preserve access to analytics, and check the live sitemap and indexing settings. Expect to monitor search and enquiries after launch. A careful migration reduces avoidable loss but cannot guarantee identical search performance.

Decision checklist

What to keep in view.

01Current-site inventory

02Analytics and search review

03URL mapping

04Content decisions

05Design system

06Launch and redirect QA

Questions after the guide

Short answers to the next questions.

01Will a redesign hurt SEO?+

It can if useful URLs or content are removed without planning. Careful redirect mapping, content preservation and crawl checks reduce that risk.

02Should every page keep the same URL?+

Not necessarily. URLs can change when there is a good structural reason, but old high-value URLs should map to relevant new destinations.

03When is a rebuild better than a redesign?+

A rebuild is often better when the existing platform or codebase prevents the new performance, structure or maintainability goals.

Use the guide

Turn the answer into a clearer project brief.

Bring the useful constraints, assumptions and questions into the project conversation before scope is fixed.

Discuss the project →