What should an SEO engagement include?

Name the services or products the business wants suitable customers to discover. Identify the customer’s stage: researching a problem, comparing options or preparing to contact a provider. Connect each priority question to an existing page or a justified content gap. This prevents a broad keyword list from becoming the whole strategy. Agree what qualifies as a useful customer action, and note whether the business can currently observe it. Scope should follow the buying journey and available evidence.

Ask for the current state of important URLs, indexation, internal links, content and relevant search performance. Identify missing access, limited data and technical restrictions. A baseline should distinguish confirmed issues from hypotheses. For example, a blocked canonical page is directly testable; a weak title’s effect on demand is less certain. Keep the source and date of each observation. This gives the team a fair reference when reviewing whether the engagement actually changed anything.

Each task should identify the affected page or template, the observed problem, the proposed change, its dependency and an acceptance check. A content deliverable should state the question it answers, required source material and the intended next step. A technical deliverable should include the behavior to verify after release. Prioritize work by expected usefulness, evidence, effort and dependency. Avoid a long undifferentiated list where urgent crawl problems compete with cosmetic metadata suggestions.

Clarify who writes content, verifies business facts, changes code and publishes the approved work. Name the owner of domain and search accounts, and use the least access required for the task. Record release windows and review dependencies so a waiting approval is not mistaken for completed delivery. If the engagement supplies recommendations only, say who will implement them. Agree how a provider requests a new page or a change in site structure without silently expanding the scope.

For a page update, check that the live page contains the approved information, has the intended title and canonical identity, and is linked from relevant destinations. For a redirect, test the old and new URLs externally. For measurement, verify that the event represents the intended action and does not count an unfinished step as a confirmed enquiry. Keep a change log with deployment dates. Search performance may take time to interpret, but technical correctness and delivery can be checked immediately.

Require the report to show what shipped, what remains blocked and what was observed for the priority pages. Separate qualified actions from raw visits and explain the reporting limits. Google’s guidance for hiring an SEO warns against guarantees of first place; treat guaranteed rankings or AI citations as a reason to inspect the proposal carefully. A credible review can acknowledge an inconclusive result and propose a focused next test. The business should understand both the work purchased and the decision it enables.