Features

Everything you need to see the machines.

Viz shows you the traffic your other analytics tools structurally cannot - without slowing your site down - and gives you the controls to decide what the machines get to do next.

Classification you never feel

Every request is classified on arrival, and the full logging pipeline adds roughly 2ms per request. Viz is the analytics tool your visitors will never notice.

🧠

60+ bots recognized, kept current

Viz recognizes the major AI players - OpenAI, Anthropic, Google, Perplexity, Common Crawl - plus search engines and traditional bots. When a new crawler appears, it shows up in your dashboard, not in a blind spot.

📊

A real dashboard, inside WordPress

Beautiful charts, date-range filters, a top-bots leaderboard, and a paginated, searchable event log. It all lives in your wp-admin - there's nowhere else to log in just to see your numbers.

Learn more →

🗂️

Eight precise categories

Human browser, AI training crawler, AI search bot, AI user agent, AI autonomous agent, search engine crawler, traditional bot, and unknown. Know not just that a bot visited - but why.

🚦

AI Control - decide who gets in

Block AI training crawlers, AI search bots, or any AI category per-bot with layered robots.txt rules and server-level 403s. A built-in probe checks whether your cache or CDN is letting blocked bots slip through - and tells you how to close the gap.

Learn more →

📣

AI visibility monitoring

On paid plans, Viz asks ChatGPT, Claude, Gemini, and Perplexity the questions your buyers ask - on a schedule - and reports mention rate, citations, sentiment, and share of voice against your competitors.

Learn more →

🔗

Google Analytics & Search Console

Connect GA4 and Search Console (read-only) to see the human visitors AI assistants send you - sessions, engagement, and conversions from AI referrers - alongside your crawl data.

🔒

Privacy-respecting by design

No external scripts. No ad networks. Every event lands in your own database first. Toggle whether humans are logged, exclude admins, and control your retention window.

☁️

Optional cloud sync

Opt in to sync classified events to the Viz cloud for cloud dashboards and longer analytics history. Delivery is HMAC-signed, batched, and acknowledgement-based.

🎛️

Controls that fit your site

Retention windows, human-logging toggle, admin exclusion, and proxy-trust settings - all native to WordPress. Tune it for a personal blog or a million-pageview publisher.

🛡️

Hardened and standards-clean

Built to WordPress coding standards. Prepared statements on every query, escaped output everywhere, and capability checks on every endpoint. No build step, no surprises.

🚀

No build step, no bloat

Plain PHP and vanilla JavaScript. No npm, no webpack, no megabytes of framework. Viz stays lean so your site stays fast.

The thinking behind it

Three principles that shape every feature.

Measure where the truth is

Crawlers never run JavaScript, so browser-based analytics can never count them - not as a gap, but by design. Everything in Viz starts from server-side observation, the only vantage point where humans and machines appear in the same ledger. The bot directory documents who you'll find there.

Never guess silently

User agents can lie, caches can bypass, and any tool that pretends otherwise is selling certainty it doesn't have. Viz keeps an explicit Unknown category, verifies its own blocks with an external probe, and tells you when your CDN is serving bots behind your back.

Observe, then control

Measurement without options is trivia. Every Viz surface leads to a decision you can act on: block a training crawler, keep a search bot, track a buyer prompt, close a cache gap. The blog covers the judgment calls the buttons can't make for you.

Where to start

A sensible first month with Viz.

1

Weeks one and two: just watch

Install, then resist the urge to block anything. Let Analytics and the request log accumulate a baseline: who reads you, what they read, at what volume. Every later decision is only as good as this baseline.

2

Week three: set policy

Now the crawl data can answer the block-or-allow question per bot instead of on vibes. Use AI Control for the bots that only take, keep the ones that send readers, and let the probe verify the result - the directory has per-bot guidance.

3

Week four: measure the outcomes

Connect GA4 to see the humans AI sends back, and start a tracked prompt in AI Visibility to watch the answers themselves. From here the loop runs monthly: crawl trend, referral quality, mention rate, adjust.

See your real traffic mix in under five minutes.