AI visibility analytics helps SEO agencies show clients which pages AI systems fetch, which pages later receive AI-referred visits, and which pages need technical or content work.
Use HitKeep when the client question is: Are ChatGPT, Claude, Perplexity, or other AI systems discovering our content, and does that discovery create useful traffic?
Run a 14-day agency pilot
Start with one content-heavy client site. The first pilot should prove that the workflow produces at least one client-facing insight, not that every analytics question is solved.
- Install hk.js for pageviews, AI-referred visits, goals, and automatic events.
- Forward server-side AI crawler fetch records from CloudFront logs, nginx, Caddy, an app server, or another edge/origin layer.
- Review at least 14 days of data so crawler fetches have time to line up with later AI-referred visits.
What to show the client
A crawler fetch is not a conversion, and HitKeep does not claim exact attribution from one bot request to one human visit.
- Fetched pages: pages AI crawlers request from the site.
- AI-referred visits: human visits where the referrer matches a known AI assistant.
- Citation yield: fetched pages that later receive AI-referred visits.
- Opportunity pages: pages AI systems fetch often but rarely send visits to.
- Failure hotspots: pages or path groups where AI crawlers hit 4xx or 5xx responses.
Setup checklist
- Create a HitKeep Cloud workspace in the client preferred EU or US region.
- Add the client domain as a site.
- Install hk.js on the site or through the WordPress plugin.
- Create a scoped API client for the site.
- Forward AI crawler fetch records into POST /api/sites/{id}/ingest/ai-fetch.
- Check the AI Visibility dashboard after the first log batches arrive.
- Review correlation after 14 days.