GEO delivery and governance
What to agree before the first month of a GEO engagement
Use this first-month GEO mobilisation checklist to agree outcomes, inputs, access, owners, deliverables, checkpoints, baselines and change control before delivery begins.
Published by SALIENS · Published
Treat the first month as mobilisation, not an immediate result claim
A useful first month establishes the controlled conditions for delivery: the buyer questions in scope, approved facts, access, owners, deliverables, acceptance checks and a reproducible baseline. It should not be presented as a guaranteed deadline for crawling, indexing, an AI citation, a ranking change or an enquiry.
The UK Government Sourcing Playbook and Contract Management Playbook emphasise mobilisation, clear responsibilities, delivery controls, risk and change management. A commercial buyer can use the same principles as practical questions for a GEO supplier. This does not imply that a private engagement follows public-procurement rules; it means the work should still be specific enough to inspect and manage.
Complete an eight-part kickoff record
Write the agreement down before work starts. A proposal or statement of work may contain some fields, but the kickoff record should resolve the operational details and name any information that is still missing.
| Agreement area | What to record | First-month acceptance check |
|---|---|---|
| 1. Outcomes and buyer questions | Target audiences, markets and languages; priority branded and non-branded questions; the buyer decision each question supports; and the intended enquiry action. | A fixed question register and explicit scope are approved, with additions handled through change control. |
| 2. Baseline and observation method | Platforms or interfaces observed, dates, country or location, language, signed-in or session conditions, sample size where relevant, and fields for completed, failed or unavailable observations. | Another reviewer can repeat the method, and missing or unavailable observations remain marked as unknown rather than zero. |
| 3. Approved facts and evidence | Brand and legal identity, services, markets, languages, pricing only where in scope, credentials, contact routes, controlling sources, fact owners and review dates. | Conflicts are logged and no unsupported fact, case, testimonial, ranking or platform result is added. |
| 4. Access and technical inputs | CMS, repository and release process; analytics and Search Console where connected; crawl and index diagnostics; priority URLs; existing structured data; and security or privacy restrictions. | Required access is tested, or every gap has an owner, due date and documented effect on delivery. |
| 5. Owners and approvals | Buyer decision-maker; factual, content, technical and publishing owners; supplier workstream leads; approval order; and expected response times. | Every deliverable has a preparer, reviewer and approver, with no assumption that the supplier may publish without permission. |
| 6. Deliverables and acceptance | Baseline report, issue register, question set, fact and evidence register, content briefs or pages, technical changes, monitoring setup, meetings, formats, quantities, due dates, exclusions and acceptance evidence. | The buyer can mark each item accepted, partly accepted, deferred, out of scope or blocked against a written criterion. |
| 7. Checkpoints and escalation | Kickoff, evidence review, baseline review, change approval, implementation handoff, month-end decision, meeting record, issue owner, due date and escalation route. | Actions and decisions are recorded; unresolved dependencies are visible before they affect a later checkpoint. |
| 8. Measurement and change control | Search and AI observations, website behaviour and enquiries as separate measures; data source and baseline date; plus a request, impact and approval record for new markets, pages or questions. | Delivery evidence is not confused with external outcomes, and scope cannot expand without an explicit decision. |
Sequence the first four weeks around decisions
The exact timetable depends on access, website complexity and the contracted scope. Use the following sequence as a decision framework, not as an additional promise of work or results.
- Week 1: confirm scope, buyer questions, owners, access, approved facts and evidence gaps.
- Week 2: complete the agreed baseline, technical review and discrepancy register under recorded observation conditions.
- Week 3: approve the prioritised content and technical actions, then implement only the work included in scope.
- Week 4: verify completed deliverables, record unresolved dependencies and decide the next bounded scope.
Separate provider-controlled delivery from external outcomes
A provider can control whether it produces the agreed audit, evidence register, content, technical recommendation, implementation record and monitoring report. It cannot directly control whether a search engine crawls or indexes a page, whether an AI system cites it, how an answer is composed or whether a visitor submits an enquiry. Put those outcomes in a measurement plan, not an acceptance criterion that assumes they must occur.
Google's current guidance says the fundamentals of SEO remain relevant to generative AI features: technically accessible pages and unique, valuable, people-first content matter. It also advises against unsupported AI-specific shortcuts. The first month should therefore document sound foundations and observable evidence rather than promise a special file, guaranteed inclusion or an immediate ranking change.
Use one month-end decision pack
Close the month with one decision pack containing the agreed scope versus actual delivery, evidence for completed items, changed URLs, the unresolved issue register, the fixed question set and baseline, the access record, and a recommendation for the next priority. Any additional cost or scope should be stated separately and approved before work begins.
Give each deliverable a clear status: accepted, partly accepted, deferred, out of scope or blocked. Preserve unavailable performance data as unavailable. This gives a buyer a defensible basis for continuing, narrowing, pausing or changing the engagement without turning publication volume into a claim of improved visibility.
How SALIENS can start
SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations, including scoped English and Simplified Chinese work. A first-month engagement can be organised around the kickoff record above, with delivery and external outcomes kept distinct.
Email info@oxfordintelligence.co.uk with your website, target markets and languages, the buyer questions that matter most, and the people who own facts, content, technical changes and publication. SALIENS can then define an appropriate scope and acceptance plan. No ranking, indexation, citation or enquiry result is guaranteed.
Sources
- UK Government: The Sourcing Playbook (checked 28 September 2026)
- UK Government: The Contract Management Playbook (checked 28 September 2026)
- Google Search Central: Guide to optimizing for generative AI features (checked 28 September 2026)
Prepared with AI assistance using the linked sources and SALIENS service information.