A B2B website audit should not aim to produce the longest possible defect list. It should prepare an investment decision: what can be optimised, where does redesign make sense and when does the current structure prevent meaningful progress?
Twenty-five questions across five decision areas. They do not replace professional assessment, but reveal which evidence is missing before budget, procurement or relaunch.
1. Business and positioning
- Priority: which business objective should the website support over the next twelve months?
- Audience: which organisations, roles and decision situations come first?
- Value: can a relevant visitor understand within seconds which important problem is solved?
- Difference: are there reviewable reasons why a suitable customer should choose this provider?
- Evidence: does content distinguish experience, verifiable fact, hypothesis and promise?
2. Offer and decision journey
- Offer architecture: can buyers find the relevant service without knowing the provider’s internal structure?
- Fit: does every core offer explain objective, baseline, outcomes, boundaries and prerequisites?
- Investment: are pricing logic or scope drivers visible enough to reduce unrealistic expectations early?
- Trust: do ownership, working model, references and claim boundaries appear where uncertainty arises?
- Next step: does the conversion match decision readiness — learning, diagnosis, conversation or project brief?
3. Content and organic discovery
- Search intent: does every priority page answer a defined professional or commercial question?
- Information gain: does it contribute original models, experience or evidence rather than interchangeable summaries?
- Page signals: do title, main heading, description, canonical and internal links match the actual content?
- Indexing: are important pages crawlable, indexable, included in sitemaps and free from contradictory signals?
- Maintenance: do business-critical pages have owners, sources and explicit review triggers?
4. Experience, accessibility and performance
- Orientation: do navigation, hierarchy and language remain understandable on mobile as well as desktop?
- Operation: can core journeys be completed with keyboard and visible focus, without a pointer?
- Understanding: do links, headings, forms, errors and status messages have clear labels?
- Stability: does the page remain visually stable while loading and does its primary content respond promptly?
- Resilience: do core contents work without unnecessary dependencies and across realistic devices, browsers and network conditions?
5. Technology, operations and measurement
- Ownership: are domain, hosting, accounts, licences, source code, data and access controlled by the organisation?
- Change: do material releases use staging, review, backup and a tested rollback route?
- Security: are updates, roles, logging, vulnerability response and data minimisation operated accountably?
- Business journeys: are forms, search, checkout, languages, integrations and scheduled jobs monitored functionally?
- Measurement: do reports distinguish reach, interaction, technical acceptance and personally reviewed business outcomes?
Turning answers into a decision
Optimise
The objective and architecture hold; specific pages, signals or journeys have bounded weaknesses.
Redesign
The offer and technology remain viable, but journeys, visual hierarchy or components create friction.
Relaunch
Positioning, information architecture, content model, technology or migration need to be reworked together.
Diagnose first
When evidence, objectives or ownership are missing, a large solution is not ready for decision.
The number of negative answers is not the decision. One structural risk — such as missing ownership of critical access or an uncontrolled URL migration — may matter more than ten small presentation issues.
Use metrics in context
Core Web Vitals provide defined technical experience signals for loading, interaction and visual stability. Search Console can show search performance and indexing states. Analytics describes observed use under its measurement configuration. None of those systems alone explains whether the offer was understood or an inquiry was commercially qualified.
A grounded assessment combines quantitative signals with content review, technical testing and direct feedback from sales, service and operations. Missing or consent-limited data is a visible uncertainty, not a reason to invent precision.
Primary sources and claim boundary
- Google Search Central: SEO Starter Guide – useful, understandable and crawlable website foundations.
- web.dev: Web Vitals – definitions and interpretation of central experience signals.
- W3C: Web Content Accessibility Guidelines 2.2 – testable requirements for accessible web content.
This checklist is neither a certification nor a legal, security or accessibility conformance assessment. Priority and effort depend on the business objective, audience, technology, data and actual risk profile.
Relevant starting point
Digital Growth Diagnostic
When optimisation, redesign or relaunch cannot yet be chosen responsibly, the Diagnostic connects business goals, user needs, technical reality and budget into a prioritised 90-day plan.