Is It Out of Scope? — SEO & marketing
Is integrating a new third-party API out of scope for an SEO / marketing project?
Yes, clearly — this is development work, distinct from the reporting-platform connections (analytics, Search Console) that most SEO retainers already assume as part of doing the job.
Worth separating two things that get conflated: connecting to a reporting/data API (Google Analytics, Search Console, a rank tracker) is baseline SEO tooling most retainers already assume — that's not what this is about. A request to integrate a new third-party service into the client's actual site or stack (a CRM, a marketing automation tool, a booking system) is development work that happens to be adjacent to marketing, and it's outside an SEO retainer's scope.
Is it out of scope?
Yes, for site/stack integrations. Reading data from analytics or search-console-style tools for reporting purposes is normal SEO work and shouldn't be confused with this; wiring a new tool into the client's actual website or systems is a development task the retainer doesn't cover.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Development/integration work is a standard exclusion, distinct from the analytics-platform read access most SEO retainers assume.
Example contract wording
Example contract wording (illustrative, not legal advice)
Happy to pull reporting from [tool] as part of our regular work — that's already covered. Integrating it into your site or CRM directly is development work outside the retainer; let us know if you'd like a referral, or we can scope that piece separately if you'd rather we handle it.
How MarginFlow flags it
MarginFlow distinguishes reporting-tool connections (inside_scope, routine) from site/stack integration requests (outside_scope) by weighing what the integration actually does, not just whether it mentions an API — this keeps the classifier from either over-flagging routine reporting requests or missing genuine development asks dressed up as "just connecting a tool."