Agency AEO: Scope Work and Prove Deliverables

Translate the service label into work

AEO can describe research, technical repairs, editorial production, entity information, measurement or some combination of these. An agency proposal should name the actual work rather than relying on the service label to imply a complete programme. Specify which website sections, markets and products are included. If the engagement concerns only public documentation, say so. A buyer cannot compare proposals fairly when one includes implementation and another supplies recommendations, even if both promise the same broad goal of improving AI visibility.

Start with a bounded AEO audit when the scale of the problem is unknown. Explain the sample, evidence and expansion rules so discovery has a useful endpoint. The audit should identify concrete work that can be estimated and assigned. Avoid an indefinite research phase that produces increasingly elaborate presentations without resolving what the client should change. Equally, do not commit to a large publication volume before understanding whether the existing website has access faults, contradictory product information or overlapping articles that require a different intervention.

Define acceptance for each deliverable

A deliverable needs a standard that both parties can inspect. For an article, that may include an agreed reader task, checked claims, appropriate internal links and a reviewed implementation. For a technical repair, it may include the affected URLs and a reproducible verification method. State who approves factual accuracy and who approves release. A delivered document is not the same as a live improvement, so clarify whether the agency writes recommendations, implements changes or supports a separate team during implementation.

Use content briefs to settle purpose and evidence requirements before writing begins. This reduces revision disputes about an article that was never meant to answer the same question in both parties' minds. Include maintenance dependencies where facts change frequently. A comparison page that is accurate on delivery can become misleading later if nobody owns product updates. The commercial scope should identify whether maintenance is included, available separately or handed back to the client, rather than leaving that responsibility implicit after the initial publication milestone.

Specify how revisions will be handled when the client discovers that an approved source was wrong. That situation differs from a writer failing to follow the agreed brief or introducing an unsupported claim. The engagement should have a practical route for correcting published information regardless of where the error began, followed by a fair allocation of additional work. Clear handling of factual corrections protects the content and the working relationship, while preventing urgent accuracy work from getting trapped in a dispute about ordinary revision limits.

Keep control and outcome separate

An agency can control the quality of its work, subject to the agreed access and client inputs. It cannot control whether an external answer product selects a source on a particular occasion. Google's guidance on hiring an SEO warns against ranking guarantees. Apply the same commercial discipline when reviewing AEO claims: require a description of the mechanism and evidence, and question promises that depend on undisclosed control over an external platform. A confident sales presentation is not evidence of that control.

Google's AI optimisation guide also cautions against third-party claims of access to internal ranking or AI systems. Tools may still be useful for collection and workflow, but their measurements need definitions. Ask what a visibility score counts, which prompts it uses and how failed observations are handled. If a provider cannot expose customer-specific evidence or explain its denominator, the client cannot independently interpret the result. The engagement should provide a useful service even when the observed outcome is uncertain or mixed.

Make client dependencies explicit

Editorial quality depends on access to people who know the product or organisation. Identify who can confirm specifications, approve claims and resolve contradictions. Technical work may require a developer, content system access or a release window. List those dependencies with the relevant deliverable so delays can be understood accurately. A stalled approval should not be reported as completed implementation, and a recommendation awaiting engineering work should not be described as a live technical fix merely because the agency delivered its report on time.

Use a responsibility map that is simple enough to operate. One person should own the final decision for each type of change, while specialists contribute where necessary. Do not require every stakeholder to approve a minor wording correction if the established policy allows an editor to handle it. Content governance covers these arrangements in depth. Within an agency engagement, the practical need is to prevent both unreviewed publication and endless approval loops, while preserving a record of who confirmed facts that the agency could not verify independently.

Make reporting independently interpretable

Agree the observation method before the first performance report. Record the question set, platforms, modes, collection schedule and comparison period. If the panel changes, disclose the change and retain a comparable subset where useful. The AEO reporting guide explains how to separate delivery, visibility and business evidence. An agency report should use that separation to make progress understandable, not to reclassify every unfavourable result as success under a different metric. Include limitations near the headline numbers rather than hiding them after the recommendation.

Provide access to the underlying records needed to inspect material claims, within the client's confidentiality and platform obligations. This may include prompt records, cited URLs, source checks, released changes and relevant analytics exports. The client does not need to own the agency's entire internal system to receive usable evidence about its engagement. Distinguish proprietary working methods from information necessary to assess the work purchased. A handover that contains only screenshots of favourable answers leaves the client unable to reproduce the baseline or judge whether later performance has changed.

Price learning and production honestly

A pilot can be useful when scope or evidence is uncertain. Define what the pilot is meant to establish, such as whether a selected documentation pattern can be maintained and whether the measurement method captures relevant questions. Do not call a small favourable sample proof of a universal ranking method. An illustrative pilot might include a few different page types and a documented decision about expansion. Its success criteria should include useful implementation and learning, rather than depending entirely on short-term citation movement that the agency cannot command.

When comparing fees, examine the included work, review depth, implementation responsibility and maintenance commitment. A lower price may cover fewer tasks, while a larger package may contain unnecessary publication volume. The right choice depends on the client's actual problem. Use an AEO backlog to identify work with clear reasons and owners. Commercial clarity improves delivery because both parties know which improvements matter first and which requests are outside the agreed scope until new evidence or priorities justify them.

Plan the end of the engagement from the beginning. The client should receive the relevant inventory, edited assets, source records, measurement definitions and remaining backlog in usable formats. Confirm ownership and access arrangements through the appropriate agreement, without relying on assumptions in a sales deck. Explain how ongoing observations and maintenance can continue after the agency leaves. A responsible service creates durable operational value: the client understands what changed, why it changed and what remains to be done, even if a future provider takes over the programme.

Sources and further reading

• Google hiring SEO guidanceGoogle warns against guarantees of top search rankings when hiring SEO providers.
• Google AI optimisation guideGoogle warns that third-party tools do not access its internal ranking or AI systems.