The data on the homepage
comes from sites like yours

AEO Pugmill is a free WordPress plugin that tracks AI crawler visits on your site, structures your content for AI answer engines, and — if you opt in — contributes anonymized data to the network.

Download Free →

Free at the core. Network participation is optional. Pro adds generation and bulk tools.

Two things connected, yet each independent

For your site: The plugin adds AEO metadata to WordPress posts — structured Q&A pairs, named entity mentions, citation links, and machine-readable endpoints like llms.txt. These are the signals AI answer engines look for when deciding what to extract and attribute.

For the network: Opting in sends a daily count summary to aeopugmill.com — which bot, which resource type, how many visits. No content, no URLs, no user data. That aggregate is what powers the intelligence dashboard.

Both features work independently. Bot analytics and AEO outputs are available without contributing to the network.

Bot analytics dashboard

—

Which AI crawlers are visiting your site, what they're fetching, and how counts trend over time — directly in the WordPress admin.

FAQPage + entity JSON-LD

—

Structured Q&A pairs and named entity mentions written to each page's JSON-LD automatically. Readable by AI engines at crawl time.

llms.txt endpoints

—

Generates /llms.txt and /llms-full.txt automatically — a content map AI crawlers use for structured discovery.

AI field generation

—

Summaries, Q&A pairs, entity tags, and keywords generated from your own API key (Anthropic, OpenAI, or Gemini). You pay only for the API calls made.

robots.txt management

—

Per-bot crawler rules — allow or restrict directives for specific bots without editing server configuration.

What gets sent to aeopugmill.com

Opting in sends one small payload per day. Here is exactly what that payload contains — and what it does not.

Participation is opt-in. The plugin runs fully without ever sending data to the network. The option to contribute appears on the plugin settings page and defaults to off.

✓

What is sent

A one-way hash of your site URL — cannot be reversed to a domain
Bot visit counts by bot name and resource type (html, llms.txt, sitemap, etc.)
Content signal distributions: word count bucket, freshness, fact density, URL depth
The date of the summary period

✗

What is never sent

Your domain name or site URL
Post titles, content, or summaries
Visitor IP addresses or user agents
Usernames, email addresses, or any personal data
Individual page URLs or post IDs

// Example daily payload — all values are counts or distributions, no identifiers { "site": "a3f8c29d...", // SHA-256 hash, one-way, non-reversible "date": "2026-04-14", "bots": { "GPTBot": { "html": 12, "llms_txt": 3, "post_markdown": 1 }, "ClaudeBot": { "html": 8, "sitemap": 2 }, "PerplexityBot":{ "html": 5, "aeo_jsonld": 1 } }, "signals": { "word_count": { "short": 2, "medium": 8, "long": 5 }, "freshness": { "recent": 6, "aging": 7, "stale": 2 }, "fact_density":{ "low": 4, "medium": 7, "high": 4 }, "url_depth": { "shallow": 9, "deep": 6 } } }

The payload is HMAC-signed before transmission. aeopugmill.com verifies the signature on receipt and discards unsigned requests.

The data on the homepagecomes from sites like yours

Two things connected, yet each independent

What gets sent to aeopugmill.com

Free to start. Pro adds automation.

The data on the homepage
comes from sites like yours