Is It Out of Scope? — SEO & marketing
Is adding schema markup beyond the original quote out of scope for an SEO retainer?
Usually yes. It's core technical-SEO work, but the retainer's schema coverage was quoted around specific page types or schema types — more of either is additional volume.
Schema markup is squarely SEO's discipline, so this one reads like it should always be included — but a retainer's technical-SEO scope is usually quoted against a specific page count or a specific set of schema types, not "all schema, indefinitely."
Is it out of scope?
Usually yes. Each additional schema type or page needs its own implementation and testing — it's more of the retainer's own work, but more than what was originally quoted.
Clause typically implicated
Clause typically implicated
Out-of-scope clause→ — Schema work is native to the retainer's technical-SEO scope; requests beyond the quoted types or page count are additional volume against that scope.
Example contract wording
Example contract wording (illustrative, not legal advice)
The quote covered schema for [types/pages listed] — expanding to [new type(s) or pages] is more of the same discipline, just beyond what was originally scoped. I can put together a quick add-on quote for it.
How MarginFlow flags it
MarginFlow compares the schema types and page scope named in a request against what the contract quoted and flags anything beyond that as outside_scope, framing it as a volume increase within the same discipline.