How to run a CRO audit on a B2B SaaS site that's below testing traffic.

What is a CRO audit, and how is it different from SEO?

A CRO audit (a conversion rate optimization audit) is a structured review of how users interact with your site on the way to its conversion goals: a demo request, a trial sign-up, a contact form, or a pricing inquiry. It combines quantitative data, which shows where users drop, with qualitative data, which explains why. The output is a ranked list of problems, each with the evidence behind it and a proposed fix.

SEO and CRO share the same visitors but work on different halves of the problem. SEO brings qualified visitors from search engines. CRO works on what happens after they land, so a larger share of the same traffic turns into pipeline. Getting the traffic is only half the battle; a site that ranks but doesn't convert still misses its targets.

On a B2B SaaS site, the audit usually covers a short list of page types: the home page, product or feature pages, the pricing page, the landing pages that receive paid or organic traffic, and the forms behind each call to action.

How much traffic does A/B testing need at your conversion rate?

More than most B2B SaaS pages get. The sample size an A/B test needs depends on two numbers: the page's current conversion rate and the smallest lift you want to detect. Low baseline rates and small lifts need far more visitors.

We computed these with the standard two-proportion formula. A test with two variants needs double the per-variant number, and the visitors have to reach the page being tested, not just the site. A pricing page with a 2% demo request rate needs about 42,200 visitors in total to detect a 20% lift. If that page gets 5,000 visitors a month, the test would run for more than eight months, and Google advises against running tests longer than necessary.

So below that level, the job of a CRO audit changes. Instead of producing a testing roadmap, it should find problems clear enough to fix directly, and save experiments for changes big enough to show up in the data.

How do you conduct a CRO audit, starting with your analytics data?

Start with the measurement itself. A CRO audit built on broken tracking ranks the wrong problems, so the first step of the CRO audit process is to check that your web analytics record the conversion objectives you care about.

1. Conversion goals are tracked as key events. Demo requests, trial sign-ups, and contact forms should each be a key event in Google Analytics. GA4 allows up to 30 key events, and marking an event as key isn't retroactive, so a missing key event means missing historical data.
2. Internal and existing-customer traffic is separated. Logged-in users heading to the app, job seekers on the careers page, and your own team inflate sessions and lower conversion rates.
3. Traffic is segmented by source. Paid, organic, referral, and AI assistant traffic convert at different rates.
4. The CRM agrees with analytics. Submit every form yourself first and check that each event fires once. Compare form submissions in analytics with leads created in the CRM for the same month. A large gap means one of the two is wrong.

Once the numbers hold up, gather quantitative data for each key page and record it as baseline data: sessions, conversion rate, the main traffic source, and user engagement metrics such as average engagement time, over the last 90 days. Read them next to the conversion metrics. That baseline is what later changes get compared against, and it shows which landing pages hold back the website's conversion rates most.

How do you run a conversion funnel analysis on a B2B SaaS site?

Define the conversion process as a sequence of steps along the customer journey and measure where users drop. In GA4, a funnel exploration lets you define up to 10 steps from events or page views and shows how many users complete each one. A closed funnel counts only users who enter at the first step; an open funnel lets users enter at any step, which suits B2B sites where people arrive on many different pages.

A typical B2B SaaS funnel has five steps:

1. Lands on a product, feature, or solution page.
2. Views the pricing page.
3. Starts the demo request or sign-up form.
4. Submits the form.
5. Books a meeting or activates the trial.

A large exit rate between the landing page and pricing may be normal for early-stage visitors, while a small drop between form start and form submit often points to friction you can remove: too many fields, an unclear next step, or a form error on mobile devices.

Break each step down by device and traffic source. A form that converts well on desktop and poorly on mobile is a usability issue, not a messaging issue. User intent matters too: a visitor from a comparison query needs different things than one from a brand query.

How do you find out why users drop off when you can't run tests?

With qualitative research. Analytics shows where users drop; it can't tell you why users abandon a form or where users struggle on a page. On a low-traffic site, analyzing user behavior through these methods carries most of the audit.

• User testing with real users. Ask five people who match your target audience to complete a task, such as finding the price for their team size and requesting a demo, while they think aloud. Nielsen Norman Group's research found that five users uncover about 85% of the usability problems in a design, and recommends several small rounds over one large test.
• Session recordings and heatmaps. Watch session recordings of visits that reached the form but didn't submit. This user behavior data shows where users click, which user interactions fail, and how far people scroll. Look for repeated clicks on things that aren't links, rage clicks on form fields, and users scrolling past the call to action.
• On-site surveys. A one-question survey on the pricing page ("What's stopping you from booking a demo today?") collects objections in the visitor's own words.
• Sales and support notes. The questions prospects ask on calls show what the site failed to answer. If every first call starts with "Do you integrate with our CRM?", that answer belongs on the product page.
• Customer feedback. Ask recent customers what nearly stopped them from buying and what convinced them.

Five sessions are enough to find usability issues, but not to measure anything. Nielsen Norman Group recommends more than 30 participants for quantitative usability studies, and 40 or more for narrow confidence intervals.

What does a CRO audit checklist cover at each conversion point?

Run the same checks on every key page and every conversion point so the findings are comparable. A comprehensive CRO audit reviews design and user experience, copy, and technical performance together. Each check needs evidence from the data above, not just an opinion.

This CRO audit checklist covers the usual conversion bottlenecks on a B2B site, where the key performance indicators are demo requests, qualified pipeline, and customer acquisition cost. Pages judged on ecommerce metrics like average order value need a different list.

How do you prioritize fixes when A/B testing isn't an option?

Your optimization efforts should go where they increase conversions most. Score each finding on three things: how many users it affects, how strong the evidence is, and how much effort the fix takes. A form error that breaks mobile submissions affects every mobile visitor, has clear evidence, and takes an hour to fix, so it goes first. A new homepage message affects everyone but rests on weaker evidence, so it needs more research or a test once traffic allows.

Then ship and measure with care:

1. Change one thing per page at a time. If you rewrite the headline and shorten the form in the same week, you won't know which one moved the conversion rate.
2. Compare like with like. Compare at least four weeks after the change with the four weeks before, by traffic source, and check for seasonality, campaigns, or pricing changes in the same period.
3. Treat the result as a signal, not proof. A before-and-after comparison can't separate the change from everything else that happened.

When a page does have the traffic for an A/B test, follow Google's guidance so the test doesn't hurt search: don't show search engines different content than users see, use rel=canonical on variant URLs that point to the original, use a 302 redirect for redirect tests, and end the test once you have a result.

A CRO audit isn't a one-time project. Repeat a thorough CRO audit after a redesign, a pricing change, or a shift in traffic sources, and review the funnel monthly in between to keep tracking the website's performance. Continuous improvement comes from that cycle, and from fixes that enhance user experience and customer satisfaction, more than from any single audit.

We offer growth work that includes conversion rate optimization for B2B and SaaS companies, so we have an interest in this topic. For how that fits with SEO and content, see our growth page.

Questions about CRO audits