What Counts as Scope in an SEO Retainer?
Scope disagreements rarely start as arguments, they start as quiet mismatched assumptions. Here's what's usually included in an SEO retainer, and what isn't.
“Scope” is the single most disputed word in any SEO retainer, and also the one businesses check least carefully before signing. Almost every scope disagreement traces back to the same root cause: the word “SEO services” meaning something different to the client than it does to the agency.
What’s almost always inside standard scope
- Keyword research and search intent mapping for agreed target terms
- On-page optimization for existing priority pages: title tags, meta descriptions, header structure
- A defined volume of new content production, whatever number was specifically agreed, not an open-ended amount
- Standard technical SEO monitoring: crawl errors, indexation issues, basic Core Web Vitals tracking
- Monthly reporting against agreed KPIs
What’s frequently assumed to be included, but often isn’t
- Code-level technical implementation: most SEO retainers diagnose technical issues but don’t include actually writing and deploying the code fix, that’s often a separate developer responsibility.
- Paid media management: even when an agency also offers PPC services, it’s typically a separate scope and separate cost unless explicitly bundled.
- Major site migrations or redesigns: these usually require a separate, one-time project scope on top of the standing retainer, given how much extra work a platform switch actually involves.
- Content beyond the agreed volume: if your business suddenly needs 15 articles in a month instead of the agreed 4, that’s additional scope, not something the existing retainer absorbs.
- Local SEO and Google Business Profile management: sometimes bundled, sometimes a distinct add-on, worth confirming explicitly rather than assuming.
- Backlink outreach volume: “link building” as a line item can mean anywhere from 2 to 20 placements a month depending on the agency, always confirm the actual number.
Why this ambiguity causes real damage
Scope disputes rarely show up as a dramatic argument. They show up as quiet disappointment, a client assuming something was included, an agency assuming it wasn’t, and neither side realizing the mismatch until months in, when trust has already eroded over something that could have been a two-minute conversation at the start.
The fix: get scope itemized, not summarized
Before signing anything, ask for scope broken into specific, countable items: how many articles per month, how many link placements, whether technical implementation is included or just diagnosis, whether local SEO is covered, all of which should already have come up if you briefed the agency properly. A proposal that only says “comprehensive SEO services” hasn’t actually defined scope yet, regardless of how detailed the surrounding language sounds.
Build in a change process for anything outside scope
Needs genuinely change over time, that’s normal. What matters is having an explicit process for it: additional scope requires written agreement and an agreed rate before work begins, rather than either side assuming extra work will simply be absorbed for free or silently billed after the fact.
A simple question that surfaces most scope gaps
Before signing, ask directly: “if we needed X, Y, or Z, would that be included in this retainer, or a separate cost?” naming a few specific scenarios relevant to your business. The answer, and how confidently it’s given, tells you whether scope has genuinely been thought through or is still vague enough to cause a problem later.
