What a report looks like

A tour of the audit report: pages table, per-URL beacon rows with extracted IDs, CSV exports, and run history.

Report sections

Every completed audit produces a job page with:

1. Summary — domain, discovery mode, pages found vs. audited, subdomain count, and whether browser rendering was used.
2. Pages table — one row per audited URL with HTTP status, title, meta description, H1, canonical URL, and word count. Dead (404) and bot-blocked (403) pages are flagged rather than hidden.
3. Beacons table — one row per tracker per URL, with the tracker name, its type, the extracted identifier, and how it loads. This is the table most people come for.
4. CSV downloads — the full pages and beacons datasets as CSVs for spreadsheets, pivot tables, or diffing against a previous run.
5. Delete button — removes the run from the server and marks it deleted in the usage log.

Example beacon rows

Beacon rows identify the tracker, classify it, show the extracted identifier, and note the load method. A few illustrative rows (from a static scan):

Tracker	Type	Identifier	Load method
Google Tag Manager	Container	GTM-W2SMVTRF	Script tag in HTML
Google Analytics 4	Analytics	G-TM6HHFGY81	Via Google Tag Manager (client-side tag)
Meta Pixel	Advertising	1234567890123456	Script tag in HTML
Hotjar	Session replay	1431489	Script tag in HTML
reCAPTCHA	Security	Enterprise	Script tag in HTML (form pages only)

Tags deployed through a tag manager appear as "via Google Tag Manager (client-side tag)" because the static scan sees the container, not the individual tag — the container row is real evidence; the deployment path is the honest inference. Browser-render mode can confirm which tags actually fire. Why one container can hide many tags.

Reading the pages table

Common flags: pages missing a meta description or H1, duplicate titles across template pages, canonical URLs pointing elsewhere (redirects, syndicated content), and sitemap URLs returning 404 — stale entries the site owner forgot to remove. The word-count column helps spot thin or accidentally empty pages.

Diffing runs over time

Download the CSVs from two runs and compare: new rows in the beacons CSV mean new trackers appeared; rows in the pages CSV with a 404 status that were previously 200 mean pages dropped. Sign in with Google to keep runs organized in your history while you do this.