Start with the question the owner needs answered
A report should help someone decide what to keep, fix, investigate or stop.
If the report does not name that decision, write it at the top before reading the charts. “Did the service-page work improve qualified demand?” is useful. “How did SEO perform?” is too broad.
Use a decision header:
| Field | Required answer |
|---|---|
| Business question | What decision must this report support? |
| Reporting window | Which dates are included? |
| Comparison | Prior period, prior year, target or no comparison |
| Sources | Search Console, Analytics, Business Profile and operating records used |
| Material change | What work, release or external incident occurred? |
| Unknown | Which missing record could change the conclusion? |
| Next action | What will happen, who owns it and by when? |
There is no universal rule to start at the front or back of a PDF. Start where the business question begins.
Check the window, comparison and source systems
Numbers are not comparable until their dates, segments and definitions match.
Check whether the report compares equal day counts. Note seasonality, weekday mix, campaigns, site releases, consent changes and known platform incidents. A monthly report should also state when late-arriving or modeled data may change.
| Contract field | Question |
|---|---|
| Time zone | Are Search Console, Analytics and operating systems aligned? |
| Scope | Whole property, canonical page, market, device or campaign? |
| Aggregation | Property totals or URL-level records? |
| Collection | Did tags, consent, calls or forms work throughout? |
| Attribution | Which model and lookback window assigned credit? |
| Freshness | Is the source complete for the reporting date? |
Search Console and Analytics should not be expected to match exactly. They cover different stages, process data differently and can use different time zones. A discrepancy can be normal or diagnostic; the report should explain which.
Read Search Console as Search evidence
Google Search Console records how a site appears and receives clicks in Google Search. It is not a revenue report.
Google’s definitions of impressions, position and clicks depend on the search feature. Click-through rate is clicks divided by impressions. Average position is an averaged relative value, not a universal rank.
Read trends in impressions and clicks before treating position as the headline. Google’s Search Console use-case guidance explicitly recommends that emphasis.
| Metric | What it supports | What it does not prove |
|---|---|---|
| Impression | Eligible exposure under a feature’s counting rules | That the result was noticed or trusted |
| Click | A click from a Google result | A measured session, qualified action or sale |
| CTR | Clicks relative to impressions | Why a user clicked or did not click |
| Average position | Averaged relative placement | One fixed ranking for every user and query |
| Page/query row | Performance for a reported dimension | Complete demand if rows are anonymized or truncated |
Property aggregation and page aggregation can produce different totals. Canonical assignment can place data on another URL. Report tables may omit anonymized queries or show fewer rows than chart totals.
Inspect page and query together. Separate brand from non-brand demand where the data supports it.
Read Analytics as measured behavior
Google Analytics 4 describes measured site or app behavior after collection rules are applied.
The Traffic acquisition report can show sessions, engagement, key events and attributed revenue by source dimensions. User acquisition and traffic acquisition use different scopes and should not be compared as if they answer the same question.
| Analytics record | Useful question | Limitation |
|---|---|---|
| Session | Did a measured visit occur? | Consent, JavaScript and filtering affect collection |
| Engaged session | Did the visit meet configured engagement conditions? | Does not prove qualification |
| Event | Did a configured interaction fire? | Can fire incorrectly or more than once |
| Key event | Did a marked event occur? | Is not automatically a lead or completed outcome |
| Channel | How did GA4 classify the source? | Classification can change and may differ from Search data |
| Attributed revenue | What credit did the model assign? | Does not prove the channel caused the revenue |
Under current GA4 definitions, AI Assistants can appear as a separate channel. Google AI Overview and AI Mode traffic remain within Organic Search. Save the definition used in the report and check it again when channel rules change.
Read Business Profile actions with their limits
Google Business Profile reports interactions that apply to the business and profile setup.
Google’s Business Profile performance guidance covers views, searches, calls, website clicks and bookings where available. These are platform interactions.
A call metric can count a call-button click. It does not prove that the call connected, qualified or became a completed job. A website click is not an enquiry. A booking interaction may depend on a supported provider and does not prove the appointment was fulfilled.
| Profile interaction | Next record needed |
|---|---|
| Call click | Call-tracking or phone-system record |
| Website click | Analytics and landing-page behavior |
| Direction request | No automatic proof of a visit |
| Booking | Scheduling status and fulfilled appointment |
| Search or view | Query and profile context where available |
Business Profile is not applicable to every business. An online-only SaaS or eCommerce company should not be forced into a local-reporting row.
Reconcile qualified and commercial records
The business’s operating systems decide whether an action was qualified or completed.
Use five ledgers:
| Record | Primary source | Decision supported |
|---|---|---|
| Eligibility | Crawl, index and platform status | Could the page or profile appear? |
| Visibility | Search Console and platform reports | Was the business shown? |
| Behavior | Analytics, calls, forms and bookings | What measured action occurred? |
| Qualification | CRM, intake, scheduling or operations | Was the action relevant and accepted? |
| Commercial | Job, practice, sales, billing or commerce system | Was valuable business completed? |
Do not let one number stand in for another. A key event is not automatically a lead. A form is not automatically qualified. An appointment request is not a fulfilled appointment. A checkout is not a return-adjusted order.
Join records only through approved identifiers and privacy-safe processes. If the join is incomplete, say so.
Read completed work, unknowns and annotations
A useful report shows what the SEO team completed during the period.
List changed pages, technical fixes, profile work, content updates and measurement corrections with dates. Separate completed work from planned work.
Then annotate events that could affect the data:
- site releases and migrations;
- tag, consent or form changes;
- product, service or pricing changes;
- campaigns and budget changes;
- seasonality and unusual demand;
- Google logging incidents or ranking updates;
- changes to qualification definitions.
Google’s Search Console anomaly log can show incidents where reports changed without a matching change in user behavior. A report that ignores data incidents may turn a logging problem into a false business story.
State unknowns beside the conclusion. Missing call outcomes or delayed returns can change the decision.
Apply the chain across all five industries
The evidence stages stay separate. The operating record changes by industry.
| Industry | Behavior record | Qualified record | Completed or commercial record |
|---|---|---|---|
| Home Services | Call, form or estimate request | Qualified service opportunity | Booked and completed job |
| Healthcare | Appointment request | Appropriate scheduled appointment | Fulfilled appointment counted under approved privacy rules |
| Legal | Prospective-client enquiry | Qualified consultation or intake | Accepted matter |
| B2B SaaS | Demo, trial or product action | Qualified opportunity | Qualified pipeline and customer record |
| eCommerce | Product view, cart or checkout | Valid paid order | Return-adjusted order and repeat purchase |
Healthcare reporting requires clinical, privacy and security review. Legal reporting requires jurisdiction, advertising and confidentiality review. Public reports should not expose patient, prospective-client, account or order details.
Choose one clear action and a date to review it
End the report with one priority that the evidence supports.
| Decision-close field | Example form |
|---|---|
| Observation | What changed, with source and window |
| Plausible explanations | Two or more explanations still consistent with the evidence |
| Selected action | The smallest consequential fix or test |
| Owner | Person or role accountable for completion |
| Due date | Date the work should be complete |
| Validation | Metric, source, segment and review window |
| Disconfirming evidence | What result would change the decision? |
One changed metric rarely proves one cause. The next action should be small enough to test and important enough to matter.
Use the reader card or request a scoped review
The Conversion and Measurement service owns the broader reporting and buyer-action work. The sample report shows how separate records can be presented, and the traffic-versus-leads guide handles that specific divergence.
Mindflow’s methodology explains the evidence-to-decision sequence.
Turn the report into one owned decision. A broader request can also begin through contact. The Visibility Check is an initial diagnostic, not an attribution or revenue audit.