How to measure local SEO leads without confusing rankings with revenue

Agree on what counts as a lead

A website visit is not a lead. A form submission may be spam, outside the service area, or for work the business does not perform. A booked consultation may still be unqualified. Define the stages before building a dashboard so the labels mean the same thing to the owner, marketing team, and person answering the phone.

Keep the model simple enough to use. For many small service businesses, six stages are enough to find the leak between being discovered and winning work.

• Discovered: the business appeared in a measurable search surface.
• Visited or acted: the person clicked, called, requested directions, or used another tracked action.
• Contacted: an inquiry reached the business.
• Qualified: the service, location, timing, and budget fit the business.
• Booked: the customer accepted an appointment, estimate, or project.
• Won: the business recorded the completed sale or agreed revenue.

Give each system one job

Google Search Console reports how pages performed in Google Search, including queries, impressions, clicks, and pages. Google Business Profile performance reports supported interactions with the profile. Website analytics describes configured on-site behavior. Call tracking, forms, scheduling, and the CRM cover the inquiry and sales stages.

No one report contains the entire customer journey. Build a shared monthly view from these sources while keeping the original definitions visible. When numbers do not reconcile, investigate the difference instead of silently choosing the larger one.

Primary sources: Google Search Console performance reports · Google Business Profile performance

Tag links before you need the history

A documented UTM convention can distinguish visits from a Google Business Profile website link or other owned campaign links. Use stable source, medium, and campaign names, then test the link and the analytics report. Changing capitalization or naming every month fragments the history.

Tagging does not identify every influence on a customer. Someone may discover the business in Maps, return through an organic result, and call later. Report what the systems observed and allow an “unknown” or “mixed” source when the record does not support a stronger claim.

Build the monthly review around decisions

Start with changes made during the period. Then review search and map visibility, profile and website actions, inquiry quality, booked work, and revenue where the client tracks it. Compare like-for-like periods when seasonality and calendar length matter.

The useful question is not whether every graph rose. Ask where qualified opportunities are being lost. A page may earn clicks but send the wrong callers. A profile may receive calls that go unanswered. A service may rank well outside the profitable travel area. Each finding points to a different fix.

• What changed on the profile, website, tracking, or offer?
• Which services and areas produced qualified inquiries?
• Where did people abandon the contact or booking path?
• Which conclusions are confirmed, and which are still hypotheses?
• What is the smallest next change that can be measured responsibly?

Protect customer information

Do not place names, email addresses, phone numbers, message content, or customer street addresses in analytics event names or properties. Use internal systems with appropriate access for customer records and send only the minimum non-identifying measurement needed to analytics platforms.

Public maps and case studies should aggregate lead locations to a useful area such as ZIP code, county, or service zone. Small samples may still identify a person, especially in rural areas or sensitive services, so leave them out when aggregation is not enough.