Website redesign without guesswork: the SEO, content and launch checklist

A redesign does not begin with a mood board. It begins with a list of existing URLs and the value each one currently provides. Export the sitemap, internal links, Search Console data, analytics entry pages and meaningful backlinks. Add the content type, owner and a decision for every URL: keep, consolidate, replace or remove.

Rankings are not the only criterion. A low-traffic page may support a high-value sales conversation; a popular page may be outdated and provide no useful next step. Review search demand, commercial relevance, accuracy and the intended journey together.

When URLs change, Google recommends permanent server-side redirects such as 301 or 308. The destination should be meaningfully equivalent. Redirecting every old page to the home page is not useful to visitors and may be treated as a soft 404. Build an explicit old-to-new map and test every row automatically, with browser spot checks.

Avoid chains. If A used to redirect to B and B has been replaced by C, point A straight to C. Update internal links, canonicals, hreflang references and the sitemap to the final URLs. Google recommends keeping site-move redirects in place for at least a year.

Build a launch matrix rather than a loose list. Test content, metadata, forms, analytics, consent, keyboard access, responsive behaviour and performance for every page type. Critical paths—enquiry, purchase, application or booking—need real end-to-end tests on narrow screens and modest hardware, not only a designer’s desktop.

Explicit performance thresholds are more useful than intuition. Core Web Vitals classifies a good experience as LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less at the 75th percentile of real visits. Lab tests are valuable before launch; field data shows what people actually experience.

Immediately after rollout, re-check indexability, robots.txt, sitemap, canonicals and structured data. Watch server errors, 404 requests, redirect destinations and form events daily, then weekly. In Search Console, movements by page, query and indexing reason matter more than one daily total.

Keep the old crawl, redirect map and baseline metrics. When something changes, you can then distinguish a missing URL from broken analytics or shifting demand. A redesign is complete when the new system can be measured and operated—not when DNS changes.