Public context for technical SEO audit planning

What to take away

Public evidence helps UK teams set audit priorities, but it does not provide a standalone measure of technical SEO demand.
Check regulatory and procurement context before scoping work; accessibility requirements can make particular checks relevant to public sector sites and apps.
Use Google Search Console (the bulk export guide explains the data) to review search performance and indexing, then crawl sites with Screaming Frog SEO Spider or Sitebulb.
Use Lighthouse or PageSpeed Insights to investigate performance issues, and verify findings against the site itself.
Revisit priorities when guidance, platform documentation, a migration or the client’s objectives change.

Why public data cannot replace a technical SEO audit

Public sources can show relevant requirements, procurement activity and platform changes, but they do not reveal the condition of an individual website. Treat them as context for an audit, not as evidence that a particular site has a technical SEO problem.

For broader planning context, the agency planning framework for England can inform questions to investigate. Confirm each finding with site data and a technical review before recommending work.

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 are relevant context for audits of public sector sites and apps. Check GOV.UK's accessibility requirements guidance for applicable requirements; treat accessibility checks as complementary to, not a substitute for, a technical SEO audit.

The Regulations were written around WCAG 2.1 level AA, GOV.UK guidance for public bodies now names WCAG 2.2 AA, and public sector sites must publish an accessibility statement. They applied to new public sector websites from 23 September 2018, to older sites from 23 September 2019 and to mobile apps from 23 June 2021. The Government Digital Service monitors compliance, and the Equality and Human Rights Commission enforces it in Great Britain. When a client is a public body, these checks go into the audit scope.

Public sources and tools for setting audit priorities

Use public sources to identify what to investigate, then use audit tools and site evidence to confirm whether an issue exists.

Source family	Named example	What it publishes	Cadence
Regulator	Information Commissioner's Office	PECR and UK GDPR expectations for analytics, cookies and log data	Guidance-led
Standards body	W3C	WCAG 2.2, published 5 October 2023	Versioned over years
Professional body	Chartered Institute of Marketing	Training and skills material; check what it publishes before treating it as a demand signal	Varies
Platform documentation	Google Search Central	Crawling, indexing and structured data rules	Frequent, undated

Four Data Sources Compared

ICO

Question answered: Lawful analytics
Buyer relevance: Data protection
Change speed: Slow
Use in audit: Compliance check

W3C

Question answered: Accessibility standard
Buyer relevance: Public sector
Change speed: Slow
Use in audit: Procurement evidence

CIM

Question answered: Training demand
Buyer relevance: AI skills
Change speed: Medium
Use in audit: Skills planning

Platform docs

Question answered: Crawling and indexing
Buyer relevance: Operational input
Change speed: Fast
Use in audit: Tool validation

Consent can affect which analytics tracking a site can use. The ICO's PECR guidance on cookies and similar technologies is relevant when an audit reviews analytics tags or tracking pixels; record the issue separately from crawl, indexing and performance findings.

Turn public evidence into an audit scope

Official statistics describe the digital sector rather than the technical condition of individual websites. Use the ONS IT and internet industry statistics as broad context, not as a proxy for the number of technical SEO issues or the need for a specific audit.

Build a defensible scope from evidence you can check:

The latest release of the ONS dataset UK businessactivity, size and location, noting its publication date. It counts enterprises by industry code, employment size band and region.
Procurement notices on Contracts Finder and Find a Tender (England), Public Contracts Scotland, Sell2Wales and eTendersNI covering website audits, accessibility and CMS work.
Job adverts naming technical SEO, schema, Core Web Vitals or log file analysis.
Companies House filings, to check whether a prospect is genuinely enterprise scale. Accounts are filed as micro, small, medium or large, which helps with sizing.

Each source changes the scope in a different way. For example, a council tender for a website rebuild that requires WCAG 2.1 AA conformance adds accessibility checks on templates, headings and keyboard focus. A run of job adverts asking for log analysis suggests the sector is monitoring crawl behaviour, so crawl-budget checks may belong in the scope. A prospect filing micro-entity accounts probably needs a lighter, cheaper audit than one filing large-company accounts.

Record the source, the date you read it and the audit check it added. If a source adds no check, leave it out of the plan.

ONS output and productivity releases may add context about the wider digital economy, but they do not establish the technical condition of a site. Treat trade body surveys as background rather than site-level evidence, and record who produced them and when if you use them.

Before recommending work, check the finding against the evidence that produced it. The technical SEO benchmark research guide can help put a site finding in context, but a benchmark does not replace checking the affected pages.

Turn findings into priorities

Buyer type changes the priorities more reliably than region. Enterprise and public sector buyers usually need accessibility, procurement and data protection evidence. Smaller businesses usually care more about cost per audit and reporting clarity. Test any regional pattern yourself by splitting the ONS enterprise counts by region and size band, and do not assume it.

Audit scope can differ between clients, even when they use similar platforms. Record the site’s objectives, platform and known changes before deciding which findings need investigation first.

Quarterly audit-planning checklist

Use this checklist to refresh priorities and keep the dated output alongside your audit plans.

Note when you last checked each public source and tool.
Record any new WCAG release or ICO guidance change.
Review Google Search Console for new indexing or search performance signals.
Re-crawl relevant sites and validate significant findings.
Log public sector accessibility notices that may affect the scope.
Revisit priorities against the client’s objectives and current site changes.

Tool contract renewals and analytics migrations are useful planning dates. Put them in the same calendar as relevant regulatory and platform changes, then check whether they alter the audit scope.

Changes that trigger an audit review

Refresh audit priorities regularly and review them after a relevant change. A new WCAG version or a revision to ICO guidance should prompt a check of the affected requirements and audit templates, rather than an assumption that every site needs the same work.

Platform documentation changes more often than regulation. Treat Google Search Central updates as operational input, and record when you checked them and whether they affect the site under review. Google's Search Status Dashboard lists confirmed ranking and crawling incidents with dates, which makes it a useful source for the log.

If budgets tighten or a migration slips, reassess planned work against the site’s evidence and the client’s priorities.

Common questions

Is there an official UK figure for the technical SEO market?

No. SEO is not a separate statistical category, so a market figure would be a proxy rather than a measure of technical SEO audits. For audit planning, use public sources for context and assess each site directly.

How often should the outlook be refreshed?

For the planning context behind an audit, review it quarterly using the checklist above, and after a relevant regulatory or platform change. Re-check any evidence older than two quarters before relying on it in a proposal.

Does the outlook differ between London and the regions?

Possibly, but check it rather than assume it. Split the ONS enterprise counts by region and size band for your own market. Enterprise and public sector buyers tend to need accessibility and data protection evidence, while smaller buyers weigh cost and reporting clarity.