Every AI visit, from the first crawl to the sale.
ChatGPT, Perplexity and Gemini read your pages and send you buyers your analytics never credit. Viz sees every AI crawl, wins you the answers, publishes what is missing, credits each purchase, booking and lead to the assistant that sent it, and gives AI agents the tools (WebMCP) to act for the visitor they work for. All inside wp-admin. Proof runs the whole way: crawled, cited, visited, converted.
Free forever plan · Installs in 2 minutes · No credit card
Illustrative numbers
The AI economy is reading your site. Now it is starting to act on it.
Automated traffic rivals human traffic on many sites, AI crawlers are its fastest-growing slice, and agents already fetch pricing and booking pages for the people they work for. Every JavaScript tracker is blind to all of it, by design.
Turning AI traffic into revenue is a loop, not a report.
Five stages, one plugin. Viz measures every stage from the server and moves the ones that can be moved: it wins the answers you are missing, publishes what is not there yet, converts the visit, and hands agents the tools to act. Proof runs the whole way: crawled, cited, visited, converted.
Crawl
Server-level analytics shows which AI engines read you, which pages they pull and how often: 8 categories, 60+ named bots, per-URL crawlability. Access stays your call with AI Control.
Answer
AI Visibility asks the engines your buyers' questions and tracks whether you are mentioned, cited and how you compare. The AI Content Pipeline turns the gaps into reviewed drafts in Posts → Drafts, and every published piece reports back.
Visit
When an assistant sends a person, Viz credits the visit to one of 13 assistants at the server, no tag manager. Landing Paths shows half of those visitors one next step and measures the lift.
Convert
AI Conversions credits every purchase, booking, lead and sign-up to the assistant that sent the visitor, captured from the plugins you already run, never names or emails. Free on every plan.
Act
Every page registers WebMCP tools generated from your business profile, contact form and catalog. An agent can describe your business, send a contact request and, on WooCommerce, search, browse and fill the visitor's cart. Every call is logged; leads and the purchases that follow are credited to the agent. The channel is early; the door is open.
Sensor and actuator, in one plugin.
Visibility tools measure but cannot act. Content tools act but cannot measure. Viz is both, inside WordPress, which is what makes it the system that moves the numbers it reports.
Inside WordPress
Viz sees the server, writes the draft, records the order and registers the tools, all from the plugin. Every other tool looks at your site from outside; nowhere else to log in.
Sensor and actuator
The same system that measures a gap publishes the fix, then verifies from your own logs that the crawlers ingested it, the answers changed, the visits arrived and the sale followed.
Agents get tools
WebMCP tools are generated from your business profile, contact form and catalog. Nothing to configure, every call logged, every lead and purchase credited, and a Verified on homepage check so you know they are live.
Three ways to count traffic. Only one sees the whole picture.
The measurement point - browser, log file, or application server - determines which visitors exist in your data at all.
JavaScript trackers
GA4, Plausible, Fathom…
Run in the browser, so they only count visitors who execute your scripts. Crawlers never do. Result: your biggest new traffic source scores a flat zero, and bot-inflated "direct" visits muddy what remains.
Blind to bots
Raw server logs
Access logs, AWStats…
See everything, understand nothing. Every hit is a text line with no classification, no dashboards, and - on managed WordPress hosting - often no access at all. Parsing them into answers is a weekend project that never ships.
Data without answers
Viz
Inside WordPress itself
Hooks the request inside WordPress after your CDN and cache have done their job, classifies it on the spot, and stores it in your own database - so "how much of my traffic is AI?" is a chart, not a grep.
Sees and explains
Live in two minutes. Insightful from the first hit.
Install the plugin
Drop Viz into WordPress, activate, and connect your free account. It hooks every request that reaches your server and adds a couple of milliseconds you'll never feel.
Every visit gets classified
Every request is identified and sorted into 8 clear categories - human, AI, search, or bot. More than 60 named bots are recognized out of the box.
Watch your real traffic mix
A clean dashboard right inside wp-admin: charts, top bots, and a searchable log of every request.
Eight categories. No more lumping bots into “direct.”
Viz tells you whether an AI is training on you, answering a live question, or acting on someone's behalf - because those three deserve very different responses from you.
Training, retrieval, referral, and now action.
Four different economies, and your site is in all of them.
Training crawls take, once
A training crawler reads your archive to improve a model. It may never come back, and it sends you nothing. If your content is your product, this is the traffic you may want to meter or block - and you can only negotiate with what you can measure.
Retrieval crawls answer questions
AI search bots fetch your pages to answer a live user query. Some of those answers cite you and send readers; many don't. Watching which pages retrieval bots hit tells you what AI engines think you're an authority on.
Referrals are the new SEO
When ChatGPT or Perplexity links you and a human clicks through, that visitor behaves differently - often high-intent, often bypassing your homepage. Viz catches those referral visits at the server and credits what they go on to do, so every assistant carries a conversion rate and a value, not just a visit count.
Agents come to act
An assistant working for a person already fetches pricing, booking and contact pages. Viz shows what those agents came to do, grades whether your site can answer them, and hands them tools: WebMCP on every page, and /ai-contact/ for the ones that arrive from outside a browser. Early, and we say so; ready sites get the first requests.
Built for the server, tuned for speed, and honest about your traffic.
60+ bots, 2ms, zero slowdown
OpenAI, Anthropic, Google, Perplexity, Common Crawl, and more - kept current so new crawlers show up the day they start knocking. The whole pipeline adds about 2ms per request; your visitors never know it's there.
Your data, your server
No external JavaScript. No ad-tech. Everything lands in your own database first. You decide what to keep and for how long.
Decide which bots get in
AI Control gives every AI bot its own allow-or-block switch, enforced with layered robots.txt rules and server-level 403s - and a built-in probe verifies your policy is actually holding.
Know what AI says about you
Paid plans track how ChatGPT, Claude, Gemini, and Perplexity answer your buyers' questions - whether you're mentioned, cited, and how you compare to competitors.
Publish what AI is looking for
The AI Content Pipeline researches topics from your own AI-traffic evidence, writes and reviews the drafts, and delivers them into Posts → Drafts. You publish; every piece is tracked for crawls, citations, and referrals.
Count what AI converts, and give agents tools
Every purchase, booking, lead and sign-up is credited to the assistant that sent the visitor, with rate and value per assistant, captured inside WordPress. Every page also registers WebMCP tools, so an AI agent working for a visitor can describe your business, send a contact request and, on WooCommerce, fill the visitor's cart. Every call is logged and credited. Free on every plan; GA4 adds session depth if you want it.
Straight answers about AI traffic.
Why can't Google Analytics see AI bots?
GA4 counts a visit when the browser executes its JavaScript tag. Crawlers like GPTBot and ClaudeBot fetch your HTML and leave - they never run scripts, so they never appear in GA4 at all. The only place they are visible is at the server, which is where Viz measures.
How does Viz tell an AI bot from a human?
The major AI operators publicly identify their crawlers - OpenAI, Anthropic, Google, and Perplexity all publish their bot names - and Viz keeps an up-to-date catalog of more than 60 of them. Every request gets sorted into one of eight categories, and anything Viz can't identify with confidence stays visible in an explicit Unknown bucket rather than being silently dropped.
Does logging every request slow my site down?
The full pipeline adds about 2 milliseconds to a request. For comparison, a typical WordPress page render is measured in hundreds of milliseconds. No external services are called during the request.
Can I block AI bots without breaking my SEO?
Yes. Viz separates AI training crawlers (GPTBot, ClaudeBot, CCBot) from search engine crawlers (Googlebot, Bingbot), so you can serve 403s to the former while the latter keep indexing you normally. A built-in probe then verifies the block is actually holding.
Is my visitor data sent anywhere?
Requests are logged to your own WordPress database first - there is no external JavaScript and no ad-tech. You control retention. Paid cloud features only sync the aggregate stats needed to power them.
Can Viz tell me whether AI traffic converts?
Yes, and without Google Analytics. When a visitor arrives from ChatGPT, Perplexity, Gemini or another assistant, Viz remembers who sent them (one consent-gated first-party cookie, no personal data) and credits the purchase, booking, form submission or sign-up they go on to make - captured on your server from WooCommerce, your forms plugin, your booking plugin or your LMS. The AI Conversions tab shows visits, conversions, rate and value per assistant, on every plan.
What does Viz do for AI agents?
Four things. It shows what agents came to do on your site - book, buy, check prices, browse - next to the same numbers for humans. It grades whether your site can even answer an agent's questions (describe, list, price, availability, act) and where each answer lives. It registers WebMCP tools on every page, so an agent running in the visitor's browser can describe your business, send a contact request and, on WooCommerce, search, browse and fill the visitor's cart (nine tools on a store, three elsewhere); every call is logged, contact requests become leads, and a purchase that follows a tool call is credited to the agent. The agent never checks out; the visitor does. And for agents that never open a browser, it publishes a plain, machine-readable contact form at /ai-contact/. Agents completing requests is still rare; agents reading money pages is already routine, so the tools are there for when they do.
What is WebMCP and do I have to set it up?
WebMCP is an open web standard (Google, Microsoft, and since August 2026 OpenAI's ChatGPT desktop browser, plus Codex and Chrome 150+) that lets a page hand the AI agent in a visitor's browser a small set of tools it can call directly instead of guessing at buttons and forms. Viz generates yours from your business profile, your contact form fields and, on WooCommerce, your catalog. There is nothing to write or configure: the tools are on by default, need HTTPS, register only in browsers that support the standard, and add about 3 KB of first-party inline script with no external requests. Viz checks your homepage and shows a Verified on homepage pill under AI Conversions, Agent tools once the tools are live.
Can Viz write content too?
On paid plans, yes. The AI Content Pipeline proposes topics from your own AI-traffic evidence; you approve one, and an outliner, writer, and adversarial reviewers deliver a finished draft into Posts → Drafts, hero image included. Publishing it is the approval - every published piece is then tracked for AI crawls, citations, and referral traffic, with a fresh report every morning.