Independent website planning guides for Canadian businessesPlanning · Design · SEO · Performance · Launch
Website Decision Guide

Website Redesign: Change What Needs Changing, Preserve What Works

A redesign should solve documented problems. Replacing everything because the site looks old can remove useful content, working URLs and conversion paths that took years to establish.

PlanChoose a DesignerUnderstand CostsSEOPerformanceLaunch Checklist

Audit before designing

Record current pages, organic landing pages, backlinks, forms, conversions, analytics, Search Console data and important rankings before making structural decisions. A redesign is easier to evaluate when you know what the old site was doing.

Separate visual problems from information problems

A dated colour palette can be fixed without changing every URL. Confusing service architecture may require deeper work. Identify whether the problem is visual design, content, navigation, performance, mobile usability, technology, conversion or a combination.

Map old URLs to their new destinations

When a useful page moves, use a permanent redirect to the closest relevant replacement. Do not send every removed URL to the homepage. Redirect planning is especially important for established service businesses with years of indexed pages and external links.

Rewrite where the visitor needs more clarity

Redesigns are a good opportunity to remove filler, combine genuine duplication and expand pages that fail to answer buyer questions. Keep useful facts and proof. New wording should improve the page, not merely make every sentence different.

Test the rebuilt site before switching

Crawl the staging site, check internal links, forms, titles, canonicals, robots directives, schema, responsive behaviour and analytics. Compare the final URL map against the existing site. Launch is not the time to discover that a whole service section was omitted.

Measure after launch

Watch indexing, crawl errors, conversions and important landing pages after the change. Some fluctuation can occur, but missing redirects, accidental noindex tags or broken forms should be caught quickly.

Create a keep, improve, combine and remove inventory

For each important existing URL, decide whether the content should remain, be improved, merge into a stronger page or be retired. Record the reason. This turns the redesign into an editorial decision instead of a blanket replacement and provides the basis for the redirect map.

Protect conversion paths as carefully as rankings

An old website can have an unattractive form that still produces qualified enquiries. Record which calls to action visitors use, where forms appear and which landing pages contribute to conversions. A cleaner design can perform worse if it makes the next step harder to find.

Redesign launch checklist

Before switching, compare old and new URL inventories, test redirects, remove staging restrictions, verify canonicals, submit forms, check analytics, inspect mobile layouts and confirm the XML sitemap. After launch, monitor 404 errors, indexing and conversions rather than assuming deployment completed the project.

Redesign decision sequence

AuditURLs, traffic, content and conversions.
DecideKeep, improve, combine or remove.
MapNew structure and redirects.
ValidateTest before and after launch.

Frequently asked questions

Will a redesign hurt SEO?

A redesign can affect search visibility, especially when URLs, content or internal links change. Auditing the old site and planning redirects reduces avoidable risk.

Should every old page be kept?

No. Keep useful pages, improve weak ones, combine genuine overlap and retire material that no longer serves users. Removed URLs need an appropriate migration decision.

When should analytics be checked?

Review existing data before redesign decisions and verify tracking immediately after launch so performance can be compared.