Is It Out of Scope? — Web design
Is migrating SEO tracking after a site redesign out of scope for a web design project?
Yes. Reconnecting tracking codes and analytics properties is technical implementation work outside a design deliverable list.
A visual redesign can knock out tracking snippets that were pasted into the old templates, and the client's first instinct is often to ask the design team — who touched the pages — to just put it all back.
Is it out of scope?
Yes. Re-wiring tracking codes and confirming they fire correctly is implementation work, not a design deliverable, even if the redesign is what disrupted it.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Tracking implementation and analytics configuration sit outside a design engagement's deliverable list.
Example contract wording
Example contract wording (illustrative, not legal advice)
The redesign covered the visual and layout work — reconnecting tracking codes and analytics properties is a technical task outside what we scoped. That's better handled by whoever manages your dev or analytics setup.
How MarginFlow flags it
MarginFlow flags tracking-migration and analytics-reconnection requests outside_scope on design contracts, since implementation tasks fall outside every category a design SOW typically covers.