Web design · development · redevelopmentStrategy before decoration
Redesign guide

A website redesign checklist that protects more than the appearance.

Redesigns should improve presentation without accidentally losing useful content, URLs, search signals or functionality.

Resource libraryAll GuidesPlanningRedesign ChecklistSEO ContentPerformance

Before rebuilding

  • Crawl or inventory the current URLs and identify pages receiving meaningful traffic or links.
  • Record current titles, canonical URLs, structured data and important internal links.
  • Test forms, navigation, mobile layouts and existing integrations.
  • Separate content worth preserving from duplication, outdated claims and genuinely obsolete material.

During architecture and design

Map every important old URL to a new destination before launch. Keep high-value URLs when the topic remains the same. Use redirects when a page has a clear replacement. Avoid sending every retired URL to the homepage.

Design reusable components for recurring content such as service summaries, FAQs, comparisons, calls to action and related resources. Consistency should reduce maintenance effort without making every page look identical.

Before launch

  • Check every internal link and navigation state.
  • Review page titles, descriptions, H1s and canonical tags.
  • Validate structured data where it is used.
  • Test forms and conversion paths on real mobile widths.
  • Check image dimensions, loading behaviour and obvious layout shifts.
  • Verify robots.txt, sitemap.xml, redirects and the custom 404 page.

Common redesign mistake

Replacing a mature website with a beautiful five-page site can be a downgrade if the old site contained dozens of useful service and resource pages. Simplify carefully, not blindly.

After launch

Watch for crawl errors, missing assets, redirect problems, unexpected indexation changes and user friction. A launch is a controlled transition, not the end of website work.

Document launch decisions.

Keep a simple record of redirects, retired pages, canonical changes, form destinations and hosting configuration. That makes later troubleshooting much easier if traffic, crawling or functionality changes unexpectedly.

Do a human review after the technical checks.

Automated validation will not tell you that two paragraphs contradict each other, a button label is confusing or a mobile menu feels awkward. Read and use the website as a customer would before calling the redesign complete.

Need a website with more substance behind the design?

Discuss Your Project