A redesign is safest when it begins with an evidence-based inventory, not a visual mood board. Before changing the site, understand which pages attract useful visitors, what customers need to decide and what business process begins after they contact or buy.

1. Define the commercial reason for redesigning

  • Which audience or offer is unclear today?
  • Which action should increase: calls, consultations, orders or applications?
  • What would a better-qualified enquiry look like?
  • Which operating problem begins after the website converts?

“The site looks old” can be a valid concern, but it does not provide enough direction for deciding page architecture, proof or measurement.

2. Preserve existing search and content value

Export the current URLs, analytics, Search Console queries and inbound links. Mark which pages receive useful traffic, have external links or support customer decisions. Decide whether each URL will stay, improve, merge or redirect.

A redesign that deletes established URLs without a migration plan can discard years of visibility. Redirects should lead to the closest useful replacement—not automatically to the homepage.

3. Build the page architecture around customer decisions

  • A homepage that explains the category and primary value
  • Dedicated pages for commercially important services or products
  • Proof appropriate to the risk of the purchase
  • About information that makes the organization credible
  • A contact journey that gathers useful information without creating friction
Do not hide every service on one page.

Important offers usually need their own crawlable URL, complete explanation, proof, questions and conversion path.

4. Inventory the proof required

Collect case studies, customer quotes, certifications, project images, team expertise, process evidence and useful numbers. Obtain permission before publication and state the context behind any result. Anonymous or fabricated claims reduce trust rather than building it.

5. Confirm integrations and ownership

List forms, CRM, email, WhatsApp, booking, payments, inventory, analytics, advertising pixels and internal notifications. For each one, identify the owner, required access, expected behaviour and failure path.

6. Define launch acceptance criteria

  • Important pages return the correct status and canonical URL
  • Old valuable URLs redirect correctly
  • Unknown URLs return a useful 404 response
  • Forms and contact actions work on real devices
  • Search sitemap and robots rules are correct
  • Analytics records qualified actions
  • Performance and accessibility issues are reviewed
  • Backup, rollback and post-launch ownership are clear

7. Plan the first 90 days after launch

Launch is the beginning of evidence, not the end of the project. Review search indexing, queries, landing pages, conversion paths and the quality of enquiries. Fix operational failures first, then improve messaging and content using real behaviour.