---
title: Automated Client Audits — 70-Step Audit Script
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-02-16-monday-call-w-melissa-122659240.md
tags:
- client-management
- automation
- audits
- google-analytics
- google-tag-manager
- google-search-console
- tooling
layer: 2
client_source: null
industry_context: null
transferable: true
---

# 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:

- **Cloudflare** (Zone ID)
- **Google Tag Manager** (Container ID)
- **GA Property ID**
- **Google Search Console** access
- **WordPress Application Password** (for website-level fixes)

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 |
|---|---|---|
| [[wiki/clients/didion/_index\|Didion]] | Partial | GSC access confirmed; missing Cloudflare, GTM |
| [[wiki/clients/jbf/_index\|JBF]] | 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 [[wiki/people/melissa-cusumano|Melissa]]
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

- **Two-factor authentication** on client accounts creates friction when obtaining access
- Clients with a history of bad agency relationships (e.g., Didion) may be slow to hand over credentials
- The script cannot audit or remediate areas where credentials are absent — partial audits are possible but incomplete

## Related

- [[wiki/knowledge/abm/abm-automation-pipeline|ABM Automation Pipeline]]
- [[wiki/clients/didion/_index|Didion]]
- [[wiki/clients/jbf/_index|JBF]]
- [[wiki/meetings/2026-02-16-monday-call-melissa|Monday Call w/ Melissa — 2026-02-16]]