An SEO deliverable is a defined output with an owner, a completion test and evidence of its current state. A technical recommendation, a published page and a verified live fix can all be valid deliverables, but they are not the same thing.
You should not receive the same work every month by default. The priority may be indexation, weak commercial pages, a blocked implementation queue, missing authority or search traffic that never becomes pipeline.
What should stay consistent is the proof standard.
Our SEO system treats these outputs as connected changes to the website, source layer and managed search loop rather than an isolated task list.
Use the five-field deliverable contract
Every deliverable should answer:
| Field | Question |
|---|---|
| Commercial reason | Which service, product, market or customer outcome does this support? |
| Output | What exact artifact or live change will exist? |
| Owner | Who researches, approves, implements and verifies it? |
| Completion evidence | What proves the output is finished and live? |
| Outcome measure | Which search or commercial evidence will show whether it helped? |
Example:
Output: Rewrite and publish the highest-value service page.
Reason: The service has strong commercial value, but the current page does not explain the job, price method, service area or proof clearly enough.
Owner: Agency drafts; business owner fact-checks; client developer publishes; agency verifies.
Completion evidence: Approved copy, production URL, source diff, mobile render, canonical and internal links checked.
Outcome measure: Relevant impressions, calls, accepted enquiries, completed sales and margin where those sources exist.
“Service page optimized” is not the same deliverable.
SEO deliverable library by workstream
Choose from the library after the baseline identifies the work that matters. A serious scope selects and sequences the right outputs instead of promising the entire menu.
Strategy and search ownership
| Deliverable | Output | Completion evidence |
|---|---|---|
| Search-demand map | Query, audience, intent, market and commercial value mapped to existing or proposed routes | Reviewed route map with conflicts and gaps |
| Page-ownership map | One primary job per indexable route | Keep, rewrite, consolidate, redirect, hold or retire decision recorded |
| Competitive page brief | Current result types, consensus floor, useful gaps and information edge | Dated evidence packet with market and method |
| Opportunity model | Search demand tied to conversion, value and capacity assumptions | Assumptions visible; scenario range rather than fake forecast |
| Prioritized roadmap | Ordered actions with impact, effort, dependencies and proof | Named owners and next action |
A keyword spreadsheet becomes useful strategy when it assigns route ownership, commercial purpose and a decision.
Technical SEO
| Deliverable | Output | Completion evidence |
|---|---|---|
| Crawl and index diagnosis | Prioritized defects affecting intended pages | URLs, examples, cause, severity and reproduction |
| Remediation ticket | Developer-ready change with acceptance criteria | Ticket accepted by implementation owner |
| Implemented technical fix | Production change to template, routing, metadata or infrastructure | Live response, render or source check against the acceptance test |
| Redirect map | Old URL, target URL, reason and status | Tested redirect, final destination and canonical alignment |
| Canonical/indexability review | Intended status for every priority route | Live canonical, robots and indexability evidence |
| Structured-data change | Valid markup reflecting visible content | Live source plus appropriate validation |
| Performance repair | Specific bottleneck reduced without breaking the page | Before/after field or lab evidence and rendered regression check |
| Migration control pack | Inventory, redirects, canonicals, launch checks and rollback | Pre-launch pass plus post-launch verification |
An audit can be complete when it produces clear decisions. A repair reaches a different state only when the production change passes its acceptance test.
Commercial and on-page work
| Deliverable | Output | Completion evidence |
|---|---|---|
| Money-page brief | Search job, offer, evidence, structure, links and CTA | Business and editorial owners approve it |
| Full page rewrite | Finished source at the owning location | Direct editorial and fact review |
| Published page | Live page at the intended canonical URL | Desktop/mobile render, metadata, links and forms tested |
| Search-presentation update | Title and snippet direction for a defined page set | Production metadata confirmed |
| Internal-link batch | Named source pages, destination pages and anchors | Links present in rendered output; no broken destinations |
| Conversion repair | Call, form, booking or qualification improvement | Live action completes and analytics event is verified where available |
| Content refresh | Useful facts, proof and intent improved without losing working value | Old-versus-new content-loss check and live verification |
Changing a title tag is a valid deliverable when the search presentation is the problem. It is too narrow when the underlying commercial page is fundamentally weak.
Supporting content
| Deliverable | Output | Completion evidence |
|---|---|---|
| Article brief | One query job, information edge, sources, link destination and CTA | Evidence and cannibalisation review complete |
| Senior-edited article | Accurate, useful source in the brand voice | Direct full-text review; sources and claim boundaries checked |
| Published resource | Canonical live article linked into the relevant journey | Render, links, metadata and indexability verified |
| Content consolidation | Useful material moved into one stronger owner | Content-loss check, redirect and internal-link migration |
| Content retirement | Low-value route removed deliberately | Reason, redirect/noindex/410 decision and downstream links checked |
| Refresh queue | Pages prioritized by decline, opportunity and commercial value | Data source, date, owner and next action recorded |
Publishing four articles is a volume statement. It becomes useful delivery when the pages have distinct jobs, pass the quality gate and support a valuable commercial route.
Local search
| Deliverable | Output | Completion evidence |
|---|---|---|
| Business Profile audit | Eligibility, ownership, categories, location/service area, hours and link review | Current fields, issues and approved actions recorded |
| Profile correction | Approved change to a real business fact | Live readback and no policy conflict |
| Service-and-area map | Valuable combinations assessed for coverage, capacity and proof | Core, growth, conditional and excluded areas approved |
| Location-page decision | Pass/fail gate for each proposed route | Distinct value and route owner documented |
| Review workflow | Policy-compliant request, response and escalation process | Trigger, data flow, owner and message approved |
| Local authority action | Legitimate local, industry or partner reference | Live source and relationship documented |
| Local measurement view | Service, area, surface and commercial outcomes | Method, location and attribution limits stated |
Local work should prioritize accurate profiles, useful location coverage and legitimate local evidence over outputs chosen only because they are easy to count.
Authority and source evidence
| Deliverable | Output | Completion evidence |
|---|---|---|
| Authority-gap analysis | Relevant sources and competitors by page or market | Source relevance and current status recorded |
| Digital PR asset | Original research, useful tool, expert contribution or story | Approved asset with a defensible outreach audience |
| Outreach campaign | Qualified sources, messages and response states | Contact log with no fabricated placements |
| Earned reference | Live link or mention from a legitimate source | Destination, context and relationship verified |
| Unlinked-mention recovery | Existing legitimate mention linked where editorially accepted | Live link and source recorded |
| Source-layer correction | Material third-party fact corrected | Before/after public source evidence |
“Twenty backlinks” is not a quality definition. Name the sources, destinations, context and commercial reason.
AI-assisted search observation
| Deliverable | Output | Completion evidence |
|---|---|---|
| Prompt panel | Stable questions by product, mode, market and customer job | Versioned prompt set and method |
| Answer observation | Response, brands, citations and links | Product, prompt, location and date preserved |
| Citation-gap review | Owned and third-party sources recurring in answers | Source classes and factual gaps recorded |
| Publisher-control audit | Search crawler and access controls by product | Official documentation and live access check |
| AI-referral view | Identifiable visits and outcomes | Source/medium rules and attribution limits stated |
| Improvement queue | Accurate page, source and conversion actions | Each action tied to an observed gap, owner and verification |
Report a mention, citation, visit and commercial outcome as separate events.
Measurement and governance
| Deliverable | Output | Completion evidence |
|---|---|---|
| Baseline | Target versus actual at the start of work | Source, date, filters and limitations recorded |
| Change ledger | Exact live changes by URL, field and date | Production verification attached |
| Performance report | Search and commercial movement with interpretation | Data sources reconcile; unavailable data labeled unavailable |
| Blocker register | Access, approval, proof, development and capacity dependencies | Owner and next action |
| Decision record | Continue, stop, repair, expand or test | Evidence and responsible approver |
| Quarterly reset | Strategy updated from current results and market | New priorities replace stale task lists |
| Exit pack | Accounts, assets, data, documentation and open actions | Client access and exports verified |
A dashboard is a useful view of evidence. Pair it with the live-change record when reporting delivery.
What a monthly delivery pack should contain
The exact work changes. The control pack does not.
- Target versus actual: the services, markets and outcomes in scope.
- Proof shipped: exact URLs, fields, assets or placements completed.
- Verification: how the live state was checked.
- Movement: search, visibility, conversion and commercial evidence.
- Blockers: access, approvals, proof, implementation or capacity.
- Decisions: what the evidence changed.
- Next action: the release, decision or approval required.
Hours, meetings and reports can support delivery, but the pack should also show the actual output and its state.
Match output to implementation ownership
There are three valid delivery states:
- Recommended: a decision-ready ticket or source is complete, but implementation belongs to the client.
- Implemented: the change is live in production.
- Verified: the live state passes the agreed acceptance tests.
Do not collapse them.
If an agency cannot touch the CMS, the retainer must price and govern the client dependency. If the agency owns implementation, it must also own QA, rollback and incident response within the agreed boundary.
Separate meaningful outputs from activity
Resolve these points when you review the delivery plan:
- the same fixed deliverables every month regardless of current need;
- “optimization” with no URLs or fields;
- audits repeatedly resold without implementation;
- blog counts with no query ownership or internal links;
- link counts without source names;
- schema volume presented as AI visibility;
- report screenshots without source access;
- completed tickets that were never released;
- rankings reported without location, device or date;
- impressions presented as leads; and
- strategy calls with no decision or next action.
The number of deliverables is not the quality metric. One implemented sitewide fix can matter more than fifty content tweaks, while a carefully finished commercial page can matter more than a large undifferentiated content batch.
FAQ
What should an SEO agency deliver every month?
It should deliver the highest-priority outputs the website and market require, plus a consistent control pack showing baseline and target, live work, verification, movement, blockers, decisions and the next action. The SEO retainer guide explains how those outputs fit an ongoing operating model.
Is an SEO report a deliverable?
Yes, when it reconciles current source data, explains what changed and drives a decision. It is not a substitute for implementation evidence.
How many SEO deliverables should be included each month?
There is no responsible universal number. A deliverable should be scoped by its output and completion test, not counted as equal to every other item.
Should recommendations count as completed work?
Only as recommendations. Keep recommended, implemented and verified states separate so a finished audit is not misreported as a live fix.
Should content be included in an SEO retainer?
Only when content is a current priority and the scope defines who briefs, writes, fact-checks, approves, publishes, links and verifies it. A monthly article quota is not automatically the best use of the fee.
What proof should accompany technical SEO work?
The affected URLs or template, the defect and acceptance criteria, the live change and the relevant response, source, render or validation result. Add before/after performance evidence only where the method is sound.
How do we know whether deliverables are creating value?
Connect each output to a commercial reason and then measure the available chain: search visibility, visits, conversion, accepted leads, pipeline, revenue and margin. State where attribution or source access ends. Use the SEO SOW template to put those definitions into the agreement.
If you are reviewing an existing proposal, use the SEO scope of work checklist to test the implementation, dependencies, measurement, ownership and exit terms around the deliverables.