Entrepreneur Resources Your source for small business information
A service business can gain search visibility and still receive the wrong enquiries. It can also receive a useful enquiry from someone whose path cannot be reconstructed. A weekly local-search report should make those situations understandable, rather than compressing them into a single success score.
Start with a decision: which service page, enquiry step or follow-up process deserves attention next? Build the report around evidence that helps answer that question.
Define a useful enquiry before counting one
Write a short qualification rule with the person who handles enquiries. For a hypothetical commercial maintenance business, a relevant request might concern an offered service, a property inside its service area and a problem the team can assess. A supplier’s sales pitch would not qualify. An incomplete message could remain unreviewed until someone checks it.
Keep the original submission count beside the reviewed count. If twelve forms arrive and only eight have been reviewed, a report of three qualified enquiries needs that denominator. It does not establish that the remaining nine were poor prospects. Give the review queue an owner and a next action.
Keep three kinds of evidence separate
| Evidence | Record | Question it helps answer |
|---|---|---|
| Search visibility | Search Console period, search type, filters, clicks, impressions, CTR and average position; relevant page/query groups | Are relevant searches reaching the intended pages? |
| Profile actions | Business Profile website and call-button clicks, with their own dates | Are people taking an available next step from the profile? |
| Reviewed business outcomes | Actual enquiries, review coverage, qualified subset and evidenced source | Are requests relevant, and what should the team do next? |
Google defines Business Profile calls as clicks on the call button. That is not a count of completed sales conversations. Website clicks likewise describe an action on the profile. Keep those labels intact rather than renaming either measure “leads.” (Google Business Profile metric definitions)
Search Console describes performance in Google Search, with metrics including clicks, impressions, CTR and average position. It is not a ledger of every website visitor (Search Console performance overview). Keep search type and other filters consistent when comparing periods. Average position should remain an aggregate observation, not a promise that every customer sees the same rank (Google’s measurement definitions).
Use a worked decision, not a victory claim
Consider a fictional four-week report: a service page receives 40 search clicks, compared with 30 in the previous four weeks. Six website enquiries are recorded across the business. Four have been reviewed; two fit the qualification rule. Only one of those two has reliable source evidence linking its enquiry journey to organic search.
The defensible conclusion is that search clicks increased by ten, two reviewed enquiries were qualified, and one qualified enquiry has an evidenced organic source. It is not defensible to claim that the ten extra clicks produced both qualified enquiries. The periods may contain different people and journeys, and two submissions are still awaiting review.
The immediate action is to review the remaining submissions. If unsuitable requests repeatedly misunderstand the service area, inspect how clearly the page explains it. If relevant enquiries wait days for a reply, address follow-up before treating traffic growth as the only priority.
Leave room for unknowns
Record attribution as unknown when it is missing. Privacy choices, cross-device visits and untagged routes can prevent a clean connection between a visit and an enquiry. A later self-reported source can add evidence, but record its basis rather than silently turning it into tracked attribution.
Use one row per actual enquiry in the private working record, with an internal reference, classification, source evidence and next action. Share aggregated findings outside that record. Do not add website and inbox totals into a count of unique people unless the identities have actually been reconciled.
Finish the meeting with one test
Choose one specific change, its owner and a review date. For example, clarify service-area wording on a relevant page and review the location fit of subsequent enquiries. Preserve the before-period, note other changes and report the sample size. A small improvement is a reason to keep observing, not proof that the wording caused it.
A useful scorecard leaves the team with a practical decision and a visible uncertainty. That is more actionable than a dashboard full of rising numbers with no agreed meaning.
Contributor bio: Skymattix is a Toronto-based digital marketing agency working across programmatic advertising, search and website strategy. This contribution was prepared for Skymattix with AI-assisted research and drafting.
