WEB / REDESIGN

Website redesign checklist: protect what works while improving what does not.

A redesign changes more than appearance. Pages, URLs, navigation, forms, tracking, accessibility, speed and search signals can all move together. The launch plan needs an inventory and acceptance tests.

Before Design Begins

Capture the current site before deciding what to replace. Inventory indexable URLs, top landing pages, conversions, forms, integrations, analytics, legal content and assets. Interview the people who answer sales and support questions: their repeated questions often reveal the missing information.

Keep or change?Decision evidence
Page and URLSearch demand, inbound links, traffic, conversions, current accuracy and a destination if removed.
NavigationPriority user tasks, service structure and whether labels are understood without internal jargon.
ContentAccuracy, usefulness, proof, ownership and the decision it helps a visitor make.
Visual componentPurpose, accessibility, responsive behaviour and maintenance cost.
IntegrationBusiness owner, data flow, failure alert and test case.

Redesign and Build Checklist

  1. Set measurable goals. Define the important journeys and conversions, plus what must not regress.
  2. Map the information architecture. Give distinct user intents distinct pages and keep labels concise.
  3. Create the redirect map early. Assign every changed or removed indexable URL to the most relevant live destination.
  4. Write real content before final layout. Design with genuine headings, proof, objections and calls to action rather than placeholder copy.
  5. Build responsive and accessible states. Include keyboard focus, readable contrast, form labels, errors, reduced motion and usable small-screen layouts.
  6. Preserve measurement. Map analytics and advertising events to the new forms, calls and journeys.
  7. Test a staging release. Crawl links, check titles and canonicals, submit forms, inspect devices and test performance.
  8. Launch with a verification list. Check DNS/SSL, redirects, robots, sitemap, analytics, conversions and high-value pages immediately.

The First Days After Launch

Watch server errors, redirect misses, form submissions, analytics events and real user feedback. Compare key journeys with the pre-launch baseline. Fix breakage before expanding the scope into new features.

A redirect is not a filing cabinet.

Map an old URL to a genuinely relevant replacement. Sending every removed page to the homepage hides gaps and creates a poor visitor experience.

Redesign Mistakes to Avoid

  • Deleting the existing URL inventory before the redirect map is complete.
  • Approving visual mockups with placeholder content.
  • Rebuilding every feature without checking whether anyone uses it.
  • Launching forms without success, error and notification tests.
  • Judging speed from one desktop lab run.
  • Changing domain, platform, content and information architecture without a rollback plan.

Sources and Further Reading

Platform requirements and recommended practices change. These primary sources were checked when this guide was reviewed.

NEED IMPLEMENTATION HELP?

Turn the checklist into a controlled delivery plan.

Share the current system, constraints and required outcome. We will identify the next useful step and explain the evidence needed.

Web Design & Development Start the diagnosis