Define the job before choosing a provider
List which work needs doing, who can change the site, and who will own outcomes. An internal team can develop business context over time. An agency may bring several disciplines sooner. A hybrid can pair internal ownership with external specialist support.
Decide which capability the business is missing
List the work that consistently gets postponed. A migration may need a technical specialist and developer access. A mature content programme may need an editor and research capacity. A multidisciplinary backlog can justify an agency or an internal team. Set a practical budget, define who can approve changes and ask whether the business can actually implement the work it commissions.
- List the missing capabilityIdentify what is delaying useful work
- Compare proposalsAsk each team to solve the same brief
- Set the handoffAgree who implements, reports and retains access
Compare deliverables and accountability
Ask who will audit, write, implement and verify fixes. Compare access, reporting, handoff documentation and the practical time needed from developers. Ask for examples of how a recommendation became a live change.
Compare proposed work using the same brief
Ask each candidate to explain which problems they would investigate first, what evidence they need and how they would prioritise changes. Ask who does the work, what the monthly or project deliverables contain and which decisions need your approval. Review examples relevant to your business, separating context and measurement from big performance claims. Keep ownership of the site, analytics and reporting accounts.
Review impact before renewing
Agree on a baseline and the business actions that matter. Use a regular review to decide which work should stop or expand. Keep control of your domain, analytics and content so you can maintain the work if the relationship changes.
Agree on a baseline and a handover process
Capture the current site condition, important queries, conversion events and revenue or lead quality where available. Agree on the work owner, meeting cadence and how recommendations become changes. Set review points measured against completed work and meaningful leading or business outcomes. Ask for a handover of content, tracking notes, redirects and decisions when the relationship ends.
Define the work before choosing the model
List technical fixes, content production, analytics, implementation, and stakeholder coordination. Identify which tasks require ongoing ownership and which need specialist input. A clear scope makes an in-house, agency, or hybrid comparison more useful than comparing retainers with a single salary.
Check implementation capacity
Ask who will publish content, modify templates, and approve changes. Recommendations have limited value if nobody can act on them. Include developer and reviewer availability in the plan, particularly when the work affects a regulated subject or a complex commerce platform.
Evaluate the evidence behind a proposal
Ask for the diagnostic method, deliverables, access requirements, and reporting definitions. Treat guaranteed rankings or unspecified link volume cautiously. A useful proposal explains uncertainty, priorities, and how progress will be verified without pretending every external search outcome is controllable.
Protect ownership and continuity
Keep the business in control of domains, analytics, content, and source code. Define handover responsibilities and access removal in the agreement. A good delivery model should remain understandable if a team member leaves or a supplier relationship ends.
Review progress against agreed decisions
Track implemented fixes, content quality, search visibility, and qualified commercial outcomes. Separate work completed from results that depend on time or external systems. Use review meetings to choose the next priorities rather than merely reading a dashboard aloud.
Choosing a partner for a site move
A retailer plans a platform migration and already has a capable marketing team. It hires a technical specialist for inventory, redirects and post-launch sampling while internal staff handle product content. Six months later, a separate capacity review determines whether ongoing editorial help is needed.
Ask how work will be handed off between the SEO provider, editors and developers. A strong technical audit is only useful if the business can review and implement its priority findings. Put the expected implementation owner next to each deliverable and decide what access can be granted and revoked. During the pitch, have each team explain one difficult tradeoff in plain language, including which work it would postpone when time is limited.
| Situation | Sensible model | What to require |
|---|---|---|
| One complex technical project | Specialist on a defined scope | Launch checks, ownership and rollback plan |
| Ongoing specialist work across channels | Agency or blended model | Named team, priorities and shared reporting |
| Constant collaboration with product teams | Internal owner with targeted support | Decision access and reliable delivery capacity |
Common questions
What should a provider guarantee?
Ask for clarity on work and delivery. Nobody can guarantee a first position in organic search because rankings depend on factors beyond the provider’s control.
How long should the first review window be?
Set checkpoints for implemented work quickly, then evaluate search and customer outcomes over a period that fits the changes, seasonality and reporting lag.
What does a useful monthly report include?
Look for work completed, the evidence behind the next priorities and the outcomes you agreed to track. It should identify decisions your team owns and distinguish observations from conclusions.
What to check next
- ScopeIdentify the team responsible for implementation
- AccessKeep ownership of domains, analytics and assets
- ReviewDecide what to continue based on evidence




