The agency pilot kit is a short path for SEO agencies that want to test AI visibility analytics with one real client site.
The goal is one useful client-facing insight after 14 days.
Who it is for
Avoid the pilot when the site has almost no public content, no access to server or edge logs, or no way to install the browser tracker.
- SEO agencies with content-heavy client sites.
- B2B teams where comparison, docs, or pricing pages matter.
- Publishers and resource sites that expect AI discovery.
- Agencies already reporting on organic traffic, content decay, or technical SEO.
What the pilot includes
- One HitKeep Cloud workspace and one client site.
- hk.js browser tracking.
- A scoped API client for server-side AI fetch ingest.
- AI crawler fetch reporting and AI-referred visit reporting.
- Fetch-to-visit correlation.
- A client report based on the AI SEO reporting template.
Required setup
AI crawler visibility requires a server-side feed. Pick the path the client can actually operate.
| Site setup | Recommended feed |
|---|---|
| CloudFront or S3 static site | CloudFront logs to Lambda |
| nginx or Caddy | Access log forwarder |
| App server | Middleware or scheduled log job |
| Custom edge | Edge log parser |
14-day workflow
| Day | Work |
|---|---|
| 1 | Create cloud workspace, site, and scoped API client |
| 1 | Install hk.js or the WordPress plugin |
| 1-2 | Connect the server-side AI fetch feed |
| 3 | Confirm fetch records arrive in AI Visibility |
| 7 | Check early failure hotspots and crawler mix |
| 14 | Review correlation, opportunity pages, and AI-referred visits |
Success criteria
- A page AI systems fetch often.
- A fetched page that later receives AI-referred visits.
- A page with crawler errors worth fixing.
- A content section that gets AI interest but weak downstream visits.
- A client-ready recommendation for the next month.