Write a business brief first

Describe what you sell, who you serve, your geographic coverage, and the outcomes you can measure. Note constraints such as a small development team or a seasonal catalog. Give a prospective partner enough context to explain how they would prioritize the work.

A useful brief might say: “We want qualified inquiries for these three services. We can publish content weekly, but template changes must go through our developer.”

Ask how the work becomes an implementation

Google’s hiring guidance encourages evaluating an SEO’s experience, approach, and references. Ask for the reasoning behind recommendations, how progress is measured, and what happens when the diagnosis is uncertain. Be cautious about guaranteed rankings.

Make the proposal specific

  • Which pages and markets are in scope?
  • What data access is needed, and who retains ownership?
  • Who approves and implements changes?
  • What evidence accompanies each recommendation?
  • How are paid placements or outside vendors disclosed?
  • What are the costs, cancellation terms, and handoff obligations?

Use a sample deliverable

Ask for an anonymized example of a useful ticket or report. Look for a clear issue, supporting evidence, proposed action, owner, and acceptance criteria. A polished PDF that does not tell anyone what to change is a weak operational handoff.

For content work, ask how factual claims are checked and who is responsible for accuracy. For technical work, ask how changes are tested and reversed if needed.

Keep reporting close to the business

Agree on a small reporting set: completed changes, open blockers, page-level search observations, and relevant customer outcomes. A partner should explain uncertainty and competing causes, not attribute every improvement to the last recommendation.

The right engagement depends on your needs and ability to implement. A focused audit with developer support may be more useful than a broad retainer that produces tasks nobody can finish.

Sources and further reading

Official documentation checked October 6, 2026. Workflow examples are illustrative editorial recommendations, not measured client results.