An SEO retainer is a recurring service relationship, not a guaranteed position or a bundle of monthly tasks. Two proposals may use the same label while covering very different work: technical diagnosis, content, analytics, development, reporting, or only recommendations. Compare what the provider will inspect, change, document, and measure before comparing the monthly fee.
For a business in MENA, also clarify which markets and languages are in scope, how Arabic and English pages will be handled, who approves content, and whether local-market work depends on the client’s product, sales, or support teams. A retainer cannot promise rankings, indexing, AI citations, or a fixed amount of qualified demand. Google’s people-first content guidance emphasizes useful, reliable content and warns against producing many pages primarily to attract search visits. Google Search Central: Creating helpful, reliable, people-first content
Define the outcome and the starting evidence
Ask what business objective the engagement supports: qualified organic visits, visibility for a set of relevant queries, better discovery of important pages, or improved conversion paths from search. These are different measures and do not move in lockstep. Agree on a baseline window, the source system, timezone, page set, and definitions before work begins.
Separate leading indicators from business outcomes. Crawl errors fixed, pages discovered, impressions, clicks, and engagement are useful operational or search signals. An inquiry counts as qualified only under a stated rule; revenue requires confirmation from the business system. Reports should identify gaps and attribution limits rather than claim every change caused a sale.
Compare deliverables, ownership, and dependencies
Request a scope table that names the recurring work, its output, owner, review cadence, and client dependency. A clear proposal might distinguish an audit, prioritized backlog, approved implementation, content brief, technical QA, and performance review. “SEO optimization” is too broad to price or accept without defining the tasks.
| Scope area | Questions to resolve |
|---|---|
| Technical health | Which templates, routes, and issues are inspected? Who implements fixes? |
| Content | Is the provider auditing, briefing, editing, or writing? Who verifies subject facts and approvals? |
| International and language | Which markets and locales are included? Who checks localization, URLs, and language signals? |
| Measurement | Which properties and systems are used? How are leads or sales validated? |
| Development | Is engineering time included, advisory only, or separately scoped? |
| Reporting | What decisions should the report enable, and who acts on the findings? |
Write down access needs and least-privilege roles. Clarify who owns accounts, documents, source files, and changes when the engagement ends. The client should retain access and be able to understand what was changed.
Test the proposal’s method before signing
Ask the provider to walk through one real page or representative issue. Can they explain the evidence, expected impact, implementation risk, acceptance check, and rollback or recovery plan? Do they distinguish a recommendation from a completed change? Can they show how they decide that content is useful for a reader rather than merely keyword-shaped?
For Arabic and English work, ask who reviews language quality and market fit. Literal translation can preserve keywords while losing the actual reader’s query and context. Confirm whether the provider understands existing URL structure and will avoid URL changes without a documented migration plan. Ask how they handle pages that should remain unchanged.
Clarify what is excluded: web development, design, legal review, new photography, paid tools, link acquisition, customer research, and copy approvals may be separate. “Unlimited” deliverables still have capacity limits; ask how priorities are set when the backlog exceeds the hours available.
Use a scorecard that exposes uncertainty
Score each proposal against the same criteria: business fit, audit quality, implementation ownership, editorial standards, language capability, measurement integrity, communication, access governance, and total operating cost. Set weights before reviewing bids. For every score, record evidence or mark it “unknown.” Do not award high marks because of a polished deck or a ranking guarantee.
Check the economics using your own capacity assumptions: provider fee, internal review time, engineering time, content approval, and any optional services. A lower fee can require substantial client implementation; a higher fee can still be poor value if the work does not match the need. Compare the expected operating load as well as cash outlay.
Field experiment thread: Compare proposals on one shared brief
This is a procurement method, not a claim that a specific vendor will produce a result.
1/ Give every candidate the same small brief: site type, target markets and languages, known constraints, and one representative page or issue.
2/ Ask each to return a short diagnosis, proposed first deliverable, implementation owner, validation method, dependencies, exclusions, and risks.
3/ Score the responses against a rubric prepared in advance. Keep “unknown” separate from “poor”; missing evidence is a question for follow-up.
4/ Ask the same follow-up questions about URL changes, account access, content approvals, AI-assisted drafts, and measurement attribution.
5/ Compare proposed effort and client time, not only the fee. Record assumptions about engineering capacity and editorial review.
6/ Select the provider whose method and responsibilities fit the business constraints. Do not treat a promised ranking or traffic number as evidence of likely performance.
Tool-neutral prompt pack: Review an SEO proposal consistently
Remove credentials and confidential customer information. Use the same scoring rubric for every proposal.
“Evaluate this SEO proposal for a [site type] serving [markets] in [languages]. Our business goal is [goal], current evidence sources are [systems], and constraints include [capacity, approvals, URL policy, and budget boundary]. Extract deliverables, owners, cadence, client dependencies, exclusions, access needs, measurement definitions, risks, and claims that lack evidence. Compare them with this rubric: [criteria and weights]. Do not predict rankings, indexation, traffic, or revenue. Mark each criterion as supported, unclear, or missing and cite the proposal section. End with the follow-up questions that would materially change the decision.”
Check the summary against the proposal itself. A language model can organize a bid but should not decide access, legal terms, or business fit on the company’s behalf.
Short-video script: Compare SEO retainers before price
Opening: “Before choosing an SEO retainer, ask what work and evidence the monthly fee actually covers.”
Scene 1: Show a scope table. “Audit, implementation, content, QA, and reporting are different deliverables.”
Scene 2: Show an owner column. “Who does the work, who approves it, and what does your team need to provide?”
Scene 3: Show an evidence column. “A ranking promise is not a measurement method.”
Close: “Compare scope, implementation capacity, language quality, access, and total operating cost.”
Educational carousel: A fair SEO retainer review
- Name the objective: what business decision should organic search support?
- Set the baseline: source systems, period, page set, and definitions.
- List deliverables: output, owner, cadence, and acceptance check.
- Include dependencies: client approvals, engineering, and subject-matter review.
- Check MENA coverage: markets, Arabic and English, and localization ownership.
- Review measurement: separate search signals from qualified inquiries and sales.
- Calculate full cost: provider fee plus internal and engineering time.
- Treat guarantees carefully: rankings and citations cannot be promised as fixed outcomes.
Stop-doing swipe file: Replace vague scope and ranking promises
Stop: “We guarantee page-one rankings.”
Use: “We will investigate [pages and queries], implement [approved work], and report [defined measures] over [period]. Search outcomes are not guaranteed.”
Stop: “Content optimization is included,” without explaining whether the provider writes, edits, briefs, or implements.
Use: “This scope includes [specific deliverable]. Your team owns [facts, approvals, or publication].”
Stop: “Unlimited work every month.”
Use: “The monthly capacity is [hours or output], prioritized using [decision rule]; work beyond that is reviewed separately.”
Stop: “Traffic increased, so revenue increased because of SEO.”
Use: “Search clicks changed by [value] in [system and period]. Qualified inquiries and verified sales are reported separately with [definitions].”
Hook–Value–Template: Ask for a verifiable monthly scope
Hook: “A useful SEO retainer explains what gets done, who owns it, and how the work is checked.”
Value: “Scope and evidence make proposals comparable. They also show whether the business can provide the approvals and engineering capacity the plan requires.”
Template: “For [site/market/languages], the retainer delivers [outputs] each [cadence]. [Provider role] owns [tasks]; [client role] supplies [inputs and approvals]. We validate changes using [checks]. We report [search indicators] separately from [qualified inquiry or commercial outcome] using [systems and definitions]. Excluded work is [list]. URL changes require [documented review]. No ranking or AI citation outcome is guaranteed.”
Source notes for reviewing the proposal
Use the provider’s actual contract and the business’s operating constraints to make the selection. This framework does not establish current market prices or guarantee that any retainer will improve search performance.