Share Buttons & AI-powered Summaries
Share Buttons & AI-powered Summaries turns every post into an AI-aware destination. It generates an inline AI summary readers can expand next to the share buttons, and offers one-click sharing to every major social network and the leading AI assistants. Among the first plugins to integrate the native WordPress 7.0 AI Connectors API: configure your AI provider once in Settings > Connectors (OpenAI, Anthropic, Google) and the plugin reuses those credentials — no API keys to manage, no extra accounts. Inline AI Summary Two-tier cascade: Level A uses the WordPress 7.0 AI Client; Level C is a built-in PHP extractive fallback with zero API cost on any WP 6.1+ install. Choose your AI model and mode: pick the provider and model used to generate summaries, or leave it on Automatic to use a fast, cost-effective model instead of the newest, most expensive one. Set how generation behaves too: AI with extractive fallback, AI only, extractive only, or disabled. Paragraph or bullet-list format: show the summary as prose (one paragraph per sentence) or as a concise bullet list, with configurable length (1-5 sentences or points). Collapsible inline block with native , data-nosnippet and Schema.org CreativeWork microdata, so Google leaves the summary out of its snippets and AI Overviews and it never competes with your own text. Editor controls in the block sidebar and the classic meta box: view, edit manually, regenerate on demand, hide per post (independently from the buttons). Visitor-facing “Generate AI summary” button for posts without a stored summary, restrictable to extractive-only or open to the AI Client. Your own content inside the box: anything you want below the summary, as text, HTML or scripts (an ad, a newsletter form, a map, a notice), loaded when a reader opens the box, with an optional label. Only where there is something to summarize: posts with fewer than 50 words of text get no summary, so the box never shows an AI reply saying there was nothing to summarize. Async generation via WP-Cron. [ayudawp_aiss_summary] shortcode also available. Sharing Social networks: X (Twitter), LinkedIn, Facebook, Telegram, WhatsApp, Email, Raindrop, Reddit, Bluesky, LINE, Mastodon, Threads, Pinterest. AI assistants: Claude, ChatGPT, Google AI, Gemini, Grok, Perplexity, DeepSeek, Mistral, Copilot, Qwen, Meta AI — each opens with a citation-ready prompt linking back to your URL. Browser actions: a Copy link button and a native Share button that opens the device share sheet (reaching WhatsApp, Signal, Instagram, Messages or AirDrop), shown only where the browser supports it. Google Preferred Source: a button that takes readers to the Google tool where they mark your site as a preferred source, with the clicks counted per post. It can go with the social networks, in a section of its own, or anywhere with the shortcode. Where they show: inline before or after the content, through the [ayudawp_share_buttons] shortcode, or in a floating bar pinned to the left, the right or the bottom of the screen — on its own or alongside the inline block. Compact on phones: optionally collapse the whole set behind a single Share button, or show a few buttons plus a More button, without touching the desktop layout. 6 visual styles, 4 sizes, custom colors, brand SVG icons, dark-mode auto-adaptation, drag-and-drop ordering, optional UTM tagging. SEO-friendly ( or , auto-exclusion on noindex content for all major SEO plugins). Analytics Click tracking per platform and per post, timeline chart with per-platform breakdown, period comparison (previous period, same period last year, custom range), CSV export. Dashboard widget with 7-day sparkline. VigIA cross-reference (clicks vs. AI crawler visits) when active. Redis/Memcached compatible. Why use it? Cite your source naturally: when readers expand the summary or share to an AI assistant, your URL travels with the content. Reach every audience: full social spectrum plus 11 AI assistants in one place. Future-proof: built on WP 7.0 Connectors and a REST API ready for agentic clients. External services This plugin connects to third-party AI providers only when the inline AI Summary feature is enabled and an AI Connector is configured (or the WP AI Client is available). All other features — social and AI share buttons, click analytics, the extractive PHP fallback summary — run entirely on your own server and do not contact any external service. AI Summary generation When a post is saved (or when the editor / a visitor explicitly clicks “Regenerate” or “Generate AI summary”), the plugin uses the WordPress 7.0 AI Client (wp_ai_client_prompt()) to request a short summary from whichever provider you configured in Settings > Connectors. The plugin never stores your API keys — they are managed centrally by WordPress core. What is sent: Post title (plain text) Post content (HTML stripped, up to ~3000 characters of plain text) A short instruction asking the provider to return a summary What is not sent: API keys (managed by core Connectors), visitor IP addresses, user accounts, analytics data, or any other personal data of your readers. Possible destinations (depending on which Connector your administrator activates): OpenAI — Terms of use · Privacy policy Anthropic — Terms of service · Privacy policy Google AI — Terms of service · Privacy policy If you do not configure any Connector, or your WordPress version is below 7.0, the plugin falls back to the local PHP extractive summarizer and no external request is made. How to opt out Set AI Summary generation to Disabled in the AI Summary tab of the plugin settings. Or choose Extractive only to keep summaries fully local — zero external requests, ever. Or choose AI only while leaving no Connector configured — no requests will be sent, and summaries simply won’t be generated. The visitor-facing “Generate AI summary” button is off by default; if enabled, you can additionally restrict it to the extractive PHP path so visitor clicks never reach an external provider. Sharing buttons The social and AI sharing buttons render as / elements that open the respective destination only when the visitor clicks them — your server does not contact those services. The same goes for the Google Preferred Source button, a plain link to Google’s preferred sources tool with your domain in it: no Google script is loaded (Terms of service · Privacy policy). The plugin’s analytics endpoint that records button clicks runs locally on your own site. Advanced Usage Shortcode parameters The [ayudawp_share_buttons] shortcode accepts several parameters: buttons: Comma-separated list of buttons to display – Example: [ayudawp_share_buttons buttons="claude,chatgpt,deepseek,twitter,mastodon"] – Available: twitter, linkedin, facebook, telegram, whatsapp, email, raindrop, reddit, bluesky, line, mastodon, threads, pinterest, copy_link, web_share, google_preferred, claude, chatgpt, google_ai, gemini, grok, perplexity, deepseek, mistral, copilot, qwen, meta_ai style: Visual style to use – Example: [ayudawp_share_buttons style="outline"] – Options: minimal, brand, outline, dark, custom, icons-only size: Button size preset – Example: [ayudawp_share_buttons size="compact"] – Options: compact, normal, large, fluid show_icons: Show icons with text (for non-icons-only styles) – Example: [ayudawp_share_buttons show_icons="true" style="brand"] – Options: true, false icon_style: Icon corner style (for icons-only mode) – Example: [ayudawp_share_buttons style="icons-only" icon_style="circular"] – Options: circular, square alignment: Button alignment – Example: [ayudawp_share_buttons alignment="center"] – Options: left, center show_title: Show or hide the section title – Example: [ayudawp_share_buttons show_title="false"] – Options: true, false title_text: Custom title text – Example: [ayudawp_share_buttons title_text="Share this content"] title_style: Title HTML element – Example: [ayudawp_share_buttons title_style="h3"] – Options: h3, h4, h5, h6, span ai_title: Section title for AI buttons group – Example: [ayudawp_share_buttons ai_title="Summarize with AI"] social_title: Section title for social buttons group – Example: [ayudawp_share_buttons social_title="Share on social media"] google_title: Title of the Google Preferred Source section, when it has a section of its own – Example: [ayudawp_share_buttons google_title="Follow us on Google"] Combined examples: [ayudawp_share_buttons buttons="claude,deepseek,twitter" style="brand" show_icons="true"] [ayudawp_share_buttons style="icons-only" icon_style="circular"] [ayudawp_share_buttons show_title="true" title_text="Share or Summarize" title_style="h3"] [ayudawp_share_buttons ai_title="Summarize with AI" social_title="Share" style="outline" show_icons="true"] [ayudawp_share_buttons buttons="chatgpt,qwen,meta_ai,mastodon,threads" size="compact" style="brand"] [ayudawp_share_buttons style="icons-only" icon_style="square" size="large"] [ayudawp_share_buttons size="fluid" style="outline" show_icons="true"] AI summary shortcode The [ayudawp_aiss_summary] shortcode renders the AI-generated summary as a standalone collapsible block. Useful when you want to place the summary somewhere other than where the share buttons are auto-inserted, or when you have buttons disabled but still want to surface the summary. post_id: Render the summary of a specific post – Example: [ayudawp_aiss_summary post_id="123"] – Defaults to the current post in the loop when omitted The shortcode outputs nothing when the post has no stored summary, so it is safe to drop into templates without conditional wrappers. Printing the blocks in theme hooks Some themes rewrite the post content after WordPress filters it, for example to place ads, and end up duplicating whatever plugins added to it. For those, the ayudawp_aiss_content_anchors filter prints what goes before the content, what goes after it, or both, in an action of the theme instead: add_filter( 'ayudawp_aiss_content_anchors', function ( $anchors ) { $anchors['before'] = array( 'hook' => 'mytheme_before_content', 'priority' => 20 ); $anchors['after'] = array( 'hook' => 'mytheme_after_content', 'priority' => 1 ); return $anchors; } ); The settings still decide whether the buttons and the summary show and where (before, after or both). The stylesheet still loads in the head, exclusions and the floating bar keep working, and each block is printed once per page. Leave an anchor as the_content to keep it inside the content. CSS Customization Guide The plugin uses CSS custom properties for all brand colors. You can override these in your theme to change any platform color globally: Override platform colors: .ayudawp-share-buttons { –ayudawp-claude: #ff0000; –ayudawp-chatgpt: #00ff00; } Main container classes: – .ayudawp-share-buttons – Main wrapper container – .ayudawp-buttons-container – Direct container for all buttons – .ayudawp-title – Title element before buttons – .ayudawp-section-title – Section title with extra top margin – .ayudawp-aiss-centered – Applied when centered alignment is enabled Button classes: – .ayudawp-share-btn – Base class for all buttons (both and elements) – .ayudawp-icon-wrapper – Container for button icons – .ayudawp-button-text – Text label inside buttons – .ayudawp-icon – SVG icon element Style modifier classes: – .brand – Brand colors style – .outline – Outline style (brand-colored borders) – .minimal – Minimal style – .dark – Dark background style – .custom – Custom colors style – .icons-only – Icons-only mode – .with-icons – Text buttons with icons – .circular – Circular icon buttons – .square – Square icon buttons Size modifier classes: – .size-compact – Compact button size – .size-large – Large button size – .size-fluid – Fluid width buttons Platform-specific classes (on buttons): – .twitter, .linkedin, .facebook, .telegram, .whatsapp – .email, .raindrop, .reddit, .bluesky, .line – .mastodon, .threads, .pinterest – .claude, .chatgpt, .google-ai, .gemini, .grok – .perplexity, .deepseek, .mistral, .copilot – .qwen, .meta-ai – .ai – Applied to all AI platform buttons Example: Change Claude button color: .ayudawp-share-buttons { –ayudawp-claude: #your-color; } Example: Change all AI buttons background: .ayudawp-share-buttons .ayudawp-share-btn.ai { background: #f0f0f0; } Example: Hide specific button: .ayudawp-share-btn.facebook { display: none; } Customize or remove separator lines: The main container has top and bottom border lines. You can hide either of them from the settings (Share Buttons → Separator lines) with no code. CSS is only needed to replace them with your own style: .ayudawp-share-buttons { border-top: 2px dashed #ccc; border-bottom: 2px dashed #ccc; } Important notes: – The use of !important is no longer needed for most overrides – Use CSS custom properties to change brand colors cleanly – Test on both desktop and mobile viewports – Icons-only buttons have fixed dimensions (44px default, 36px compact, 54px large) Technical Details System requirements WordPress 6.1 or higher (7.0+ for AI-generated summaries) PHP 7.4 or higher (compatible up to PHP 8.4) Theme compatible with wp_head() and wp_footer() Performance features Modular file structure for maximum efficiency Selective loading of resources (CSS/JS only where buttons display) No external dependencies: the front end script is plain JavaScript and does not load jQuery The floating bar ships its CSS and JS as separate files, loaded only where the bar is shown Optimized CSS with custom properties and minimal specificity Lightweight SVG icons (under 1KB each) Minimal database impact: analytics queries are cached (5 min) and compatible with persistent object cache (Redis, Memcached) Smart responsive layouts REST API for lightweight analytics data retrieval Developer features Clean, documented code WordPress coding standards compliant Hook-based architecture Modular class structure in /includes folder Extensible icon system using Simple Icons Translation ready Comprehensive shortcode API SEO-friendly markup options Post meta for individual exclusions Centralized platform color definitions Filters: ayudawp_aiss_floating_bar_buttons (which buttons the bar shows), ayudawp_aiss_show_floating_bar (whether it renders on a given request), ayudawp_aiss_utm_args (the campaign parameters added to a shared link), ayudawp_aiss_trusted_proxies (which addresses may set the forwarding header behind a CDN or load balancer), ayudawp_aiss_content_anchors (print the blocks in theme actions), ayudawp_aiss_summary_min_words (minimum length for a summary), ayudawp_aiss_summary_custom_html (the custom content inside the summary box, per post) and ayudawp_aiss_google_preferred_domain (the domain sent to Google) Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.
LLMAffiliate AI Traffic Monetizer
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 and interceptor diagnostic headers. HOW IT WORKS The plugin intercepts incoming HTTP requests and: Identifies whether the request originates from an LLM or standard browser. If LLM traffic is detected: Fetches enhanced content from a configured external service. Applies headers and response transformations. If the service fails: Falls back to WordPress rendering safely. 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 decision logging. When disabled, no logs are stored. When enabled (default), the plugin may store operational logs. These may include: * IP address * User agent * Requested URL * Referer * Selected HTTP headers * Detection and decision metadata * Request decision 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 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: 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: When an administrator clicks Generate Token or Regenerate Token in Settings → LLMAffiliate AI Traffic. If a token already exists but onboarding has not yet succeeded, the plugin also retries this request from WordPress init until a successful response is stored. After onboarding succeeds, it is not sent again on later page loads. 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. 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 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. User sitemaps (for the plugin sitemap endpoint only) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/public/user-sitemaps?host= 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: On GET requests that match the plugin’s dedicated sitemap path, and when the plugin builds 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). Data sent: host only, in the query string. Each item in the JSON sitemaps array includes site_url, last_modified, products_count, and total_traffic. Non-200 responses result in an empty (no URLs listed). llms.txt (LLM content index) — GET https://api.llmaffiliate.com/api/v1/enhanced-content/internal/llms-txt?host= Purpose: Returns Markdown content for the /llms.txt file, which provides LLM crawlers with a structured site overview including product categories, brands, price ranges, and links to enhanced pages. When it is sent: Only on GET requests to /llms.txt. Data sent: host only, in the query string. 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= Purpose: Returns detailed Markdown content for the /llms-full.txt file, which includes full product details (brand, price, category, description, buy link) for every product across all enhanced pages. When it is sent: Only on GET requests to /llms-full.txt. Data sent: host only, in the query string. 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: Terms of Service: https://llmaffiliate.com/terms Privacy Policy: https://llmaffiliate.com/privacy Service provider homepage: https://llmaffiliate.com/