In short
White-label GEO reporting needs a clear rule: the PDF you deliver and the portal a client opens later must identify their measurement scope, not necessarily display an identical latest number. A new audit, a revised question or a different mode may explain a discrepancy. Before choosing a platform, check its delivery formats and maintain a delivery register. The workflow below is an agency practice, not a claim that automatic document versioning is included.
“The report says something different from the portal. Which number should I present?” Answer that question before your next client review. Your brand appears on both outputs, so your team must explain the difference. This playbook addresses a specific reporting problem: keeping a delivered document intelligible alongside results viewed later, without treating every change as evidence that your work improved visibility.
A delivered PDF and a viewed portal have different jobs
A PDF is a file you can retain in the version you sent. A portal is a viewing environment. Its existence does not establish that the screen still corresponds to the audit behind that document. Check the reference actually displayed. Do not assume either continuous updating or automatic preservation of earlier views: those behaviours need verification in your account, rather than inference from the word “portal”.
Our view: professional reporting should let someone recover the measurement behind a delivery even after a newer measurement exists. That matters more than promising “always synchronised numbers” at the expense of context. An agency does not need to stop results changing. It needs to stop readers accidentally comparing different things. Your buying decision therefore depends on your reporting process as well as the design of the finished document.
Choose delivery capabilities before organising versions
AI Labs Audit provides white-label PDF reports from Consultant and a read-only client portal from Consultant+. Portal recipients access results through a secure link without creating an account. Centralised white labelling and a shared credit pool belong to Agency+. These are separate capabilities: a branded PDF does not imply portal access or shared team administration. Buy the capability you need, not an assumption attached to a plan name.
Check current entitlements on the pricing page. For viewing arrangements, the client portal guide is the dedicated resource. Here we propose an editorial workflow around deliverables. We are not presenting a document vault, electronic signatures or an immutable PDF history as established platform features. If one of those is a procurement requirement, verify it separately before putting it into your proposal.
Maintain a delivery register your team controls
A spreadsheet or your document management system can provide a starting point. For each delivery, record the exact brand, the available audit reference, collection date, language, market, models and mode. Add the filename actually sent, its editorial version, authorised recipients and the chosen viewing link. Maintaining this register is a recommended agency procedure, not an assertion that the platform generates these records automatically for every delivery.
- Measurement reference: which audit and responses support the findings?
- Delivery reference: which file did the client receive?
- Viewing reference: which audit does the portal show when checked?
- Accountability: who investigates differences and approves the explanation?
Distinguish generation date from observation date. A PDF created today may describe an earlier collection. Its filename should help recover that collection, not imply a new measurement occurred. A typographical correction should not be announced as a new audit either. Otherwise your own naming convention creates the discrepancy you later have to explain.
The denominator belongs to the number’s version
Our 2026 AI visibility barometer illustrates the problem. Its broad corpus covers 6,820 responses, 104 audits, 65 brands and 44 models between September 2025 and June 2026. However, the published 16% spontaneous visibility result uses 106 mentions in 657 responses, from a subset of 13 brands with entity extraction. It is not a rate calculated across all 6,820 responses.
| Published scope | Volume | Context to retain |
|---|---|---|
| Broad barometer corpus | 6,820 responses | 104 audits, 65 brands, 44 models |
| Spontaneous visibility subset | 657 responses | 13 brands with entity extraction |
| Mentions within that subset | 106 | Published result rounded to 16% |
Keeping “16%” while losing “657 responses” removes part of the evidence from a client report. If another output shows a metric based on another corpus, the difference is not necessarily a mistake. Reconcile denominators first. These voluntary audit data are not representative of all businesses, and they promise no outcome for your client. They show how carefully a reported number needs to travel with its scope.
Do not reconstruct study volume with a quick multiplication
The public invoicing software study reports 20 active questions, 480 analysed responses and 28 ranked brands. The page lists 11 September 2026 as the collection date and 29 October 2026 as the publication date; both the market and question language are French. The protocol distinguishes question, model, mode and repetition. Question count alone therefore does not reconstruct response count. Use the volume the study documents rather than assuming one answer per question.
Keep the data date separate from the publication date. These two dates do not establish continuous collection between September and October. Localising a report does not change its underlying market. An English explanation of that study is still an explanation of French questions, not a fresh measurement of an English-speaking market. In a multinational client organisation, make that distinction visible before the slide moves beyond the original presentation.
Investigate a discrepancy before running another audit
When a client reports different numbers, request the actual file and the screen they viewed. Check the audit reference, metric name, period and any filters. Are they comparing a brand mention, a cited URL or a recommendation? These are different events. A bot request or a human visit is not proof of citation either. Familiar labels can hide different definitions, even when two percentages happen to look comparable.
Then check questions, models, language and mode. Spontaneous visibility requires questions that do not supply the brand name. Repeating a supplied name is a different signal. Even when settings appear identical, responses may vary. Do not immediately collect another batch to obtain the number you prefer: that adds an observation, not an explanation of the versions already delivered. First establish what those versions actually contain.
Separate report corrections from new measurements
A misspelt client name is an editorial correction. A wrongly transcribed result requires a factual correction referencing the source measurement. Changing questions or models creates a different measurement scope. These situations call for different messages. Describing all of them as an “updated report” prevents the client from understanding whether the evidence changed, the commentary changed or a presentation mistake was fixed.
Keep the previously delivered file in your authorised document system and record why it was replaced. Explain which findings are affected and which remain valid. This procedure does not imply that the platform manages these versions automatically. Its purpose is to avoid a poor reporting habit: silently replacing a document already used in a committee, then leaving two stakeholders discussing different files with the same name.
Add a reconciliation note someone can use in a meeting
Here is wording to adapt, not an automatic platform message: “The delivered document describes the audit identified in its scope note. The viewing space presents another collection. Questions, models and modes need to be reconciled before interpreting the difference as a trend.” Replace these terms with references you actually checked. If the screen shows the same audit, investigate another explanation instead of using a convenient template.
The note should answer one question, not recite every product limitation. State the identified difference, its effect on comparison and the proposed decision: retain the original reference, correct a transcription or examine a new collection. If you cannot conclude, say so. White labelling does not justify disguising uncertainty behind a confident sentence. The agency’s name on the cover makes the explanation more important, not less.
Keep measurement, interpretation and implementation separate
A number describes an observation. Your analysis explains its relevance to the engagement. Implementation consists of separately agreed work. AI Labs Audit’s AI-generated action plan is reserved for Agent and Agency+; your consultant commentary should not be presented as that automatic capability. You can propose your own priorities, clearly identified as agency analysis rather than an automatically included platform deliverable.
If a metric changes after an intervention, document comparison conditions. A change does not by itself demonstrate that your intervention caused it. A model or web search behaviour may also have changed. Your client is buying defensible analysis, not an assurance that a higher percentage automatically validates every action billed. This boundary also helps you explain a lower number without inventing a technical failure or concealing an inconvenient result.
Protect continuity without promising unverified portability
Define who retains delivered files, who receives the portal link and who answers questions when the account contact changes. Read-only access does not mean unrestricted redistribution. Before an engagement ends, verify actual access conditions; promise neither a perpetual portal nor a complete migration into another platform without evidence. Keep the reporting arrangement consistent with the permissions and agreements you really have.
The agency offering helps distinguish PDFs, portals and team operations. To assess a solution more precisely, ask a colleague to recover a delivered number and explain a later discrepancy without calling you. That test does not demonstrate increased visibility. It shows whether your organisation can stand behind the reports carrying its name, after the original presenter has left the room.
Questions and answers
Why do the delivered PDF and the portal show different numbers?
First check the audit reference, collection date, metric and denominator, then the questions, models, languages and modes. The outputs may describe different measurement scopes. A discrepancy alone proves neither an error nor improved visibility.
Which plan provides a branded PDF and a client portal?
White-label PDFs are available from Consultant and the read-only client portal from Consultant+. Centralised white labelling and shared credits belong to Agency+. Check current entitlements on the pricing page.
Does the platform automatically archive every version of our PDFs?
This guide does not establish automatic, immutable archiving of every PDF version. It recommends that agencies retain sent files and a delivery register in their authorised document system. Any requirement for automatic version control needs separate verification.
Do we need another audit to correct a report?
Not for an editorial or transcription correction when the source measurement supports the correction. A new collection is another observation; it does not replace an explanation of versions already delivered. Document the nature of the correction.
Can we describe a higher number in a later report as the result of our work?
Not from the increase alone. Check measurement comparability and changes to models, modes or questions. Responses can vary even with similar settings; a difference alone does not establish that your intervention caused it.
Agencies, consultants and in-house teams: compare the answers generated for your own scenarios, languages and selected models. Our infrastructure, your scenarios, your expertise.