What our website audit checks: 260 items in 13 areas.

Titles, descriptions, headings, indexing, canonical URLs, sitemaps, internal links, pages that used to exist, and available search-result signals.

Live ranking signals depend on configured services. Findings reflect the pages reached.

Structured data, a consistent business name, question-and-answer content, details present in the first HTML, and crawler-rule signals.

Configured OpenAI and Perplexity samples separately look for real mentions at scan time. They need a clear kind of business and location, and they can't guarantee recommendations.

55 WCAG 2.2 A and AA criteria plus 5 related accessibility and policy items. Image descriptions, accessible names, labels, keyboard, focus, contrast, zoom, reflow, video, and PDF concerns.

Combines automation, configured browser tests, and human review. This is not a legal certification.

Lighthouse, available real-user Core Web Vitals data, image sizing, loading behavior, blocking scripts, and third-party script weight.

Real-user data needs sufficient traffic. Browser and template checks require successful measurement.

Viewport, body text, tap-to-call, horizontal scrolling, reflow, fixed-width regions, zoom, and interaction.

Rendered checks are sampled and browser-dependent. They do not cover every device or journey.

Page metadata, image descriptions, broken links, duplicate content, soft 404s, robots rules, script errors, analytics tags, and network diagnostics.

Browser diagnostics may be incomplete or unavailable.

HTTPS, TLS, response headers, cookies, redirects, SPF, DMARC, common DKIM selectors, DNSSEC, CAA, exposed files, known script vulnerabilities, and consent tools.

These are configuration and risk signals. They are not a penetration test and do not establish compliance with any privacy law.

Reading level, blog freshness, FAQ content, distinct titles and descriptions, privacy and terms links, and leftover placeholder text.

Factual and legal accuracy still need professional review.

Name, address, phone, hours, business schema, available Google profile data, directions links, social links, and selected multi-location checks.

Google data requires configured access and a usable business and location match. Not every directory is checked.

Contact forms, where your buttons lead, phone links, booking and chat widgets, and analytics.

The default audit does not send real enquiries or complete every journey. Some checks are conditional.

Click-to-call, navigation while scrolling, media that plays by itself, font loading, cookie banners that get in the way, and not-found pages.

Several observations rely on sampled browser tests and available evidence.

Visible heading, business name, clear next step, contact visibility, oversized hero images, body text size, and zoom restrictions.

These are practical first-screen signals, not a complete design critique. Unreliable captures may need human review.

Phone numbers that disagree across the site, call links versus the number shown, accessibility-policy claims, and whether your main button is in the first HTML.

Observable signals do not independently verify every business or policy claim.