SEO Advisory vs. Implementation vs. Managed Service: What Are You Buying?

01

Definition

SEO is commonly sold as though it were one homogeneous service. It is not. Google’s current hiring guidance lists several distinct activities an outside SEO may perform, including reviewing content and structure, providing technical advice, developing content, researching keywords, training staff, and bringing market or geographic expertise. ^[1]

Advisory means the provider investigates and recommends. Typical outputs include an audit, strategy, roadmap, content brief, measurement plan, migration specification, vendor review, or experiment design. The client or another vendor implements the work.

Implementation means the provider changes content, code, configuration, data, redirects, structured data, CMS settings, analytics, dashboards, or deployment artifacts. Managed service means the provider repeatedly operates a function such as monitoring, publishing, reporting, local listing management, release QA, or incident support. Staff augmentation supplies people who work under the client’s priorities and processes.

These labels describe different allocations of authority, labor, access, and risk. They are not interchangeable synonyms for “monthly SEO.”

02

Mechanism

The service model determines who diagnoses, prioritizes, specifies, changes, deploys, verifies, and operates the system. A responsibility matrix makes that mechanism visible:

The exact matrix can differ. The missing cells cannot.

A competent advisory engagement identifies the question, scope, evidence, assumptions, recommendation, implementation owner, risk, expected verification, and unresolved uncertainty. Google advises site owners to ask providers to explain recommendations, cite official guidance, disclose proposed changes, and avoid guarantees. ^[2] Advisory work is complete when a decision is better supported, not merely when a slide deck reaches the inbox.

Implementation requires bounded write access, staging where practical, version control, test cases, rollback, a named approver, production verification, and defect correction. The implementer should not quietly become the sole owner of the client’s domain, analytics, repository, or Search Console property.

A managed service requires a recurring unit: monitoring coverage, publishing volume, support windows, incident severity, report cadence, implementation capacity, decision queue, and retained evidence. NIST supplier guidance emphasizes provenance, resilience, foundational practices, and downstream dependencies before acquisition. ^[3] Its broader supply-chain guidance treats supplier access, downstream services, resilience, and lifecycle risk as continuing governance responsibilities. ^[4]

Staff augmentation works differently. The client normally owns the backlog, supervision, technical direction, approval, quality standard, and deployment. The provider supplies capacity rather than an independently managed outcome.

03

Examples

A useful advisory engagement may diagnose a migration risk, produce a redirect specification, and identify the developer who must implement it. The advisor can later verify the release without ever holding production write access.

A project implementation may include structured-data code, CMS configuration, content changes, deployment support, and post-release checks. Its acceptance criteria should identify the exact pages, templates, status codes, fields, or events that prove completion.

A managed service may operate technical monitoring every week, maintain a publishing queue, investigate Search Console anomalies, and coordinate corrections under defined service levels. A monthly invoice labeled only “SEO management” does not identify that operating function.

A staff-augmentation engagement may provide a technical SEO specialist for forty hours per month under the client’s product manager. It succeeds when the client already has strategy, architecture, standards, and deployment authority. It fails when the buyer expects the contractor to discover the strategy while simultaneously behaving like an employee with no decision authority.

Hybrid engagements can be sensible: the advisor diagnoses, the client approves, the agency implements, managed monitoring verifies, and the client retains ownership. Each transition needs an owner. A proposal saying “technical recommendations included; development excluded” is especially dangerous because the buyer may assume the site will change while the provider believes the PDF is the product.

Access should also follow the model. Advisory normally needs public data, exports, or read-only accounts. Implementation needs bounded edit access and staging. Managed service needs recurring role-based access. Staff augmentation receives access defined by the assigned client role. Google specifically recommends read-only Search Console access during an initial audit. ^[1]

04

Boundaries

The right model depends on the missing organizational capability. Advisory is appropriate when the client can implement but lacks diagnosis or strategy. Implementation is appropriate when the client needs controlled changes. Managed service is appropriate when a recurring operating function needs an owner. Staff augmentation is appropriate when the client already owns prioritization and supervision but lacks capacity.

Pricing should follow the model. Advisory can use fixed scope or milestone pricing. Implementation can use fixed deliverables, units, or time and materials. Managed service can use a retainer or service-level structure. Staff augmentation commonly uses role and time. A one-time audit and a monthly monitoring service should not be compared as though their price units were equivalent.

Before signing, ask what capability is missing, who owns prioritization, who makes production changes, who approves risk, who verifies the work, what repeats monthly, what remains after termination, and what evidence proves delivery. A complete proposal identifies the service model, scope, implementation owner, access, output, acceptance criteria, service levels, client dependencies, retained evidence, and exit process.

The useful question is not “Do we need SEO?” It is “Which job needs an owner?” The acronym has been asked to conceal enough organizational ambiguity already.

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. NIST SP 800-161 Rev. 1: Cybersecurity Supply Chain Risk Management Practices — National Institute of Standards and Technology (accessed August 3, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.