What does a B2B technical SEO audit include?
An audit tests the systems that publish your commercial pages. A crawler can reveal patterns, but the analyst must check those patterns against real pages, Search Console and the site's business priorities. A report of every warning from a tool is not a diagnosis.
The scope should name the domain, subdomains, markets, languages, page types and data sources before work begins. For a B2B site, service, solution, industry, product, integration and comparison pages deserve explicit sampling. They do different jobs in a buying journey and can fail in different ways.
Crawlability and indexation
The first question is whether search engines can reach the pages that matter and whether Google has chosen to index them. The auditor checks robots.txt, response codes, noindex directives, canonical tags, XML sitemaps, redirect chains and the Page Indexing report in Google Search Console. A crawl finds technical patterns; Search Console shows how Google's systems are treating the property.
The deliverable should distinguish a deliberate exclusion from an accidental one. A login page excluded from indexing is normal; a service page excluded by a shared template is urgent. Google's indexing guidance is the reference for how discovery and indexing differ.
Site architecture and internal links
An audit maps how a buyer and a crawler move from the homepage and hubs to high-value pages. It identifies orphaned pages, excessive click depth, broken links and navigation that relies on scripts rather than ordinary links. It also checks whether canonical URLs and breadcrumbs describe the intended structure.
For B2B, the test is practical: can a reader reach a relevant service page from an educational guide, and can a product page lead to a comparison or integration answer? An internal-link export is useful only when it is tied to a proposed page relationship. The B2B SEO audit checklist is a self-review; a commissioned audit should turn those checks into assigned fixes.
Rendering and JavaScript
JavaScript rendering can change what Google sees after the initial HTML response. The auditor compares source HTML with rendered output for representative templates, then checks whether titles, body copy, canonical tags and links are present and stable. Search Console URL Inspection can help diagnose a particular URL, while a rendering crawl tests a broader pattern.
Do not assume that every JavaScript site needs a rebuild. The issue is whether essential content and links can be reliably discovered and rendered. Google's JavaScript SEO basics explains the mechanism. A recommendation should identify the affected template and a test that proves the fix.
Mobile performance and Core Web Vitals
Performance work compares field data with lab diagnostics. Core Web Vitals assess loading, responsiveness and visual stability; the relevant Google measures are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. The auditor should say which page templates have enough field data, which do not, and what the lab tests suggest.
A slow page should not be assigned a vague “improve speed” ticket. The report should identify likely causes, such as an oversized hero image or script work on a key landing template, and give engineering a way to confirm the change. Google's Core Web Vitals documentation separates user experience signals from a promise of rankings.
Structured data, international targeting and migration risk
The audit checks whether structured data matches visible content and is valid for the page type. It may also review hreflang when regional versions exist, and redirects when a redesign or migration is planned. These modules should be scoped explicitly: a UK-only single-language site does not need a full international audit.
A migration review needs a URL mapping, staging access and launch checks; it is a different job from a snapshot of the current site. The B2B migration guide covers that separate work. Ask whether the quote includes pre-launch and post-launch checks before treating it as migration cover.
What should the audit deliver?

A buyer should receive evidence that can be acted on. The minimum useful package is a short decision summary, a findings register and a handover with a named owner for each proposed change. Large crawls and screenshots can sit in an evidence appendix; they should not bury the priorities.
| Deliverable | What it must show | Who uses it |
|---|---|---|
| Scope record | Domains, markets, page types, access and exclusions | Buyer and auditor |
| Executive summary | Highest-risk problems and the commercial pages affected | Marketing lead |
| Findings register | Example URLs, evidence, cause, severity and affected cohort | SEO and engineering |
| Fix specification | Required change and acceptance test | Developer or CMS owner |
| Verification plan | Sample URLs and Search Console checks after release | SEO and project owner |
Here is a sample finding format: Issue: canonical tags on integration pages point to the category hub. Evidence: three sampled integration URLs show that pattern; Search Console reports the sampled URLs as alternate pages. Likely cause: a shared template variable. Fix: make the canonical self-referential on indexable integration pages. Acceptance: inspect a sample from each integration template after deployment. This is an example of a report entry, not a claim about this site or a client.
How should findings be prioritised?
Severity should reflect business exposure and confidence, not the colour of a crawler warning. An accidental noindex on lead-generating service pages is a blocker. A broken link to an archived webinar may be lower priority. The register should state how many pages share the issue, whether the cause is verified, what the fix depends on and the expected effort.
Ask for a proposed order of work. If a template change will resolve 300 URL warnings, the report should identify that one change rather than issue 300 tickets. If a recommendation requires a content decision, it should name that dependency rather than hand everything to engineering.
What does a technical SEO audit cost in the UK?
There is no standard fee for every site. A fixed quote is meaningful only with a defined scope: number of domains and templates, URL volume, regional variants, rendering complexity, Search Console access, log analysis, migration work and post-fix verification. Published UK offers range from a small fixed audit at £495 to a defined larger audit at £1,500 and above. These are supplier examples observed in November 2026, not a market average or a quote from us.
The UK Digital Marketplace listing shows an hourly technical audit and support model. That illustrates why comparing only headline prices is misleading. One provider may include a crawl and report; another may include developer handover, implementation and verification.
Before approving a proposal, ask whether fixes are included, how many page templates receive manual review, whether international and migration work is covered, and what happens if access is incomplete. Our technical SEO service and B2B SEO audit pages explain the available support and current offer.
How do you choose an audit service?
Choose a service that can show a sample finding, explain its method and define what your team receives. Ask who will do the work, which data they need, and how they distinguish a crawl anomaly from a genuine indexing problem. A strong provider should be comfortable stating exclusions.
The best question is, “What will my developer be able to change after reading your report?” If the answer is unclear, request a sample issue register. For a small site with one template, a focused review may be enough. For a multi-market SaaS platform or a planned migration, budget for broader sampling and follow-through.
If you want a first view of the highest-impact issues, request the free 20-minute audit. Use its findings to agree whether a full technical investigation is warranted.

