Define a useful enquiry
Agree on the services, customer locations and types of projects that fit your business. A call about an unsupported service is different from a qualified request. Make room for the team’s feedback so reporting reflects commercial relevance without exposing unnecessary personal details.
Record a baseline before changing the site
Capture current search visibility, important landing pages and the enquiry actions you can reliably measure. Note seasonal patterns, paid campaigns and major business changes. If tracking is new, explain that historical comparisons may be limited. A missing event is not evidence that nobody contacted the business.
Separate activity from outcomes
Publishing a service page is completed work. More search impressions are a visibility signal. A submitted form is an interaction. A qualified opportunity or sale is a business outcome. Reporting these separately helps avoid claiming revenue from a page view or crediting every new enquiry to SEO.
Compare like with like
Look at branded and non-branded searches separately when useful. Compare similar service groups and devices. For seasonal tourism or trade work, a year-over-year view can add context to a month-over-month view. Small sample sizes and changing demand should temper strong conclusions.
Keep an observation log for AI answers
Use a defined set of relevant questions and record the answer engine, date, mention and linked source. Treat the results as observations from that method, not a complete picture of all users. Changes in answers can reflect the system and prompt as well as changes on your site.
Turn the report into the next decision
End each review with the main finding, the level of confidence and the next action. That might be improving a weak enquiry path, expanding a useful service explanation or investigating an indexing issue. A short report that changes what you do is more useful than a large export with no interpretation.