SEO Deliverables: How to Define Acceptance Criteria, Not Just Activities

An SEO deliverable is an output that another person can inspect and accept. “Perform technical SEO,” “build links” and “optimize content” are activities, not deliverables. They do not identify the affected pages, the expected change, the evidence required or the condition that marks the work complete.

Acceptance criteria solve that problem. They describe the observable requirements a deliverable must meet before the client approves it. The criteria do not guarantee a ranking or revenue result; search outcomes depend on competition, demand, implementation and systems outside an agency's control. They do make the work itself reviewable.

Google advises businesses hiring an SEO to request a technical and search audit, realistic estimates and explanations of proposed changes. That is a useful baseline: a deliverable should show the diagnosis, recommended action and reasoning clearly enough for the site owner to make an informed decision.

Use four states instead of “done”

Most reporting confusion comes from collapsing different states into one completed checkbox. Use these four states for material SEO work:

1. Recommended: the team has documented what should change and why.
2. Approved: the authorized owner has accepted the recommendation and risk.
3. Implemented: the change is present in the production environment.
4. Validated: the team has tested the production outcome against stated criteria.

An audit finding is not a fix. A developer saying a ticket was deployed is not validation. A published article is not automatically indexed, useful or commercially effective. The monthly report should preserve those distinctions.

For each deliverable, record a responsible owner, approver, due date, dependencies and evidence link. If a client team performs implementation, the agency still needs to specify how it will verify the outcome.

Acceptance criteria for an SEO audit

An audit should prioritize decisions rather than export every warning a crawler can produce. A complete audit deliverable should include:

• the audited properties, hostnames, environments and crawl date;
• tools and access used, including known limitations;
• findings grouped by business and search impact;
• affected templates or representative URLs;
• evidence that reproduces each material finding;
• a recommended action, owner and dependency;
• an explicit priority method;
• a list of checks that passed, not only failures.

A suitable acceptance test is: “A developer unfamiliar with the audit can reproduce every critical issue, identify the affected component and understand the expected behavior after the fix.” A 200-page PDF full of generic warnings fails that test even when it looks comprehensive.

The audit should also state uncertainty. A crawl may not see authenticated pages, recently changed content or every rendering condition. Analytics may be incomplete. The agency should distinguish verified defects from hypotheses that need investigation.

Google's guidance for hiring an SEO says the audit should explain what needs to be done, why, and what the expected outcome is. It also cautions against guaranteed rankings. Put those boundaries directly into the acceptance criteria.

Acceptance criteria for technical SEO tickets

A technical ticket is ready for implementation when it contains enough information for engineering to act without guessing at the search requirement.

Each ticket should specify:

Avoid prescribing an implementation that the SEO cannot defend technically. “Block all parameters in robots.txt” may prevent crawling without removing indexed URLs. “Add a canonical” is incomplete unless the target is correct and the other discovery signals support consolidation.

Validation belongs in production because templates, edge rules and rendering can differ from staging. Sample every affected template and important exception. Record the date, URL and result of the post-deployment check.

Acceptance criteria for content briefs and drafts

A content brief should define the reader problem, primary intent, necessary evidence, page relationship and conversion purpose. It should not become a rigid list of phrases that forces awkward repetition.

Accept a brief when it identifies:

• the target reader and decision stage;
• the primary question or task;
• the existing URL to update or the reason a new URL is needed;
• overlapping pages and the cannibalization decision;
• required first-party expertise and external evidence;
• essential sections, comparisons or examples;
• internal links and the next useful action;
• claims requiring legal, technical or subject review.

Accept a draft when it satisfies the brief, represents sources accurately, makes no unsupported performance claim, uses a logical heading structure and has passed the named reviews. The Google SEO Starter Guide emphasizes readable, organized, unique, current and helpful content. Those qualities can be translated into editorial checks without pretending that a checklist guarantees rankings.

Do not accept a draft merely because it reaches a word count or includes every keyword variant. A shorter page can satisfy intent better than a padded one. Require the writer to remove repetition and disclose important limitations.

Acceptance criteria for on-page optimization

“Optimize ten pages” should become a page-level change record. For every URL, list the current element, proposed element, reason and approval state. Typical elements include title, main heading, introductory answer, content gaps, internal links, images, structured data and conversion path.

Acceptance should confirm that:

1. the page still represents the business offer accurately;
2. the title and heading align with the primary intent without misleading users;
3. the canonical URL and indexability are intentional;
4. links work and their destinations are relevant;
5. no approved content or tracking was accidentally removed;
6. the live HTML contains the approved change.

Separate the agency's change recommendation from the measured outcome. A new title is complete when it is approved, deployed and validated. Its effect on clicks is evaluated later with an agreed comparison window and awareness of other changes.

Acceptance criteria for structured data

Valid syntax is necessary but insufficient. Structured data must describe the visible page accurately and follow the requirements for the relevant search feature.

An acceptable structured-data deliverable includes:

• the eligible page type and business reason for using the markup;
• the exact supported type and required properties;
• a mapping from each property to visible page content;
• validation output from the appropriate testing tool;
• a production URL check after deployment;
• monitoring ownership for future template changes.

Google's general structured-data guidelines say markup should be representative, relevant, complete and visible to readers. They also state that correct markup does not guarantee a rich result. Acceptance criteria should therefore say “eligible and valid,” not “rich result achieved.”

Reject markup for fake reviews, hidden content or irrelevant types even when a validator reports no syntax error. Automated tools cannot approve the truthfulness of the data.

Acceptance criteria for authority and digital PR

Define authority work by process and evidence, not a guaranteed count of links from unspecified sites. A campaign deliverable can include the research asset, target-audience rationale, outreach list criteria, approved pitch, outreach log and resulting coverage.

For every acquired placement, record:

• source and destination URLs;
• publication date;
• relationship or acquisition method;
• whether payment, sponsorship or exchange was involved;
• link attribute when relevant;
• relevance to the audience and page.

Do not make third-party publication entirely within the agency's acceptance obligation; editors and publishers control their own sites. Instead, accept the campaign preparation and execution against documented quality criteria, then report outcomes separately. Prohibit automated spam, undisclosed paid placements and metrics that can be met through irrelevant sites.

Acceptance criteria for monthly reporting

A report should answer what changed, why it matters, what remains uncertain and what decision is required. Accept it when the reporting period, comparisons, filters and metric definitions are visible.

At minimum, require:

• search visibility and click trends for the agreed scope;
• landing-page behavior and named conversion events;
• lead or revenue quality where the client can provide it;
• completed work separated by recommended, approved, implemented and validated states;
• material site, tracking and market changes;
• concise interpretation, not screenshots without analysis;
• next actions with owners and dates.

The report should not silently substitute rankings for qualified demand, count all conversions as equal or claim causation from a simple before-and-after chart. If a metric definition changes, annotate the date and preserve the previous definition for comparison.

Build an acceptance matrix into the statement of work

Put the recurring deliverables in one operating table before the engagement begins.

Include a review window and revision rule. State what happens when client approval is late, required access is unavailable or implementation capacity changes. Define whether unused production rolls forward and which deliverables are dependent on earlier approval.

The practical standard

Good acceptance criteria make the agency easier to manage without turning SEO into false certainty. They focus on observable work: the diagnosis can be reproduced, the recommendation is specific, the responsible owner is named, the production change matches the requirement and the evidence is retained.

Use outcomes to evaluate the program, but do not use hoped-for outcomes to define whether a deliverable existed. Rankings cannot be guaranteed. Clear reasoning, responsible implementation and honest measurement can be required in every statement of work.

Related decisions

• Client vs Agency SEO Responsibilities: Who Owns Implementation? — the adjacent hiring an seo agency decision.
• How Much Internal Time Does an SEO Agency Engagement Require? — the adjacent hiring an seo agency decision.
• How to Manage a Remote SEO Delivery Team Across Time Zones — the adjacent seo governance decision.

Sources checked

• Google Search Central: Do you need an SEO? — audit expectations, explanations of changes and warning against guaranteed rankings.
• Google Search Central: SEO Starter Guide — crawlability, organization and helpful-content fundamentals used to frame editorial checks.
• Google Search Central: General structured-data guidelines — relevance, completeness, visibility and rich-result limitations.