Why privacy sits next to performance and SEO
Shoppers and regulators both notice when a site ignores opt-out signals or hides controls behind dark patterns. Outside-in audits can observe those signals without claiming to certify GDPR or CCPA compliance.
AuditHQ stamps privacy findings as AHQ-PRV-* observations in Lab measurements (Privacy group) — separate from Best practices security checks — so a missing GPC acknowledgment does not masquerade as a CSP fail.
Signals worth fixing first
Global Privacy Control (Sec-GPC) — when the client sends the signal, acknowledge it in a way users can see (and document on your privacy page).
CMP / consent UI — conspicuous controls beat buried toggles; dark patterns that push Accept-all while hiding Reject are observable.
Obvious third-party pixels and cookies described honestly on the Cookie Policy — AuditHQ does not invent a consent banner for analytics that already run.
How to remediate with an agent
Open Lab measurements → Privacy (observation). Copy the category AI fix prompt or the Lab Fix-first spotlight when a privacy row is in the top fails.
Prefer additive UX: show the opt-out state, honor GPC, remove the observed signal — do not ask the model to invent a legal memo.
Re-audit after deploy. Observation wording stays observation wording; clearing the finding means the measured signal changed.