Four technical SEO business models and when they fit

What to take away

The right model depends on release cadence, the scope of the work and who is responsible for implementing fixes.
Four models dominate: hourly consulting, fixed-scope audits, monthly retainers and productised tool-plus-service packages.
Retainers suit sites that ship code weekly; audits suit sites that change twice a year.

Four technical SEO business models

Many UK agencies sell one of four things, and you can compare their quotes by scope. Hourly consulting trades senior time. A fixed-scope audit is a document. Monthly retainers cover ongoing crawl and release checks, and productised packages bundle a tool licence with a set number of reviews each month.

A technical SEO audit may cover crawlability and indexation, log-file analysis, JavaScript rendering, hreflang, canonicals, redirects, Core Web Vitals and structured data. Agree which areas are included and excluded before work starts.

Risk bearer

Hourly consulting: Client
Fixed-scope audit: Client
Monthly retainer: Shared
Productised package: Shared

Cadence

Hourly consulting: Ad hoc
Fixed-scope audit: One-off
Monthly retainer: Weekly or monthly
Productised package: Monthly

Pricing unit

Hourly consulting: Hour or day
Fixed-scope audit: Property or template count
Monthly retainer: Crawl volume or sprint
Productised package: Seat or domain

Deliverable

Hourly consulting: Advice and second opinion
Fixed-scope audit: Document of fixes
Monthly retainer: Ongoing crawl and release checks
Productised package: Tool licence plus set reviews

Four models compared

Hourly consulting

What is sold: Senior time
Who carries risk: Shared
Priced per: Hour

Fixed-scope audit

What is sold: A document
Who carries risk: Client
Priced per: Property

Monthly retainer

What is sold: Ongoing checks
Who carries risk: Partly agency
Priced per: Crawl volume

Productised package

What is sold: Tool plus reviews
Who carries risk: Bundled
Priced per: Seat

The models differ in who carries risk, and the risk scenarios for each are worth mapping. An audit transfers risk to the client, because the fixes are theirs to schedule. A retainer keeps part of that risk with the agency, which is why it can cost more per month but less per fix.

Pricing units and provider examples

Audits are priced per property or per template count. Blue Array, an SEO-only agency with a Reading office, lists technical SEO audits among its core services.

Retainers are priced per crawl volume or per developer sprint. Aira, based in Milton Keynes, says on its website that it works best with clients who can invest at least £5,000 a month and recommends a 12-month contract.

Productised packages are priced per seat or per domain, as a tool licence plus a fixed number of reviews. For example, a package might cover one domain, a crawler licence and two scheduled reviews a month for a flat fee. Screaming Frog in Oxfordshire sells its SEO Spider licence for £199 a year, which prices only the licence half. Ask any provider to price the reviews separately.

Hourly consulting is priced per hour or per day. Search Laboratory in Leeds offers technical SEO among its services, so ask any such provider whether it quotes by the day.

Margin comes from reuse. A team with crawl comparison scripts already built can deliver a retainer in fewer hours than a team starting from scratch. Model choice therefore affects profit more than headline price does.

When each model fits

Retainers fit sites with continuous deployment, where a fix can regress within a fortnight. Audits fit migrations, replatforms and pre-acquisition checks, where the deliverable is evidence rather than maintenance.

Productised packages fit mid-market firms with no in-house specialist but a developer who can action tickets, and a site that changes little between monthly reviews. They suit firms that want predictable cost and can live with a fixed scope.

Hourly consulting fits teams that already own the tooling and want a second opinion on a specific question, such as a redirect plan or a rendering fault. It suits short, well-defined problems. It is a poor fit for ongoing monitoring, because nobody is paid to look between calls.

Tooling and measurement

Tool choice follows the model, and a separate piece covers software selection. Audit shops favour crawlers that export spreadsheets. Retainer shops favour crawlers with scheduling and alerting, because the value sits in the delta between crawls.

Google Search Central's guidance on valid page metadata is a useful test of any model. Titles and snippets should be checked on every release rather than once a year, and a model that never re-checks them is underselling the work.

Measurement needs an agreed unit because models produce different records: an audit records findings at a point in time, while a retainer can track changes across reviews. Agree the reporting unit before signing: pages fixed, traffic change, or both.

Buyer checklist

Confirm whether the deliverable is a document, a schedule of fixes or a monthly report.
Ask who owns the crawl licence and what happens to historical crawl data at exit.
Check your own release cadence before choosing between audit and retainer.
Agree the reporting unit and review date in writing.
Ask for the last three crawl diffs, not a sample report.

Common questions

Which model suits a small UK ecommerce site?

A fixed-scope audit usually suits sites that replatform rarely, because the fix list stays valid for months. Move to a retainer once you deploy changes weekly.

Are productised packages cheaper than retainers?

Often, but the scope is narrower. Check how many reviews are included and whether template changes count as new work.

Should an in-house team buy audits at all?

Yes, for migrations and platform changes. An external audit gives a second crawl and a written record that internal teams rarely keep.

How do I compare two quotes on different models?

Convert both to a cost per fixed issue over twelve months. That normalises a one-off audit against a monthly retainer.