Checklist
Website redesign checklist
Last updated:
What should you inventory before touching anything?
A redesign that starts with moodboards before an inventory is how businesses lose organic traffic. Before any design work begins, list every indexed URL, which pages actually earn enquiries or sales in analytics, and which pages have external links pointing to them. This becomes the URL map that governs everything after it.
Alongside the URL list, decide who owns content for each template — an unowned page usually ends up thin in the new build, which is a common self-inflicted ranking injury. If the current site has no analytics access or unclear ownership, resolving that comes before any visual work, not after.
How do you protect SEO during a redesign?
Three things matter more than anything visual: a one-to-one redirect map for every URL that changes, content parity on high-intent "money" pages (the offer, proof and calls to action carry over even if the layout changes), and a staging crawl before launch to catch broken links, missing titles and orphaned pages.
Redirect maps are deliverables, not a post-launch scramble — draft them alongside the new sitemap so nobody discovers a missing redirect the week after go-live. Canonical tags need checking too: a redesign that leaves stale canonical references pointing at old URL patterns quietly confuses indexing for months.
What should change versus what should stay the same?
Domain, core brand assets and analytics history should survive a redesign untouched. Structure — templates, navigation, information architecture — is what actually changes. Treating a redesign as "replace everything" usually means re-fighting battles (like why a particular page structure works for a particular audience) that were already settled the first time.
A full rebuild, a phased rollout, and a visual reskin carry very different risk profiles. A reskin that keeps the same URLs and information architecture is the lowest-risk path when the brand needs updating but the site structure still works. A full rebuild is higher-risk and usually only justified when the underlying CMS or stack is the actual problem, not the visual design.
How do you plan a safe cutover?
Cutover is the moment the new site goes live for a given set of URLs, and it should never be a surprise. A documented rollback plan — the way to restore the prior site if something critical breaks — is worth having even if it is never used. After launch, monitor 404s, crawl errors and ranking volatility for a defined window rather than assuming silence means success.
For revenue-generating or high-traffic sites, a phased cutover (moving one template or section at a time) reduces the blast radius of any single mistake compared with a big-bang launch of the entire site at once.
What does a realistic redesign timeline look like?
There is no honest fixed number that applies to every business — timeline depends on how many templates change, how much content needs rewriting, and how complex the redirect map is. What is consistent: ranking recovery after a well-executed redesign is measured in months, not days, and any programme that promises an exact recovery date is not being straight with you.
