The Free Audit · two free scans
Run a free Audit on your agency's website.
Two free scans that show exactly why AI engines aren't citing you, and whether your site is a HIPAA liability.
Can ChatGPT and Perplexity cite you?
See how you show up (or don't) in ChatGPT, Perplexity, and Google AI Overviews, flags missing schema, weak E-E-A-T, and no .gov data anchors.
Is your tracking a liability door?
Scans for pre-consent tracker firing, PHI-adjacent data exposure, CIPA/ECPA wiretap risk, and privacy-policy mismatch.
Each result points to the fix, server-side, consent-gated tracking (a full remediation service is coming soon; reach out and we'll walk you through it) or Digital Foundation (a full rebuild). Compliance reference: HIPAA Security Rule §164.312(e)(1) and HHS-OCR tracking guidance. The Audit flags risk; it isn't legal advice.
How the scans work
What does the AEO Audit check on an insurance website?
The AEO Audit reads your page the way ChatGPT, Perplexity, and Google AI Overviews do. It checks for the three schemas AI engines use to decide who to cite (Article, FAQPage, and Dataset markup in the page head), organization-level authorship for YMYL topics like Medicare and life insurance, answer-first page structure, an llms.txt file at your site root, and whether your robots.txt or firewall is blocking AI crawlers like GPTBot and PerplexityBot. It is the same pre-publish checklist we run on every Medicare, health, and life agency site we build.
Sample finding: your Medicare Advantage page quotes CMS enrollment numbers but carries no Dataset schema pointing at the CMS source, so an AI engine has no machine-readable reason to treat your page as the authority. It cites a competitor who does.
What your score means: the Audit returns 0 to 100. Above 85, AI engines can read, verify, and cite you. 60 to 84 means fixable gaps, usually missing schema or thin answers. Below 60, the engines are citing someone else when your prospects ask about plans in your county.
What does the HIPAA Tracking Audit look for?
The HIPAA Tracking Audit loads your site and watches what every tracker does before a visitor gives consent. It flags client-side GA4, Google Tag Manager, Meta Pixel, and TikTok pixels that fire on page load, page URLs and form fields that leak PHI-adjacent detail (the plan someone asked about, a health condition, an age plus ZIP), CIPA and ECPA wiretap exposure from session-recording tools, and gaps between what your privacy policy promises and what your trackers actually send.
Sample finding: a Meta Pixel fires on your ACA quote form before consent, sending Meta the page URL, which names the health coverage the visitor asked about. Under HHS-OCR tracking guidance, that pattern is exactly what regulators and class-action firms look for.
What your result means: every finding is one liability door. A clean result means zero pre-consent trackers and no PHI-adjacent leakage. One or more findings means the fix is a flip to server-side, consent-gated tracking, which keeps your ad measurement without the exposure.
Common questions
Free Audit questions, answered.
What is an AEO audit for an insurance agency?
An AEO audit scores how your agency shows up when buyers ask AI engines like ChatGPT, Perplexity, and Google AI Overviews. It flags missing schema, weak E-E-A-T, and the absence of authoritative .gov data anchors that AI engines use to decide who to cite.
How do I check if my agency website's tracking is HIPAA compliant?
The HIPAA Tracking Audit scans your site for trackers firing before consent, PHI-adjacent data exposure, CIPA/ECPA wiretap risk, and privacy-policy mismatch. Each finding is a potential liability door.
Are the Audit tools really free?
Yes. Both the AEO Audit and the HIPAA Tracking Audit are free. They ladder into Up to Code (the fix) or Digital Foundation (a rebuild).