LLMAffiliate AI Traffic Monetizer is a WordPress plugin that detects Large Language Model (LLM) traffic and dynamically serves enhanced content while ensuring compliance with search engine parity requirements.
It mirrors the behavior of an interception layer (e.g., Cloudflare Worker) directly inside WordPress, enabling controlled content delivery for AI crawlers and agents.
The plugin intercepts incoming HTTP requests and:
By default, the plugin may store operational logs to support debugging, security analysis, and request classification for its own LLM-detection logic. These may include:
* IP address
* User agent
* Requested URL
* Referer
* Selected HTTP headers
* Detection and decision metadata
* Request decision logs
Data is stored within your WordPress database and is never transmitted off your site. Retain it in accordance with your privacy policy and applicable regulations.
The plugin can serve a public /ai-terms page (or equivalent) that displays your site’s AI usage and content terms. It functions as a site-published policy page that visitors—including AI systems and human readers—can view. Site owners are responsible for the contents and legal suitability of the terms. The plugin includes a default template; you may customize it to match your needs.
The LLMAffiliate service can provide a Google Search Console token and a Bing Webmaster Tools token on llmaffiliate.com for connected sites (see your dashboard or integration docs). If you choose to use them, open Settings LLMAffiliate AI Traffic in WordPress and paste each token into its matching field, then save:
<meta name="google-site-verification" content="…"><meta name="msvalidate.01" content="…">Paste only the token value (the content part), not the whole meta tag, and do not swap the two tokens. Each token is stored only in your site’s database and its tag is printed on your public frontend. You can clear either field at any time to remove its tag.
Why this helps: With your consent, LLMAffiliate can verify the site in Search Console and Bing Webmaster Tools tied to those tokens, which helps the service monitor indexing coverage and page performance for your integration and support you more effectively. This is fully optional; if you leave the field empty, nothing is added to your HTML.
No extra HTTP request is made to Google or Bing from the plugin for this feature—the meta tags are for their crawlers when they visit your site.
This plugin connects to the LLM Affiliate cloud service to detect visiting AI crawlers (ChatGPT, Perplexity, Claude, Gemini, Copilot, etc.) and return an LLM-optimized, monetizable version of the requested article. Without this external service the plugin still performs local LLM detection, search-engine parity, and renders the /ai-terms page, but the enhanced-content feature is not available.
This service is provided by LLM Affiliate (llmaffiliate.com).
Service endpoints used:
Site Onboarding — POST https://api.llmaffiliate.com/api/v1/enhanced-content/onboarding/
init until a successful response is stored. After onboarding succeeds, it is not sent again on later page loads.token – the authentication token generated by the pluginsite_id – an internal site identifier (e.g., site_xxxxxxxx) generated by the pluginhost – your site’s public URL (WordPress home_url())Enhanced Content Render — GET https://api.llmaffiliate.com/api/v1/enhanced-content/render
url – the public URL of the article being requested (query string + path)llm_profile – the detected LLM profile name (e.g., chatgpt, claude, gemini)User-Agent header – forwarded from the visiting LLM clientX-LLM-Profile header – the plugin’s detected profileX-LLM-Confidence header – a numeric confidence score (0–1) from the local detectorAuthorization: Bearer <token> header – the same per-site token generated in Settings LLMAffiliate AI Traffic and already sent to the onboarding endpoint (see #1), used to authenticate the request. Sent only if a token has been generated; requests made before onboarding are unauthenticated.User sitemaps (for the plugin sitemap endpoint only) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/public/user-sitemaps?host=<hostname>
/sitemap.xml (or the configured sitemap path) as a simple URL index for search engines.robots.txt additions so it can list monetized paths. It is not sent on normal page views. The host query parameter is your site’s hostname from WordPress home_url() (no path, no user input from forms).host in the query string, plus the same per-site token described in #2 (sent only once a token exists). Each item in the JSON sitemaps array includes site_url, last_modified, products_count, and total_traffic. Non-200 responses result in an empty <urlset> (no URLs listed).llms.txt (LLM content index) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/internal/llms-txt?host=<hostname>
/llms.txt file, which provides LLM crawlers with a structured site overview including product categories, brands, price ranges, and links to enhanced pages./llms.txt.host in the query string, plus the same per-site token described in #2 (sent only once a token exists). If the API is unreachable, a minimal fallback is served locally.llms-full.txt (full product catalog) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/internal/llms-full-txt?host=<hostname>
/llms-full.txt file, which includes full product details (brand, price, category, description, buy link) for every product across all enhanced pages./llms-full.txt.host in the query string, plus the same per-site token described in #2 (sent only once a token exists). If the API is unreachable, a minimal fallback is served locally.All requests are made over HTTPS. If the service is unavailable or returns a non-200 response, the plugin adds an X-LLMAFFTM-Interceptor: fallback header and allows WordPress to render the normal (origin) page — humans and LLMs always receive something.
Use of the LLM Affiliate service is governed by the provider’s terms. Please review them before generating a token: