SEO Contracts: What to Check Before You Sign One

An SEO contract is the commercial agreement that fixes what an agency owes you, for how long, what it costs, and what you keep when the relationship ends. Most of the page-one results on the subject are blank templates rather than guidance, and a template answers only the questions its author thought to include. This guide is written for the other side of the table: the founder, CMO or head of growth with an agreement sitting in their inbox and a signature due. It walks the document clause by clause and says what each line actually decides, what to ask for, and which versions to refuse.

To be clear about the scope: this is a review checklist, not a contract template and not legal advice. It will tell you which lines deserve a second read and what to ask about them. Anything material should go to a lawyer before you sign it.

The short version

• Across the page-one results we reviewed in September 2026, the dominant format is a blank downloadable template rather than buyer-side guidance. The questions built into a template are the seller's questions, not yours.
• Four clauses decide what happens when an engagement goes wrong: term length, notice, ownership of the work product, and transfer of accounts. The rest is negotiable detail.
• No one can guarantee a ranking, and Google says so in writing. A contract that implies otherwise is telling you something about the provider before any work starts.
• Access is not ownership. In Google Search Console a verified owner cannot be downgraded to a lower permission level, only removed, and their verification token has to be deleted as well.
• The exit test: read the whole document as though the engagement ends in month four, then write down what you still have.

What is an SEO contract, and what is it actually for?

It fixes four things: scope, time, money, and ownership. Everything else in the document exists to support one of those four.

The word contract covers several shapes. A master services agreement plus a statement of work splits the legal terms from the deliverables so the scope can change without renegotiating the whole document. A single-document retainer folds both together. A project agreement covers one defined piece of work, such as a migration or a technical audit, and ends when it is delivered.

What all three have in common is that they are risk allocation documents. They are not a description of the SEO strategy, and a good agreement does not need to contain one. Read the document for what happens when things go badly, because that is the only question it exists to answer. The strategy lives in the proposal; the leverage lives here.

What should be in an SEO contract?

Thirteen clauses, and only about half of them are about search. The table below is the review pass: read each line of the agreement against the middle column, then use the right-hand column as the thing to raise before signing.

Clause	What it actually decides	What to ask for
Scope of work	Which requests are included and which trigger a new fee	Named workstreams, plus an explicit list of what falls outside them
Deliverables versus effort	Whether you are buying named outputs or a block of hours	Whichever one you actually want, stated as such, not both at once
Term and auto-renewal	How long you are committed and how the commitment repeats	Term and renewal written as two separate decisions
Notice and termination	How you leave, how fast, and what it costs	Termination for convenience, with a notice window you can actually meet
Reporting cadence	How often you see results and in what form	A fixed cadence and a named set of metrics, in writing
KPIs and outcome language	Whether any result is promised, and what happens if it is missed	Leading indicators the agency controls, never a ranking position
Content and creative ownership	Who holds the rights to articles, briefs, designs and assets	Assignment to you on payment, stated for each asset type
Links and placements	What happens to earned coverage if you stop paying	A written commitment not to request removal of placements
Account access and transfer	Who controls Search Console, Analytics, the CMS and the hosting	Your accounts, agency added as a user, not the reverse
Work product at exit	What is handed over, in what format, and by when	A named handover list with a deadline attached to it
Exclusivity and non-compete	Whether the agency can work with your competitors, and whether you can hire elsewhere	Clarity in both directions, with the category defined narrowly
Indemnification	Who carries the cost if the work causes a third party to bring a claim	Symmetry, and a cap you have actually read, rather than a one-way obligation
Fees, escalators and pauses	What you pay, when it rises, and whether you can pause	The renewal price and the pause terms written down, not left to a later notice

Five versions to refuse

Some clause language is a signal on its own, regardless of how the conversation has gone. These five are worth stopping the process over.

• Silent renewal with a short window: the agreement renews for a full further term unless you cancel inside a narrow period, and nothing obliges the agency to remind you. A renewal you can miss by forgetting is not a renewal you agreed to.
• Termination only for cause: you may leave only if you can prove the agency breached the contract. In practice that means you are unlikely to leave, because the thing you are disappointed about may never have been promised in the document at all.
• Ownership conditioned on completing the term: content and assets transfer to you only if the engagement runs to its natural end. This converts your own published material into a hostage.
• Agency-held accounts: Search Console, Analytics or the CMS sit in the agency's account and you are granted access, rather than the other way round. You are then renting visibility into your own website.
• A promised position: any wording that commits to a specific ranking, a page-one placement, or a traffic figure by a date. Treat it as disqualifying and read the rest of the section below.

How long should the term be, and should you accept auto-renewal?

Long enough for the work to produce something worth judging, short enough that leaving does not require a negotiation. Those two pressures point in opposite directions, which is why the term is the clause most worth spending your negotiating capital on.

There is no defensible number to quote here, and anyone quoting one is describing their own pricing rather than a standard. What there is instead is a test. Ask the agency when the first meaningful checkpoint falls for your specific site: the point at which the technical work is done, the first content has been crawled and indexed, and there is enough signal to tell whether the plan is working. Then set the term to reach that checkpoint and no further. Our guide to realistic timelines for SEO results explains where that checkpoint actually falls, and why a term that ends before it tends to close on a mutual shrug.

Auto-renewal is a separate decision, and the easy mistake is to read it as part of the term. A renewal clause is acceptable when three things are true: the notice window is long enough to act on, the renewal price is written into the document, and the renewal period is shorter than the initial term. A renewal that repeats the full original commitment at an unstated price is a second contract you did not read.

When a longer term is genuinely in your interest: if the work involves a migration, a large technical rebuild, or a content program with a long production lead time, a short term forces the agency to front-load quick wins over the structural work you are actually paying for. Length is not automatically the seller's friend.

Who owns the content, the links and the accounts when it ends?

Three separate questions, and an agreement can answer one of them cleanly while leaving the other two open. This is the section that costs the most when it is left vague, because none of it matters until the day it is the only thing that matters.

Content and creative: the document either assigns the intellectual property to you, licenses it to you, or says nothing. The clause may sit under a heading about intellectual property or work-for-hire rather than the word ownership, so search the document for all three. Silence is the problem, and it is the case to check for deliberately rather than assume away. Look for whether the assignment covers every asset type you are paying for, because a clause naming articles may not cover briefs, keyword research, design files, or the strategy document itself. Look for whether the assignment is conditioned on anything. Full payment is a reasonable condition to find there. Completion of the term is not.

Links and placements: nobody can transfer ownership of a link, because it sits on a third party's website and the third party decides whether it stays. What can be written down is a commitment not to request removal after the engagement ends, and a handover of the placement list with live URLs. The second item is the one people forget, and without it you cannot tell what you paid for.

Accounts: this is where the contract language and the technical reality come apart, and it is worth knowing the mechanics before you negotiate the clause. In Search Console, Google's documentation on managing owners, users and permissions distinguishes a verified owner, who proved ownership with a verification token, from a delegated owner, who was granted the status by a verified owner. A delegated owner can be removed by any owner. A verified owner is different: their access can be removed but not downgraded, and their verification token must be deleted too, or they can simply verify again.

The practical consequence is a clause worth adding yourself. If the agency verified the property, removing them is a two-step job and the second step is easy to miss. Ask for the verification method to be documented at the start of the engagement, and for the handover list to name the token or DNS record explicitly.

Analytics has a parallel trap at a different layer. Google's documentation on adding, editing and deleting Analytics users notes that a user added at the account level also has access to every property in that account, with the same permissions. An agency added at account level to run one website can see all of them. Check the level, not just the name on the list.

The rest of the stack: the CMS, the hosting, the domain registrar, and any third-party tooling bought on your behalf. The rule that resolves all of them is the same: the account is yours and the agency is a user on it. If an agreement proposes the reverse for operational convenience, the convenience is real and so is the cost.

What should the contract say about reporting and KPIs?

A cadence, a named metric set, and a source of truth. Three specifics, and an agreement that names all three has closed the gaps that reporting arguments come from.

Cadence is the easy part: a monthly rhythm is a reasonable default, and a clause promising "regular reporting" promises nothing. The metric set is where the negotiation is. Ask for the report to name the metrics in advance, so that a bad quarter cannot be reported through a different lens than a good one. Our breakdown of what a monthly SEO report should contain covers the difference between a report that shows progress and one that shows activity.

The source of truth matters more than it sounds. A report built from the agency's own rank tracker and a report built from your Search Console property can tell different stories about the same month, and only one of them is your data. Specify that the underlying data comes from accounts you own.

On KPIs: the useful ones are the inputs the agency genuinely controls, such as pages shipped, technical issues resolved, or placements earned. Outcome metrics like traffic and revenue belong in the report as context, not in the contract as a commitment. A clause that ties payment to a ranking position is not a stronger contract; it is an incentive to chase the cheapest query that satisfies it.

Can an SEO agency guarantee results, and what if the contract implies it?

No, and Google states it directly in its own documentation. The Search Central page Do you need an SEO? puts it in one line: "No one can guarantee a #1 ranking on Google." The same page adds a warning worth reading twice: "Beware of SEOs that claim to guarantee rankings, allege a 'special relationship' with Google, or advertise a 'priority submit' to Google."

That covers the obvious case. The version you are more likely to meet in a contract is softer and harder to argue with: a performance schedule, a milestone table, or a clause offering free months if agreed targets are missed. It reads as accountability, and it can be meant that way.

Read what the target is measured against before you accept it. A guarantee attached to a keyword nobody searches for, or to a metric the agency can influence by choosing which pages to report on, transfers no risk at all. The question to ask is simple: who picks the keyword list, and can it change after signing? If the answer is the agency and yes, the guarantee is decoration.

There is a quieter failure mode worth guarding against: a commitment made warmly in the pitch that never reaches the document, and therefore has nothing behind it at the moment it starts to matter. If something was promised verbally and you are relying on it, the response is not to distrust the person who said it. It is to ask for it in the agreement, and to notice what happens next.

How should the money clauses work?

Predictably, and with every increase visible in advance. The fee is the easy number to scrutinize. The clauses around it are where the cost hides.

• Escalators: a clause raising the fee on renewal by a stated percentage is fine when the percentage is stated. One that allows an increase "on notice" is an open-ended price.
• Pass-through costs: tools, content production, freelancers and media spend. Ask whether these sit inside the retainer or are billed on top, and whether a markup applies.
• Pause rights: engagements get paused for budget freezes, funding rounds and migrations. A pause clause that caps the duration and holds the price is worth asking for before you need it.
• Scope reduction: check that the agreement describes what happens when scope shrinks, not only when it grows. A fixed fee against reduced work is the quiet version of a price rise.

If the fee itself is the open question rather than the terms around it, our guide to how SEO gets priced breaks down the retainer, project and hourly models and where each one tends to break. It is worth reading before the contract stage, because the pricing model determines which clauses in this checklist even apply to you.

Is a no-contract or rolling arrangement better?

Sometimes, and the honest answer depends on which risk you are more exposed to. A rolling month-to-month arrangement is a reasonable default when the work is well defined, the provider is new to you, or the budget is genuinely uncertain.

It carries a real cost worth naming. An agency on thirty days of notice is rationally incentivized toward work that shows movement inside thirty days, which is not the same as work that compounds. Technical debt, information architecture, and content that takes two quarters to mature all lose out to a structure that could end before they pay off.

Arrangement	Fits when	Costs you
Rolling, no fixed term	New provider, defined scope, uncertain budget	Bias toward short-horizon work; weaker planning
Fixed term with termination for convenience	Ongoing work with structural components	A notice period commitment, in exchange for a usable exit
Fixed term, cause-only exit	Rarely, and only with a provider you have worked with	Your leverage, entirely

Our recommendation is the middle row. A fixed term gives the agency the planning horizon that structural work requires, and a termination-for-convenience clause with a fair notice period gives you the exit that makes the term safe to accept. The two together are better than either alone, and asking for both is a reasonable request that a confident provider will not resist.

If what you want is direction rather than a delivery team, that is a different engagement shape, and the clauses that fill this checklist carry far less weight in it. A consulting arrangement is scoped around a roadmap and a set of decisions rather than ongoing production, so there is less work product to hand back at the end. Organic growth consulting is the version of that shape we offer.

What should you ask before you sign?

Two sets of questions: the ones about the provider, and the ones about the document. Both sets belong in the same conversation.

Google lists eight questions to ask a prospective SEO. Among them: show examples of previous work and success stories, whether they follow the Google Search Essentials, what results they expect and in what timeframe, how they measure success, their experience in your industry, and whether they will share every change they make to your site along with the reasoning behind their recommendations. That last one carries the most weight here, because it is the habit a handover clause depends on. For judging the provider rather than the paperwork, our guide to choosing an SEO partner covers the selection criteria.

The document questions are shorter, and a provider comfortable with their own agreement will not mind them:

1. What is the notice period, and when does the clock start?
2. Can the agreement be terminated without proving a breach?
3. Does the renewal price appear anywhere in this document?
4. Which assets transfer on exit, and is the transfer conditioned on anything?
5. Whose Google account will Search Console and Analytics live in?
6. What exactly is handed over at the end, and by when?
7. Which of these commitments are in the contract, and which were only in the pitch?

Question seven is the one that changes conversations. Ask it late, after the enthusiasm has been established, and listen to whether the answer is "let's add it" or an explanation of why the document is fine as it stands.

What is the exit test?

A single pass over the agreement, read as though the engagement ends badly in month four. Not month twelve, and not by mutual agreement. Month four, awkwardly, because that is the scenario the document exists for, and the one least likely to be modeled while the plan still sounds exciting.

Answer these six questions using only what is written in the document. If any answer requires a phone call, an assumption, or a sentence beginning "they'd probably", that clause needs work before you sign.

1. Can you leave? Find the termination clause and the notice period. Write down the earliest date you could actually be out.
2. What does leaving cost? Remaining fees, early termination charges, and anything payable on handover.
3. What do you keep? List the content, assets, research and documentation that transfer to you, and check whether the transfer is conditioned on completing the term.
4. What can you still log into? Search Console, Analytics, the CMS, the hosting, the registrar, and any tool paid for on your behalf. Name the account holder for each.
5. What breaks? Anything running on agency-owned infrastructure: tracking scripts, redirects, landing pages, plugins, or a staging environment.
6. What proof survives? The placement list, the change log, and the reporting archive. If none of these is promised in writing, you will be reconstructing the engagement from memory.

Questions four and six are the ones to run first. Both are easy to leave out of a document, both are fixable with a single email before signing, and both are close to impossible to fix after a relationship has soured.

The habit worth building

Read every commercial agreement from the ending backwards. Scope and price are what the conversation is about, and they are also the two things you can renegotiate later without much difficulty. Term, notice, ownership and access are the clauses that decide what you are holding on the worst day of the engagement, and they are close to impossible to improve once the document is signed.

This week, take whichever SEO agreement is currently in front of you, or the one you signed last year and have not reread, and run the six exit-test questions against it. Twenty minutes. If any answer is missing, you have found the clause to raise, and the request is reasonable enough that raising it costs you nothing. If you want a second read on the SEO work itself rather than the paperwork, see how we run SEO as an acquisition engine.