If your website feels dated, underwhelming, or harder to trust than it should, a redesign can sound like the obvious answer. Sometimes it is. But many websites do not have a design problem first. They have a diagnosis problem.
A site can look old and still convert well. It can look modern and still confuse visitors, hide the next step, load badly, or disappear in search. If you pay for a redesign before checking what is actually broken, you risk rebuilding the same problems with nicer visuals.
This checklist is for that moment before the redesign quote, not after. It is a practical pre-redesign audit focused on four areas that usually determine whether a website is pulling its weight: message clarity, conversion path, technical trust, and search visibility.
Use it to identify whether you need a rebuild, a focused repair job, or simply better priorities. The logic is the same whether you audit manually or with software: find the constraint before you buy the solution.
Short answer
Before paying for a redesign, check whether the real issue is clarity, path, trust, or discoverability. Many problems that feel like design failures are actually copy, structure, performance, measurement, or search problems. For search snippets and AI answer systems, the useful answer should be visible, specific, and easy to extract from the page itself.[1][2]
| Pattern you find | What it usually means | First move |
|---|---|---|
| Visitors cannot understand the offer | Positioning is weak | Fix copy, proof, and page hierarchy first |
| Visitors understand but do not act | The conversion path is weak | Simplify CTAs, forms, and next steps |
| The site is slow, broken, or awkward | Technical trust is weak | Repair performance, mobile, errors, and accessibility |
| Important pages are hard to find in search | Visibility structure is weak | Fix titles, headings, indexability, and internal links |
How to use this checklist
Go through the 27 points page by page, starting with your homepage and top service or product pages. For each item, ask a blunt question: is this clearly helping performance, clearly hurting it, or unclear? If you cannot answer, that is already useful. It means you need evidence before you commit to a redesign.
The goal is not to produce a perfect score. The goal is to avoid paying to redesign symptoms while leaving the root cause untouched. Mark each section as pass, mixed, or fail, then look for the pattern before deciding what kind of work to fund.
Message and positioning checks
Pass/fail signal: a first-time visitor should be able to name what you do, who you help, the problem you solve, and the next step without reading the whole site. Fix messaging first when the offer is vague. Consider redesign work only when the page structure itself cannot support a clear offer, proof, and decision path.
1. Can a first-time visitor tell what you do in five seconds?
Your homepage should make the offer obvious without effort. If a stranger lands on the page and still has to decode your business, your problem may be message clarity, not layout.
2. Does the headline describe the outcome, not just the category?
“We build innovative solutions” says almost nothing. Strong homepage messaging tells people what you help with, who it is for, and why it matters now.
3. Is the site written for buyers rather than insiders?
Founders and teams often write from the inside out. Check for jargon, vague claims, and industry shorthand that makes sense internally but not to prospects.
4. Does each key page have one main job?
A service page should not also try to be an about page, a blog hub, and a feature dump. If pages are overloaded, conversion usually drops because attention gets split.
5. Is the ideal customer visible in the copy?
People need to feel the site is for them. If your copy never names the type of client, situation, problem, or buying context you serve best, relevance stays weak.
6. Are your differentiators specific?
Check for claims like “high quality,” “trusted,” or “tailored.” Those are too generic on their own. Strong differentiation is concrete: speed, process, specialty, scope, response time, experience, or business model.
7. Does the site answer the basic trust question: “Why should I believe you?”
Even strong messaging fails if it is unsupported. Look for proof close to the claims: examples, credentials, recognizable clients, case evidence, or clear process detail.
Conversion path checks
Common failure pattern: the site explains the business but does not make the next step feel natural. Fix this first when CTAs are inconsistent, forms are too heavy, or pages dead-end. Redesign becomes more relevant when the whole journey requires new page types, comparison sections, pricing context, or proof modules.
8. Is the primary call to action obvious on every important page?
If you want people to book, call, request a quote, or start an inquiry, that action should be visible without hunting. Hidden or inconsistent CTAs are often mistaken for a “design issue” when they are really a conversion-path issue.
9. Is there one primary next step, not five competing ones?
Too many calls to action create friction. Decide what matters most for a ready buyer and make that path dominant.
10. Do your calls to action match buyer intent?
“Contact us” is weaker than “Book a consultation” when the visitor is close to deciding. The CTA should fit the level of commitment you are asking for.
11. Is the path from homepage to inquiry short and logical?
Trace the route yourself. Can someone land on the homepage, understand the offer, review proof, and reach the form or booking step without detours?
12. Do service and product pages help people decide, not just browse?
Key pages should answer practical questions: what is included, who it is for, how it works, what happens next, and how to take action.
13. Is the contact or lead form proportionate to the value of the offer?
If you ask for too much too early, submissions drop. If you ask for too little, lead quality drops. Review form fields with intent in mind.
14. Are there dead ends on key pages?
Look for pages that explain something well but do not offer a next step. A page without a clear onward path wastes attention you already paid for.
15. Are trust elements placed near moments of hesitation?
Trust signals work best where visitors are likely to hesitate, such as near pricing context, forms, consultation requests, or unfamiliar claims.
Technical trust and quality checks
Audit signal: a site can pass a visual review while failing in real use. Check it on a phone, a slower connection, and a real browser with forms and navigation open. Fix targeted technical defects first; redesign is a stronger case when performance, templates, scripts, and mobile behavior are broken across the site.
16. Does the site load cleanly in a real browser?
Check real mobile and desktop pages against the Core Web Vitals thresholds: LCP under 2.5s, INP under 200ms, and CLS under 0.1.[7] Treat poor scores as diagnostic evidence, not an automatic rebuild verdict. For example, LCP above 4s on mobile may point to oversized hero images, slow hosting, render-blocking scripts, or template bloat; fix the specific bottleneck first unless the pattern is spread across the whole site architecture.
17. Are there broken links, failed requests, or obvious runtime errors?
A site can look fine on the surface while quietly throwing JavaScript errors, calling dead resources, or loading broken scripts. These problems affect trust, usability, and sometimes measurement.
18. Is mobile experience genuinely usable?
This is not about “responsive” in the technical sense. Check tap targets, sticky elements, menu behavior, form usability, image cropping, and whether key actions stay easy on a phone.
19. Are titles, headings, buttons, and forms internally consistent?
Inconsistent labels create friction. If one page says “Book a Call,” another says “Request a Quote,” and another says “Get Started,” users may not know whether those actions are different.
20. Does the site show basic trust hygiene?
Check for HTTPS, a functioning privacy policy, clear contact information, accurate business details, and no outdated notices that make the company feel neglected.
21. Are images helping credibility or hurting it?
Generic stock images, poor cropping, oversized files, and irrelevant visuals weaken trust fast. Before paying for a redesign, determine whether the real issue is simply weak visual proof.
22. Are performance and accessibility issues affecting real use?
Page speed scores are not the whole story, but slow pages, layout shifts, poor contrast, inaccessible buttons, and clumsy form states can absolutely suppress results. Google treats page experience as one part of helpful, usable web performance, so connect technical findings to actual user impact before deciding on scope.[3]
Search visibility checks
Pass/fail signal: important pages should be indexable, clearly titled, internally linked, and specific enough to earn useful snippets. Fix search structure first when pages are buried, duplicated, or vague. Redesign only becomes the priority when the templates prevent clean headings, metadata, content depth, or crawlable navigation.
23. Do important pages have unique title tags and meta descriptions?
If titles are duplicated, missing, or vague, search visibility usually suffers. Google’s guidance on title links and snippets makes this a basic but important quality check: titles should describe the page clearly, and meta descriptions should help explain why the result is useful.[4][5]
24. Is there a clean heading structure on each page?
Your H1 should describe the page clearly, and subheadings should support the page topic logically. Messy headings usually point to weak page structure overall.
25. Are canonical tags, indexability, and crawl signals sane?
Before assuming a redesign will improve SEO, confirm that important pages can actually be indexed correctly and are not fighting duplicates, odd canonicals, or accidental noindex issues.
26. Can search engines and users discover your important pages easily?
If key pages are buried, orphaned, or weakly linked, visibility drops. Internal linking is often a structural problem, not a visual one.
27. Is there enough evidence connecting traffic to business outcomes?
A site can have traffic and still underperform. Check whether you can see which pages attract search visits, which pages support conversions, and where drop-off happens. If you have GA4, Plausible, or Search Console data, bring that context into the audit. If you do not, be careful about approving a redesign based on instinct alone.
What your findings usually mean
Once you finish the checklist, the pattern matters more than any single item.
- If message and conversion issues dominate: fix positioning, page structure, proof, and calls to action before you redesign.
- If technical trust issues dominate: clean up errors, speed, mobile usability, and broken components before changing the look.
- If search visibility issues dominate: repair titles, headings, indexability, page discovery, and content structure before rebuilding templates.
- If problems are severe across all four areas: a redesign may be justified, but only after the diagnosis is clear enough to guide it.
This is why a pre-redesign audit is worth doing properly. Without one, redesign projects often get framed as visual refreshes when the real job is to fix a weak message, an unclear path, technical instability, or poor discoverability.
What to document before spending money
Before you approve any redesign proposal, make sure you can answer these questions in plain language:
- What is the website supposed to do for the business?
- Which pages matter most to that outcome?
- What is currently working well enough to preserve?
- What is clearly underperforming?
- What evidence supports that judgment?
- What should be fixed before design is discussed?
If those answers are fuzzy, the redesign brief will be fuzzy too. And fuzzy briefs create expensive projects with vague outcomes.
A redesign should be a response to a defined problem, not a substitute for diagnosis. Before you pay for new templates, branding tweaks, or a rebuilt homepage, make sure you know whether the actual issue is clarity, conversion path, technical trust, search visibility, or a mix of the four.
This 27-point checklist helps separate problems that need rebuilding from problems that need fixing. In many cases, a focused set of repairs will outperform a full redesign because it targets the real constraint instead of replacing everything at once.
CTA: Want a structured scan before you redesign?
If you want one pass that checks message, path, technical quality, and search-related signals together, use WebsiteAdvisor alongside this checklist. Review the evidence page by page before deciding whether to repair, redesign, or leave a page alone.
Sources
- Google Search Central, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search Central, AI features and Search visibility: https://developers.google.com/search/docs/appearance/ai-features
- Google Search Central, page experience guidance: https://developers.google.com/search/docs/appearance/page-experience
- Google Search Central, title links and snippets: https://developers.google.com/search/docs/appearance/title-link
- Google Search Central, meta descriptions and snippets: https://developers.google.com/search/docs/appearance/snippet
- Google Search Central, Article structured data: https://developers.google.com/search/docs/appearance/structured-data/article
- web.dev, Core Web Vitals thresholds: https://web.dev/articles/defining-core-web-vitals-thresholds?hl=en