VIET SEO / INSIGHTS
Contract, SLA and Legal Terms for SEO/AEO/GEO Services: Checklist
A practical checklist and sample contract clauses for businesses procuring SEO, AEO and GEO services. Covers account access, SLAs, acceptance criteria, data privacy, content ownership and rollback.
Purpose: provide a practical checklist of contract clauses and SLA items for buyers (business owners, CTOs, PMs, procurement) hiring SEO, AEO and GEO services. Focus areas: account access and handover, technical acceptance, data protection, AI-related incidents and rollback.
1. Account access and handover mechanics
- Inventory required accounts: Google Search Console, Google Analytics/GA4, Google Tag Manager, hosting, DNS, CMS, FTP/SFTP, technical email, Ads platforms, paid SEO tools, code repository.
- Access levels: specify Owner/Administrator/Editor/View only for each account. Require final Owner/Administrator control by the client at acceptance.
- Granting process: client creates named accounts for vendor or vendor is granted temporary workspace users; sharing of personal accounts by vendor staff must be prohibited.
- Proof of handover: screenshots, email confirmations, and an appended inventory table in the contract listing accounts and granted roles.
- Require non-reliance on vendor personnel accounts; mandate transfer of any assets created by vendor to client-owned accounts.
2. SLA — incident response and remediation times
- Define incident severity levels (P0–P3) with concrete examples (site down, widespread noindex, redirect errors, SEO-impacting content removal).
- Specify SLA targets: initial response time and expected remediation or mitigation windows per severity. These targets must be negotiated and agreed in the contract.
- Escalation and out-of-hours support: list contacts, escalation path, and hours when emergency support applies.
- Go‑live support: include smoke test checklist and guaranteed support window (e.g., first 48–72 hours after launch) — finalize timing in the contract.
3. Acceptance criteria
- Acceptance by deliverable: each task requires evidence (screenshots, code diffs, issue tracker items, staging/production test pages, GSC coverage reports).
- Testing workflow: require staging → preproduction → production promotion steps and automated/manual checks for robots/meta directives, redirects, canonical tags, structured data.
- Client review period and criteria for acceptance/rejection. State retention period for acceptance evidence (to be agreed; mark for verification if unspecified).
4. Data security, PII handling and privacy/consent compliance
- PII handling: explicit list of prohibited data collection/sharing; encryption and least‑privilege access; deletion obligations on contract end.
- Consent and tracking: vendor must not deploy tracking beyond user consent; record consent logs and enable auditability.
- Breach notification: timelines and responsibilities for incident disclosure and remediation coordination.
5. Content copyright and revision history
- Ownership of content: clarify who owns copyright in produced content and usage rights after contract termination.
- Version history: require CMS revision history, notes on edits and labeling for AI-assisted drafts. If AI tools are used, require internal metadata and fact‑check records.
6. Penalties and remediation for technical breaches
- Define technical breaches (e.g., accidental site‑wide noindex, wrong redirects blocking crawl) and mandatory remediation steps in SLA windows.
- Remedy mechanics: fee credits, service reductions or other agreed remedies if SLA targets are missed. Avoid promises of rankings or traffic increases in legal terms.
7. Dispute resolution, termination and rollback
- Termination rights: conditions, notice periods and required handover deliverables.
- Rollback requirements: vendor must maintain and provide tested backups and a documented rollback plan for major changes.
- Dispute path: internal remediation steps, mediation/arbitration or courts as agreed; define acceptable technical evidence (logs, snapshots, diffs).
8. Sample clauses and pre‑start checklist
- Appendix templates: account inventory table, SLA table by severity, acceptance sign‑off form, incident report template, pre‑go‑live checklist and post‑go‑live verification list.
- Pre‑start checklist for procurement: scope confirmed, accounts identified, SLA agreed, acceptance criteria signed off, data protection obligations set, content ownership agreed, rollback and backup validated, primary technical contacts listed.
Note: specific SLA timings, retention durations and penalty amounts must be negotiated. Items left unspecified in this draft should be highlighted and verified by legal/technical teams before signing.
Questions & Comments
You can ask a question about this article. Viet SEO will review and reply after moderation.