LLMAffiliate AI Traffic Monetizer

Description

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.

CORE FEATURES

• Detects major LLM user agents including ChatGPT, Claude, Gemini, Copilot, Perplexity, Pi, LLaMA, Grok, Cohere, Mistral, Anthropic, and OpenAI.
• Ensures Googlebot and search engine crawlers always receive original content (configurable parity enforcement).
• Serves enhanced HTML responses via a remote content service.
• Automatically falls back to native WordPress rendering if the external service fails.
• Adds cache-control, licensing, and optional Text and Data Mining headers.
• Supports secure QA overrides using HMAC-signed query parameters.

HOW IT WORKS

The plugin intercepts incoming HTTP requests and:

1. Identifies whether the request originates from an LLM or standard browser.
2. If LLM traffic is detected:
   • Fetches enhanced content from a configured external service.
   • Applies headers and response transformations.
3. If the service fails:
   • Falls back to WordPress rendering safely.
4. Ensures search engines always receive unmodified content.

USE CASES

• AI traffic handling and request analysis
• Controlled content delivery for LLM vs. human visitors
• Response parity handling (search engines receive origin content)
• Experimentation with LLM-specific rendering in compliant deployments

OPERATIONAL LOGGING & PRIVACY

An in-plugin setting (Settings → LLMAffiliate AI Traffic → Advanced Detection Settings) allows you to disable request and suspicious-event logging. When disabled, no logs are stored. When enabled (default), the plugin may store operational or security logs. These may include:
* IP address
* User agent
* Requested URL
* Referer
* Selected HTTP headers
* Detection and decision metadata
* Suspicious-event or request logs

This logging is used for debugging, security analysis, and request classification. Data is stored within your WordPress database. Configure and retain logs in accordance with your privacy policy and applicable regulations.

AI TERMS PAGE

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.

GOOGLE SEARCH CONSOLE (OPTIONAL)

The LLMAffiliate service can provide a Google Search Console HTML tag verification token on llmaffiliate.com for connected sites (see your dashboard or integration docs). If you choose to use it, open Settings → LLMAffiliate AI Traffic in WordPress and paste the token into the prominent Use LLMAffiliate’s Search Console verification field, then save. The token is stored only in your site’s database and outputs the standard <meta name="google-site-verification" …> tag on your public frontend. You can clear the field at any time to remove the tag.

Why this helps: With your consent, LLMAffiliate can verify the site in Search Console tied to that token, 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 from the plugin for this feature—the meta tag is for Google’s crawler when it visits your site.

External services

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:

1. Site Onboarding — POST https://api.llmaffiliate.com/api/v1/enhanced-content/onboarding/

   • Purpose: Registers your WordPress site with the LLM Affiliate backend so the site can receive enhanced content. Think of it as a one-time (idempotent) handshake.
   • When it is sent: Only when you click Generate Token in the plugin admin screen (Settings → LLMAffiliate AI Traffic). It is also re-sent if you regenerate/rotate the token. It is not sent on every page load.
   • Data sent (JSON body):
     • token – the authentication token generated by the plugin
     • site_id – an internal site identifier (e.g., site_xxxxxxxx) generated by the plugin
     • host – your site’s public URL (WordPress home_url())
   • No post content, no user data, no visitor IP, and no visitor PII is transmitted by this endpoint.

2. Enhanced Content Render — GET https://api.llmaffiliate.com/api/v1/enhanced-content/render

   • Purpose: Fetches the LLM-optimized HTML version of a single article URL to serve back to the detected AI crawler.
   • When it is sent: Only when the plugin’s LLM detector classifies an incoming request as an AI/LLM user-agent (ChatGPT, Perplexity, Claude, Gemini, Copilot, LLaMA, Grok, Cohere, Mistral, DeepSeek, Pi, and similar). It is not sent for human visitors, for search-engine crawlers (Googlebot, Bingbot), or for admin/REST/static-asset requests.
   • Data sent (query string + pass-through headers):
     • 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 client
     • Accept-Language header – forwarded from the visiting LLM client
     • X-LLM-Profile header – the plugin’s detected profile
     • X-LLM-Confidence header – a numeric confidence score (0–1) from the local detector
   • No cookies, session IDs, logged-in-user identifiers, or page body content are sent. Only the public URL and the minimum context needed to produce and attribute enhanced content is transmitted.

3. User sitemaps (for the plugin sitemap endpoint only) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/public/user-sitemaps?host=<hostname>

   • Purpose: Returns JSON listing LLM-optimized sitemap URLs for the given site hostname so this plugin can serve /sitemap.xml (or the configured sitemap path) as a simple URL index for search engines.
   • When it is sent: Only on GET requests that match the plugin’s dedicated sitemap path (not on normal page views). The host query parameter is your site’s hostname from WordPress home_url() (no path, no user input from forms).
   • Data sent: host only, in the query string. Non-200 responses result in an empty <urlset> (no URLs listed).

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:

• Terms of Service: https://llmaffiliate.com/terms
• Privacy Policy: https://llmaffiliate.com/privacy
• Service provider homepage: https://llmaffiliate.com/