CRO Audit: What It Is, How to Run One, and What It Costs

Most conversion problems go undiagnosed. A CRO audit finds which of the twenty things that could be wrong, are the two actually costing you money.

Without a diagnosis, teams fix whatever the loudest person in the room believes is broken. A stopped clock is right twice a day, so sometimes that works. Usually, it produces a lot of activity with very little progress, resulting in another quarter of small changes and a conversion rate that has not moved.

What a CRO audit actually is

A CRO audit is a structured review of your conversion path that identifies where qualified visitors drop out, ranks those problems by expected impact, and produces a testing roadmap you can act on.

Three things separate an audit from a general site review:

It is scoped to conversion, not quality. An audit does not tell you whether your site is good. It tells you where it is losing people who were ready to buy. Those are different questions and they produce different recommendations.

It is evidence-led. Every finding traces to something observable: analytics, session behavior, form drop-off, page performance, or a specific comparison against competitors. “The hero could be stronger” is an opinion. “62% of mobile visitors never scroll past the hero, and the only CTA sits below it” is a finding.

It ends in a ranked list. An audit that surfaces thirty problems without telling you which three to do first has moved the work sideways. Prioritization is the deliverable, not the findings.

What a CRO audit covers

A complete audit works through the conversion path in layers, from the traffic entering the site to the form that produces pipeline.

Analytics and measurement integrity. Before anything else, confirm the data is trustworthy. Misconfigured conversion tracking, missing events, and unfiltered internal traffic will produce a confident audit built on nothing. If GA4 is not set up correctly, fix that first.

Conversion path mapping. The actual route visitors take from entry to conversion, not the one the sitemap implies. This is where most audits find their biggest single opportunity, because the assumed path and the real path are rarely the same.

High-intent page review. The pages closest to the decision get the most scrutiny: contact, demo request, and pricing. A weak blog post costs you a reader. A weak demo page costs you a qualified meeting.

Friction inventory. Form length and field-level abandonment, competing links on conversion pages, unclear or duplicated CTAs, and anything that adds a step between intent and action.

Messaging and clarity. Whether a visitor can tell who the product is for and what it does within the first few seconds, and whether the page matches the promise that brought them there. Message match matters most on paid traffic, where the ad sets an explicit expectation.

Trust placement. Not whether you have proof, but whether it sits near the ask. Logos three sections below the form are not doing conversion work.

Performance. Core Web Vitals interpreted in terms of conversion impact rather than as a score. Load time is a conversion problem before it is a technical one.

Competitive benchmark. The same rubric applied to two or three competitors, so you know whether a weakness is a real gap or an industry norm.

How to run a CRO audit

The sequence matters more than the checklist. Working in this order stops you from optimizing pages that turn out not to be the problem.

1. Verify the data before you trust it. Confirm conversion tracking fires correctly, internal traffic is excluded, and your primary conversion event is defined the way you think it is. Skipping this step invalidates everything downstream.

2. Establish the baseline. Pull at least three months of conversion rate by page, by traffic source, and by device. You need to know what normal looks like before you can identify what is broken.

3. Map the real conversion path. Trace the most common routes from entry to conversion event. Note the entry pages, the intermediate steps, and the exits.

4. Find the largest drop-off. One step in that path is losing more qualified people than any other. That is the constraint. Fixing anything else first produces smaller returns for the same effort. The full diagnostic framework is here.

5. Diagnose the cause, not the symptom. A low form completion rate is a symptom. The cause might be form length, a trust gap, a mismatch with the ad that drove the click, or a mobile layout that hides the submit button. The fix depends entirely on which.

6. Rank every hypothesis. Score each proposed change on expected impact, your confidence in it, and the effort required. ICE scoring is the simplest version that works. Without ranking, teams default to the easiest change rather than the most valuable one.

7. Split the roadmap by horizon. Quick wins you can ship in 30 days, strategic bets that need 60 to 90. Both matter. Only shipping quick wins produces a plateau.

8. Test, do not just ship. Where traffic supports it, run the change as a test so you learn something either way. One test is not A/B testing. The value compounds across rounds.

CRO audit vs UX audit vs SEO audit

These get used interchangeably and they answer different questions.

A UX audit asks whether the site is usable. It covers navigation, task completion, accessibility, and interaction patterns. A site can pass a UX audit comfortably and still fail to convert, because usable is not the same as persuasive.

An SEO audit asks whether the site can be found. Crawlability, site structure, indexation, keyword coverage. It is concerned with getting people to the site, not with what happens once they arrive.

A CRO audit asks whether the site converts the traffic it already has. It borrows from both, since usability problems and load times affect conversion, but its organizing question is revenue. The longer comparison is here.

If you are running paid acquisition and your conversion rate is flat, the CRO audit is the one that pays for itself first. More traffic into a leaking funnel costs more than it returns.

What a CRO audit costs

Pricing varies more than it should, largely because scope varies.

Agency engagements typically run $5,000 to $15,000 and up, take three to six weeks, and often arrive attached to a proposal for the implementation retainer. The audit is sometimes the sales instrument rather than the product.

Freelance audits range from a few hundred dollars to several thousand. The variance in quality is wide. The risk is a report assembled from generic best practices rather than your actual data.

Automated tools cost very little and produce a list of flags with no prioritization and no understanding of your buyer. Useful as an input. Not a diagnosis.

Fixed-scope senior audits sit in between. The web experience audit is $3,500, delivered in five business days, with a fixed deliverable and no retainer attached. That is the version of this work I sell, and the pricing is on the page.

The number worth calculating is not the cost but the cost of not knowing. If you are spending $50,000 a month on acquisition and the site converts at 2% when it could convert at 3%, the audit is not an expense. The business case math is here.

What this looks like when it works

At Tableau, where I was Director of Digital Strategy at Salesforce, the contact page had accumulated years of additions from every team that wanted a link on it. Conversion was flat, with no decline to point to. The behavioral data showed visitors looping: clicking a support link, landing elsewhere, coming back.

The diagnosis was that the page no longer had one job. The fix was subtraction. Three months of iterative testing on that direction lifted contact form conversions 61%, which Tableau’s own historical data put at $6.9M in annualized pipeline. The full case study is here.

Nothing about that finding required a redesign. It required looking at the data before forming an opinion.

What you’ll find here

• How to Diagnose Why Your B2B Website Isn’t Converting - The six-part framework for finding the actual constraint before you change anything.
• ICE Scoring for Website Experiments - How to rank a backlog of hypotheses so you work on the valuable ones first.
• Conversion Audit vs UX Audit - Which one you need, and what each will and will not tell you.
• How to Prepare for a Website Audit - What to gather beforehand so the audit produces findings instead of questions.
• The Business Case for a Website Audit - How to justify the spend to someone who controls the budget.

Takeaway

A CRO audit is a diagnosis, not a report card. The process is always the same: verify the data, map the real path, find the largest drop-off, diagnose the cause rather than the symptom, and rank the fixes before touching anything.

The companies that get good at this treat it as an ongoing discipline. The ones that do not keep redesigning, and keep landing in the same place.

If you want this run on your site, the web experience audit is the fixed-scope version: $3,500, five business days, ranked roadmap, no retainer.

FAQ

Common questions