Tools
Website Audit Checklist: 25 Things to Check Before You Redesign
Before you redesign, audit what you have. 25-point website audit checklist covering strategy, content, UX, SEO, and tech to save months of rework.
Contents
Introduction
A redesign without an audit is just a reskin. You keep the same structural problems, wrap them in newer visuals, and wonder why conversion didn't move.
The job of a website audit before a redesign is to answer: What is working and must be preserved? What is failing and must be rethought? What are we completely missing?
At Designing Dots, we audit every site before we redesign it — even if the client says just make it look better. The audit is where we find the expensive disconnects between positioning, content, and user journey. Fix those first and design decisions become obvious.
Why most redesigns fail without an audit
Teams redesign because bounce rate is high, sales says the site doesn't convert, or the brand looks dated. Those are symptoms. The root causes usually live across five areas. This 25-point checklist covers them.
The 25-Point Website Audit Checklist
A. Strategy & Positioning (Points 1-5)
- ICP Clarity: Does the homepage speak to one primary ICP or three equally? If three, your hero is generic.
- Value Proposition Specificity: Can a first-time visitor complete This product helps [X] do [Y] without [Z] after 10 seconds?
- Category Fit: Do you help visitors understand what you are an alternative to? Notion vs. docs, for example.
- Message Match: Does the promise in your ads and LinkedIn posts match the headline they land on? Mismatch kills trust.
- Pricing Alignment: Is pricing findable, honest, and consistent with positioning? Hiding it when competitors show it is a positioning decision.
B. Content & Messaging (Points 6-11)
- Hero Copy: Is the H1 outcome-focused or feature-focused? Ship twice as fast beats The developer platform.
- Proof Proximity: How many scrolls before you show real proof (logos, metrics, case study)? If more than one, move it up.
- Product Story: Are product pages structured by user problem and outcome, not by internal feature hierarchy?
- Jargon Density: Count buzzwords in your above-the-fold. 3+ is too many.
- Content Depth: Do you have pages that answer the real buying questions: comparison, integration, security, migration, ROI?
- Voice Consistency: Read homepage, careers, and blog in sequence. Same voice? Different authors writing unchecked sites show up here.
C. User Experience & Information Architecture (Points 12-17)
- Navigation Logic: Can a new visitor categorize your product mentally from your nav labels alone? Avoid labels like Solutions without context.
- Task Completion: Pick 3 core tasks (e.g., book demo, see pricing, compare plans). Can users complete them in under 3 clicks from homepage without using search?
- Funnel Leaks: Where do users drop in GA, Mixpanel, PostHog? Check scroll depth and exit on pricing, demo, and product pages.
- Form Friction: Does your demo form ask for information you don't actually use to qualify? Every extra field drops conversion.
- Mobile Core Tasks: Complete your primary CTA on mobile with poor signal. Does it work, or does the menu cover the form?
- Empty & Error States: Search for no results, 404, newsletter unsubscribe success — do they maintain brand tone or feel broken?
At Designing Dots, we've seen sites lose 20% of demo requests because the calendar embed breaks on Safari mobile — only caught by testing real devices, not Figma prototypes.
D. SEO & Performance Foundation (Points 18-21)
- Index & Cannibalization: Search site:yourdomain.com + top keywords. Are multiple pages competing for the same term?
- Metadata Hygiene: Are title tags unique, under 60 chars, and intentionally written for click, not auto-filled?
- Page Speed Reality: Run PageSpeed Insights for top 5 pages on mobile. Look at LCP and CLS, not just overall score. A hero video that scores 95 but shifts layout is still a problem.
- Analytics Integrity: Are events firing correctly for primary conversions? Check for double-firing, missing UTM capture, and cookie banner blocking.
E. Technical & Operations (Points 22-25)
- CMS Scalability: Can a non-developer create a new product page, case study, and integration page from templates in under 30 minutes?
- Component Consistency: How many button styles, card styles, and header styles exist in production? More than 3 is a system failure.
- Accessibility Basics: Keyboard navigation, alt text on informative images, focus states, color contrast on CTAs. Don't ship a redesign that introduces new a11y violations.
- Handoff Debt: Is the current site documented? Where does content live, who owns deployment, and what breaks when marketing changes a page?
How to run the audit in a week
Day 1-2: Analytics + heatmaps + search data. Pull top 10 pages by traffic, top 5 exit pages, top 10 queries.
Day 3: Content review — hero, product, pricing, proof. Take screenshots, log copy verbatim.
Day 4: UX walkthrough — complete 3 tasks on desktop and mobile, record session.
Day 5: Tech + SEO sweep — speed, indexation, metadata, CMS template test.
Score each point: Green (keep), Yellow (refine), Red (rethink). Anything red in Strategy block means you need positioning work before visual design.
Why this matters for startups about to raise or relaunch
A website is your most scalable proof document. Investors, customers, and candidates all check it before saying yes. If it misrepresents your maturity, you attract the wrong leads and repel the right ones.
A pre-redesign audit prevents the most expensive mistake: redesigning around internal preferences instead of customer behavior. It gives your agency or in-house team evidence to prioritize.
Common mistakes
- Starting with inspiration boards. Moodboards before audit means you're choosing style before solving structure.
- Copying competitor navigation. Their IA may also be broken. Design from tasks, not from their sitemap.
- Preserving pages because they rank. A page that ranks but converts 0.2% and confuses positioning is not an asset; it's a trap. Redirect and consolidate.
- Ignoring post-launch governance. You audit once, redesign, and slip back in 6 months. Build templates and ownership into the redesign.
Designing Dots Approach / Framework: The Keep / Kill / Rewire Model
After the 25-point audit, we bucket everything into three:
Keep: High-performing, high-clarity assets that should not be touched beyond visual refresh.
Kill: Content that creates confusion, cannibalization, or low-intent traffic. Kill with redirects and notes.
Rewire: Right intent, wrong execution. These need restructure: new flow, new proof, new copy skeleton.
This model focuses redesign effort. Usually only 30% of pages are Rewire; 50% can be kept with system updates, and 20% should be killed. That is how you avoid a 6-month rebuild for a problem that needed 6 key pages.
Key Takeaways
- Don't redesign what you haven't diagnosed. 25 checks across strategy, content, UX, SEO, and tech give you the full picture.
- Strategy reds block everything — fix positioning before pushing pixels.
- Audit real behavior: device testing, task completion, and form analytics reveal more than heatmaps alone.
- Make decisions with Keep / Kill / Rewire to cut scope and increase impact.
- Build governance into the new site so drift doesn't return.
Next Steps / Internal Ecosystem
If you scored mostly yellow/red on Strategy and Content, pair this with the Brand Audit Checklist first. If UX and Tech dominated, jump to the Website UX Checklist for a deeper usability pass before writing your redesign brief.
Keep going with Website UX Checklist: How to Find Usability Problems Before Your Users Do and How to Audit Your Brand: A Complete Brand Audit Checklist — or put it into practice with DOTS UX before your next review.