Website audit checklist for local-service companies.

Audit the business function first, then the technology. A familiar CMS or hosting brand is not evidence that a site is generating, routing, or measuring leads correctly.

Where this sits. Operator map: How we audit. Personal-brand QA master: Website QA audit. This page is the older local-service checklist — a skin, not a second trunk.

Platform-neutral rule. Record the provider, CMS, dependencies, licenses, and access actually in use. Do not recommend a host or CMS merely because BlitzMetrics has used it before. Choose and test the architecture against the site’s accepted functional baseline.

1. Business job

Primary services and service areas are clear.
The intended action—call, form, booking, or purchase—is visible.
Ownership exists for every lead destination.

2. Public experience

Important pages, navigation, media, and URLs work.
Mobile layouts have no clipping or horizontal overflow.
Trust proof is specific, sourced, and relevant.

3. Lead path

Primary forms and phone links are tested.
Spam/consent behavior and success states are recorded.
Notifications, CRM routing, and responsible people are verified.

4. Measurement

Analytics and tag-manager ownership are known.
Calls, form submissions, bookings, and qualified leads are measurable.
Conversion events fire once and reach the right account.

5. Search controls

Titles, descriptions, canonicals, robots directives, and sitemaps are verified live.
Organization/local-business schema matches the real entity.
Important redirects are inventoried and tested.

6. Delivery and recovery

HTTPS and delivery behavior are correct for the recorded architecture.
A recovery method, retention, and rollback owner are recorded.
No uptime or recovery guarantee is inferred from a provider logo.

7. Dependencies

Used plugins, snippets, APIs, frameworks, and licenses map to a business function.
Unused, abandoned, unknown, or unlicensed components are flagged.
Custom behavior and third-party fees have an owner.

8. Migration readiness

Content/data exports and key URLs are available.
The destination has acceptance tests for every recorded function.
The source and rollback path remain until tests pass.

The output is a functional baseline.

A useful audit leaves behind a testable record of pages, lead routing, tracking, redirects, search controls, publishing, dynamic behavior, dependencies, recovery, and exceptions. That record can survive a move to a new host, CMS, headless stack, or static build.

Need this managed for an existing client site?

Review the company-site hosting add-on and its exact service boundaries.

View the hosting add-on Read the standards