Service · Visibility Monitoring
Visibility analytics & continuous monitoring
Recurring measurement that keeps every discovery signal separate, catches regressions early, and ties visibility to real business outcomes.
Why it matters
“AI crawler traffic up 400%” is not a business result. Crawlers fetching your pages tell you about access, not demand, and not whether anyone is recommending you. Bots, assistants, agents and people need to be counted separately before any of the numbers mean anything.
The classification rule
Seven buckets. Never one number.
| Bucket | How we identify it | Is it demand? |
|---|---|---|
| Human organic search | Analytics + Search Console | Yes |
| Human referrals from AI interfaces | Known assistant referrers and assistant-added UTMs | Yes, where identifiable (undercounted) |
| Verified AI crawlers | User agent plus verification (published IPs, reverse DNS, verified-bot signals) | No — access, not recommendation |
| User-initiated AI fetches | e.g. ChatGPT-User, Claude-User, Perplexity-User — verified | A weak signal that someone asked about you |
| Identified agent API activity | API keys, signed requests, MCP client info | Possibly — if calls convert |
| Unclassified automation | Bot-like traffic that isn't verified | No |
| Qualified leads & conversions | Spam-checked submissions meeting qualification criteria; sales | The outcome |
Scope
What's included
Search & AI
- Search Console and Bing Webmaster dashboards, including generative AI reports
- AI citation and brand-mention sampling on a fixed prompt set
- AI-referral segment in analytics
Crawlers & agents
- Verified crawler activity by provider and purpose
- Agent API request monitoring
- Cloudflare traffic and bot instrumentation
Health
- Technical SEO regression detection: status codes, canonicals, noindex, robots, sitemaps
- Domain, DNS and certificate monitoring
Outcomes
- Landing-page and conversion measurement
- Monthly visibility report with caveats and data gaps
Deliverables
What you receive
- A baseline snapshot of every metric before changes
- A dated change log, with external events annotated
- Monthly report: summary, search, AI interfaces, crawlers & agents, technical health, outcomes, caveats
- Alerts for regressions, expiring domains and certificates
Measured outcomes
What we report
- Qualified leads and conversions by source bucket
- Regressions caught and fixed, with time to fix
- Trends in each bucket against baseline, with confidence notes
How we work on this
Method: a 28–90 day baseline, a logged change, an equal post-change window once changes have been crawled, and comparison against unchanged page sets where possible. Short windows and external algorithm changes limit what any attribution can prove, and we say so in every report.
What we won't promise
- To count bot traffic as demand
- That more AI crawler requests means you're being recommended
Related services
Start with an assessment.
A fixed-scope review of your domains, search infrastructure, AI discoverability and agent readiness — with prioritized findings and a plan you can act on.