The short version
- WordPress runs a large share of the web, and it is where your content actually lives. That makes it the natural place to both measure AI visibility and act on it.
- The llemmy for WordPress plugin is free and self-hosted. Download the .zip from llemmy.com/wp-plugin/llemmy.zip, install it like any plugin, paste an API key, pick a project. Under two minutes.
- It auto-installs the cookieless AI-traffic tag in your head, but only if one is not already there. No snippet to copy, no double-tagging.
- The wp-admin dashboard reports every proportion with a sample size and a 95% confidence interval, so you read a signal, not a vanity number.
- In the editor, a content-brief meta box turns citation gaps into a GEO scaffold grounded in the questions AI is actually asked about your brand.
If you run marketing on WordPress, your GEO work is split across two screens: a visibility tool in one tab, the CMS where you actually publish in another. Measuring in one place and acting in another is where good intentions go to die. The llemmy for WordPress plugin closes that gap. It puts the measurement (how AI engines cite you) and the action (writing the content that earns those citations) in the same place your content already lives.
This is what it does, how to set it up, and how to read what it shows you without fooling yourself.
Why WordPress sites start ahead in GEO
Generative engines assemble answers from sources they can crawl, parse and trust. WordPress sites tend to be well-placed for that: clean, server-rendered HTML that engines can read without executing JavaScript, sensible heading structure, canonical URLs, and a publishing workflow that makes it cheap to ship a focused answer to a specific question. The raw material for getting cited is usually already there. What is missing is the feedback loop: knowing which of your pages the engines actually pull into answers, and which questions they answer with someone else's page instead. That loop is exactly what the plugin adds.
Connect in under two minutes
Download the plugin .zip from llemmy.com, then install it the ordinary way: Plugins, Add New, Upload Plugin, choose the file, activate. In the new llemmy settings screen, paste a llemmy API key (create one under API Keys in the app), load your projects, and pick the project this site maps to. Save. That is the whole setup.
Two things worth knowing about how that connection is handled:
- Your API key is stored on your server, never in the browser. The wp-admin dashboard does not call llemmy directly from the page. It goes through a server-side proxy in the plugin, so the secret key stays on your WordPress host and never reaches a visitor or the page source.
- By default it points at llemmy.com. If you self-host llemmy, you can change the base URL. Everyone else leaves it alone.
The AI-traffic tag installs itself (and only once)
Turn the tag on in settings and the plugin injects the cookieless llemmy AI-traffic tag into your site's <head> for you. There is no snippet to copy into your theme and no functions.php edit. It just appears on the front end.
The part that keeps it safe on a real site: before it injects, the plugin scans your home page for a llemmy tag that is already there from some other install (a tag manager, a hardcoded snippet, another plugin). If it finds one, it steps aside and shows a notice instead of injecting a second copy. A "re-check tag on site" button re-runs that scan on demand. So you get the tag with zero copy-paste, and you never end up double-counting yourself.
The tag measures the humans who arrive on your pages from AI answers. It is cookieless by default and does not store raw IP addresses. It is worth being precise about what a client-side tag can and cannot see: AI crawlers do not run JavaScript, so the tag never fires for them. It measures people who clicked through from an AI answer, not bots. If you want the full picture of the tag, see how the llemmy Tag works.
Read the GEO snapshot as a signal, not a number
Once connected, the wp-admin dashboard shows four things without you leaving WordPress.
Connection and tag health. A status line that tells you the truth about the tag: "tag detected" once llemmy has actually seen it fire, "waiting" until then, or a note that an external tag is already present. No guessing whether the install worked.
A GEO snapshot. Visibility, share of voice, sentiment and your GEO score for the connected project. Here is the important part, and the thing most tools get wrong. Each proportion is shown with its sample size (n) and a 95% confidence interval, rendered as something like "34% (n=180, 95% CI 27 to 41%)". A metric that does not yet have enough answers behind it reads "not enough data yet" rather than showing a shaky number you might act on. Sentiment is shown as a mean over its sample, without a false-precision interval it does not earn.
Why this matters: AI visibility is a rate estimated from a finite, non-deterministic sample. A single day's figure is noisy. The confidence interval is how you tell a real change from wobble. If this week's interval has pulled clear of last week's, something moved. If they still overlap, it is within noise and you should keep collecting answers before you report a win. The plugin gives you the raw material to make that call instead of hiding it behind one confident-looking percentage.
AI-referral traffic by engine. The tag's data, summarized: how many sessions arrived from AI answers versus everything else, broken out by engine (ChatGPT, Perplexity, Gemini and the rest), over a window you choose (7, 14, 28 or 90 days). This is the "did anyone actually come?" number that a mention-only tool cannot give you.
Top cited pages and domains. Which of your pages the engines are pulling into answers, and which domains are winning citations. This is the bridge from measurement to action, and it feeds directly into the next step.
Turn a citation gap into a content brief, in the editor
Knowing a question gets answered with a competitor's page is only useful if you do something about it. So the plugin puts a "llemmy: Content brief" meta box right in the WordPress post and page editor.
Pick a tone, click generate, and it produces a GEO content scaffold for that page, grounded in the questions AI is actually asked about your brand and the gaps in what currently gets cited. It appears in the editor for you to read and copy in. In this version it is deliberately display and copy only: it never rewrites or auto-inserts anything into your post, and it never asks for an Application Password or any handoff to another tool. The draft stays in your hands, inside WordPress, and you decide what to keep.
The brief generator is the one paid feature in an otherwise free plugin. On a free plan the meta box shows an upgrade nudge with a link to pricing; on a paid plan it generates. Everything else (the connection, the tag, the whole dashboard) works on every plan.
The agency angle: one account, every client site
For an agency, the plugin scales the way agencies actually work. Each client's WordPress site connects to the project that represents that client in your one llemmy account. Install the free plugin on every site you manage, point each at its project, and every client gets an in-dashboard GEO view and an in-editor brief generator, all reporting back to the same account you already run. No per-site tool sprawl, no separate logins to hand out, and the same confidence-interval discipline on every client so the numbers you present are ones you can defend. Pair it with Campaigns and each brief you ship has a before-and-after attached to it.
What we will not claim
A confidence interval fixes noise, not bias. It tells you how stable a rate is at a given sample size. It does not change the fact that we query the official model APIs and read Google AI Overviews off the search results page, which is not identical to a logged-in, personalized consumer app, and that personalization is not modeled. We are explicit about that in how we measure. So the plugin will tell you, honestly and with its uncertainty attached, how AI engines answer defined questions about your brand and who is getting cited. It will not pretend to know what one specific person sees in their personalized session, and we would be wary of any tool that says it can.
Get started
Download the free llemmy for WordPress plugin, install it, and connect it to a project with your API key. If you do not have a project yet, run a free GEO audit to see how AI engines describe your brand today, or start free and create one. The honest promise: measure and improve your AI visibility from inside WordPress, in under two minutes, with confidence intervals instead of vanity numbers.
FAQ
Is the llemmy plugin for WordPress free?
Yes. It is free and self-hosted: download the .zip from llemmy.com and install it like any plugin. Connecting it needs a llemmy account and API key, and the dashboard and AI-traffic tag work on every plan. The in-editor content brief generator is the one paid feature, so free plans see an upgrade nudge and paid plans generate briefs.
Do I have to paste a tracking snippet into my theme?
No. When you enable the tag, the plugin injects the cookieless llemmy AI-traffic tag into your site head automatically. It scans your home page first and only installs when no llemmy tag is already present, so it never double-tags a site that already has one. There is no code to copy into your theme.
Where is my llemmy API key stored?
On your WordPress server, not in the browser. You paste it once in settings and it is saved server-side. The dashboard fetches your llemmy data through a server-side proxy, so the secret key never reaches the page or a visitor, and API responses are written to the page as text rather than raw HTML.
Why does the plugin show confidence intervals instead of one number?
Because AI visibility is a rate estimated from a finite, non-deterministic sample, and a single number hides how much data is behind it. Every proportion is shown with its sample size (n) and a 95% confidence interval, and a metric reads "not enough data yet" until llemmy has collected enough answers to say anything honest. That is how you tell a real change from sampling noise.
By the llemmy team, July 2026. Related reading: The llemmy Tag: measure the traffic AI search actually drives, How llemmy measures AI visibility (and what we don't claim), and The AI Citation Gap.