Indexing eligibility
Record the canonical page, response, index directive and source observation date.
Reporting · Synthetic example
A monthly report should end with a decision.
A useful report shows the work, the evidence, what changed, what did not and what the business should decide next. Search visibility, AI citations, visits, onsite actions, qualified opportunities and commercial outcomes stay separate.
Synthetic example · No client or Mindflow performance data
Start with what changed—and what did not.
The first page should help an owner decide. It should not force the reader to interpret a dashboard before learning what matters.
The example below demonstrates the reporting structure. Every statement and value is synthetic. It does not describe a Mindflow Marketing campaign or any real business.
| Field | Synthetic example | Evidence required in a real report |
|---|---|---|
| What changed | Non-branded search visibility improved for one approved topic group | Named Search Console report, scope, period, comparison and query definition |
| What did not | Qualified action volume showed no reliable movement | Written qualification rule and operating-system comparison |
| Evidence | Published pages, indexing checks and source-specific visibility records | Work Ledger, URLs, dates and source links |
| Business meaning | Eligibility and visibility moved; commercial impact remains unknown | Plain interpretation with uncertainty stated |
| Next decision | Improve the action path on the highest-fit landing page | Owner, due date, expected signal, retest date and reversal condition |
SYNTHETIC EXAMPLE. The report says “unknown” when the evidence cannot support a stronger conclusion.
Seven separate records
Do not jump from completed work to revenue.
A monthly report should show each step in order. Movement at one step does not prove movement at the next.
| Rung | Example source | What it establishes | What it does not establish |
|---|---|---|---|
| Completed work | Work Ledger and evidence link | The named task was completed | Indexing, visibility or impact |
| Eligibility and technical health | Indexing, profile or tracking checks | The asset can participate or be measured under the stated conditions | Visibility or buyer response |
| Visibility | Search, Maps or AI-source record | The platform reported or a disclosed test observed exposure | A visit, recommendation or buyer choice |
| Visit | Analytics referral or session | A trackable visit reached the site | Qualification |
| Onsite action | Configured key event | The instrumented action fired | A valid enquiry, patient, client, opportunity or order |
| Qualified action | Business review against a written rule | The action met the approved criteria | A completed commercial result |
| Commercial outcome | Scheduling, intake, CRM, field-service or commerce system | The business recorded the outcome | Sole causation by one page, query or AI answer |
See how Mindflow Marketing records AI-answer observations without calling them revenue →
Synthetic example · Work Ledger
Verify the work before judging the result.
A Work Ledger names the asset, reason, completion date, owner and evidence. “SEO completed” is not an auditable row.
Completion still does not prove impact. The next sections check eligibility, visibility and downstream records separately.
| Task | Affected asset | Reason | Owner and date | Evidence and status |
|---|---|---|---|---|
| Clarify service answer | Example service page | Match one approved buyer question to one page owner | Content owner · sample period | Version record · complete, impact not established |
| Repair internal route | Example hub and child page | Make the approved child reachable from its owner | Technical owner · sample period | Crawl record · complete, indexing pending |
| Test action handoff | Example request form | Confirm the record reaches the responsible team | Operations owner · sample period | Test record · passed, real submissions excluded |
SYNTHETIC EXAMPLE. These tasks, assets and statuses are illustrative only.
Metric definition
Make every number explain itself.
A label such as “organic traffic” is incomplete. The report must name the source, exact report, date range, comparison, scope, denominator, exclusions, freshness and limitation.
Google Search Console can aggregate data by property or page, and those methods can produce different totals, click-through rates and positions. Recent values may also be preliminary. A useful report prints the chosen method beside the number instead of hiding it in a footnote.
| Field | Synthetic definition |
|---|---|
| Metric | Non-branded Search clicks |
| Source and report | Google Search Console Performance report |
| Period and comparison | Named monthly period against the previous comparable period |
| Scope and aggregation | Named property, page aggregation and approved query classification |
| Denominator and exclusions | All eligible clicks in scope; anonymized or unavailable query records stated separately |
| Freshness and limitation | Source extraction date shown; click does not establish qualification or revenue |
SYNTHETIC EXAMPLE. No traffic number is displayed because this page contains no client or Mindflow performance data.
See Google’s current explanation of Search Console Performance data. Source definitions checked 16 August 2026 and require a release-day recheck.
Eligibility before movement
Check technical health before interpreting visibility.
A page cannot earn search visibility if it is not eligible for indexing. A Business Profile performance record depends on a verified, eligible profile. Analytics reports depend on the tracking configuration and event definitions in place during the period.
Report the checks and their limitations. A successful crawl, valid tag or completed profile edit is not a ranking, visit or business result.
Profile eligibility
Record the real operating model, verification state and performance-field availability.
Tracking configuration
Record the property, event definition, test result and date of any configuration change.
Search, Maps and AI
Keep each visibility source separate.
Search Console clicks and impressions answer a Search question. Business Profile views and actions answer a Maps or profile question. Official AI-impression fields, citations, referral sessions and synthetic prompt observations each answer something narrower.
Combining them into one visibility score can hide the denominator and turn unlike records into a neat but misleading number.
| Record | What to show | Do not call it |
|---|---|---|
| Search Console | Clicks, impressions, page/query scope, aggregation, period and freshness | Qualified demand or revenue |
| Business Profile | Available views or actions with the exact profile and field definition | Answered calls, appointments or booked work |
| Google generative-AI report | Available impression fields, page, country, device and rollout limits | Recommendation, citation quality or lead |
| ChatGPT referral | Trackable session with the documented source parameter | All ChatGPT exposure or influence |
| Microsoft Clarity citation | Citation count, cited page, stated denominator and grounding-query limits | Rank or prominence inside the answer |
| Synthetic prompt panel | Exact prompt, surface, date, method and retained output | Platform-wide audience behaviour |
SYNTHETIC EXAMPLE. No prompt score, AI citation count or referral volume on this page comes from a real account.
See Google’s generative-AI performance report announcement, OpenAI’s publisher and developer guidance and Microsoft Clarity’s citation-dashboard definitions.
Qualification
A visit is not a qualified opportunity.
Google Analytics can record a session and a configured key event. That shows an instrumented action under the stated setup. It does not show that the request fits the business.
Qualification needs a written rule and an approved review process. The commercial result then comes from the appropriate system of record. Attribution can assign credit under a model; it does not prove that one touchpoint caused the outcome.
Record the referral or session
Name the analytics report, user or session scope, channel rule, landing page and period.
Record the onsite action
Name the event, trigger, exclusions and test state. Remove spam and duplicate records under written rules.
Apply the qualification rule
Use service, location, care, matter, buyer, product or order criteria approved by the business.
Check the commercial record
Use scheduling, intake, CRM, field-service, product or commerce data for what happened next.
Google defines a key event as a configured important action and attribution as credit assigned to touchpoints under a model.
Five systems of truth
Change the final record by industry.
The reporting ladder stays consistent. The qualification rule and commercial record must fit how the business actually operates.
| Industry | Onsite action | Qualified action | Commercial record |
|---|---|---|---|
| Home Services | Call, form or booking action | Valid service request in the served area | Booked or completed job in the field-service or CRM system |
| Healthcare | Appointment-request action | Appropriate request routed to the correct service | Scheduled appropriate appointment in the approved system; no PHI in the public sample |
| Legal | Consultation-request action | Prospective matter meeting the firm’s approved criteria | Accepted or signed matter in the governed intake system; confidentiality review required |
| B2B SaaS | Demo, trial or activation action | Account meeting the agreed qualification rule | Qualified opportunity or pipeline record in CRM and product analytics |
| eCommerce | Cart, checkout or purchase action | Valid order after approved exclusions | Completed order, refund and repeat purchase in the commerce platform |
SYNTHETIC EXAMPLE. No patient, legal-client, buyer or order-level identity enters this public page.
For eCommerce, standard reports depend on correctly sent events and parameters; see Google’s GA4 ecommerce implementation guide. Healthcare and Legal public examples require privacy and confidentiality controls.
Uncertainty belongs in the report
Show exclusions, gaps and no movement.
A useful report states when data is preliminary, sampled, unavailable, omitted or based on a changed denominator. It records tracking changes, missing integrations and signals that did not move.
Use labels consistently. Observed means a retained check showed it. Reported means a named system supplied it. Inferred means evidence supports an interpretation. Attributed means a model assigned credit. Unknown means the evidence does not support the answer yet.
Say it plainly
Name the expected signal, period and source. Do not hide a flat result behind a blended score.
Name what is missing
State the unavailable integration, field, history or denominator and who owns the repair.
Do not compare unlike periods
Record changes to tracking, classification, aggregation, prompts or qualification before interpreting movement.
Synthetic example · Decision record
Name the next decision, owner and retest date.
A report ends when someone knows what to approve, change or stop. The record should also say what signal would support the decision and what result would reverse it.
| Field | Synthetic example |
|---|---|
| Decision | Improve the action path on the approved high-fit landing page |
| Reason | Eligibility and visibility moved; qualified actions did not show reliable movement |
| Owner and due date | Named page and operations owners · agreed delivery date |
| Expected signal | More valid action completions without a drop in qualification rate |
| Retest date | After the agreed observation window and enough comparable records |
| Reversal condition | Stop or roll back if completion quality falls or the change creates a user barrier |
SYNTHETIC EXAMPLE. The decision, owner, timing and signals above are illustrative only.
See Conversion and Measurement for the operating boundary and Mindflow Marketing’s methodology for evidence, ownership and retesting.
Review your current report
Bring the report you cannot act on.
Mindflow Marketing can show which numbers are source-backed, which are sampled, which are qualified and what decision the report should support. This does not promise an analytics repair, attribution proof, lead result or revenue outcome.
Do not submit patient information, legal-client information, personal call records or order-level identity through a general web form.
Private draft. Every sample value remains synthetic. Proof, data-contract, Healthcare privacy and Legal confidentiality review remain required before publication.