wiki/knowledge/client-management/automated-client-audits.md · 515 words · 2026-04-05

Automated Client Audits — 70-Step Audit Script

Overview

Asymmetric has developed a 70-step automated audit script that generates comprehensive technical reports for clients. The tool covers website health, Google Analytics (GA), Google Tag Manager (GTM), and Google Search Console (GSC), and is designed to surface issues, document fixes, and provide clients with clear evidence of work performed.

Reports are delivered as structured documents (visible in Slack channels) and serve both internal QA and client communication purposes.

What the Script Audits

Area What It Checks
Website Meta descriptions, technical issues, content gaps, fixes applied
Google Analytics Tracking integrity, traffic sources, data quality
Google Tag Manager Tag count, event configuration, variable validation
Google Search Console Traffic data, top queries, indexing signals

The script also draws on a client characteristics table — a structured reference sheet containing each client's business model, goals, geographic scope, size, and budget — which improves AI-assisted analysis and report quality.

Credential Requirements

The script's full capabilities depend on having complete access credentials for each client. Required credentials include:

Without these, the script runs in a degraded mode and cannot audit or fix certain layers of the client's stack.

Client Credential Status (as of Feb 2026)

Client Status Notes
[1] Partial GSC access confirmed; missing Cloudflare, GTM
[2] Incomplete Key credentials not yet received; follow-up needed with Lisa
Next Level Incomplete Credentials not yet on file
Advanced Health & Safety Full Used as example of complete audit output

Example Output

A full audit for Advanced Health & Safety included:
- 13 missing meta descriptions identified → 10 added and fixed
- GA tracking verified as healthy
- GTM tags, events, and variables reviewed and validated
- GSC top queries and traffic trends documented

This level of detail is difficult to convey in a plain email to clients — the generated report document is the appropriate artifact for client communication.

Didion Case Study

Diana (Didion) requested an explanation of recent technical fixes. Rather than attempting to summarize the work in an email, the plan is to:

  1. Mark runs a partial audit using available GSC access
  2. Report is sent to [3]
  3. Melissa forwards the report to Diana

This establishes a repeatable pattern: use the audit report itself as the client-facing deliverable when explaining technical work.

Known Limitations

Sources

  1. Index\|Didion
  2. Index\|Jbf
  3. Melissa Cusumano|Melissa
  4. Abm Automation Pipeline|Abm Automation Pipeline
  5. Index|Didion
  6. Index|Jbf
  7. Melissa — 2026 02 16