Hot take: most SEO contracts don’t fail because the agency is “bad.” They fail because the agreement is foggy, the expectations are vibes-based, and nobody bothered to define what “success” means in writing.
If you’re about to hire an SEO provider, your job isn’t to become an SEO expert overnight. Your job is to remove ambiguity. That’s it. Clarity beats charisma every time.
One line to remember: if it can’t be measured, it can’t be managed—and it definitely can’t be enforced.
Start here (yes, before tactics): what are you actually buying?
Some agencies sell “SEO.” Others sell content. Some are basically technical consultants with a few writers attached. A lot are project managers relaying work offshore. None of those are inherently wrong, but you need to know what’s being sold.
Ask this plainly:
– Are we paying for outcomes (leads, revenue influence) or outputs (audits, content, fixes)?
– Who implements changes—your team or theirs?
– What’s the model: retainer, project, performance-based, hybrid?
– What do you not do? (The best agencies answer this quickly.)
If they can’t explain their service like a menu, you’re not buying a service—you’re buying uncertainty. View more
The Pre-Sign Contract Checklist (the unglamorous stuff that saves you)
This section is more “specialist briefing” than friendly chat, because contracts are where SEO dreams go to die.
1) Pricing that doesn’t hide in the shadows
You want a pricing schedule that separates:
– setup/onboarding fees
– monthly retainer
– content production costs (per piece, per word, per brief—whatever they use)
– dev/engineering work (hourly? included? capped?)
– tools and subscriptions (Ahrefs/Semrush/etc.)
– add-ons and “nice-to-haves”
Also: ask how they handle scope changes. A simple change-control policy is boring… and incredibly expensive to not have.

2) Deliverables you can point to
A contract that promises “ongoing optimization” is basically a permission slip for vague work.
Request a deliverables table that includes:
– what gets delivered
– how often
– who owns it (agency or you)
– the acceptance criteria (what makes it “done”)
– how it’s handed over (Google Docs, CMS access, Git PR, etc.)
Ownership matters more than people think. You should own the assets you paid for: briefs, content, technical recommendations, templates, dashboards.
3) The documentation they should already have
If an agency is mature, they’ll have these docs or they’ll create them fast:
– onboarding questionnaire / client brief template
– glossary of terms (yes, really—SEO jargon gets abused)
– reporting sample (real format, not a vague promise)
– example roadmap with milestones
– sample content brief
– escalation path (who you call when things break)
Now, this won’t apply to everyone, but… if they act offended by documentation requests, that’s usually a sign they run on improvisation.
KPIs: don’t get hypnotized by rankings
Rankings are a means. Revenue is the point. I’ve seen businesses win “top 3 rankings” and still lose money because those pages didn’t convert, or targeted the wrong intent, or cannibalized existing traffic.
So set KPIs that track business impact and SEO progress.
A practical set might include:
Business KPIs
– organic leads / organic revenue (or pipeline influence if you’re B2B)
– conversion rate from organic sessions
– revenue per visit (or lead value per visit)
SEO KPIs
– non-branded organic traffic growth (brand can mask everything)
– share of voice / ranking distribution for a defined keyword set
– clicks and CTR from Search Console (CTR is underrated)
– indexation quality (how many pages indexed that shouldn’t be?)
– Core Web Vitals / key technical health metrics (only if relevant to your site)
Here’s the thing: you also need a baseline. If they won’t document baseline performance in week one, you’re flying blind for the entire engagement.
A stat that’s useful for expectation-setting: Google has said it can take “several months” for SEO changes to show results depending on the site and changes made (Google Search Central, SEO Starter Guide). That’s not an excuse for zero progress—it’s a reminder that you should measure leading indicators early.
Timelines & process (what a real plan looks like)
Some agencies hand you a “90-day plan” that’s basically three buzzwords and a dream. Don’t accept that.
A credible engagement usually has a rhythm like this:
Week 1–2: Discovery + baseline
Audit, analytics review, tracking verification, business goals alignment, keyword universe mapping.
Weeks 3–6: Priority sprints
Technical fixes with highest impact, internal linking structure, content refreshes, new content briefs, quick wins.
Ongoing: biweekly or monthly cycles
Publish/optimize, measure, adjust. Not random acts of SEO.
And yes, demand milestones. If the agency can’t put dates next to work, they’re not managing a project—they’re managing an invoice.
A good roadmap ties activities to expected impact like:
– “Fix index bloat → improve crawl efficiency → stabilize rankings for key directories”
– “Rewrite product category pages for intent match → lift CTR and conversion”
– “Build topical cluster around X → expand long-tail reach → increase qualified traffic”
Not perfect predictions. Just coherent hypotheses.
Content strategy: “more blogs” isn’t a strategy
Look, content calendars are easy. Content that ranks and converts is hard.
You want to see:
– how they choose keywords (intent first, not volume worship)
– how they map keywords to pages (to prevent cannibalization)
– what “quality” means in their system (depth, usefulness, first-hand experience, structure, internal links)
– how they handle approvals and revisions (two rounds? three? unlimited? that’s a cost driver)
Ask for 2–3 sample briefs. If the briefs are thin, the content will be thin. In my experience, great SEO writing starts with a great brief, not a heroic writer.
Reporting: show me the dashboard, not the narrative
If reporting is a monthly PDF full of screenshots, you’re going to hate your life by month three.
Minimum reporting standards I’d push for:
– shared dashboard access (GA4, Search Console, Looker Studio, whatever)
– trendlines over time, not single-point stats
– annotations for major site changes, releases, migrations
– “What we did / what changed / what we learned / what’s next”
– anomaly flags (traffic drops, indexing shifts, CTR dips)
And you should know exactly when you’ll meet. Weekly? Biweekly? Monthly? Who attends? Who makes decisions?
Communication cadence is not a soft skill. It’s operational risk management.
Agency fit: case studies should be usable, not shiny
A case study that says “we increased traffic 200%” is basically marketing confetti unless you can connect it to your world.
Ask for case studies with:
– similar business model (ecommerce vs SaaS vs local services matters)
– similar site complexity (10 pages vs 10,000 pages is a different sport)
– similar constraints (regulated industry, dev bottlenecks, long sales cycles)
Then push one level deeper:
What did they actually do? What changed? What resources did it take? How long until lift? What didn’t work?
If they can’t talk about failures or tradeoffs, you’re not hearing the real story.
Red flags (pause vs walk away)
Some red flags are “slow down.” Others are “run.”
Pause if you see this
– they won’t define KPIs, baselines, or reporting cadence
– timelines are vague (“we’ll start soon” is not a timeline)
– you can’t identify who’s doing the work
– everything sounds like a one-size-fits-all package
– they dodge questions with jargon (a classic)
End the deal if you see this
– guaranteed 1 rankings (still happens… absurd every time)
– refusal to share references or credible examples
– they want admin access to everything but won’t explain why
– contract auto-renews without clear exit terms
– deliverables are undefined, but the payment schedule is extremely defined
Also, watch for the sneaky one: “We can’t share our methodology.” That’s usually code for “We don’t have one.”
Contract terms that protect you when reality shows up
Because it will.
You want clarity on:
– termination terms (notice period, partial month billing, offboarding support)
– data portability (you keep dashboards, accounts, logins, files)
– confidentiality / NDAs
– who owns what (content, code, briefs, strategy docs)
– performance clauses (careful here—SEO isn’t fully controllable, but you can enforce deliverable and reporting standards)
One practical move: require a 30–60 day checkpoint written into the agreement. Not “results,” but verification that fundamentals are in place: baseline recorded, tracking validated, roadmap delivered, initial fixes shipped, first content briefs approved.
That checkpoint prevents long, quiet months where you pay and hope.
The critical step most people skip (and it’s the whole game)
Before signing, insist on a one-page success definition that both sides agree to.
Not a manifesto. A page.
It should include:
– target outcomes (business + SEO)
– what the agency controls vs what depends on you (dev, approvals, product changes)
– timeline expectations and what “early progress” looks like
– reporting cadence and decision-making process
I’ve watched this single page save engagements that would’ve otherwise imploded from misaligned expectations. It forces honesty early, when honesty is cheapest.
And if they won’t agree to it?
You just learned something valuable—before the contract taught you the hard way.