GEO content procurement
Building useful evidence pages for service claims
Map each service claim to an inspectable source, scope, owner and review date before asking buyers or AI systems to rely on it.
Published by SALIENS · Published
Treat an evidence page as a buyer decision record
A service page may say what a provider does, but a buyer still needs to know which parts of the statement are facts, what they apply to and where the supporting record sits. An evidence page should make that path shorter. It is not a collection of badges or a place to repeat the same promise in more confident language.
The UK CAP Code says marketers should hold documentary evidence before publishing objective claims that can be substantiated. It also requires significant qualifications to be clear and not contradict the claim. The practical procurement question is therefore not simply whether a page sounds credible, but whether a reviewer can trace each material claim to current evidence and understand its limits.
Classify the claim before choosing the evidence
Different claims need different records. A company identity can be checked against an owned legal or corporate record. A service-scope statement needs a current specification or order form. A professional credential needs the issuer, holder, status and validity period. A performance statement needs a defined metric, population, period and method. A price or availability statement needs the current commercial source and its conditions.
Do not turn a completed deliverable into an outcome guarantee. A published page, a corrected technical setting or a finished monitoring round can be evidenced as work completed. Indexing, ranking, citation, leads and revenue are separate outcomes decided or influenced by systems and people outside the supplier's control.
- Identity: legal entity, trading name, location and contact route.
- Scope: audience, included work, exclusions, dependencies and handover.
- Method: what is checked or changed, by whom, under which conditions.
- Credential or affiliation: issuer, exact status, holder and validity.
- Performance: metric definition, denominator, period, source and limitations.
- Price or availability: effective date, taxes, minimum commitment and eligibility.
Build a claim-to-evidence register
Start with the claims that could change a buyer's shortlist, budget or risk assessment. Record the visible wording, the evidence a reviewer can inspect, the qualification that must stay beside it, the accountable owner and the next review date. If a source is unavailable, mark the claim as unverified and remove or narrow it before publication rather than leaving a blank evidence field.
| Claim type | Evidence to retain | Visible qualification | Owner and review |
|---|---|---|---|
| Identity | Approved legal or corporate record and current contact details. | State the exact entity and trading relationship; do not imply an unauthorised endorsement. | Owner: ___; checked: ___; next review: ___ |
| Service scope | Current service specification, deliverable list, exclusions and dependency record. | Say which package, market, language or client condition the scope covers. | Owner: ___; version: ___; next review: ___ |
| Method | Dated method note, sample record and acceptance criteria. | Separate the method from any unguaranteed platform outcome. | Owner: ___; tested: ___; next review: ___ |
| Credential or affiliation | Issuer page or certificate, named holder, status, permission and validity date. | Use the issuer's exact description; do not broaden it into institutional backing. | Owner: ___; valid to: ___; next review: ___ |
| Performance | Source dataset, metric definition, denominator, period, comparison and limitations. | Name the measured population and avoid implying causation that the evidence cannot establish. | Owner: ___; period: ___; next review: ___ |
| Price or availability | Current rate card or commercial source, tax treatment, commitment and eligibility conditions. | Keep material conditions next to the amount or availability statement. | Owner: ___; effective: ___; next review: ___ |
Put the limitation where the buyer will see it
A qualification hidden in a general disclaimer cannot repair a prominent claim that gives a different impression. Keep the market, language, package, date range, sample size and material exclusions beside the claim they qualify. Use specific wording such as 'observed in 24 completed checks during August' rather than an undefined phrase such as 'highly visible in AI'.
Apply the same discipline to testimonials and reviews. Retain the source, permission and relationship; do not invent a customer, remove context or turn a person's opinion into a universal performance claim. If there is no genuine, authorised evidence, leave the testimonial out.
Align visible content, metadata and structured data
Google's people-first guidance asks whether content has clear sourcing, demonstrates relevant expertise and gives readers enough information to achieve their goal. An evidence page should therefore explain who is making the claim, why the source is relevant, how the evidence was produced where that matters, and when it was last reviewed.
Structured data can describe information that is already visible, but it is not a substitute for evidence. Google's guidelines say markup should represent the main visible content and should not contain irrelevant, misleading or fake information. Correct markup does not guarantee a rich result. Keep names, dates, ratings, offers and organisation details consistent across the page, metadata and markup.
Use an acceptance check before publication
Ask a reviewer who did not draft the page to trace every material claim. They should be able to identify the source, scope, owner, review date and limitation without relying on an internal explanation. Keep a dated change log when the claim or evidence changes, and remove expired credentials, prices or availability statements promptly.
SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations. We can help build claim registers, evidence pages and review workflows that support informed enquiries without presenting publication as a ranking or citation guarantee. Email info@oxfordintelligence.co.uk with your website, target market and the service claims buyers need to verify. SALIENS is operated by Oxford Intelligence Limited.
- Can every objective claim be traced to a current source?
- Are material limits beside the claim rather than hidden elsewhere?
- Do visible copy, metadata and structured data describe the same facts?
- Are endorsements, reviews and credentials genuine and authorised?
- Is an owner responsible for the next review or withdrawal?
- Are completed work and external outcomes reported separately?
Sources
- CAP Code Section 3: Misleading advertising (checked 22 September 2026)
- Google Search Central: Creating helpful, reliable, people-first content (checked 22 September 2026)
- Google Search Central: General structured data guidelines (checked 22 September 2026)
Prepared with AI assistance using the linked sources and SALIENS service information.
