SEO Agency Contract Disputes

Why the contract rarely defines the deliverable

SEO retainers are written in categories, not artifacts. On-page optimization. Content strategy. Link building. Technical audit. Monthly reporting. None of those phrases has a definition with an edge to it, and none is defined anywhere with authority a court could adopt. The consequence is structural: performance is almost never measurable against the contract's own terms, so the dispute becomes an argument about what the words meant.

That is where a technical expert can help and where one can overstep. The opinion that fails is the agency did not perform, because adequacy in a field with no published baseline is an opinion about a standard the witness invented. The opinion that holds is narrower: what artifacts exist, when they were created, what was published, what changed on the site and on what date, and whether the work product corresponds to the invoiced categories.

That opinion is built from files, not from a judgment about whether the work was any good.

The artifacts that answer the question

Every category in a typical retainer leaves traces. The work is to find them and put them on a timeline against the invoices.

• Version control and CMS revision histories, with author and timestamp for each change to a page.
• Deployment logs and staging records, showing when a change reached the live site rather than when it was written.
• Ticketing and project-management exports, with task, assignee, created date, and closed date.
• Published URLs with first-crawl evidence, taken from Search Console's URL Inspection data — the lastCrawlTime field records when Google last fetched the page — and corroborated with archived captures.
• Link acquisition records: target URL, source URL, anchor text, placement date, and cost.
• Invoices, mapped line by line onto all of the above.

The mapping is the deliverable. An invoice for content strategy in a month with no CMS revisions, no closed tickets, and no newly crawled URLs is a fact, not an accusation, and it can be evaluated without accepting anyone's view of what content strategy means.

Guaranteed-ranking clauses and what they leave undefined

Google's published position is unambiguous: no one can guarantee a #1 ranking on Google. The same page lists guaranteed-ranking claims, a claimed special relationship with Google, and priority-submit offers as warning signs.

A guarantee clause creates a problem for both sides. For the plaintiff it converts an unmeasurable services obligation into a measurable one, and it is a plain-language promise a jury understands. For the defendant it is usually drafted loosely enough to be attacked on its own terms. Guaranteed first page for which query? In which country and city? On which device? Measured by which tool, at what time?

A ranking is not a scalar. Google itself documents that results differ by time, location, language, device, and personalization. A guarantee that does not specify its measurement conditions is a guarantee of an undefined thing, and an expert can establish that without a word about enforceability. The common defensive drafting — money back, a guarantee across a basket of long-tail queries, a guaranteed improvement in an aggregate visibility score — shifts the measurement question rather than resolving it. Visibility scores in particular are proprietary vendor indices with no published definition.

Retainer, renewal, and suspension patterns

These disputes recur in a small number of shapes, and identifying the shape early tells you what evidence matters.

• Automatic renewal and notice periods. Termination is attempted after the notice window closes and the agency invoices the balance of a renewed term.
• Minimum term with front-loaded effort. The agency argues that the heavy work — audit, migration, initial content build — occurred in the first months and that the back end of the term was the payoff.
• Scope creep. Additional sites, locations, or languages absorbed into one retainer and later invoiced.
• Suspension for non-payment. The agency removes work product, disables tracking, or lets a tool subscription lapse.
• Pass-through costs. Link placements, writers, and tool licenses billed at cost or markup with no documentation of the underlying spend.

The suspension cases are where a technical opinion carries the most weight. Removing a script, reverting a template, or deleting placed links produces observable changes with dates attached, which can be compared against the payment history.

Who holds the accounts when the engagement ends

Account control in the Google ecosystem is not a matter of who holds the password, and this is the part clients understand least.

Search Console. Ownership is proven by a verification token, not by an account. A verified owner holds a token — an HTML file uploaded to the site, a DNS record, or a tag. A delegated owner was granted owner status without one. If every verified owner is removed, Google states that remaining users lose access after a grace period, and that data continues to be collected but nobody can reach it. Verification tokens persist on the site unless deleted, so whoever controls the DNS or the file system controls verification. Establishing which verification method was used belongs in the first request for production. See Google's documentation on users and permissions.

Google Analytics 4. The asset that matters is not the login, it is the historical data, and the data is bound to the property. Creating a replacement property does not migrate history. Retention is a property setting rather than a fixed period, so it has to be checked for the specific property; a property left unchanged may be holding as little as two months of event-level data. Google states that the retention setting does not affect standard aggregated reports, so an opposing expert who says the analytics data is gone because retention was set low is overstating it.

Google Business Profile. Only owners can add or remove users or delete a profile; managers do everything else. A profile must have at least one other owner or manager before primary ownership can be transferred. Where the holder is unresponsive, a request for access gives the current owner three days to respond, after which the requester may have the option to claim the profile — with Google's caveat that the option is not always available. It is the asset most often lost in an agency separation, because it is frequently created under an agency-controlled account and the reviews are bound to the profile.

Content, code, and link assets after termination

Three questions get conflated whenever a client says the agency took the work.

Copyright in the content. Absent a written assignment or a valid work-made-for-hire arrangement, authorship and ownership are not automatic, and agencies routinely subcontract writing, which puts a third party into the chain of title. The CMS author field is where that records exercise starts.

The hosting and the code. Where the agency built the site on its own infrastructure or on a proprietary content management system, termination can leave the client holding a domain name and nothing else. The technical question is what is portable: the database, the templates, the media library, the redirect rules.

Link assets. This is the one clients least expect, and where the agency placed links through its own network, its own guest-post relationships, or paid placements, those links can be pulled on termination — and the removal is testable. Capture the linking pages before and after, compare against any placement log produced, and check the Links report in Search Console. Note the tension: paid link placement is itself a link spam violation under Google's published policies, so an agency that documents its placements documents its own violations. That is why placement logs are among the most contested items in these cases.

Proving performance, and the two metrics that will never agree

When the question is whether the site performed, the sources have a defensible order of preference.

1. Search Console performance data for the engagement window, exported at the full sixteen-month range at daily granularity, by query and by page. Two limits produce arguments: the table displays a maximum of 1,000 rows, and rare queries are anonymized and omitted from the table while still counting in chart totals.
2. Server access logs, which record actual requests and do not depend on whether a browser ran JavaScript.
3. Analytics standard aggregated reports, which survive the retention setting.
4. Archived captures of the site and of results pages.
5. Third-party rank trackers and visibility indices, last, with their limitations stated on the exhibit.

Search Console and Analytics will never match, and Google documents why. Analytics depends on a tag and on how it was implemented. Consent management and opt-outs suppress it. Search Console defaults to Pacific Time while an Analytics property has its own time zone. Search Console counts every click in Google Search while Analytics applies an attribution model. Search Console reports on the Google-selected canonical URL while Analytics reports on any URL carrying the tag. And Analytics excludes known bots while Search Console does not necessarily filter them.

An expert who puts Search Console clicks and analytics sessions on the same axis without addressing those divergences has handed the cross-examiner a gift. Pick one metric per question and reconcile the other in a footnote. Google's own comparison of the two tools is the citation.

Where the opinion overreaches

Three overreaches account for most of what gets struck in these matters.

The first is opining on adequacy. The work was substandard requires a standard, and in this field the standard has to be built from dated sources before it can be applied. If the report does not show that construction, the sentence is the witness's preference wearing a suit.

The second is opining on the contract. Whether a deliverable was contractually required, whether a renewal clause was triggered, whether a guarantee is enforceable — none of that is technical, and a technical witness who answers it invites exclusion of the whole opinion.

The third is causal overreach. Establishing that an agency deleted 400 pages is a factual finding. Establishing that the deletion caused a revenue decline requires ruling out concurrent changes and a method that survives scrutiny — a separate question, and usually a separate witness.

One contract artifact is worth flagging because it is new. Google's data anomalies record shows FAQ rich results permanently discontinued as of 7 May 2026. A retainer that promised FAQ schema for rich results is now promising a result type that no longer exists. The date is a fact an expert can establish; what it does to the contract is counsel's question.

Frequently Asked Questions

Published 2026-08-11