How to audit Google Ads: check the lead journey first

A Google Ads account can show activity while the website fails to deliver an enquiry. Before changing bids or rewriting every ad, follow one important journey from the landing page to the business’s record of the lead. A success message is one piece of that journey; it is not proof of delivery.

This guide combines a practical audit worksheet with a source-level finding from our own lead-generation portfolio. The example documents website behaviour and controlled tests. It does not claim that we inspected a client’s advertising account, measured lost revenue or improved return on ad spend.

A real finding: the form said “submitted” without sending a request

During our October 18 portfolio review, the listing-claim form on our accessibility directory changed its screen to a submitted state without making a network request. A separate contact form also displayed success when a submission failed. Both behaviours could make the interface look successful without establishing that the business had received anything.

We changed the submission logic to use the directory’s registered form endpoint and show success only after an accepted HTTP response. We added controlled tests covering accepted responses, rejected requests and network failures for both forms. The submission checks passed within a ten-test directory test suite. These are source and test observations, not evidence of a completed production lead or an email reaching an inbox.

The marketing implication is a hypothesis to investigate: if an advertising conversion were triggered by that success display, the reporting could count an action that did not reach the business. We did not establish that such a Google Ads tag existed on these forms, and we have not assigned a number to lost leads. That boundary keeps a useful finding from becoming an invented performance case study.

Minutes 0–10: follow one conversion end to end

Pick the action that matters most: a completed enquiry, a booked appointment or a purchase. Write its definition before opening the reporting dashboard. For a lead, identify what counts as received, what makes it qualified and who checks the record.

1. Open the actual landing page and follow its main call to action.
2. Check required fields, errors and the confirmation message.
3. In an authorised test environment, confirm that the request is accepted and that the expected record is created.
4. Check what happens after a rejected request, a lost connection or a second click.
5. Record the separate evidence for the website event, advertising event and business receipt.

Use a designated test record and coordinate any production submission with the person receiving enquiries. Do not create real appointments, purchases or customer messages just to test a funnel. A server response, an analytics event and a qualified sales opportunity are different observations; the worksheet keeps them separate.

Minutes 10–20: inspect the goals the campaign uses

List the conversion actions used by the campaign, their source and their intended business meaning. Look for duplicate imports, page views labelled as leads, and actions that no longer match the current website. Treat these as checks, not assumptions that your account contains those problems.

Google distinguishes primary and secondary conversion actions. Primary actions normally support bidding when their standard goal is used by the campaign; secondary actions normally support observation. Custom goals are an important exception: included actions can be used for bidding regardless of that label. Check the campaign’s actual goals before changing anything. See Google’s explanation of primary and secondary conversion actions.

Save the current settings, the reason for any proposed change and the owner who will approve it. Do not make several measurement and bidding changes together simply to finish a checklist. If you cannot reconcile the conversion definition with the website and lead records, that is the first work order.

Minutes 20–30: compare search intent with the destination

Choose one campaign and review a manageable sample of its search terms, ads and landing pages over a defined period. Note whether the visitor’s question, the ad’s promise and the page’s next action agree. Check the actual service area and offer rather than assuming every click is suitable.

Record potential exclusions and copy changes for review. A term that looks irrelevant in isolation may serve a deliberate campaign purpose. Likewise, a low-volume period may not support a confident performance conclusion. Keep the original date range, spend and conversion definitions alongside each observation.

Turn the first pass into a work order

Download the Google Ads audit findings worksheet. It includes the form example as a clearly labelled source-review finding and blank rows for your own conversion and campaign checks. For each issue, record the observed behaviour, evidence, expected behaviour, owner and retest. Mark unverified steps as unverified.

Start with a broken or misleading customer journey, then validate measurement, then assess campaign changes. Thirty minutes is a useful triage window; it is not a complete account audit or a promise that every problem can be found that quickly. Close each repair with the same observation that exposed the problem, and assess business outcomes separately over an agreed reporting period.

If you need help, review our Google Ads service or request a scoped audit. Bring the campaign goal, landing-page URL, reporting window and access to the relevant lead records. We can then define the evidence needed before proposing changes.