Most website redesigns fail before a single pixel gets pushed. Not because the design is bad or the developer is incompetent, but because nobody defined what “success” looks like before the work started. No audit. No migration plan. No performance baseline. Just a vague brief that says “make it modern” and a launch date that keeps slipping.
After leading redesigns for enterprise companies, government agencies, and growth-stage startups, I've built a checklist that I run through on every single project. It's not glamorous. It's not a framework you can buy. It's a sequence of decisions and tasks that, when followed, prevent the two most common outcomes: a site that looks different but performs the same, or a launch that tanks your search rankings overnight.
Here's the full checklist, phase by phase.
Phase 1: Pre-Redesign (before you touch design)
This is the phase most teams skip entirely, and it's the one that determines whether everything after it succeeds or fails. You need to understand what you have before you decide what to build.
Define business goals
What should this website actually do? Generate leads? Reduce support tickets? Increase demo bookings by 30%? If you can't answer this in one sentence, you're not ready to redesign. Every design decision, every page, every CTA should trace back to a measurable business outcome. “We want it to look better” is not a goal — it's a symptom of not having one.
Audit current performance
Pull your analytics baseline: traffic by source, top landing pages, conversion rates, bounce rates, average session duration. Pull your SEO data: which keywords you rank for, your domain authority, your backlink profile. Pull your technical audit data: Core Web Vitals, page load times, crawl errors. This is your “before” snapshot. Without it, you have no way to measure whether the redesign actually improved anything.
Map current user journeys
Where do visitors enter your site? Where do they go next? Where do they drop off? Tools like Microsoft Clarity or Hotjar give you heatmaps and session recordings. You'll often find that visitors are doing things you never expected — clicking on elements that aren't links, ignoring your main CTA, rage-clicking on broken forms. This data tells you what to fix, not just what to redesign.
Inventory your content
Every page on your current site needs to be categorized: keep as-is, rewrite, merge, or cut. Most sites have significant content bloat — old blog posts that get zero traffic, duplicate service pages, landing pages from campaigns that ended two years ago. One client I worked with had 1,722 URLs that needed redirect mapping during their migration. That inventory work took days, but skipping it would have meant thousands of broken links and lost search equity post-launch.
Competitive review
Look at 3-5 direct competitors. What do they do better? Where are the gaps? Pay attention to their site structure, messaging clarity, page speed, and how they handle conversion paths. You're not copying — you're identifying the baseline your market expects and the opportunities they've missed.
Phase 2: Strategy & Architecture
With the audit data in hand, you can now make informed decisions about structure and approach instead of guessing.
Information architecture
Build your sitemap and navigation structure based on what the data tells you, not what your internal org chart looks like. I've seen enterprise sites with 60+ items in their navigation when competitors in the same space had 11. Visitors don't care about your internal departments — they care about solving their problem in the fewest clicks possible.
Wireframes for key pages
Before anyone opens Figma, sketch the layout of your 5-7 most important pages: homepage, primary service/product page, about, contact, and your top 2-3 landing pages by traffic. Wireframes force decisions about content hierarchy and conversion flow before visual design distracts from the structural questions.
Content plan
Who writes the copy? When is it due? Content is the single biggest bottleneck in every redesign project I've ever run. If you don't have a content plan with owners and deadlines, your launch date is fiction. Decide now whether you're writing in-house, hiring a copywriter, or having your design partner handle it — and budget accordingly.
SEO migration plan
If your current site has any search equity at all, you need a URL mapping document: every old URL matched to its new URL, with 301 redirects configured before launch. This is non-negotiable. I've seen companies lose 40-60% of their organic traffic after a redesign because nobody mapped the redirects. For that client with 1,722 URLs, we built a complete redirect map and verified every single one pre-launch. Their organic traffic held steady through the transition.
Platform decision
Webflow, Next.js, WordPress — the platform should follow the strategy, not lead it. If you need a marketing site with a CMS that your team can edit, Webflow is probably right. If you need custom application logic, portals, or maximum performance, Next.js makes more sense. If you're already on WordPress and it's working, sometimes the right move is a theme rebuild rather than a full platform migration. I cover the cost implications of each platform in my website redesign cost breakdown.
Phase 3: Design & Development
This is where most people think a redesign starts. In reality, it's step three of five. If you've done the first two phases well, this phase moves fast because the decisions are already made.
Design system and visual direction
Establish your typography, color palette, spacing scale, and component library before designing individual pages. A design system ensures consistency across every page and makes development significantly faster. It also means future pages and sections can be built without starting from scratch every time.
Mobile-first development
Over half of web traffic is mobile. Build for the smallest screen first, then scale up. This isn't just about responsive breakpoints — it's about content priority. What matters most on a 375px screen? That question forces better design decisions than starting with a 1440px canvas and trying to squeeze it down later.
Performance budgets
Set targets before development begins: total page weight under 1MB, Largest Contentful Paint under 2.5 seconds, Time to Interactive under 3.5 seconds. On a recent project for PCH, we optimized the build to achieve sub-1-second load times — but that was a target we set from day one, not something we tried to fix after launch. If performance isn't a requirement, it won't be a result.
Form and CTA implementation
Every form on the site should be tested end-to-end: submission, validation, error states, confirmation, and wherever the data lands (CRM, email, Slack notification). For the StratFusion rebuild, we designed the conversion paths around measurable lead quality — not just volume. The result was fewer but higher-quality submissions that the sales team could actually close.
Analytics and tracking setup
Configure analytics before launch, not after. Set up goal tracking, event tracking for key interactions (CTA clicks, form submissions, scroll depth), and connect to Google Search Console. If you wait until after launch to set this up, you lose your most valuable data — the first 30 days of user behavior on the new site.
Phase 4: Pre-Launch
The week before launch is where attention to detail separates professional work from amateur hour. This phase is tedious. It's also where you catch the things that would embarrass you in front of a client's customers.
QA across devices and browsers
Test on real devices, not just browser dev tools. Chrome, Safari, Firefox, Edge — on desktop, tablet, and mobile. Check every page, every form, every interactive element. On a recent audit, I found 14 distinct bugs and typos on a single site that had supposedly gone through QA. Broken links, misaligned elements, placeholder text that was never replaced. Every one of those is a credibility hit with visitors.
SEO verification
Check every page for: unique title tag and meta description, proper heading hierarchy (one H1 per page), image alt text, Open Graph tags for social sharing, canonical URLs, and structured data (schema markup). Verify your XML sitemap generates correctly and submit it to Google Search Console. Confirm every redirect from your migration plan resolves correctly.
Performance testing
Run Lighthouse audits on every key page. Target 90+ for Performance, Accessibility, Best Practices, and SEO. Test with real-world conditions — throttled CPU, slow 3G connection. A site that scores 100 on your MacBook Pro might score 45 on a mid-range Android phone on a cellular connection. That Android phone is what most of your visitors are using.
Content review
Read every single page out loud. You'll catch typos, awkward phrasing, and placeholder text that your eyes skip when scanning. Check for broken links, missing images, and inconsistent formatting. Have someone outside the project team do a fresh read — they'll catch things you've gone blind to after weeks of staring at the same pages.
Phase 5: Post-Launch
Launch is not the finish line. It's the starting line. The most valuable work happens in the 60 days after your site goes live, because now you have real data from real users.
Monitor search rankings for 60 days
It's normal to see fluctuations in your search rankings immediately after a redesign — Google is re-crawling and re-evaluating your site. If you did the redirect mapping correctly, rankings should stabilize within 2-4 weeks. If they don't, something in the migration went wrong and you need to diagnose it fast. Watch Google Search Console daily for the first two weeks, then weekly after that.
Set up behavioral analytics
Install Microsoft Clarity or Hotjar on day one. Session recordings and heatmaps will show you exactly how real visitors interact with the new design. You'll see where they hesitate, where they scroll past your CTA without clicking, and where they rage-click on something that isn't interactive. This data is gold for your first optimization cycle.
First optimization cycle at 30 days
At the 30-day mark, pull your analytics and compare against your pre-redesign baseline. What improved? What didn't? Make targeted adjustments based on data: move a CTA above the fold if nobody's seeing it, simplify a form if completion rates are low, rewrite a headline if bounce rate is high on a key landing page. Small, data-driven changes in the first month often have more impact than the redesign itself.
Ongoing: monthly performance review
Schedule a monthly review of traffic, conversions, page speed, and search rankings. Websites are not “set and forget” projects. The companies that get the most value from their redesign are the ones that treat their site as a living product — continuously tested, continuously improved, continuously aligned with business goals. Learn more about what ongoing website strategy and optimization looks like.
The checklist is the strategy
There's nothing revolutionary in this list. No proprietary methodology, no secret sauce. The value is in actually doing every step, in order, without skipping the ones that feel tedious. The content inventory. The redirect mapping. The cross-device QA. The post-launch monitoring.
Every redesign failure I've seen — the ones that tanked SEO, the ones that launched with broken forms, the ones that looked beautiful but didn't move the business needle — can be traced back to a skipped step on this checklist. The process is the competitive advantage, not the tools or the design trends.
If you're planning a redesign, run through this list before you talk to a single vendor. You'll walk into those conversations with clarity about what you need, realistic expectations about timeline and cost, and a framework for evaluating whether someone can actually deliver.
Want us to run this checklist on your site?
We follow this exact process with every client — from pre-redesign audit through post-launch optimization. Book a call to see where your site stands and what a redesign would look like for your business.