Landing pages · 9 min read
A Landing Page Audit That Starts Before the Page
Audit the ad, landing page, form, and follow-up as one journey. Identify message gaps, mobile friction, tracking errors, and lead-quality problems.
When paid traffic is not turning into qualified leads, the landing page is the usual suspect. Sometimes rightly. But a page can look fine in a design review and still fail, because the problem is in the ad that sent the visitor, the form that did not deliver, or the follow-up that never happened. Other times the page really is the constraint, and the team spends a month changing ads instead.
A useful landing page audit treats the page as the middle of a journey: ad, page, action, and what the business does with the lead. This guide walks through that journey in order, then shows how to prioritize what you find and decide whether you need a repair, a test or a rebuild.
You can run most of it yourself in an afternoon with a phone, the ad account, and access to wherever leads end up.
Define the action and the visitor before scoring the page
Qualified action versus submission volume
Start by writing down the one action the page exists to produce: a booked consult, a tour request, a call, a quote request. Then write down what makes that action qualified for your business. A page that produces more submissions from people you cannot serve is not performing better. It is costing your sales or front-desk team time.
If you cannot say how many of last month’s submissions became qualified opportunities, that is the first finding. The page cannot be judged on a number nobody has.
Segment by campaign and intent, without slicing the data into noise
Different campaigns send different people. Someone who searched for a specific service near them arrives with a clearer intent than someone who saw a video in their feed. Review the page’s performance separately for its main traffic sources if volume allows. If each segment only has a handful of conversions, combine them and say so: small samples can make an ordinary page look broken or brilliant.
Check the promise that earned the click
Open the two or three ads that send the most spend to the page. Then open the page beside them and compare:
- Offer. If the ad says “free consultation,” does the page say the same thing, or does it introduce a deposit, a waitlist or a different offer?
- Language. Does the headline answer the question the ad raised, in similar terms?
- Imagery. If the ad shows the actual location, product or person, does the page?
- Eligibility. Does the page make clear who the service is for, where it is available and any requirements, so people who cannot proceed self-select out?
- Next step. Does the ad’s call to action match the page’s? “Book a tour” in the ad and “Request information” on the page is a mismatch.
Most published landing page checklists include message match at the headline level, and they are right to (Instapage checklist, May 2026; SiteTuners audit guide, March 2026). The point here is to check the whole promise, not just the headline. A visitor who was promised one thing and asked for another rarely tells you why they left.
Inspect the mobile decision path
Most paid social traffic and a large share of search traffic arrive on phones. Audit on a phone first, on a cellular connection, not on office Wi-Fi.
First-screen clarity and access to contact
Without scrolling, can a visitor tell what this is, whether it is for them, and what to do next? Where phone calls matter, is the number visible and tappable? If the action is a booking, is the booking path one tap away?
Readability, speed, form completion and accessibility
- Speed. Time the load. Google’s Core Web Vitals give useful reference points: the main content should appear within about 2.5 seconds, the page should respond to taps within about 200 milliseconds, and the layout should not jump around as it loads (web.dev, Web Vitals). Use these as diagnostics, not as a score to chase for its own sake.
- Forms. Fill in the form with your thumb. Check error messages, field types (does a phone field bring up the number keypad?), and whether anything forces you to start over.
- Fields. Ask only what you need to respond and qualify. Every field should have a reason. Sometimes that reason is a useful qualifying question, and keeping it is the right call.
- Accessibility. Check that text is readable, buttons are large enough to tap, form fields have labels, images that carry meaning have text alternatives, and the page can be used with a keyboard. The W3C’s WCAG 2.2 is the reference standard. An accessible page is usually an easier page for everyone.
Required privacy, safety and policy information is not optional clutter
Removing distractions is good practice. But some content must stay: privacy notices, required disclosures, terms of an offer, safety information in regulated categories, and accessible ways to contact the business. A page that converts better because it hid something a visitor needed to know is a problem waiting to surface. If you are unsure whether an element is required, ask whoever owns compliance before removing it.
Test the conversion rather than assume it works
This is the step most design-focused audits skip, and it is often where the biggest finding is.
Submission, confirmation, notification and CRM entry
Submit a real test inquiry, clearly labeled as a test, through every form on the page. Then check:
- Did the confirmation message or page appear?
- Did the right person or inbox receive a notification, and how quickly?
- Did the inquiry appear in the CRM or booking system, with the source recorded?
- Did the ad platforms record exactly one conversion for it?
Calls, duplicate events and consent
If calls matter, call the number shown on the page from a phone. Does it ring the right place during business hours? What happens after hours? If you use call tracking, does the call appear in the tracking report with the right source? Our earlier article on call tracking covers this in more depth.
Check whether the conversion fires once per real action. A conversion that fires when the thank-you page loads can double-count refreshes. Also check how your page behaves when a visitor declines cookies: some tracking will not fire, which is expected, but forms and calls must still work.
Follow the lead into the business
A page can generate qualified inquiries that the business then loses. Before redesigning anything, look at what happens next:
- Response time. How long does a new inquiry wait before someone responds?
- Qualification. Who decides whether a lead is qualified, and is that recorded?
- Booking completion. Of the people who requested a consult or tour, how many actually booked and attended?
If inquiries are healthy but bookings are not, the fix may be in staffing, scheduling or scripts rather than on the page. That is still a useful audit finding, even if it is not the one you expected.
Prioritize observations, not aesthetic preferences
An audit produces a list. The hard part is deciding what to do first. Score each finding on five things, and write them down:
| Field | Question it answers |
|---|---|
| Evidence | What did we actually observe, and where? |
| Suspected effect | What is this likely costing, and how confident are we? |
| Effort | How much work is the fix, and who has to be involved? |
| Owner | Who will make the change? |
| Validation | How will we know it worked? |
Here is how that looks for a set of hypothetical findings (not from a client account):
| Finding | Evidence | Confidence | Effort | Owner | Do first? |
|---|---|---|---|---|---|
| Form submissions not reaching CRM for one service line | Test submission never arrived; routing rule missing | High | Low | Web developer | Yes: broken path |
| Phone number not visible on mobile without scrolling | Phone test on two devices | High | Low | Web developer | Yes |
| Ad promises same-week appointments; page says “contact us for availability” | Side-by-side review of top ad and page | Medium | Low | Media buyer and copywriter | Yes |
| Main image is generic stock rather than the real location | Visual review | Low | Medium (needs a shoot) | Production | Test later |
| Page uses brand colors the founder dislikes | Stakeholder feedback | None (preference) | Low | n/a | No |
Broken paths and outright mismatches come first because the evidence is strong and the fixes are small. Ideas that might improve conversion go into a test backlog. Preferences go nowhere until there is evidence.
What a landing page audit cannot tell you
An audit is a structured inspection, not an experiment. It is good at finding broken paths, mismatches and friction. It is weaker at predicting how much any single change will move results, for three reasons.
First, a before-and-after comparison is not proof. If you fix the form and conversions rise the following month, the fix may be the reason, or the season, a budget change or a new ad may have contributed. When several things change at once, no single change can be credited with the result.
Second, better tracking can look like better performance. If the audit finds that calls or form submissions were not being recorded and you fix that, reported conversions will rise even if the number of real inquiries has not. That is a measurement improvement, which is valuable, but it is not new demand. Keep the two separate in your reporting.
Third, the page may not be the constraint. If the audit finds a fast, clear, well-matched page that delivers every inquiry correctly, and results are still weak, the problem is more likely the audience, the offer, the price or the follow-up. Saying so is a legitimate audit outcome, and it saves you from redesigning a page that was doing its job.
Know whether you need a repair, a test or a rebuild
Not every weak page needs to be rebuilt. Use the evidence to choose:
- Repair when something is broken or plainly mismatched: a form that does not deliver, a hidden phone number, an offer that contradicts the ad. Fix it now; no test needed.
- Test when you have a reasonable hypothesis but not certainty: a different headline, real photography instead of stock, a shorter form. Change one meaningful thing, run it against the current version long enough to see a difference in qualified actions, and keep the winner.
- Rebuild when the page was designed for a different job (a general about page receiving campaign traffic is a common example), when it cannot be edited quickly enough to keep up with campaigns, or when repairs keep failing because the underlying structure is wrong.
A full redesign is the most expensive option and the hardest to learn from, because so much changes at once. Choose it when the evidence supports it, not as a default.
A quick self-check
If you only have twenty minutes, do this:
- Open your highest-spend ad and its landing page side by side on your phone.
- Write down the ad’s promise and check the page keeps it.
- Time the load on cellular.
- Find the phone number or booking button without scrolling.
- Submit a test inquiry and confirm it reaches the CRM.
- Call the number shown.
- Ask whoever handles inquiries how quickly they respond and how many last month were qualified.
You will likely find at least one thing worth fixing before you touch the design.
If the problem you find involves the ad promise, the creative or the tracking as well as the page, our Marketing Audit reviews all of them together and leaves you with a written plan.