Technical SEO services: what a proper scope includes

Technical SEO services are easy to buy and hard to compare. One proposal promises a "full technical audit", another a "technical SEO retainer", a third a "site health programme", and the documents behind them can differ enormously. Some deliver a spreadsheet exported from a crawler. Others deliver prioritised tickets, work with your developers until fixes ship and verify the result. This article describes what a proper scope for technical SEO services should include, what it should explicitly exclude and how to write acceptance criteria, so that you can compare a technical SEO agency or consultant on substance rather than on the length of their checklist. If you need the basics first, our explainer on what technical SEO is and how to prioritise it covers the concepts; this piece is about buying the work.

Start with the problem, not the checklist

A good scope begins with a short discovery phase: what changed, what the business needs from organic search, which templates carry the most revenue or leads, and what is planned on the roadmap, such as a redesign, a migration or a new market. Without that context, an audit treats every issue as equal. With it, the same audit can separate the issues that block growth from the ones that are merely untidy. Ask any provider how they will learn about your site before they crawl it.

The core audit areas

Google's own documentation on crawling and indexing is a useful map of what technical SEO covers. A proper scope should say which of these areas are included and at what depth:

• Crawling: robots.txt rules, crawl paths, internal linking to important pages, handling of parameters and faceted navigation, and server responses and status codes.
• Indexing: which pages are indexed and which are not, noindex and canonical signals, duplicate content, and how the site appears in Search Console's indexing reports.
• Site architecture and URLs: logical, readable URL structure, depth of important pages, pagination and navigation.
• Sitemaps: whether XML sitemaps list the right URLs and are kept up to date.
• Rendering and JavaScript: whether content and links that matter are visible to Google when pages rely on JavaScript.
• Page experience: Core Web Vitals and mobile usability. Google recommends that site owners achieve good Core Web Vitals, noting that this aligns with what its core ranking systems seek to reward, alongside other page experience aspects.
• Structured data: whether markup is valid, relevant to the page and eligible for the search features you care about.
• International and multilingual setup, where relevant: hreflang, locale handling and redirects.
• Site changes: redirects, migrations and how temporary changes are handled.

Not every site needs every area at the same depth. A small brochure site might need a light review of most items; a large e-commerce or multilingual site may need deep work on crawling, indexing and internationalisation. The scope should say which is which.

Deliverables that can be acted on

The most common weakness of technical SEO services is the deliverable. A list of issues is not a plan. Ask for:

• A prioritised backlog: each issue with its evidence, the affected templates or URL patterns, the expected impact, the effort estimate and the owner.
• Developer-ready tickets: written in the format your team uses, with acceptance criteria that a developer can test.
• A short executive summary: the handful of decisions that leadership needs to make, in plain language.
• A measurement plan: which reports in Search Console and analytics will show whether a fix worked.

If the provider cannot show you an anonymised example of a ticket and an executive summary from previous work, ask why.

Implementation support and verification

Technical SEO only creates value once fixes are live. A proper scope says how the provider will support implementation: reviewing pull requests or staging environments, answering developer questions, and checking releases for regressions. It should also include verification: re-crawling after deployment, confirming status codes and canonicals, and watching the relevant Search Console reports. For higher-risk work such as a migration, the scope should cover pre-launch checks, launch-day monitoring and a post-launch review period.

Clarify who has access to what. Google's advice on hiring an SEO suggests giving an auditor read access to Search Console at first rather than full write access, and reminds site owners that they remain responsible for the actions of the companies they hire.

What a proper scope excludes

Exclusions prevent disputes. Typical exclusions to write down include content writing, link building, design changes, hosting or server administration and the development work itself, unless it is explicitly included. Also exclude promises that no provider can keep. Google states that no one can guarantee a first-place ranking, so a scope should never promise positions, traffic numbers or visibility in AI answers. What it can promise is defined work, clear deliverables, agreed response times and honest reporting.

Acceptance criteria and reporting

Write acceptance criteria for each phase. For an audit, that might be: every issue in the backlog has evidence, affected URL patterns, priority and owner, and the executive summary is reviewed with your team. For implementation support, it might be: agreed tickets verified after release, with results recorded. For an ongoing technical SEO agency retainer, agree a monthly rhythm: what was checked, what changed, what is next and which risks were spotted in upcoming releases.

Reporting should connect technical work to outcomes you care about, such as indexed pages for key templates, crawl errors, Core Web Vitals status and organic performance of the pages that were fixed, without implying that any single fix caused a ranking change on its own.

Questions to ask before you sign

• Which areas are in scope, at what depth, and why for our site?
• What does a finished ticket look like, and who writes it?
• How will you work with our developers, and what access do you need?
• How do you verify that a fix worked?
• What is explicitly out of scope?

If you would like a scoped proposal built this way, our technical SEO services start with discovery and a prioritised backlog, and sit alongside the rest of our SEO and search services.

Sources

• Crawling and indexing overview — Google Search Central
• Understanding Core Web Vitals and Google search results — Google Search Central
• Do you need an SEO? — Google Search Central