GEO contract scope, exclusions and handover: a buyer's checklist

Turn a broad ambition into an inspectable scope

A goal such as 'improve AI visibility' is useful direction, but it is not an acceptance-ready scope. A buyer still needs to know which markets, languages, pages, questions and systems are included; what the provider will deliver; what the buyer must supply; and how both parties will decide that the work is complete.

Write those decisions into the order, statement of work or attached schedule before delivery starts. The UK Government's Sourcing Playbook calls for a clear articulation of the service in a well-written technical specification and for early planning at contract end. Its rules are aimed primarily at central government and associated bodies, but the underlying questions are useful to any buyer commissioning a bounded professional service. This article is a practical scoping aid, not legal advice.

Complete eight fields before signing

Use the table as a negotiation and approval record. Every row should contain a specific answer, an owner and, where relevant, a linked schedule or source. If something is unknown, record the assumption and what will happen when it changes.

Separate deliverables from external outcomes

A provider can control whether an audit is complete, an approved page is changed, metadata and structured information match the visible content, monitoring is run on the agreed query set, and evidence is delivered. It cannot control whether a search engine crawls or indexes a page, whether an AI product cites it, how another source is interpreted, or whether a prospect makes an enquiry.

Google states that the normal technical and content requirements for Search also apply to its AI features and that no special AI file or schema is required. It also says that meeting requirements does not guarantee crawling, indexing or serving. Write contracts so controlled outputs can be accepted on evidence, while external visibility and commercial results are measured as outcomes rather than guaranteed deliverables.

• Accept a content change against the approved brief and rendered page, not a promised answer position.
• Accept technical work against test evidence, URLs and change records, not an assumed indexation date.
• Define the monitoring query set, engines, locations, languages, baseline date and reporting method before comparing periods.
• Record visibility, website visits and qualified enquiries as separate measures with their own data sources.

Make responsibilities and changes explicit

Add a compact responsibility matrix covering fact ownership, drafting, technical implementation, approval, publication, monitoring and reporting. For each activity, name the person responsible for doing the work and the person authorised to approve it. Shared responsibility without a named decision-maker is a common source of delay.

A change request should identify the requested change, reason, affected deliverables and assumptions, timing and commercial impact, approver, effective date and revised acceptance test. Do not treat a new language, integration or page group as a casual clarification if it changes effort or dependencies. The UK Government's Model Services Contract is designed to be assessed and tailored to the project; it is not a substitute for project-specific legal and commercial review.

Specify the handover before work begins

The Sourcing Playbook recommends planning early for contract end and setting clear expectations for exit and transition. Its suggested exit plan covers activities, milestones, resources, roles, risks, timelines, standards, interfaces, dependencies and asset transfers. A GEO engagement can apply the same discipline at a proportionate scale.

Agree the handover package at the start, update it during delivery and test it before final acceptance. State the file formats, storage location, recipient, due date and retention or deletion rule. The buyer should also know which accounts it owns, which access the provider will lose, and which unresolved items remain after the final date.

• Final audit, prioritised issue register and evidence links.
• Approved organisation facts, page map, content sources and decision log.
• Monitoring query set, configuration, baseline, exports and reporting definitions.
• Technical change record, implementation notes, tests and known limitations.
• Open risks, unfinished items, responsible owners and next review dates.
• Credential and access register, transfer or revocation evidence, and agreed data deletion or retention.

Use the checklist to brief SALIENS

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations. We can turn buyer questions and approved facts into an inspectable scope, keep English and Simplified Chinese work aligned, and document implementation, monitoring and handover. We do not promise rankings, inclusion in AI answers or enquiry volume.

Email info@oxfordintelligence.co.uk with your website, target markets and languages, priority buyer questions, the pages or systems you expect to include, and any draft scope or procurement timetable. We will help identify the decisions that need to be written down before delivery. SALIENS is operated by Oxford Intelligence Limited.