Website Redesign Checklist — Everything You Need to Plan

Signs It's Time for a Redesign

• Design feels dated. Visitors judge credibility in seconds. An obviously-2018 design costs leads you don't know about.
• Mobile experience is poor. Mobile-first indexing means mobile is the primary version. Bad mobile experience caps SEO.
• Slow load times. Core Web Vitals failing. Speed-only fixes have hit their ceiling.
• Hard to update content. Every content change requires developer involvement. Marketing velocity is constrained.
• Plugin maintenance overhead. WordPress sites with monthly maintenance bills approaching what a new build would cost.
• Conversion rates have plateaued. No structural changes have lifted CR in 12+ months.
• Business has outgrown current site. New services, new audiences, new positioning need new architecture.

If three or more apply, redesign is probably the right move. One or two: optimisation usually beats redesign.

Pre-Redesign SEO Audit (What to Preserve)

The most-skipped step in most redesigns — and the source of the "we redesigned and our traffic crashed" stories. Before touching design, document:

• Every URL currently indexed (Search Console + crawl)
• Top 100 pages by organic traffic
• Top 100 pages by backlinks
• Keywords currently ranking and their landing pages
• Existing meta titles, descriptions, H1s, schema markup
• Internal linking structure
• Existing redirects (don't accidentally remove these in the migration)

The output: a baseline document that becomes the SEO preservation plan. Every URL gets mapped to a destination URL in the new site (same URL, redirected URL, or merged URL). Every high-value page keeps its meta data unless there's a deliberate reason to change.

Content Audit and Migration Plan

Decide before redesign starts: what content moves, what gets rewritten, what gets deleted.

• Move as-is: Strong-performing pages with current content.
• Refresh and move: Decent content needing updates. Most content falls here.
• Rewrite: Outdated or off-brand content worth rewriting in the new structure.
• Consolidate: Multiple thin pages merging into one stronger page.
• Delete and redirect: Content that should be gone. Redirect to closest relevant alternative.

Without this plan, content migration becomes a panic at the end of the project. With it, the redesign is also a content audit.

Design Goals — What Do You Actually Want to Achieve?

"It looks dated" isn't a design goal. Specific goals that drive design decisions:

• Increase conversion rate from organic traffic by X%
• Reduce bounce rate on key landing pages
• Improve mobile conversion (specific pages, specific actions)
• Communicate new positioning or new market segment
• Support new pricing tier or new product line
• Reduce visual complexity / cognitive load
• Improve accessibility (WCAG compliance)

Every design decision should ladder up to a goal. "I want it to feel more modern" without a tied conversion goal is taste, not strategy.

Technical Requirements Checklist

• Tech stack decision (Astro, Webflow, WordPress, custom) with reasoning
• Hosting platform and SSL setup
• Analytics setup (GA4, Tag Manager, Search Console)
• Conversion tracking setup (form submissions, calls, bookings)
• CRM integration if applicable
• Email platform integration if applicable
• Booking/scheduling tool if applicable
• Schema markup plan (Organization, LocalBusiness, Service, Article, FAQPage)
• Sitemap and robots.txt configuration
• Performance budget (target Core Web Vitals scores)
• Accessibility requirements (WCAG 2.1 AA minimum)

Launch Day Checklist

The hour-by-hour launch checklist:

• 301 redirect map fully implemented and tested
• Search Console: submit new sitemap, fetch and render key pages
• Verify no robots.txt blocking
• Verify no noindex tags accidentally left on production pages
• Verify SSL working across all pages
• Test forms (contact, lead gen, booking) end-to-end
• Test analytics tracking firing correctly
• Test conversion tracking firing correctly
• Test on multiple browsers and mobile devices
• Notify stakeholders, send announcement, update social bios

For broader technical SEO context during launch see our technical SEO guide.

Post-Launch Monitoring

The first 30 days post-launch are critical. Monitor:

• 404 errors. Check Search Console daily. Any 404s for indexed URLs need immediate redirects.
• Indexation. Pages getting indexed properly? Compare new sitemap submission to indexed count.
• Crawl errors. Search Console crawl stats. Sudden spikes mean technical problems.
• Rankings. Track key commercial keywords daily. Some short-term volatility is normal; sustained drops need investigation.
• Organic traffic. Watch for sustained declines vs pre-launch baseline.
• Core Web Vitals. Real-world performance should be at or above pre-launch.
• Conversions. Lead/sale volume by source. Big drops mean tracking issues or UX problems.

Most well-executed migrations show a 2–4 week dip followed by ranking recovery to or above pre-launch. Sustained drops at 6 weeks indicate technical issues that should have been caught earlier. For the broader redesign context see our web design Melbourne service.