A useful report should help an owner decide what to do next. That starts with naming what the number measures. A search click, a recorded form action, a saved enquiry and a suitable project opportunity are different steps. They become a story only when the evidence connects them.
- Attention
- Search appearances and click-throughs.
- Actions
- A recorded interaction or a saved enquiry.
- Outcomes
- A consistently qualified enquiry, accepted quote or recorded sale.
These are not automatically one measured funnel. Connect them only where the records, definitions and coverage support it.
Separate attention, actions and business outcomes.
Search impressions record appearances; clicks record click-throughs. Analytics can record sessions and actions under its own setup. A business register can record an enquiry, a quote or an order. Those systems have different definitions, coverage and limits.
Lola Famulegun's reporting article at Nielsen Norman Group makes the distinction between activity, experience measures and business outcomes. For a small business, the useful habit is to say what is actually known and identify the missing connection.
Reading behind this section: Lola Famulegun / Nielsen Norman Group
Check the scope before comparing totals.
Keep the exact website property, dates, search type, filters and grouping with the export. A query table and a site-level daily total are not interchangeable. Search Console documents differences caused by aggregation, row coverage and anonymised queries.
A discrepancy needs investigation before it becomes a headline. The specific reason in one dataset should be traced from that dataset; do not assume every mismatch has the same cause. Keep page-level figures separate from whole-site denominators unless the comparison is valid.
Reading behind this section: Google Search Console Help
Compare a meaningful period, with the context beside it.
Complete months can have different numbers of days. A busy season may differ from the previous one, and tracking can begin part-way through a comparison window. Missing measurement is not evidence of zero activity.
Show absolute counts before a percentage, especially with a small starting number. Keep the wider trend visible where it changes the interpretation. A dated historical comparison can be useful without claiming the change was caused by one piece of work.
Follow the record through to a useful decision.
For enquiries, confirm that a record was actually received and separate tests, spam and duplicates. Qualification needs a consistent definition from the business. A submitted form event does not establish that the project was suitable, quoted or won.
Choose the next action around the gap: improve a product explanation, investigate an enquiry path or join the saved records to later outcomes. Reporting earns its place when the owner can see the decision, the evidence and what remains uncertain.
Put it to use
A useful check for your business.
- What exactly is being counted, and by which system?
- Are dates, filters, grouping and tracking coverage comparable?
- What business decision follows from this observation?
The thinking behind this guide
Sources & further reading.
Our practical interpretation, with the references below for the specific principles and further detail.
- Stop Reporting UX Activity and Report Business Outcomes
Distinguishing delivered activity and experience metrics from business outcomes.
- Troubleshooting Search Console data discrepancies
Why table and chart totals can differ; a specific dataset still needs its own lineage check.
