SEO Proposal Scope Checklist: Find the Work Hiding Outside the Retainer

01

Checklist

• Identify the service model, covered properties, and measurable deliverables.
• Assign implementation, deployment, verification, access, and client dependencies.
• Document additional charges, ownership, supplier risk, support, and offboarding.

02

Name the service model

• Advisory engagement.
• Project implementation.
• Managed recurring service.
• Staff augmentation.
• Hybrid model with responsibilities separated.

Google’s hiring guidance lists distinct provider activities such as technical advice, content development, market research, training, and implementation support. Those activities do not automatically belong to one product merely because the proposal calls all of them SEO. ^[1]

Write down who diagnoses, prioritizes, specifies, implements, deploys, verifies, and operates the recurring process. A proposal can include technical SEO while excluding developers. That may be legitimate advisory work, but it is not the same purchase as technical implementation.

03

Define the property and market scope

• Domains and subdomains.
• Protocol and host variants.
• Markets and countries.
• Languages.
• Business locations.
• Apps, social channels, and platform properties.
• Staging and preview environments.
• Acquired or redirected domains.

Avoid phrases such as all company websites unless the complete inventory is attached.

04

Convert deliverables into units

• Ongoing content needs a number, format, research standard, and cadence.
• Technical optimization needs an audit scope, specification, implementation capacity, and QA.
• Reporting needs sources, definitions, filters, cadence, and commentary.
• Link building needs a method, qualification standard, ownership, and disclosure.
• Local SEO needs locations, profiles, citations, reviews, and support boundaries.
• Strategy needs decisions, roadmap, prioritization, and an implementation owner.

State quantities, quality criteria, cadence, unused-capacity treatment, revisions, and correction obligations. A deliverable list with no units is not flexible. It is difficult to verify by design.

05

Separate advice from implementation

For every recommendation, record the finding, specification, implementation owner, deployment owner, acceptance test, and monitoring owner.

• Engineering included or excluded.
• CMS entry included or excluded.
• Media production included or excluded.
• Legal and subject review included or excluded.
• Translation and localization included or excluded.
• Analytics implementation included or excluded.

The companion strategy-versus-implementation article applies when the quoted fee funds diagnosis but the repair layer remains a separate budget.

06

Define client dependencies

• Access delivery.
• Developer availability.
• Content approval.
• Subject experts.
• Legal review.
• Product data.
• Release windows.
• Executive decisions.

For each dependency, state the deadline and what happens to the provider’s schedule when it is late. Do not permit every delay to become a client dependency after the fact. The dependency must be named before it affects the commitment.

07

Control access

• Client retains account ownership.
• Provider receives least-privileged users.
• Shared passwords are prohibited.
• Production publishing authority is explicit.
• Emergency access is time-bounded.
• Subcontractor access is disclosed.
• Access removal is defined.

Google recommends limited access during evaluation and tells owners to review proposed changes and explanations rather than surrendering control at the start of the relationship. ^[1]

08

Require evidence and acceptance

• Source standard.
• Audit evidence.
• Test environment.
• Acceptance criteria.
• Defect classes.
• Correction window.
• Approval authority.
• Final version record.

Google’s current third-party SEO guidance advises site owners to evaluate external recommendations against official documentation, ask providers to qualify claims, and avoid treating third-party tools as Google endorsements. ^[2]

A screenshot can support an observation. It does not automatically prove the cause, implementation, or business impact.

09

Inventory software and pass-through costs

• Dedicated client licenses.
• Shared agency software.
• Seats.
• Tracked keywords.
• Crawl or API usage.
• Storage and retention.
• Reseller margin.
• Automatic renewal.
• Export and exit.

Classify each charge as included, direct pass-through, cost plus margin, or optional.

10

Define change orders

A scope change should record the baseline, requested change, new work, schedule impact, price, assumptions, acceptance, and approval.

• Ordinary clarification is not billed as expansion.
• Provider correction is not billed as new work.
• Material work begins only after approval.
• Rush premiums have an evidence basis.
• Overage has a cap.

GAO’s cost-estimating guidance emphasizes a technical baseline, work breakdown structure, assumptions, risk, documentation, and updates with actual cost. Those disciplines make change pricing more defensible. ^[4]

11

Check subcontractors and supplier risk

• Roles are disclosed.
• Data access is disclosed.
• AI use is disclosed when material.
• Conflicts are disclosed.
• Replacement and continuity are defined.
• Security requirements flow downstream.

NIST’s current supplier due-diligence guide recommends evaluating provenance, stability, foundational security practices, resilience, and downstream dependencies before acquisition. ^[3]

12

Define support and incidents

• Covered hours.
• Severity definitions.
• Acknowledgement target.
• Diagnosis target.
• Containment target.
• Communication cadence.
• Exclusions.
• Service credits or remedies.

Do not convert a ranking outcome into a service-level guarantee. The provider can commit to actions and evidence it controls.

13

Preserve ownership

The client should own or receive accounts, exports, reports, source files, code, content, media-rights records, keyword and URL inventories, dashboards, documentation, and correction history.

Any license granted instead of ownership should be explicit and adequate for continued operation.

14

Define offboarding

• Notice period.
• Final deliverables.
• Open-work classification.
• Account transfer.
• Data export.
• Source and code handoff.
• Subcontractor deletion.
• Credential rotation.
• Final invoice and credits.
• Transition support.

The vendor-offboarding playbook provides the operational sequence. The proposal should fund or at least require that sequence before a dispute occurs.

15

Normalize total expected cost

Calculate total expected cost as setup charges plus recurring fees, implementation, tools, internal labor, approved changes, and exit costs.

• Setup charges.
• Recurring fees.
• Implementation.
• Internal labor.
• Software.
• Usage.
• Travel or expenses.
• Rush work.
• Exit.

The lowest retainer can be the highest expected cost when implementation and internal labor are hidden outside it.

16

Completion criteria

Approve the proposal only when it states what service is being bought, which properties and markets are covered, what is delivered and how often, who implements and deploys, what the client must provide, what evidence proves delivery, what creates an extra charge, who owns accounts and data, how suppliers and conflicts are handled, how support works, and how the relationship ends.

A proposal should make later invoices boring. If the scope becomes understandable only after the first change order, the ambiguity was not harmless. It was inventory.

References

Sources behind this record

1. Do you need an SEO? — Google Search Central (accessed August 3, 2026)
2. Google Search guidance on third-party SEO tools, services, and advice — Google Search Central (accessed August 3, 2026)
3. NIST SP 1326: Cybersecurity Supply Chain Risk Management Due Diligence Assessment Quick-Start Guide — National Institute of Standards and Technology (accessed August 3, 2026)
4. Cost Estimating and Assessment Guide — U.S. Government Accountability Office (accessed August 3, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.