68% of Google searches now end without a click. Every day, AI systems are crawling your site to train their models, fetching your pages live to answer someone's question, and — increasingly — sending you real human visitors after quoting you in a chat. Most WordPress sites have no visibility into any of this, and nothing in place to make it work well.
FocusWeb AI Visibility gives you both sides: the infrastructure that makes your content easy for AI to read, and a dashboard that shows you exactly what's happening once it does.
Part 1 — Get Found
A live map of your site, built for AI
/llms.txt is the plain-text convention AI systems check first — a machine-readable summary of who you are and what's on your site. It's generated automatically, updates as you publish, and gives every page a real description (pulled from your SEO meta description plus page content), not just a bare list of titles and links.
Structured data that doesn't fight your SEO plugin
Baseline JSON-LD (WebSite, Article/WebPage schema) is added automatically — and steps aside cleanly the moment it detects Yoast, Rank Math, or AIOSEO, so you never get duplicate or conflicting markup.
A door AI agents can actually use
A read-only API (/wp-json/aiv/v1/ask) lets AI agents search your published content directly, and registers with WordPress's official Abilities API so MCP-compatible clients discover it automatically — no extra setup.
Part 2 — See What's Happening
Crawler monitoring, not just chatbot detection
The dashboard tracks 16 distinct AI systems by name — split into training crawlers (GPTBot, ClaudeBot, Google-Extended, Bytespider, Amazonbot, Common Crawl, and more) that are indexing your content for AI models, and live agent requests (ChatGPT-User, Perplexity-User, Claude-User, OAI-SearchBot) fetching a page right now to answer someone's question. A daily, color-coded chart shows the split over time.
llms.txt reads and agent questions, logged
See exactly how often your llms.txt file is fetched and by whom, plus a running log of the actual questions AI agents asked through your search endpoint — real signal on what people are asking AI about your business.
Human traffic attribution via GA4 (optional)
Crawler logs show AI reading your site — this shows AI sending you visitors. Turn on the optional Google Analytics integration to fire an ai_referral event (source / medium / campaign) whenever a real visitor arrives from ChatGPT, Gemini, Perplexity, Claude, or another AI chat, using your existing GA tag or a Measurement ID you provide.
One screen for AI-visibility health
Settings & Status shows live pass/fail indicators for Analytics, llms.txt availability, and schema enforcement, backed by a self-test with error codes and a rolling diagnostic log — so if something breaks, you find out from the plugin, not from a drop in AI traffic.
Schema, page by page
The Schema Browser lists the generated JSON-LD for every post and page, with a one-click Validate link to Google's schema validator and an inline editor for a custom override when the default isn't enough.
Why It Matters
Search traffic is splitting three ways: people who click a blue link, AI systems that crawl and cite you without a click ever happening, and people who ask an AI and get sent to you directly. Most SEO tools only see the first group. FocusWeb AI Visibility is built for the other two — making sure you're structured for them, and showing you proof that it's working.
Getting Started
No settings required. Activate the plugin and:
- The
/llms.txtfile goes live immediately - Structured data starts publishing automatically
- The agent search endpoint opens for AI queries
- Crawler and agent activity start logging directly on your Dashboard
The free version includes full functionality for a single site, with a 7-day analytics history.
Frequently Asked Questions
Does this replace my SEO plugin?
No — it complements it. Schema output is automatically skipped when Yoast, Rank Math, or AIOSEO is active, so you get the AI-specific layers on top, not a conflict.
Does the agent endpoint expose private content?
No. Only published, public content is ever returned, and every endpoint is read-only.
Do I need to configure anything?
No. Everything — llms.txt, schema, the agent endpoint, and crawler logging — works the moment you activate the plugin.