SEO consulting contracts: scope, KPIs and exit clauses
What an SEO consulting contract should define: two-way scope, KPI selection, reporting duties, data ownership and exit clauses. Ten checks before signing.
By Roozbeh Nazari · CEO
Most disputes in an SEO consulting relationship come not from the quality of the work but from the fact that nobody wrote down what the work was. "Rankings will improve" sounds like a promise, but in a contract it means nothing definite: which queries, which market, which device, which date range? This article walks through the headings to check before signing a consulting contract, using the framework we apply in our own practice. It is not legal advice; discuss the legal side with your lawyer and the technical side with this list.
Scope: what will be done, and what will not
The longest section of the contract should be scope, and it should consist of two lists. First, what the consultant will do: a technical audit with prioritised findings, a content plan and briefs, on-page optimisation recommendations, post-implementation verification, a monthly report and meeting. Second, and more critical, what will not be done: who implements code changes, who writes the content, whose responsibility translation is, whether link acquisition is in scope. Leaving this second list empty is where the sentence "we assumed that was on your side" comes from six months later. We separated the consulting model from the implementation model, and when each makes sense, on our services page; you want to see the same separation in the contract.
The second part of scope is the working surface. On a multilingual site the word "site" is not enough: which locales, which subfolders or domains, which countries are the subject of the contract? On a clinic site, does the service provided for the Turkish pages also cover the Arabic and Persian versions, or are those a separate phase? The answer ties directly to budget and to KPIs.
KPI selection: measurable, influenceable, owned
A good KPI passes three tests. It must be measurable: its source should be data that sits in your own accounts, such as Search Console, GA4 or your CRM, not a "visibility score" produced by the consultant's own tool. It must be influenceable: a metric that can change through work inside the consultant's scope; if content writing is out of scope, an organic traffic target alone is not fair. It must be owned: next to every KPI, write down who owns the work that moves it.
In practice we use a three-layer KPI set. The outcome layer: the number of qualified organic enquiries, meaning form or WhatsApp submissions that the coordinator marks as real. The intermediate layer: clicks and impressions on the target query set, the share of target pages indexed, the share of URLs passing the "good" threshold in Core Web Vitals. The input layer: briefs delivered, technical findings closed, recommendations waiting for implementation. In the contract, the outcome layer serves as the target, the intermediate layer as early warning, and the input layer as accountability. We explained which layer maps to which report block in our article on report content.
One thing should not be written into a contract: a guarantee of a specific position for a specific query. Google's own "Do you need an SEO?" guide lists a consultant who guarantees rankings as a warning sign. Rankings depend on dozens of variables outside your site; they cannot be guaranteed, only measured and reported.
Reporting and meeting obligations
The frequency, format and data source of the report belong in the contract. Our recommendation: once a month, one page, with data pulled directly from the client's Search Console and GA4 accounts, reproducible by anyone with read access to those accounts. Next to the word "report", also write "access to raw data": if the consultant builds a dashboard in their own tool, the dashboard's source connections should live in the client's account, and the dashboard should stay with the client when the contract ends.
For meetings, a reasonable frame is one conversation a month, with an agenda and a decision log. The output of the meeting should be a list of decisions: who, what, by when. That list is the first item of the next meeting.
Ownership of data and access
The Search Console property, the GA4 property, the Tag Manager container, Business Profile management and the ad accounts should be tied to the client's own Google account; the consultant should be added as a user, not as the owner. Without this clause, the data history risks leaving with the consultant when the relationship ends. The same goes for content: delivered briefs, articles and technical documents belong to the client; if the consultant has the right to reuse them for other clients, that should be stated explicitly.
Exit clauses
The least-read and most-needed section of the contract. It should define four things. The notice period: one month is common and reasonable; longer periods kill budget flexibility. A trial period: a unilateral right to exit at the end of the first three months lowers the risk for both sides. Handover: on termination, what the consultant delivers, in which format, within how long; the open findings list, the content calendar, the access list and ownership of dashboards belong in that package. A ban on permanent dependencies: no component the site needs in order to run (a script, a proxy, a DNS record) should sit in the consultant's account; if one does, it moves before termination.
Pricing and payment model
The price itself is not the subject of this article; how the model is written into the contract is. A fixed monthly fee, a project fee and a performance-based fee each require a different scope definition; a performance model should not be signed until the contract states which KPI the fee is tied to and how that KPI is verified. We covered where each model breaks down in our comparison of pricing models. One more clause to add: how is out-of-scope work priced when it comes up? Without it, every new request turns into a negotiation.
Additional clauses for the health sector
For clinic and hospital clients we add two more clauses. First, a content approval flow: under the regulation on promotion and information in health services, every published text must be approved by the institution; the consultant proposes content, the clinic approves, and the division of responsibility is written in that order. Second, a list of prohibited claims: outcome guarantees, comparative superiority statements and demand-generating campaign language are out of scope, and the consultant has the right to refuse such a request. These clauses protect both parties.
Ten questions before you sign
Is the scope list two-directional? Is the working surface defined per locale? Is every KPI's data source in your account? Is there a ranking guarantee, and if so, why? Are the report frequency and format in writing? Do you have access to raw data? Are all Google assets tied to your account? Are the notice period and trial period defined? Is the handover package listed? How is out-of-scope work priced? Every item where you cannot get a "yes" will become a meeting agenda item some month later in the relationship. Writing it down at the start means not having that meeting. We described our own way of working, in this same order, on our approach page; the contract follows the same order.