llemmy — AI Visibility, GEO & AI Traffic Analytics

AI search is where your next readers already are. llemmy is a GEO (Generative Engine Optimization) intelligence platform: it tracks how AI engines like ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews answer questions about your brand, and this plugin brings that AI visibility data, plus AI traffic analytics for your own site, straight into wp-admin.

Useful in the first ten seconds, before any account. Activate the plugin and the dashboard immediately scores this site’s AI readiness out of 100, measured on your own server from real signals: structured data, AI-crawler access in robots.txt, llms.txt, content freshness, permalink quality and more. Most gaps are a one-click fix, and the score updates as you go. No signup, no external requests, no waiting.

Built for AI agents (WordPress 6.9+)

llemmy registers its GEO data and actions through the native WordPress Abilities API and exposes them as Model Context Protocol tools, so the WordPress editor’s assistant and outside clients like Claude, Cursor and Copilot can measure your AI visibility and act on it in plain language. Read tools (visibility, citation gaps, cited pages, AI traffic, crawler activity, freshness) carry their sample size and confidence interval; action tools (generate a brief, start a campaign) write drafts only and respect your plan. The layer is inert on WordPress below 6.9, so older sites are unaffected.

The plugin is free to use with a free llemmy account. Install it, connect in one click, and you get:

Free: measure

1. An instant AI-readiness score, no account needed. The moment you activate, the llemmy dashboard grades this site’s AI readiness (0-100) from local signals and lists exactly what to fix, most of it one click: JSON-LD schema, AI crawlers welcomed in robots.txt, an llms.txt overview, content freshness, readable permalinks. Copy the summary to share it with your team or a client.
2. The llemmy AI-traffic tag, installed automatically. See which sessions on your site came from AI engines, broken out by engine. If a llemmy tag is already on your site, the plugin detects it and pauses auto-injection so you never load a duplicate. Your secret API key stays server-side; the tag carries only a public site token.
3. Your GEO analytics inside wp-admin: visibility, share of voice, sentiment and GEO score, plus your top cited pages and domains. Every proportion is reported with its sample size and a 95% confidence interval, so you always see how solid a number is.
4. Content opportunities. The questions AI is actually asked about your brand, and the gaps where you are not yet part of the answer.
5. AI readiness, built in. Three individually toggleable generators that run entirely on your site, no llemmy account needed: Organization and Article JSON-LD schema (with datePublished and dateModified), explicit Allow rules for the major AI crawlers in your robots.txt, and an llms.txt overview of your site name, key pages and recent posts. If Yoast SEO, Rank Math, All in One SEO or SEOPress already outputs schema, the plugin detects it and leaves schema to that plugin by default.
6. Content freshness. Content Studio ranks your published posts and pages by how long they have gone without a real update. Studies of AI citations skew toward recently updated content, so anything aging or stale comes with a practical, no-nonsense refresh checklist. This also works without a llemmy account.
7. AI crawler visits (off by default, opt-in). An AI Crawlers screen counts requests from known AI bots (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and others) on your own server: totals by kind (training versus answer-time retrieval), top bots, top crawled paths and bot 404s over the last 7 days. Where an operator publishes its bot IP ranges (OpenAI does), hits are also verified against them. Bots only: no visitor IPs and no human data are ever stored. The feature is off until you enable it in settings, where the daily bot-IP-list download it performs is disclosed. Counts come from PHP requests, so a full-page cache or CDN can serve bots without reaching PHP; treat the numbers as a floor, not a census. The 7-day view is free and local; 90-day history, the retrieval-versus-training trend, the crawl-to-citation lag and the cloud rollup are part of any paid llemmy plan.
8. IndexNow pings (off by default, opt-in). When enabled in settings, publishing, updating or unpublishing a post notifies IndexNow (api.indexnow.org), which fans out to Bing and the other participating search engines, so they hear about the change immediately instead of waiting for a recrawl. Bing’s index is one of the sources ChatGPT search reads, so faster indexing can mean your content becomes citable sooner. Free on every plan, no llemmy account needed, and there is a test button in settings. No ping is ever sent until you turn the toggle on.

Paid: create and track

1. Content generation. Turn any opportunity into a content brief, and the brief into a WordPress draft in one click, from Content Studio or the post editor. A batch control drafts your top opportunities in one pass. Content always lands as a draft; you decide when to publish.
2. Campaigns effectiveness tracking. Track how the content you ship changes your visibility. Each campaign compares a baseline to the latest data for visibility, share of voice, sentiment and citation rate, and lists the drafts and posts this site created against it. When you publish a tracked draft, the plugin marks the moment on the campaign timeline in llemmy.

All llemmy calls are made server-side from PHP, so your secret API key never reaches the browser. The plugin reads and writes your data through the llemmy public API using an API key you control. It creates content only as drafts and never publishes automatically.

An optional «AI visibility by llemmy» footer badge exists, and it is OFF by default on every plan: nothing is ever shown on your site unless you explicitly opt in by checking the badge box on the settings screen, and you can turn it off again at any time.

You need a llemmy account and an API key. Connecting, analytics and content opportunities are free; generating briefs and drafts and Campaigns effectiveness tracking need a paid plan. Sign up at llemmy.com.

External services

The plugin makes no external requests at all until you take one of two explicit actions: (1) connect a llemmy account (the service this plugin is a client for), or (2) enable one of the two clearly labelled opt-in integrations (IndexNow, AI crawler tracking) on the settings screen. There is no telemetry, no usage tracking, no phoning home: fresh install with no connection and default settings = zero network requests. The plugin does not use Google Analytics or any other analytics in wp-admin.

This plugin connects to llemmy (https://llemmy.com), a GEO intelligence service, or to your own self-hosted llemmy instance if you change the base URL in settings. A llemmy account and API key are required for the llemmy features to function; connecting is your action and your consent.

What is sent, and when:

• wp-admin screens: server-side API calls to your configured llemmy instance, authenticated with your API key. Requests carry your selected llemmy project id and, for citation reports, this site’s domain.
• Site registration: when you connect, the plugin registers this site’s domain with llemmy to create the public site token used by the AI-traffic tag.
• AI-traffic tag: when enabled, visitors’ browsers load the tag script from your llemmy instance and it reports page-view beacons (page URL, referrer, user agent) so AI-referral sessions can be counted. It sends no WordPress user accounts and nothing from your database.
• Content briefs and drafts (paid): when you generate a brief, the opportunity title, topic and keywords, and from the post editor the post title and URL, are sent to llemmy to produce the brief.
• Campaigns (paid): campaign names, descriptions and tracked prompt text are sent when you create them; publishing a tracked draft reports the publish event so the campaign timeline can mark it.
• AI crawler telemetry (paid cloud sync only): on accounts entitled to crawler analytics, a daily job sends aggregated bot counts for this site’s domain (per day and bot: hits, verified hits, error hits and top crawled paths) to your llemmy instance so it can keep history and roll up a portfolio. Aggregates only, bots only: no visitor IPs and no human data are collected or sent. On other plans nothing is sent and all crawler data stays on your server.

This service is provided by llemmy: terms of service, privacy policy.

The plugin can also talk to two services that are independent of llemmy. Both are OFF by default and contacted only after you explicitly enable the matching toggle on the settings screen, where each external call is disclosed next to its checkbox:

• IndexNow (api.indexnow.org): only when you have enabled the IndexNow toggle (off by default) and a post of a public type is published, updated or unpublished, the plugin sends the post URL, your site host and your IndexNow key to https://api.indexnow.org/indexnow, which shares the notification with the participating search engines (Bing, Seznam, Naver, Yandex and others). The key is a random token generated by the plugin and proves site ownership; it is also served publicly at a key file URL on your site, as the IndexNow protocol requires. No content and no visitor data are sent. IndexNow is operated by its participating engines; see the protocol site at indexnow.org and each engine’s own terms and privacy policy, for example Microsoft Bing’s privacy statement. Turning the toggle off stops all pings; with the toggle off, no key is even generated.
• OpenAI published bot IP lists (openai.com): only when you have enabled AI crawler tracking (off by default), a daily job downloads OpenAI’s published crawler IP ranges from https://openai.com/gptbot.json, https://openai.com/searchbot.json and https://openai.com/chatgpt-user.json so bot hits can be verified as genuinely coming from OpenAI. This is a download only: nothing about your site or visitors is sent beyond the HTTP request itself. See OpenAI’s privacy policy. Turning crawler tracking off stops these fetches.