An SEO scope of work turns a commercial objective into work that can be prioritized, implemented, accepted and measured. Copy the template below, adapt every placeholder and attach the result to a properly reviewed agreement.
This is an operating template, not legal advice. It does not replace qualified counsel, procurement, privacy, security or jurisdiction-specific contract review.
Searchmaxxed uses this operating logic to connect technical, page, authority and measurement work inside a managed SEO system.
If you already have a draft SOW, run it through the SEO scope of work checklist rather than starting again.
The SEO SOW in one page
Complete this control page before expanding the detail.
| Field | Agreed position |
|---|---|
| Client and provider | [legal names] |
| Term or project period | [dates or review cycle] |
| Commercial job | Improve discovery and conversion for [offer] in [market] |
| Primary business outcome | [pipeline / revenue / bookings / sales / other] |
| Search surfaces | [Google organic / local / AI features / named answer products / other] |
| Current baseline | [source, date range, actual state and limitation] |
| First priority | [technical / pages / local / authority / conversion / measurement / governance] |
| First release | [specific output or live change] |
| Provider lead | [name and authority] |
| Client lead | [name and authority] |
| Implementation owner | [name or team] |
| Approval owner | [name or role] |
| Reporting cadence | [weekly operating / monthly decision / other] |
| Pricing model | [project / retainer / advisory / sprint / hybrid] |
| Critical exclusions | [list] |
| Exit requirement | [account, asset, evidence and open-work handover] |
If this page cannot be completed, the engagement needs discovery before a large execution scope.
Copyable SEO scope of work template
1. Parties and purpose
Client: [legal entity]
Provider: [legal entity]
Effective date: [date]
Term or project period: [date / review cycle]
Purpose: The provider will [diagnose / advise / implement / manage] the agreed search work for [offers, markets and properties] under this scope.
Keep legal interpretation, liability, payment enforcement and governing law in counsel-reviewed agreement terms.
2. Commercial objective
Improve discovery and conversion for [offer] among [customer] in [market], measured through [search evidence] and [commercial outcome], while respecting [capacity, margin, brand, legal or compliance boundary].
Define:
- valuable offers;
- customers and qualification;
- markets, locations and languages;
- conversion events;
- revenue or gross-profit measure where available;
- capacity constraints;
- compliance or claims controls; and
- explicitly excluded outcomes.
3. Properties and search surfaces
List exact:
- domains and subdomains;
- applications or storefronts;
- Google Business Profiles and locations;
- country/language versions;
- repositories and environments;
- analytics and tag containers;
- reporting properties;
- third-party profiles;
- traditional search surfaces;
- local surfaces; and
- named AI answer products or prompt panels, if in scope.
Do not write “all digital properties” unless the list and access are genuinely known.
4. Baseline and evidence
Baseline date range: [dates]
Latest final data date: [date]
Sources: [Search Console / analytics / CRM / rank evidence / local / logs / other]
Known limitations: [privacy suppression / attribution / missing events / incomplete access / other]
| Evidence layer | Target | Actual | Source | Limitation |
|---|---|---|---|---|
| Availability | [state] |
[state] |
[source] |
[limit] |
| Discovery | [state] |
[state] |
[source] |
[limit] |
| Visibility | [state] |
[state] |
[source] |
[limit] |
| Visits | [state] |
[state] |
[source] |
[limit] |
| Conversion | [state] |
[state] |
[source] |
[limit] |
| Qualification | [state] |
[state] |
[source] |
[limit] |
Record unavailable data as unavailable, not zero.
5. In-scope workstreams
Select only the work justified by diagnosis.
| Workstream | In scope | Boundary |
|---|---|---|
| Market and demand research | [yes/no] |
[markets, competitors, queries and outputs] |
| Technical SEO | [yes/no] |
[templates, systems and implementation] |
| Information architecture | [yes/no] |
[page families, routes and navigation] |
| Commercial pages | [yes/no] |
[types, volume method and approval] |
| Supporting content | [yes/no] |
[brief, expert input, production and editorial QA] |
| Local search | [yes/no] |
[profiles, locations, reviews and site work] |
| Authority | [yes/no] |
[reclamation, PR, links, listings and standards] |
| Structured data | [yes/no] |
[eligible types and implementation] |
| Conversion | [yes/no] |
[pages, forms, experiments and events] |
| Measurement | [yes/no] |
[sources, events, reports and ownership] |
| AI-search observation | [yes/no] |
[engines, modes, prompts, market and event definitions] |
| Governance and training | [yes/no] |
[teams, controls and outputs] |
6. Deliverable schedule
Use one row per output or repeatable deliverable class.
| ID | Output | Reason | Surface | Provider action | Client action | Acceptance evidence | Outcome measure |
|---|---|---|---|---|---|---|---|
SEO-001 |
[artifact or live change] |
[priority] |
[URL/system] |
[action] |
[action] |
[test/readback] |
[evidence] |
Examples of operational language:
- “Rewrite, approve, publish and verify the
/services/xpage”; - “Implement canonical rule on
[template]and validate[sample set]”; - “Create decision-ready migration tickets with affected URLs, test and rollback”;
- “Recover client ownership of
[profile], verify facts and log all changes”.
Avoid:
- “ongoing optimization”;
- “technical improvements”;
- “quality backlinks”;
- “AI visibility”;
- “content support”; and
- “monthly reporting”
unless the scope translates each phrase into outputs, owners and proof.
The SEO deliverables library provides practical output and completion-evidence examples for the schedule.
7. Work states and acceptance
Work is reported as one of:
recommended,approved,implemented,verified,observed,blockedorrejected.
Define:
- who can approve each release class;
- what provider delivery means;
- what production implementation means;
- the acceptance test;
- the review period;
- correction or rework rules;
- deemed acceptance, if counsel approves it;
- rollback requirements; and
- how defects are escalated.
A recommendation is not a completed implementation.
8. Roles and responsibilities
| Role | Named owner | Decision or action | Service expectation |
|---|---|---|---|
| Executive sponsor | [owner name] |
Commercial priority and escalation | [timing] |
| Search lead | [owner name] |
Strategy and prioritization | [timing] |
| Subject-matter owner | [owner name] |
Facts and claims | [timing] |
| Editorial approver | [owner name] |
Voice and content approval | [timing] |
| Development owner | [owner name] |
Code and release | [timing] |
| Analytics owner | [owner name] |
Events and data definitions | [timing] |
| Legal/compliance | [owner name] |
Regulated claims and review | [timing] |
| Production approver | [owner name] |
Final release approval | [timing] |
Name a backup and escalation path for material roles.
9. Access, security and account ownership
Define:
- required accounts and permission levels;
- who owns each primary account;
- secure invitation or credential method;
- least-privilege boundaries;
- production and sensitive-data restrictions;
- logging and audit requirements;
- incident notification;
- access review cadence; and
- revocation at exit.
The client should own the business’s core accounts wherever possible.
10. Measurement and reporting
The provider reports:
- work completed and current state;
- evidence and reason for the work;
- movement across available layers;
- attribution limitations and anomalies;
- blockers, risks and decisions;
- next priority and release.
For AI answer products, define retrieval, mention, citation, link, visit and conversion separately.
Attach a metric dictionary:
| Metric | Definition | Source | Owner | Limitation |
|---|---|---|---|---|
[metric] |
[exact definition] |
[system] |
[owner] |
[limit] |
11. Dependencies and assumptions
Examples:
- client provides correct business and product facts;
- named reviewers meet agreed response times;
- development capacity exists;
- current access and data are materially complete;
- production platform behaves as documented;
- third-party policies and interfaces may change;
- legal review is available for regulated claims;
- market, demand and competitor conditions may change; and
- search systems retain control of crawling, indexation, serving and ranking.
An assumption should trigger review when it proves false.
12. Exclusions and third-party costs
List:
- development beyond named systems;
- design, photography or video;
- translation;
- legal or compliance services;
- paid media;
- public relations or placement fees;
- paid tools and data;
- hosting and platform fees;
- customer research;
- review acquisition;
- historical remediation;
- after-hours incident work; and
- markets or properties outside scope.
State whether prices include GST and other applicable charges in the commercial agreement.
13. Prioritization and change control
The backlog is prioritized by commercial impact, evidence confidence, effort, dependency, risk and time to useful observation.
Define:
- fixed versus adaptive deliverables;
- who can reprioritise;
- change-request threshold;
- price and schedule effect;
- incident override;
- approval method;
- decision record; and
- treatment of displaced work.
14. Commercial schedule
| Item | Amount or method | Trigger | Invoicing | Acceptance dependency |
|---|---|---|---|---|
[phase / retainer / milestone] |
[price] |
[date/event] |
[terms] |
[if any] |
Base any performance-linked payment on a clearly defined metric, a stable source and an attribution method both sides accept.
15. Ownership and handover
At exit, provide:
- confirmed client-owned access;
- source files, content, code, briefs and approved assets;
- live URL and redirect inventory;
- profile and account roles;
- analytics and metric definitions;
- authority, outreach and placement records;
- open backlog, defects and risks;
- approved facts and claims;
- current baseline and final report; and
- recommended next actions.
Define any provider-owned private methods or tooling separately.
16. Sign-off
Client authorised representative: [name, role, date]
Provider authorised representative: [name, role, date]
Attachments: [agreement, data/security schedule, deliverable register, baseline, pricing, other]
SOW quality-control table
Before approval, run this final check:
| Question | Yes/No | Required fix |
|---|---|---|
| Can a new operator explain the commercial job? | ||
| Is the baseline dated and sourced? | ||
| Does every deliverable have an owner and test? | ||
| Is implementation capacity real? | ||
| Are reporting layers and limitations explicit? | ||
| Are dependencies and exclusions visible? | ||
| Are unsafe or guaranteed claims prohibited? | ||
| Can priorities change through a recorded process? | ||
| Does the client keep accounts, assets and evidence? | ||
| Has appropriate legal counsel reviewed the agreement? |
FAQ
What is an SEO scope of work?
It is the operating schedule that defines the commercial objective, properties, baseline, work, deliverables, responsibilities, acceptance, measurement, dependencies, change, pricing and handover.
Is this SEO SOW template a contract?
No. It is a delivery template designed to sit within or alongside a properly drafted agreement. Have appropriate legal counsel adapt the legal terms for your jurisdiction and risk.
How specific should deliverables be?
Specific enough to identify the output, reason, affected surface, owner, acceptance evidence and outcome measure. Adaptive priorities can remain flexible when the decision process is explicit.
Should the SOW include a timeline?
It should include delivery dates, review cycles, dependencies and decision points. It should not turn those operating dates into guaranteed ranking, traffic, lead or revenue dates.
Who should own implementation?
Name the owner for every deliverable. The provider, client or both can implement, but the scope must define capacity, approval, acceptance and verification.
How should AI-search work appear in an SOW?
Name the engines, modes, prompt or question panel, market, observation method and event definitions. Separate retrieval, mentions, citations, links, visits and conversions.
When should the SOW change?
When a material assumption, dependency, market condition or priority changes. Use the agreed change-control process so flexibility remains visible and priced.
For an ongoing engagement, pair this template with the guide to SEO retainer deliverables, cadence and KPIs.