How to Write a Scope of Work for an SEO Campaign

Write an SEO SOW That Defines Work, Review and Payment#

An SEO statement of work connects the campaign promise to tasks that someone can deliver, review and pay for. Name the site, market, outputs, implementation owner and billing events before work starts. The example below uses a fixed-fee campaign; adapt its quantities and terms to the engagement you actually sell.

Step 1. Separate proposal, SOW, and master agreement#

A proposal describes the offer and price; a statement of work sets the agreed work, dates and handoffs. A master services agreement (MSA), if used, holds recurring legal terms. You can combine them in one agreement for a small project. Identify the incorporated documents and the order of precedence, because a document’s title alone does not determine its binding effect. Read more about the proposal and SOW distinction.

Step 2. Draft for five predictable failure points#

For scope creep, record the original URLs, markets, deliverables and implementation duties. Agree how authorized contacts approve changes, including price and schedule. This is a proposed commercial process, not a rule imported from federal procurement: FAR 43.103 also permits certain unilateral government modifications and does not govern an ordinary private SEO contract. Correcting work that fails the agreed standard remains part of the original obligation; it is not automatically a paid change.

Name a primary approver and backup. State the review window, what a rejection must identify and how you respond. Keep acceptance, invoice issuance and the payment due date separate: an invoice can follow delivery if that is what the parties agreed, while a valid defect still requires correction. A missing approval should trigger the agreed follow-up rather than leave the next action undefined.

Cross-border enforcement is another place where sloppy drafting creates avoidable risk. Keep the SOW consistent with the signed dispute mechanism in the contract set, whether that is court or arbitration. Do not overstate what will be easy to enforce across countries.

Identify project-created material, pre-existing templates and third-party assets separately. If U.S. copyright law applies, §204 generally requires a copyright ownership transfer to be in writing and signed by the rights owner or authorized agent, with an exception for transfers by operation of law. Merely handing over a file does not transfer its copyright. Define any assignment or license and its payment condition in the signed agreement; work-for-hire and assignment are different mechanisms.

Step 3. Run this pre-kickoff check#

Before kickoff, confirm these basics:

• Every output has a quantity, delivery date, responsible owner and test for completion.
• The client supplies the agreed access and implementation owner; added work follows the agreed change process.
• Invoice triggers, review/correction steps, dispute route and ownership terms agree across incorporated documents.

That is your minimum baseline. The next section turns those checks into clause-level drafting.

What each of the seven SOW sections should include#

Use these seven sections to draft a campaign that can be operated from the page. Oregon’s SOW writing guide is a public-procurement reference for tasks, responsibilities and acceptance standards; the illustrative commercial clauses below are not mandatory statutory wording. Example engagement: one English-language site, one U.S. market, 20 named priority URLs, a technical recommendation log, five content briefs and a campaign report over four weeks. Implementation and content production are excluded.

Scope wording that is specific#

Scope is where a lot of preventable friction starts. Tighten it early so the rest of the document has a clear boundary.

Deliverable acceptance criteria that can reduce disputes#

Test completion against the deliverable, rather than an uncontrolled ranking result. Google’s hiring guidance warns that nobody can guarantee a number-one ranking. Record organic clicks, impressions and business conversions as campaign measures, with the period and data source specified; distinguish those goals from the acceptance tests for the work you promise.

Milestone-to-invoice mapping that finance can follow#

Choose the invoice trigger deliberately and attach evidence. In this illustrative $6,000 project, a $2,000 advance is invoiced on signature and credited against the $3,000 audit phase. A further $1,000 is invoiced on complete audit submission, and $3,000 on submission of the five briefs and final report. The total is $6,000, not $8,000. These are submission-based billing terms; acceptance and correction remain separate. State the agreed due-date anchor and follow the overdue payment process if needed.

1) Define the objective. Separate the business goal from the work commitment. For this example, the aim is to improve the site’s organic acquisition by identifying technical issues and preparing useful content plans. Search engines, competitors, client implementation and buying behavior affect the eventual result.

• Sample objective: “Provide the audit, recommendations, five briefs and report specified in Exhibit A for the named site and market over four weeks.”
• Track the agreed campaign measures against a stated baseline and comparison period. Record major site changes and missing analytics data alongside results.
• Make acceptance depend on the agreed outputs and quality criteria, rather than a promised ranking, traffic increase or revenue total.

2) Define scope and exclusions. Attach the URL list and identify whether the engagement is an audit, implementation, content production or recurring support. A recommendation to repair a template is a different deliverable from changing and testing that template.

• Sample scope: “Review the 20 URLs in Exhibit A and provide recommendations on crawl/index status, page metadata, internal links and content gaps. Review site-level evidence relevant to those URLs.”
• Sample boundary: “The client implements recommendations through its developer. New pages, markets, languages, article writing, migrations and provider CMS changes are excluded.”
• If a site-level issue requires work beyond the named review, describe it in the recommendation log and quote implementation separately; do not silently convert the audit into development.

3) List deliverables and acceptance. Give the client a workable review process. In this example, the primary marketing approver has five business days after each complete delivery to accept it or identify specific unmet criteria, copying the backup approver.

• Sample review clause: “The client supplies one consolidated response identifying the affected deliverable and unmet criterion within five business days. The provider corrects agreed nonconformities without an additional fee and resubmits.”
• Include one consolidated preference-revision round for each brief within the original audience and subject. Changing the market or requesting additional briefs follows change control. Required corrections are distinct from discretionary revisions.
• If the approver is unavailable, contact the named backup and document affected dates. In this example silence is not deemed acceptance; delivery-based invoicing still follows the agreed event, with valid defects handled through the correction/dispute process.

4) Map milestones to invoice triggers. State the amount and whether the trigger is signature, submission, acceptance or a calendar event. The advance funds work and is credited to a phase; it is not an extra fee or proof that the phase has been earned.

• Sample billing clause: “The total project fee is USD 6,000 before any separately applicable tax. Invoice USD 2,000 on execution,USD 1,000 on complete audit submission and USD 3,000 on complete final submission, as shown in the payment schedule.”
• Project day 1 begins only once the agreement is executed, the advance is received and required access is available. The advance is due before work begins; the later invoices are due 15 calendar days after receipt of a proper invoice.
• Name the finance address, purchase-order requirement, remittance reference, permitted payment methods and responsibility for transfer fees. If conversion is permitted, agree its rate source and date rather than leave the amount to a later interpretation.

5) State assumptions, dependencies and client responsibilities. Allocate access, content facts, implementation and approval to named roles. For the audit, request read access to Search Console and analytics; additional permissions need a reason tied to included work.

• Sample access clause: “Before project day 1, the client supplies read access to Search Console and agreed analytics, the priority URL list and the named marketing, developer and finance contacts.”
• The client provides accurate product facts and legal/brand approval. Its developer implements and tests recommended changes unless implementation is expressly included. The provider records which recommendations were implemented before attributing results.
• If access or a required input is late, notify the client, identify the blocked task and continue unaffected work. Record a revised affected delivery date and any proposed extra cost in the agreed written process; a missing login does not automatically justify pausing every task.

6) Control revisions, changes and early stop scenarios. Compare a request with the agreed output and standard before pricing it. A missing source in one of the five agreed briefs is a correction. Five additional briefs are added scope. An internal underestimate is not by itself a client-authorized change.

• Change example: “Add five briefs for the same site at USD 200 each:USD 1,000 additional fee; move the affected batch date by five business days. The named client and provider contacts approve the revised scope, fee and date before added work begins.”
• If the change is declined, continue the original deliverables where feasible. Keep the request and decision with the SOW version; do not treat informal enthusiasm as approval of a price.
• Agree cancellation valuation before kickoff. Example only: the USD 3,000 audit phase is allocated USD 1,500 to the completed crawl/evidence component and USD 1,500 to analysis and recommendations. If cancellation occurs after only the first component is completed and earned under those terms, apply USD 1,500 of the USD 2,000 advance and refund USD 500, assuming no other agreed charges. Do not use an undefined “nonrefundable deposit” to skip reconciliation.
• Specify the notice method, due date for the final statement, treatment of approved external costs and handoff of paid work. If cancellation happens after different work is completed, calculate the balance from the agreed component values rather than reuse the USD 500 figure.

7) Align payment, disputes and ownership. Put recurring legal terms in the MSA if used and identify exactly where the SOW relies on them. Use the agreed notice and cure process before a permissible suspension; a payment issue is not permission to delete site content, revoke client-owned accounts or withhold everything indiscriminately.

• State the invoice dispute window, evidence required and treatment of undisputed amounts. Resolve a genuine delivery defect through correction, then apply the agreed billing remedy to the affected amount.
• Specify any lawful late-payment remedy and its trigger under the applicable contract and law. Country-specific statutory interest is not a universal cross-border penalty; verify the relevant regime before inserting a rate.
• Identify final project-created reports and briefs covered by an assignment or license, any payment condition, and rights needed to use retained templates or third-party material. Client-owned accounts, existing content and credentials remain separate.
• Align governing law, court forum or arbitration mechanism, precedence and notice details across the contract set. Have the intended mechanism reviewed for the jurisdictions involved rather than promise automatic worldwide enforcement.

Before signature, read the SOW as the approver, the finance contact, and the replacement operator. If any of them would still need a call to understand boundaries, approvals, or payment triggers, revise the wording and validate the legal terms with qualified counsel.

Check the SOW Against a Real Delivery and Invoice#

A good SOW is your control point before work starts. It aligns both sides on deliverables, timeline, and cost in writing before anyone starts tracking time.

Walk through a delivery before signing: the audit arrives, the approver reports a missing evidence field, and finance receives the agreed USD 1,000 balance invoice after the USD 2,000 advance credit. The provider corrects the missing field without a new fee and follows the agreed treatment of any disputed amount. A request for five additional briefs is handled separately through the USD 1,000 change example. The contract should make each next action clear.

Before you send the SOW, run this final check:

1. Verify the site, market,20 URLs and five-brief quantity match the appendix and fee schedule.
2. Check access, implementation owner, delivery dates, review window, correction and included revision duties.
3. Reconcile USD 2,000+USD 1,000+USD 3,000 to the USD 6,000 total; confirm the advance is credited once.
4. Record the named approver, backup, finance contact and authorized change contacts.
5. Check added-scope approval, cancellation valuation and the final statement/refund process.
6. Confirm governing law, dispute route, precedence and rights for paid deliverables agree across the executed documents.

Apply this checklist to your current draft now, line by line, before you send it.