The Ultimate Website Redesign Checklist (40 Points)

A poorly executed website redesign can destroy a business in 6 weeks. We've seen companies that lost most of their organic traffic overnight after a redesign that "looks more modern". Leads dropped. Revenue dropped. And recovery took 9-12 months.

A serious redesign, conversely, is a real growth opportunity. Better traffic, higher conversions, longer time on site, stronger brand. The difference between the two scenarios is not the budget. It's the discipline to follow a process that catches all risks.

This checklist is built from real lessons from 30+ redesigns we've done or audited. 40 concrete points organized in 4 phases. If you tick 35+, you're safe.

Phase 1: before starting (10 points)

1. Establish the measurable objective of the redesign

"We want it to look more modern" is not an objective. "We want to grow conversion rate from 1.2% to 2.5% in 6 months" is an objective. Without a measurable number, you can't evaluate whether the redesign succeeded.

2. Document the current state

Screenshots of all main pages. Export GA4 with traffic, conversion rate, bounce rate, pages per session for last 12 months. Export GSC with top ranking keywords, average CTR, impressions. Backup documents for important content. This gives you baseline for post-redesign comparison.

3. Identify top 20 pages by traffic and conversions

In GA4, sort pages by sessions and conversions. First 20 will have special attention: they must keep their URL, SEO structure, and be improved, not rewritten from scratch.

4. Document current backlinks

Ahrefs Webmaster Tools (free) or Moz Link Explorer (free tier). Export top 100 backlinks: which pages they go to, source site authority, anchor text. These pages must remain accessible (same URL or correct 301 redirect) to avoid losing link juice.

5. Audit existing content

Spreadsheet with all pages: URL, title, primary keyword, last update, traffic last 90 days, decision (keep/improve/remove). Pages with zero traffic and weak content can be deleted with noindex or redirect.

6. Set up GA4 + GSC for transition tracking

Goals in GA4 set identically before and after. GSC property kept (don't move to another). Annotations in GA4 marked at launch date.

7. Decide the technical stack

Stay (same CMS, just new design) or Switch (from WordPress to Next.js, from custom to Webflow)? Switch means URL change risk, different SEO behavior, double implementation time. Decide with a cool head.

8. Clear design brief for designer/agency

Complete brand book. Positive and negative inspirations with explanations. Target personas with clear needs. Tone of voice. Mandatory components (contact form, social proof, primary CTA buttons).

9. Realistic budget and timeline

Average redesign (15-25 pages): 8-16 weeks time, 18000-45000 RON total budget. Less = compromises on quality or iteration cycles.

10. Internal communication

Who approves? How many revisions included? Who provides new content? Who validates technically? Without clear roles, redesign goes into parallels and delays.

Phase 2: design and development (10 points)

11. Wireframes before visual design

Decide information architecture and user flow before discussing colors or fonts. Low-fidelity wireframes (Figma or hand-drawn) save weeks of unnecessary visual iteration.

12. Responsive design from start, mobile-first

In Romania, most traffic comes from phones in nearly every niche. Mobile-first designer builds for the hard case (small mobile) and escalates to desktop. Desktop-first designer misses details that appear only on mobile.

13. Reusable component library

Define 30-50 Figma components that then transform into code components. Buttons, cards, forms, modals, navigation. Visual consistency guaranteed.

14. Performance planned from design

Designer uses self-hosted fonts (max 2 families, max 4 weights). Images optimized WebP/AVIF from Figma source. Animations that can be disabled for `prefers-reduced-motion`. Hero without 3D if target performance is <2s LCP.

15. SEO-friendly URLs defined

For new pages: kebab-case, lowercase, under 60 characters, contain primary keyword. For existing pages with traffic: URL identical to old (don't "update" just because new structure seems more logical).

16. Schema markup planned

Organization, LocalBusiness (if applicable), Service (per service), Article (per blog post), BreadcrumbList, FAQPage (where appropriate). Implemented at build, not added post-launch.

17. Accessibility built-in

Contrast verified in Figma with plugin. Correct ARIA roles in components. Focus management on modals. Keyboard navigation tested. See our dedicated accessibility article for details.

18. Content migration planned

For blog with 100+ articles, automated (script that extracts from old base and imports into new base preserving URL, publish date, author, images). For static content, manual copy with fact-check.

19. Testing on staging

Staging environment with different URL (staging.domain.com), password-protected, blocked by robots.txt with Disallow: /. All tests done here, not on live.

20. Formal sign-off on design and content

Before full frontend development, signed design lock. Before launch, signed content lock. Changes after these moments cost extra and delay launch.

Phase 3: launch (10 points)

21. Complete pre-launch backup

Full backup of old site (code + DB + uploads) in an accessible location. If something goes wrong in the first 48h, you can return in 30 minutes.

22. 301 redirects for all changed URLs

Spreadsheet with mapping old URL → new URL. Implemented in .htaccess or Nginx config or next.config.js. Tested before launch with curl -I for each critical URL.

23. New sitemap.xml submitted in GSC

Immediately after launch. Old sitemap replaced, not kept in parallel.

24. Verified robots.txt

Don't accidentally block entire site with Disallow: / from staging. Verify first thing after launch.

25. Verified internal linking

Links to old URLs in content: updated to new URLs. Crawl with Screaming Frog (free up to 500 URLs) confirms.

26. Performance test on live

Lighthouse on homepage and top 5 pages. Target: Performance 85+, Accessibility 95+, SEO 100. Below these thresholds, fix before public communication.

27. Verified analytics

GA4 sends events correctly. Conversion tracking functional. Search Console doesn't report errors. UTMs on active campaigns work.

28. Email marketing and PPC pause or update

Links from email and PPC campaigns that led to old URLs: update to new or pause until verification. Otherwise users land on 404 right in the critical days post-launch.

29. Change communication to clients

Email to existing list with "we redid the site, here's what's new". Increases engagement and brings traffic in first days.

30. Aggressive monitoring 48h

Someone checking analytics, GSC, error logs every 4-6 hours in first 2 days. Problems caught in first 24h fix without traffic impact. Problems caught after 2 weeks cost months of recovery.

Phase 4: post-launch (10 points)

31. Week 1: metrics comparison vs baseline

Traffic in GA4: identical, higher, or declining? Bounce rate? Conversion rate? Instantly identify negative trends.

32. Week 1-2: monitor GSC for errors

Coverage report in GSC shows new problems: 404, soft 404, redirect chains. Immediate fix.

33. Week 2-4: ranking tracking

Positions on top 50 keywords tracked in Ahrefs or Ubersuggest. Fluctuations in first 2 weeks are normal, but consistent loss over 10 positions = serious problem.

34. Week 2-4: fix pages with low CTR

Pages with OK impressions but CTR under 2%: revise title and meta description.

35. Month 1-3: consistent new content

Minimum 4 new articles/month on blog. Google interprets "active site" and grants larger crawl budget.

36. Month 2-3: backlink reclamation

Check top 50 backlinks from pre-launch report. Still working? (Correct 301 redirect, not 404?) For those you lost accidentally, reach out to source site for update.

37. Month 3: first formal evaluation

Stakeholder meeting with metrics spreadsheet vs targets. What worked? What didn't? Action plan for month 4-6.

38. Month 3-6: A/B testing on critical elements

Headlines, CTAs, product layout. Free tool: Google Optimize (retired) → use VWO Free, Posthog Free, or custom implementation via GA4 experiments.

39. Month 6: full comparative audit

Vs pre-redesign baseline, vs launch. Traffic, conversions, ranking, CWV. Documented in written report.

40. Continuously: iterate based on data

A redesign is not "done" at launch. It's a starting point. Monthly iterations based on what analytics show make the difference between a mediocre and a transformative redesign.

Conclusion

A serious redesign is a 12-26 week project from decision to post-launch stabilization. With this checklist run disciplined, the risk of breaking what was already working drops dramatically, and chances of obtaining real improvements on metrics that matter (traffic, conversions, brand) grow.

At DCL we take clients through this process for every redesign we undertake. Rigorous documentation, planned redirect map, post-launch monitoring, data-based iterations. If you're planning a redesign in 2026, contact us for an evaluation of opportunities and risks specific to your business.