Is It Out of Scope? — SEO & marketing
Is adding a blog to the website out of scope for an SEO / marketing project?
Usually yes for the build itself, though it overlaps with content strategy the retainer may already cover — the build (template, page) is the out-of-scope part; the ongoing content plan may or may not be.
The SEO retainer scopes keyword research, on-page optimization, and a monthly content quota — writing and publishing a set number of articles into an existing blog. The client, mid-retainer, asks the agency to "just add a blog to the site" because they don't have one yet and assume it's part of the same service. It isn't the same thing: publishing content into a blog is what the retainer covers; building the blog itself — the template, the URL structure, the CMS setup — is development work the retainer was never scoped to include.
Is it out of scope?
The build itself is out of scope — most SEO retainers don't include site development, and building a blog section is exactly that. The retainer's content quota and optimization work are unaffected either way; the distinction worth making explicit to the client is "we can write the content once it exists, but building the page it lives on is outside what this retainer covers."
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Names what the retainer explicitly does not cover — site development and template building are a common exclusion even on comprehensive SEO/content retainers.
Example contract wording
Example contract wording (illustrative, not legal advice)
Our retainer covers keyword research, on-page optimization, and [X] articles/month — it doesn't include building new site sections or templates, which is development work outside this scope. If you don't already have a dev partner for the blog build itself, we can refer one, or scope it separately at [$X]. Once the blog exists, publishing into it is already covered under the retainer.
How MarginFlow flags it
For SEO/content clients, MarginFlow's classifier weighs the request against the retainer's extracted scope — the monthly content quota and optimization deliverables, not a generic "site work" bucket. A request to build a new page or template is flagged outside_scope even though it's adjacent to work the retainer does cover, with the explanation calling out that distinction explicitly ("content quota covers writing into an existing blog, not building one") so the account manager isn't left to make that judgment call cold.