SERP Cohort Audit

The SERP Cohort Audit is the audit you reach for when you already suspect a problem in this dimension and need a fast, copy-paste-able fix list. It reuses the same chrome as every other jwatte.com tool — deep-links from the mega analyzers, AI-prompt export, CSV/PDF/HTML download — but the checks it runs are narrow and specific.

Enter 3-10 target queries, and the audit runs DuckDuckGo SERPs to build a competitor cohort map — which domains appear repeatedly across your queries, how often your own domain appears, and who dominates the share of voice.

What it actually checks

This is a partial extract of the audit's real findings — the same strings the tool prints when a check trips. Use it as a quick sanity check before you run the audit live:

Why this dimension matters

Analytics misconfigurations silently compound. A missing <script> tag on one page type, a hardcoded streaming ID that survives a site rename, consent-mode defaults that drop 30% of real sessions — each is invisible until you audit it directly. And the GA4 data that looks "fine in the dashboard" may be dropping AI-referrer visits into "(direct)" because the referrer isn't in the Traffic Source channel grouping.

Common failure patterns

GA4 default channel grouping misses AI referrers — chatgpt.com / perplexity.ai / claude.ai / gemini.google.com / copilot.microsoft.com get bucketed as "Referral" or "(direct)" instead of their own channel. The audit recommends a custom channel grouping or a regex filter to surface AI traffic.
GTM container loaded without Consent Mode v2 — analytics fires before consent, breaking GDPR compliance. Consent Mode v2 shipped in March 2024; older GTM configs still fire without it.
Server-side GTM container without a fallback — if the first-party GTM endpoint goes down, data is lost. Keep a client-side fallback or a dual-destination setup.
Raw log data not aggregated — every hosting platform (Netlify, Vercel, Cloudflare) exposes raw access logs but most sites never process them. Daily log summarization catches 4xx/5xx spikes, AI-crawler visits, and suspicious patterns hours-to-days before Search Console surfaces them.

How to fix it at the source

Audit GA4 + GTM configs once per quarter against a known-good checklist: Consent Mode v2, custom channel groupings for AI traffic, event taxonomy consistency (snake_case, bounded parameter vocabulary). Set up a daily log-summary cron on your hosting platform — the signal is faster than Search Console.

When to run the audit

After a major site change — redesign, CMS migration, DNS change, hosting platform swap.
Quarterly as part of routine technical hygiene; the checks are cheap to run repeatedly.
Before an investor / client review, a PCI scan, a SOC 2 audit, or an accessibility-compliance review.
When a downstream metric drops (rankings, conversion, AI citations) and you need to rule out this dimension as the cause.

Reading the output

Every finding is severity-classified. The playbook is the same across tools:

Critical / red: same-week fixes. These block the primary signal and cascade into downstream dimensions.
Warning / amber: same-month fixes. Drag the score, usually don't block.
Info / blue: context-only. Often what a PR reviewer would flag but that doesn't block merge.
Pass / green: confirmation — keep the control in place.

Every audit also emits an "AI fix prompt" — paste into ChatGPT / Claude / Gemini for exact copy-paste code patches tied to your stack.

Related tools

GA4 / GTM Configuration Audit — Detects Google Analytics 4 + Google Tag Manager on a page.
AI Referrer Log Parser — Paste access-log lines.
Web Log Anomaly Detector — Paste raw access logs (Netlify, Nginx, Apache, CloudFront).
Mega Analyzer — One URL, every SEO/schema/E-E-A-T/voice/mobile/perf audit in one pass..

Fact-check notes and sources

This post is informational and not a substitute for professional consulting. Mentions of third-party platforms in the tool itself are nominative fair use. No affiliation is implied.

Why SERP Cohort Audit Exists