Start with the business outcome
Do not audit every page with the same weight.
Start with the outcomes the site should support:
- consultation requests
- demo or sales calls
- qualified contact form submissions
- pricing or cost-guide engagement
- resource downloads from the right audience
- newsletter or nurture signups when they support sales
- direct inquiries from referral, search, or outbound traffic
Then map those outcomes to the pages that influence them.
For most serious business websites, the highest-priority pages include the homepage, service pages, product pages, pricing or cost pages, case studies, comparison pages, resource pages, and contact paths. A blog post with low intent should not get the same attention as a service page that sits one click before a sales conversation.
Write the audit around decisions. Which pages should create qualified conversations? Which pages should help a buyer decide if the company fits? Which pages should support sales after a referral or outbound touch?
If the team cannot answer that, the redesign brief is not ready.
Check whether each key page has one clear job
A page should know what it is there to do.
For each high-intent page, write the job in one sentence:
| Page | Page job | Primary action |
|---|---|---|
| Homepage | Help the right buyer understand the offer and choose a next step | Book a consultation |
| Service page | Explain the problem, process, fit, and reason to talk | Request a project conversation |
| Cost guide | Help buyers understand budget logic and project shape | Discuss scope |
| Case study | Show how the team thinks and works | View related service or contact |
| Comparison page | Help buyers choose between two paths | Talk through the right fit |
If a page has five jobs, it has no real job. Buyers feel that. They scan, hesitate, and leave because the page asks them to assemble the argument themselves.
A redesign should reduce that burden. The page should lead the buyer from problem to context to decision. Not with pressure. With order.
Audit the offer above the fold
The first screen does not need to explain the entire company.
It needs to answer three questions fast:
- What do you do?
- Who is it for?
- Why should this buyer keep reading?
Vague hero sections weaken conversion before the page has a chance. Phrases like “digital solutions for modern brands” or “websites that drive growth” make the buyer work too hard. They sound interchangeable because they are interchangeable.
For Virdis-style custom web projects, the stronger opening names the actual offer: custom design and development, conversion-focused site structure, maintainable systems, clean CMS workflows, analytics, and launch discipline.
Run this test on each key page:
- Can a buyer name the service after five seconds?
- Can they tell whether the service fits their company?
- Can they see the next step without hunting?
- Can they tell why this approach differs from a template, theme, or generic agency build?
If the answer is no, design will not save the page. Fix the message first.
Review CTAs against buyer intent
Most CTA audits stop at button color. That is not the work.
Look at whether each CTA matches the buyer's stage.
A buyer on the homepage may need a clear primary action and a lower-friction secondary path. A buyer on a cost guide may be ready to discuss scope. A buyer reading a technical checklist may need proof that the team can handle implementation details.
Check each key page for:
- one primary CTA
- a secondary path only when it helps the buyer
- CTA language that says what happens next
- repeated CTA placement after meaningful sections
- mobile CTA visibility without crowding the screen
- no competing CTAs with equal weight
“Submit” is not a CTA. “Learn more” does weak work. “Book a consultation” works when the next step is a consultation. “Discuss a website project” works when the buyer wants to test fit before committing to a call.
The CTA should reduce uncertainty. If it creates another question, rewrite it.
Inspect forms like a buyer
Forms carry a lot of quiet damage.
A buyer may trust the company, like the offer, and decide to reach out. Then the form asks for too much, fails on mobile, loses the source data, or gives no clear confirmation after submission.
Test every important form by hand:
- Visit the page from a tagged URL.
- Read the form labels on desktop and mobile.
- Fill it out with realistic test data.
- Submit it once.
- Confirm the success message or thank-you state.
- Confirm the lead reaches the right system.
- Confirm the source, page, form name, and campaign data survive.
- Confirm the right person receives the notification.
The offer should set the form length. A high-ticket custom website project can ask for budget range, timeline, company, and project context. A newsletter signup should not.
The audit question is not “short or long?” The question is whether each field helps qualify the conversation or adds friction because nobody made a decision.
Check trust proof without inventing proof
Trust sections often fail in two ways.
Some sites bury their best proof where buyers never see it. Others pad the page with claims the company cannot support.
Audit the proof you can use:
- named services and process details
- real client logos only when approved
- real testimonials only when approved
- real case studies only when the team has verified the claims
- screenshots, diagrams, or implementation details when public
- founder or team expertise that buyers can evaluate
- clear explanation of how the project runs
Do not invent conversion lifts, traffic gains, rankings, or client outcomes. Buyers with serious budgets can smell fake certainty. So can lawyers, which is less poetic but more expensive.
If you do not have approved quantitative proof, use qualitative proof. Show how you think. Explain the decisions. Name the tradeoffs. Give the buyer enough substance to judge fit.
Review page structure for decision flow
A conversion audit should read the page like a buyer would.
For each important page, check whether the sections move in a useful order:
- Clear offer and audience fit.
- Problem context the buyer recognizes.
- What the service or product does.
- Why the approach works.
- Proof, process, or examples.
- What the buyer gets.
- Who it fits and who it does not fit.
- Next step.
Many websites scatter those pieces. The buyer gets a headline, a feature grid, a vague testimonial, a process section, then another feature grid. The page may look full, but it does not build a decision.
A custom redesign gives you a chance to fix the sequence. The design system should support the argument, not decorate a pile of sections.
Audit mobile paths before desktop polish
Your desktop page may look controlled in Figma. Your buyer may meet it on a phone between meetings.
Check the mobile path for each core page:
- the hero message fits without awkward line breaks
- the primary CTA appears near the start of the path
- sticky elements do not block content
- forms are easy to complete
- tables or comparison sections remain readable
- page speed does not collapse under scripts and media
- navigation helps buyers move to high-intent pages
Mobile conversion problems often hide inside spacing, tap targets, accordions, script weight, and forms. The site may pass a visual review and still feel tiring to use.
Do the audit on an actual phone. Not only responsive preview. Thumbs tell the truth faster than a 1440-pixel artboard.
Check analytics before you trust the numbers
A conversion audit needs measurement, but bad measurement can send the redesign in the wrong direction.
Before you use analytics as evidence, check the setup:
- GA4 belongs to the right property and production domain
- key events reflect real buyer actions
- forms, booking flows, and downloads send events once
- internal traffic does not dominate reporting
- UTMs survive redirects and form submissions
- CRM records capture the source, medium, campaign, landing page, and form
- thank-you pages or success states match actual submissions
If analytics cannot separate real leads from team testing, spam, or duplicate events, treat the numbers with caution. Use them as clues, not courtroom evidence.
A redesign should also improve the measurement layer. If the current site cannot tell the team which pages create qualified conversations, that is part of the conversion problem.
Look for maintenance friction
Conversion does not stop at launch.
The team will need to update pages, create new offers, add proof, adjust CTAs, publish resources, and test messaging. If the CMS or component system makes that hard, the site gets stale. Stale pages lose trust.
Audit the maintenance layer:
- Can the team update page content without breaking layout?
- Can editors manage SEO titles, descriptions, and social images?
- Can CTAs change without developer help for every page?
- Can proof sections stay approved and current?
- Can analytics events survive content edits?
- Can new pages reuse existing components with enough control?
This is where custom design and development matter. A good custom site does not hand marketing a blank canvas. It gives the team structured choices that protect the brand, the page flow, and the technical foundation.
If the current site cannot support the next year of changes, the redesign should fix the operating model, not only the front end.
Prioritize the findings
A conversion audit can produce a long list. Do not treat every item as equal.
Use four buckets:
| Priority | Meaning | Example |
|---|---|---|
| Critical | Blocks qualified leads or breaks measurement | Contact form fails, primary CTA unclear, source data missing |
| High | Creates serious buyer friction | Service page does not explain fit, mobile form is painful |
| Medium | Weakens trust or clarity | Proof section is thin, section order feels scattered |
| Low | Cosmetic or preference-based | Button style, minor spacing, nice-to-have animation |
This keeps the redesign focused. A team can waste weeks debating low-priority polish while the form still fails to send source data.
The audit should end with a short set of decisions:
- what the new site must fix
- what the team should keep
- what content needs rewriting
- what the design system must support
- what analytics and CRM connections need rebuilding
- what can wait until after launch
That list becomes the bridge between strategy and production.
The website conversion audit checklist
Use this before the redesign brief is final:
- Define the business outcomes the website should support.
- Identify the pages that influence qualified leads.
- Give each key page one clear job.
- Rewrite vague above-the-fold messaging.
- Match CTAs to buyer intent.
- Test every important form on desktop and mobile.
- Confirm lead routing, notifications, and CRM fields.
- Review proof for approval and accuracy.
- Remove unsupported claims.
- Reorder page sections around buyer decision flow.
- Test mobile paths on a real device.
- Check page speed, script weight, and interaction friction.
- Verify GA4 events and key actions.
- Confirm UTMs survive redirects and form submissions.
- Audit CMS fields, component rules, and editor workflows.
- Prioritize fixes by business impact.
- Turn the findings into redesign requirements.
Where Virdis uses this in a custom website project
Virdis uses conversion thinking before design direction hardens.
That means the audit shapes the site structure, content model, page templates, CTA system, analytics plan, and launch QA. The goal is not to bolt conversion language onto a finished design. The goal is to build a site that gives qualified buyers a clearer path and gives the team a cleaner system to maintain.
If you are planning a redesign, start with the friction. Find where buyers lose clarity, confidence, or momentum. Then design the new site around the fixes that matter.
A better website brief does not say, “make it modern.” It says what the site must help the business do next.
Frequently asked questions
What is a website conversion audit?
A website conversion audit reviews the pages, CTAs, forms, proof, analytics, and technical paths that affect whether qualified visitors take the right next step. It turns buyer friction into redesign requirements.
Should a conversion audit happen before or after a redesign?
Run the audit before the redesign. Post-launch testing still matters, but the audit should shape the strategy, site structure, copy, CMS model, analytics plan, and QA process before production starts.
What pages should a conversion audit include?
Start with high-intent pages: the homepage, service or product pages, pricing or cost guides, case studies, comparison pages, resource pages, and contact paths. Then add pages that sales or campaigns use.
Do you need conversion metrics to run the audit?
Metrics help, but you can still audit the site when analytics are incomplete. Use available data as clues, then inspect the buyer path, message clarity, form behavior, mobile experience, proof, and tracking setup by hand.
