llemmy - AI Visibility, GEO & AI Traffic Analytics

Create one in your llemmy account under Settings then API Keys, at llemmy.com. The key is a secret; the plugin stores it encrypted and never sends it to your browser.

Yes. The key is stored in the WordPress options table, encrypted at rest with AES-256 when your server supports it. Every call to llemmy is made from PHP on your server, so the key never appears in page source or in JavaScript.

Yes, on WordPress 6.9 and later. llemmy registers its GEO tools through the native WordPress Abilities API and exposes them as Model Context Protocol tools, so the WordPress editor's assistant and external MCP clients such as Claude, Cursor and Copilot can read your AI visibility, citation gaps and crawler activity, and generate briefs or start campaigns, in plain language. Read tools require the manage_options capability and action tools require edit_posts plus your plan, and nothing publishes on its own. On WordPress below 6.9 the layer is inert and everything else works normally.

No. When Yoast SEO, Rank Math, All in One SEO or SEOPress is active, llemmy detects it and turns its own schema output off by default, so your pages never carry duplicate markup. The settings screen shows which plugin is handling schema. You can still enable llemmy's schema manually, but two schema sources on one page is rarely what you want.

Yes, immediately. The dashboard's AI-readiness score, its one-click fixes, the JSON-LD schema, the robots.txt AI-crawler rules, the llms.txt overview, the content freshness list and (once you opt in) the AI crawler counts and IndexNow pings all run on your own site with no account. The account adds the measurement layer: what AI engines actually say about you, and which AI sessions land on your site.

No. The JSON-LD schema, the robots.txt AI-crawler rules, the llms.txt overview and the content freshness list all run locally on your site and are free. Only the analytics, opportunities, generation and campaigns features talk to llemmy.

The plugin scans your home page for an existing tag. If it finds one that it did not add, it pauses its own injection so your site never loads two tags. You can re-run the check any time from the Dashboard.

The in-editor brief is read and copy only. Content Studio can create new posts, but only ever as drafts: nothing is published or edited on your behalf. Publishing is always a separate, human action, and that is the guardrail.

When you create a draft from a Content Studio opportunity, you can attach it to a campaign. The plugin resolves the opportunity's tracked prompt (or creates one), adds it to the campaign, and stores the link on the draft. When you later publish that draft, the plugin tells llemmy the content shipped, so the campaign timeline marks the moment. On the Campaigns screen you then see the baseline-vs-current lift for visibility, share of voice, sentiment and citation rate, each with its sample size and 95% confidence interval.

Any user who can edit posts. Connecting the site and changing settings still requires an administrator.

No. Connecting, analytics and content opportunities are free. Generating briefs and drafts and Campaigns effectiveness tracking need a paid llemmy plan; on the free plan those controls show a clear upgrade nudge instead of failing. If your plan or monthly quota does not allow a generation, the plugin shows a clear message and a link to plans.

One small, unobtrusive "AI visibility by llemmy" link that can appear in your site footer, but ONLY if you choose to show it. It is off by default on every plan, including free, and appears only after you explicitly check the badge box on the settings screen (an intentional opt-in). No plan state can force it on, and you can turn it off again at any time.

No. A fresh install makes zero network requests: the plugin has no telemetry, no usage tracking, and does not use Google Analytics or any analytics in wp-admin. It only ever talks to (a) the llemmy service after you connect your account, and (b) IndexNow and OpenAI's published bot-IP lists, each only after you explicitly enable its off-by-default toggle in settings, where the exact request is disclosed. Upgrade notices appear only inside the plugin's own screens, and the one first-run connect notice is dismissible and confined to the Dashboard and Plugins screens.

No. The AI crawler telemetry records bots only: a request is counted only when its User-Agent matches a known AI crawler, and what is stored is an aggregate row per day, bot and path. No visitor IPs, no cookies and no human browsing data are ever recorded. The requesting IP of a matched bot is compared in memory against the operator's published bot IP ranges to mark the hit verified, then discarded.

IndexNow is an open protocol that lets a site tell search engines about new, updated or removed URLs the moment it happens, instead of waiting for a recrawl. When you enable the toggle in settings (it is off by default), the plugin pings the shared endpoint at api.indexnow.org, which fans the notification out to Bing and the other participating engines. Why it matters for GEO: Bing's index is one of the sources AI answer engines such as ChatGPT search read, so faster indexing can mean your content becomes citable sooner. It is free and needs no llemmy account.

Yes for AI-traffic analytics. The AI-traffic tag is client-side JavaScript, so it fires even when your pages are served from cache. The AI crawler telemetry is different: it counts requests that reach PHP, so pages a cache or CDN serves directly are not counted there. Treat crawler counts as a floor, not a census; the screen says so too.

Yes. Point the base URL in Settings at your own llemmy instance; everything else works the same.

Yes. Every subsite keeps its own connection, so each client site can feed its own llemmy project. Network admins also get a llemmy overview page in network admin: every subsite with its connection status and headline visibility (with sample size and confidence interval), plus a configure link into each subsite's settings.

Yes. Fill in the optional "Managed by" field on the settings screen and a small "Site managed by" note appears at the bottom of the llemmy dashboard in wp-admin. Leave it blank and nothing shows.