What Do SEO Services Include? Deliverables, Scope and Reporting

BUYER’S FIELD GUIDE · REVIEWED 22 OCTOBER 2026

SEO services should turn a business goal into a prioritized plan, implemented website improvements and evidence of what changed. A useful proposal names the deliverables, the person responsible, the approvals required and how the work will be verified. A list of keywords or a monthly ranking PDF is not a complete service.

This independent guide helps you compare scope, not buy a package from this page. Use the deliverables worksheet below to separate research from implementation and activity from results. For judging a provider’s methods and promises, use our agency-vetting guide.

An SEO specialist assembles a coordinated toolkit for search visibility, content, technical work and links.
Editorial illustration.

What do SEO services actually include?

Scope depends on the website. An established shop with crawl problems needs different work from a new local business with no useful service pages. Start with a diagnosis and the commercial outcome, not a fixed number of articles or links. Google describes possible SEO services including technical advice, content development, keyword research and reviewing site structure; it also warns that no one can guarantee a number-one ranking. Read Google’s advice on hiring an SEO.

A scope checklist: require evidence, not just a service label
Workstream Concrete deliverable How to verify it Important boundary
Baseline and goals Property access, tracked actions, dated page/query baseline and agreed business goal Open the source reports and complete a test action Visits, leads and revenue are different measures
Keyword and intent research A question-to-page map with audience, intent, existing destination and rationale Inspect a sample of searches and explain why each destination helps Estimated volume is not guaranteed demand or traffic
Technical audit Issue list with affected URLs, evidence, severity and proposed fixes Reproduce a sample issue on a live URL An audit is not an implemented fix
Technical implementation Approved change log, code/configuration changes and retest evidence Read public responses and repeat the original test Developer time may be a separate budget
On-page and content Briefs, reviewed copy, published pages, useful media and internal-link changes Compare the brief with the public page and intended reader task Writing, editing and CMS publishing may be separate
Promotion and earned links Relevant outreach targets, actual placements and transparent paid arrangements Inspect destination pages and link attributes Outreach does not guarantee editorial acceptance
Local visibility, where relevant Eligible Business Profile work and accurate service/location information Check ownership, eligibility and public details Not every website qualifies for or needs a local profile
AI-search readiness Access review, source-quality checks and a documented citation sample Check source URLs, timestamps and whether citations support the claims Not a promise of ChatGPT recommendations
Reporting and next decisions Changes shipped, outcomes, limitations and the next prioritized actions Trace figures back to first-party sources A hand-picked ranking chart is not the whole business outcome

A service can be valuable without covering every row. The problem is ambiguity: if publishing or development is excluded, record the owner and budget before signing. See our strategy roadmap for sequencing those dependencies.

PRACTICAL WORKSHEET

Does this proposal have a verifiable scope?

Tick only what the written proposal actually specifies. This is a completeness check, not a supplier-quality score. No account or personal data is required; answers stay in this page and reset on reload.






0 of 6 scope items documented. Check the written proposal before marking an item complete.

Download the scope worksheet (CSV)

The checklist is usable without JavaScript. Count the documented items yourself or use the downloadable worksheet.

An example 90-day scope—not a ranking deadline

Hypothetical teaching example: a small plumbing business has a WordPress site, limited developer time and an enquiry form. This is an illustrative plan, not a customer case study or a promise that results arrive in three months.

  1. Days 1–15: establish what is true. Verify Search Console access, inspect priority service URLs, test the form and agree what counts as a qualified enquiry. Deliver a baseline, a short issue list and a decision on what not to do yet.
  2. Days 16–45: implement the highest-priority work. If a valuable page has an accidental noindex instruction, resolve it with approval and inspect the live response. If the main service page fails to explain coverage or booking, fix that reader task. Deliver a change log and tests—not only recommendations.
  3. Days 46–75: improve content and connections. Publish or revise a small number of justified pages, add relevant internal links and review a legitimate Business Profile if applicable. Do not create a separate thin page for every nearby town.
  4. Days 76–90: evaluate and reprioritize. Compare equivalent periods, identify what was recrawled and separate measurement errors from weak performance. Decide the next work package, with dependencies and review dates.

If development approval is delayed, report the blocked task rather than taking credit for an expected improvement. If Search Console still shows old crawl data, state that the changed version has not yet been observed there.

A modular website is improved with technical tuning, content, internal links and steady organic growth.
Editorial illustration.

What should a monthly SEO report contain?

A useful report answers four questions: what shipped, what happened, what might explain it, and what happens next. Avoid treating a position change as proof that one edit caused it.

Illustrative report structure—not actual client results
Section Example entry Evidence
Delivered Accidental noindex removed from the agreed service page Approved change ID, public HTML and retest date
Search visibility Compare the same URL/query group over complete periods GSC export, dates, search type and filters
Business actions Report valid enquiries separately from form tests and spam Consented analytics and reconciled enquiry records
AI citations Record a linked source and whether it supports the answer Question, system, timestamp and captured answer
Uncertainty Recrawl pending; seasonal change or other site work may matter Inspection timestamp and annotated change history
Next decision Review coverage and internal links before commissioning more copy Owner, evidence needed and review date

Keep search impressions, AI mentions, citations, visits and conversions separate. A link in an AI answer is not a visit, and a visit is not a lead. Use our citation-audit protocol and AI referral measurement guide rather than inventing one combined visibility score.

Which SEO claims should you challenge?

  • “We optimize meta keywords.” Google does not use the keywords meta tag for web ranking. A proposal should focus on the reader’s language and page usefulness instead.
  • “We achieve the right keyword density.” There is no universal repetition quota that makes a page rank. Explain the subject naturally; do not force phrases into every heading.
  • “A meta description improves your ranking.” A useful description can inform a search snippet; Google does not use it as a ranking signal and may choose other page text. Google’s explanation.
  • “Sitemap submission guarantees indexing.” A sitemap helps discovery; submission is a hint, not a guarantee. Google’s sitemap guidance.
  • “Hundreds of directory submissions are a core deliverable.” Question the purpose, relevance and methods. Low-quality directory/bookmark links and manipulative distributed links are listed in Google’s link-spam policy. Legitimate promotion is not the same as a ranking-link scheme.
  • “Our AI schema guarantees recommendations.” Google requires no special schema for AI Overviews or AI Mode, and eligibility does not guarantee inclusion. Read the AI-feature requirements.

Agree on access, acceptance and exit before work starts

Keep ownership of your domain, hosting, Search Console, analytics and relevant business accounts. Give the least access required, with a named approval process and rollback plan for risky changes. Ask who maintains content and code after delivery, where source files live and what happens when the agreement ends.

Ask the provider to complete this sentence for every material task: “We will deliver this artifact, this person will implement it, and you can verify completion with this test.” If they cannot, clarify the scope before debating a monthly price. Price comparisons without matching implementation responsibility are not like-for-like comparisons.

Questions worth asking

Is an audit enough?

It can be, if you have the people and budget to implement the recommendations. Require a reproducible issue list and priorities. If nobody owns implementation, the audit may become an unused document.

Do I need separate GEO services?

You may need additional access checks and citation measurement, but not a magic replacement for useful, accessible content. Ask for specific deliverables and distinguish search inclusion from model-training permissions or promised recommendations.

Can a provider guarantee delivery?

They can contractually define work, deadlines and acceptance criteria within their control. They cannot control Google’s indexing decisions, independent publishers or every answer produced by an AI system.

Primary sources and editorial note

Reviewed 22 October 2026 by Vlad Samohvalov. The worksheets and illustrative plan are editorial tools, not certifications, legal advice or performance forecasts. No customer results are claimed.