+84917212969
VIET SEO / INSIGHTS

SEO/AEO/GEO Service Contracts & SLAs: Essential Checklist

A practical guide to SEO, AEO and GEO service contracts and service-level agreements (SLAs). Learn how to define project scope, manage client-owned accounts, establish incident response times, verify deliverables, protect personal data and clarify content ownership. Includes sample SLA tables, contract clauses, acceptance criteria, technical rollback procedures, termination requirements and a pre-signing checklist for businesses and agencies.
Written by Viet SEO Team Updated: 1 views
SEO/AEO/GEO Service Contracts & SLAs: Essential Checklist

What should an SEO, AEO and GEO service contract include? A useful agreement defines what the provider will deliver, who owns each account and asset, how work is approved, when incidents receive a response, and how data and access are returned at the end. A service-level agreement (SLA) should describe measurable service obligations—not guarantee specific Google rankings or AI citations.

This practical checklist is for business owners, marketing leads, procurement teams and SEO agencies. It provides sample operational clauses and acceptance criteria to adapt with legal counsel. It is not a ready-to-sign agreement or jurisdiction-specific legal advice.

1. Define the scope of SEO, AEO and GEO services

Begin with an itemized statement of work (SOW). Separate activities that the provider controls from outcomes influenced by search engines, AI products, competitors and market demand.

Workstream Examples of verifiable deliverables Evidence of completion
Technical SEO Crawl audit; indexing and canonical checks; redirect mapping; structured-data validation Issue list, changed URLs, test outputs, before/after records
Content / on-page SEO Approved briefs, page updates, new articles, internal-link improvements Published URLs, editorial approvals, revision history
AEO / GEO Question research, answer-focused content, source verification, baseline AI-answer sampling Question set, timestamped observations, methodology and content change log
Measurement GSC and GA4 setup review, reporting dashboard, monthly performance review Access verification, report exports, action log

Contract tip: specify quantities, languages, website sections, expected review cycles, dependencies and any out-of-scope work. An AI citation observation is a sampled indicator, not a promise that a platform will cite a particular page.

2. Account ownership, access and handover

The client should retain appropriate control of business-critical assets. Record who owns each account, what role the provider needs and what happens when a team member leaves.

  • Search and analytics: Google Search Console, GA4, Google Tag Manager and related integrations.
  • Website infrastructure: domain registrar, DNS, CDN, hosting, CMS, repository, backups and deployment tools.
  • Advertising and SaaS: Google Ads, business profiles, reporting tools and any licensed third-party services included in scope.
  • Least privilege: grant named user accounts with only the permissions needed; avoid shared passwords and enable MFA where available.
  • Handover: confirm client access, transfer agreed deliverables and revoke vendor credentials when engagement ends.

Not every platform uses an “Owner” role or permits ownership transfer in the same way. The contract should name each platform's actual roles rather than impose a nonexistent permission level.

Asset Client owner / administrator Agency role Exit action
Google Search Console [Client account] [Approved level] Verify client control; remove agency access
GA4 and GTM [Client account] [Approved level] Export settings; revoke access
Domain / DNS / hosting [Client account] [Temporary access] Return credentials and configuration records
CMS / source repository [Client account] [Named user] Deliver code, content and change history

3. Define SLA severity, response times and escalation

Distinguish acknowledgment (someone receives and triages a ticket), mitigation (reducing immediate impact) and resolution (verified correction). The table below is an illustrative negotiation template, not a universal industry SLA.

Priority Illustrative incident Initial response target* Next action
P0 — Critical Production outage caused by an in-scope change; widespread accidental noindex Within 1 hour Activate incident lead and mitigation / rollback plan
P1 — High Major redirect or template defect affecting priority pages Within 4 business hours Investigate impact; agree workaround and update cadence
P2 — Medium Noncritical markup defects or localized content regression Within 1 business day Open tracked remediation item
P3 — Routine Editorial request or scheduled optimization Within 2 business days Plan in agreed work cycle

*Illustrative targets only. Define business hours, time zone, holidays, support channels, exclusions, escalation contacts and any additional mitigation or resolution commitments in the signed SLA.

Specify who can declare a P0 incident, who authorizes a rollback, and how frequently the agency updates stakeholders during an active incident.

4. Deliverable acceptance and evidence requirements

  1. Submit each deliverable with its affected URL(s), description, owner, completion date and supporting evidence.
  2. For technical work, attach relevant crawl checks, screenshots, configuration diffs or staging/production test results.
  3. For content, provide the approved brief, final copy, citation/source checks and publication URL.
  4. Allow the client a defined review period of [X business days] and specify how requested corrections are logged.
  5. Close the task only when objective acceptance criteria are met or an agreed exception is documented.

Reports should distinguish completed work from delayed performance effects. A newly fixed indexing issue may be technically accepted before Google recrawls and updates its reporting.

5. Performance reporting without ranking guarantees

Define baseline dates, reporting sources and attribution limits. Useful indicators include GSC clicks, impressions and indexing status; GA4 organic sessions and key events; conversions; publication status; and documented technical issues.

  • SEO: prioritize visibility and business outcomes but report data latency, seasonality and major site changes.
  • AEO/GEO: identify the AI platforms, prompts, country/language, test date and citation criteria; maintain snapshots when feasible.
  • Commercial KPIs: agree lead definitions, source attribution and data ownership before calculating performance-based fees.
  • No implied guarantee: do not promise a particular ranking, inclusion in AI answers or a fixed number of conversions unless the parties explicitly define a controllable contractual obligation.

6. Data security, privacy and AI tool usage

Identify the parties' responsibilities for personal data, account security and third-party software. At minimum, the agreement should address permitted processing, access controls, storage, retention, deletion requests, incident notification and subcontractor restrictions.

  • Use named accounts, MFA, encrypted transport and access logs where practical.
  • Do not upload client confidential data, personal information or unpublished commercial material into third-party AI tools without the agreed authorization and safeguards.
  • Define the handling of customer leads, form submissions and analytics identifiers. Server-side tracking does not remove privacy and consent obligations.
  • Define the breach notification workflow and responsible contacts. Legal notification deadlines must be checked against the applicable jurisdiction, not assumed from this article.
  • For Vietnam-based processing, assess applicability of the Personal Data Protection Law No. 91/2025/QH15, effective 1 January 2026, and relevant implementing regulations.

7. Content ownership, licenses and AI-assisted work

  • Identify ownership and license terms for commissioned text, images, code, templates and third-party assets.
  • State whether transfer of agreed rights occurs upon creation, approval, payment or another specified event, subject to law and existing licenses.
  • Require source verification and human review of materially factual AI-assisted content; retain appropriate internal records without unnecessarily collecting sensitive prompts.
  • Describe whether the agency may use client work in its portfolio and whether training or reuse of client-provided materials is permitted.

8. Change management, backups and rollback

Any material change to robots directives, redirects, canonical tags, templates, hosting or structured data should follow an agreed change process.

  1. Record the change request and business/SEO risk.
  2. Capture a backup or rollback-ready version where feasible.
  3. Test on staging when available, then verify production URLs and user journeys.
  4. Document deployment time, approver, implementation owner and post-release checks.
  5. Invoke the incident SLA and rollback decision process if material regressions are detected.

Not all content or infrastructure changes are instantly reversible. Identify restoration limitations and recovery dependencies before promising a rollback deadline.

9. Fees, SLA remedies and excluded events

Separate the base retainer, project fees, third-party subscriptions, additional scope and taxes. Specify payment milestones and the procedure for approving extra work.

Any fee credits, penalties, indemnities or liability limits should be negotiated with legal advice and local law in mind. Clearly distinguish errors caused by the agency from incidents linked to customer changes, third-party outages, search-engine updates or unauthorized access.

10. Termination, offboarding and dispute resolution

  • Define notice periods, payment for accepted work and treatment of unfinished deliverables.
  • Require delivery of agreed content files, reports, configuration documentation, credentials or access invitations, and backup information.
  • Set timelines to revoke agency users, close tokens, and return or delete protected data in line with retention obligations.
  • Document escalation, negotiation, mediation, arbitration or court procedures as applicable; identify governing law and jurisdiction.

11. Short sample clauses for review

Access: “The Client retains administrative control of its designated digital assets. The Provider receives named, revocable access limited to the agreed services and shall return or relinquish that access during offboarding.”

Acceptance: “Each deliverable is accepted against the criteria in Appendix [X], supported by the evidence agreed in the statement of work. Performance fluctuations outside the Provider's direct control do not, by themselves, establish non-delivery.”

Incident response: “The Provider will acknowledge in-scope incidents according to the agreed priority table and provide status updates and mitigation efforts under the agreed support schedule.”

Search visibility: “The Provider commits to performing the documented work and reporting agreed metrics, but does not guarantee rankings, AI citations, organic traffic or revenue.”

These clauses are drafting examples only. Legal counsel should review them for the contract's governing law, liability allocation and commercial context.

12. Pre-signing checklist

  • Scope, quantities, languages, deliverables and exclusions agreed
  • Baseline metrics and reporting cadence documented
  • Asset inventory and account roles verified
  • Priority levels, support hours, response targets and escalation contacts agreed
  • Acceptance evidence and client review period specified
  • Confidentiality, personal data and AI tool rules documented
  • Copyright and reuse rights defined
  • Change controls, backups and rollback responsibilities recorded
  • Fees, tax, additional work and remedies clarified
  • Termination, handover and deletion process agreed

13. Frequently asked questions

Can an SEO contract guarantee Google rankings?

No provider controls Google's ranking systems or search demand. A stronger contract specifies work, measurable deliverables, reporting, acceptance and remedies for failure to perform agreed services.

Can AI citation rate be used as a contract KPI?

It can be tracked as a carefully defined observational indicator using a fixed question set and recorded methodology. It should not be treated as a platform-wide, exhaustive citation count or a guaranteed outcome.

Who should own Search Console and Analytics accounts?

Generally, the client should retain the strongest appropriate administrative control available for its properties and grant the agency limited, revocable permissions for delivery.

What is the difference between SLA response and resolution?

Response measures how quickly the provider acknowledges and begins triage. Resolution requires confirming that the problem has been fixed. The two targets should be separately defined.

What must happen at the end of the agreement?

Reconcile outstanding work and payment, return agreed outputs and configuration records, verify client account control, revoke access and follow documented data retention or deletion rules.

Conclusion: A well-structured SEO/AEO/GEO agreement protects both sides by linking scope, ownership, technical acceptance, security, incident response and handover to verifiable evidence. Customize the sample SLA and clauses before signing; do not confuse operational commitments with search-engine or AI-platform outcomes.

EXPERT Q&A

Questions & Comments

You can ask a question about this article. Viet SEO will review and reply after moderation.

Private consultation via Zalo ↗
No questions yet. Be the first to ask.

Send a question

Your email address will not be displayed publicly.

Your question will be reviewed before being published.

CAPTCHA

Please do not include private addresses, phone numbers or sensitive documents in your public question.

Chat Zalo VietSEO