An SEO retainer should buy an operating system for finding and fixing the next limit on search-led growth. The work should adapt as the website, market and evidence change rather than repeating the same monthly task list.
The retainer needs to define:
- the commercial outcomes and markets in scope;
- the search surfaces covered;
- what the provider can decide and change;
- who implements, approves and verifies work;
- how priorities change;
- which data both sides can access;
- how progress and uncertainty are reported; and
- what remains when the engagement ends.
If those things are vague, a detailed monthly task list will not save the engagement.
Decide whether a retainer is the right buying model
Use a retainer when the work requires recurring diagnosis, implementation, measurement and reprioritisation.
| Situation | Better starting model | Why |
|---|---|---|
| One known technical defect | Bounded project | Clear cause and finish line |
| Website migration | Project with pre/post-launch support | High-risk event with defined controls |
| Strategy exists; internal team implements | Advisory retainer or review cadence | Decision and QA capacity limit progress |
| Search spans technical, content, authority and conversion | Managed retainer | The next priority changes as work ships |
| No baseline or access | Paid discovery first | Scope cannot be priced honestly yet |
| Search is not commercially important | No retainer | Recurring work has no defensible business case |
| Internal implementation is consistently blocked | Fix ownership before adding SEO hours | More recommendations will deepen the backlog |
Ongoing SEO is useful when priorities will keep changing and the implementation path supports recurring work. For a side-by-side decision, compare a monthly SEO retainer with project-based SEO.
Put the commercial contract above the SEO task list
Define:
- products or services;
- customer types;
- markets and locations;
- valuable search journeys;
- primary conversion events;
- valuable-customer criteria;
- baseline pipeline or revenue where available;
- capacity and margin context; and
- excluded markets or offers.
Then state the job:
Improve valuable discovery and conversion for [offer] in [market], with target-versus-actual reporting across [search surfaces] and [commercial outcomes].
Without that boundary, “grow organic traffic” can reward the provider for attracting visitors who will never buy.
Scope the search surfaces
SEO can involve different systems:
| Surface | Typical work |
|---|---|
| Organic web | Technical discovery, page ownership, on-page work, content, internal links and authority |
| Local and Maps | Business Profile integrity, service/location architecture, reviews, local sources and conversion |
| Ecommerce search | Category/product architecture, crawl control, feeds, structured product data and revenue measurement |
| AI-assisted search | Publisher access, answer and citation observations, source-layer gaps and identifiable referrals |
| Site conversion | Message, proof, forms, calls, booking, qualification and measurement |
Name what is in and out. “SEO, AEO and GEO included” is not scope.
Google says the usual SEO fundamentals remain relevant to its AI features and that there is no special AI schema or machine-readable file required. A provider should not inflate the retainer with renamed standard work or magic markup.
Separate six responsibilities
For every work type, assign:
- Research: who gathers the evidence.
- Decision: who chooses the action.
- Production: who writes or builds it.
- Approval: who authorises claims or live changes.
- Implementation: who publishes or deploys.
- Verification: who proves the live state.
Use a responsibility matrix:
| Work type | Provider | Client | Dependency |
|---|---|---|---|
| Technical diagnosis | Owns evidence and priority | Supplies access | Search Console, logs, CMS |
| Developer ticket | Writes acceptance criteria | Developer accepts | Engineering capacity |
| Commercial page | Drafts and edits | Fact/claim approval | Offer and proof inputs |
| Publication | Implements or hands off | Approval boundary | CMS and release process |
| Authority campaign | Researches and executes | Approves brand use | Spokesperson and evidence |
| Reporting | Reconciles sources | Supplies CRM/revenue data | Source access and definitions |
If nobody owns implementation, recommendations will pile up and the provider can still claim the month was “delivered”.
Make the scope adaptive without making it vague
A useful retainer contains a controlled backlog, not unlimited discretion.
Each item needs:
- commercial reason;
- evidence;
- impact;
- effort;
- dependencies;
- owner;
- approval level;
- completion test; and
- outcome measure.
The monthly plan should select the highest-value work that is ready to move. If a critical item is blocked by client development, the provider should either remove the blocker, prepare a decision-ready handoff or move to the next defensible action, not quietly replace strategy with easy content volume.
Change control should answer:
- Who can move budget between technical, content and authority work?
- Which changes require approval?
- What happens when an incident displaces planned work?
- How are new sites, markets or page families priced?
- How are paused dependencies treated?
- When is the scope formally reset?
Define deliverables by proof
A deliverable should include:
- exact output;
- implementation state;
- completion evidence;
- commercial reason; and
- owner.
Keep these states separate:
| State | Meaning |
|---|---|
| Recommended | Decision-ready source or ticket exists |
| Approved | Responsible person authorised it |
| Implemented | Change is live |
| Verified | Live state passes acceptance tests |
| Outcome observed | Search or commercial evidence changed |
An approved draft is not a published page. A published page is not an indexed page. An indexed page is not revenue.
Use the SEO deliverables library to define individual outputs without turning the retainer into a rigid monthly menu.
Use a cadence that makes decisions
Live or continuous
- incident alerts;
- release verification;
- major crawl, form or tracking failures;
- approval and implementation blockers.
Weekly operating view
- what shipped;
- what is blocked;
- material search or commercial movement;
- decisions required;
- the next owned action.
Monthly review
- target versus actual;
- full change ledger;
- source-backed performance;
- valuable conversion and commercial evidence;
- budget or scope use;
- dependencies;
- continue, stop, repair, expand or test decisions.
Quarterly reset
- opportunity and market changes;
- route ownership and cannibalisation;
- technical and authority gaps;
- content performance;
- sales and capacity feedback;
- revised priorities and scope.
Meetings are not the cadence. Decisions are.
Choose KPIs by causal layer
| Layer | Examples | Limitation |
|---|---|---|
| Availability | Uptime, forms, call route, bot access | Does not prove search visibility |
| Discovery | Indexed intended pages, impressions, query coverage | Does not prove visits |
| Visibility | Position, local observation, answer mention/citation | Method and location matter |
| Visit | Organic or identifiable referral sessions | Attribution can be incomplete |
| Conversion | Calls, forms, bookings, trials or purchases | Can include poor-fit demand |
| Qualification | Service, location, value and customer fit | Requires operational feedback |
| Commercial | Pipeline, revenue and gross margin | Multi-touch attribution is imperfect |
Do not set “more rankings” as the top-line KPI. Set a commercial outcome, then use earlier layers to diagnose why it moved.
Where a source is unavailable, say unavailable. Missing GA4 access is not zero conversion. Missing CRM discipline is not evidence that traffic failed to create pipeline.
Protect account, asset and data ownership
The business should retain appropriate ownership and role-based access to:
- domain and DNS;
- CMS, code and hosting;
- Search Console and analytics;
- Business Profiles and merchant accounts where relevant;
- call tracking and form data;
- reporting sources;
- creative and content rights;
- outreach and placement records; and
- change history.
Google's hiring guidance recommends asking for a technical and search audit and checking that recommendations are supported by trusted sources. It also warns that nobody can guarantee a number-one Google ranking.
Shared passwords, agency-owned properties and unexportable dashboards create avoidable exit risk.
Put claim, policy and release boundaries in writing
Define:
- which claims require client approval;
- regulated or high-risk topics;
- evidence standards for case results;
- platform-policy boundaries;
- review and testimonial governance;
- who can publish;
- who can change profiles;
- backup and rollback requirements;
- incident escalation; and
- how errors are corrected.
This is not legal advice or a substitute for a properly drafted agreement. It is the delivery layer the commercial agreement must make possible.
Make reporting prove four things
- The work: exact outputs and live changes.
- The reason: the evidence and constraint behind them.
- The movement: search and commercial data, with limits.
- The decision: what happens next.
A provider should not need a heroic end-of-month deck to explain what happened. The change ledger and operating view should already tell the story.
Set a clean exit before work begins
The exit pack should include:
- client-owned access confirmed;
- content, code, briefs and source files;
- live URL and redirect inventory;
- profile and account roles;
- analytics and reporting definitions;
- authority and outreach records;
- open defects and risks;
- outstanding approvals;
- current baseline and final report; and
- recommended next actions.
The provider may keep its private methods and tooling. The business should not lose the assets, accounts and evidence it paid to create.
What a well-run SEO retainer looks like
- Forecasts state their assumptions and limits.
- Monthly priorities follow the current evidence and commercial opportunity.
- Every workstream has an implementation and verification owner.
- Reports show source access and the live changes behind the performance discussion.
- Content has clear route ownership, evidence and approval.
- Authority work identifies the relevant sources and quality standard.
- AI-search observations record the prompt, surface, date and source.
- Your business retains account, asset and data ownership.
- Ongoing work has specific decisions and outputs.
- Meetings end with decisions, owners and dates.
- Dependencies are visible early enough to manage.
- Exit produces a usable handover of access, assets, evidence and open work.
FAQ
What is an SEO retainer?
It is an ongoing commercial arrangement for recurring search strategy, execution, implementation management, measurement and reprioritisation. Its value depends on the operating system and ownership, not the fact that it bills monthly.
What should an SEO retainer include?
It should include outcomes and markets, covered surfaces, responsibilities, an adaptive backlog, deliverable proof, cadence, KPIs, source access, approval boundaries, exclusions, change control and an exit process.
Is an SEO retainer better than a project?
Use a retainer when the next priority will change and ongoing measurement and implementation matter. Use a project for a defined audit, migration, repair or build with a clear finish line.
How much should an SEO retainer cost?
Price should follow the scope, opportunity, complexity, implementation responsibility, authority gap, governance and evidence required. Compare exact ownership and outputs rather than accepting a universal market band.
How long should an SEO retainer run?
Long enough to address the agreed problem and observe the relevant evidence, with review and exit points defined. Do not invent a guaranteed performance date or use a long lock-in period as a substitute for a credible plan.
Which SEO KPIs matter most?
Start with valuable pipeline, revenue or another commercial outcome, then track the earlier layers that explain it: availability, discovery, visibility, visits, conversions and customer fit.
What if our team must implement the recommendations?
The scope should define decision-ready tickets, client implementation owners, capacity, acceptance tests and post-release verification. If the backlog cannot ship, fix that dependency before buying more recommendations.
Make every month build on the last
A strong retainer keeps the market, live website and commercial evidence in one decision loop. The work remains visible, priorities change for a reason and your team knows what happens next. See how that fits into the wider SEO system, then establish the operating controls during the first 30 days of SEO onboarding.