Share Buttons & AI-powered Summaries vs BeeClear WebMCP AI Visibility

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 search engines treat it as derived content, not competition. 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. 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. 6 visual styles, 4 sizes, custom colors, brand SVG icons, dark-mode auto-adaptation, drag-and-drop ordering. 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 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, 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"] 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. 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 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 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.

AI visibility and WebMCP discovery for WordPress BeeClear WebMCP AI Visibility helps WordPress sites describe public content, navigation, media, forms and selected actions in a structured way for compatible AI agents and browser clients. The plugin adds WebMCP-style REST tools, agent discovery files, Markdown content output and OpenAPI metadata so automated clients can understand what the site offers before making requests. It is designed for site owners, publishers, agencies and developers who want their public WordPress content to be easier for AI assistants, browser agents and discovery tools to inspect without changing the normal frontend experience for visitors. What the plugin adds REST manifest: Provides a machine-readable entry point at /wp-json/beeclear-webmcp/v1/manifest. Agent discovery files: Adds optional /agent-manifest.txt, /agents-manifest.txt, /agents.txt and /.well-known/api-catalog endpoints, detects whether /llms.txt and /llms-full.txt are already available, and can optionally provide WebMCP fallback output for each llms file independently. Agent policy hints: Publishes controlled capability tokens, robots.txt cross-reference directives and optional DID / W3C Verifiable Credential identity hints with admin-side previews. Markdown for agents: Serves singular content as Markdown when compatible clients request Accept: text/markdown. OpenAPI schema: Publishes endpoint metadata at /wp-json/beeclear-webmcp/v1/openapi. Content discovery tools: Exposes public post search, post retrieval, post types, taxonomies, terms, menus and media metadata. Contact Form 7 tools: Detects Contact Form 7 forms, exposes field schemas and supports authenticated submission testing. Custom form definitions: Lets administrators describe frontend forms with selectors, fields, labels and field purposes. Custom REST functions: Exposes selected same-site REST endpoints as structured WebMCP tools. Discovery links and headers: Adds HTML head links and HTTP Link headers for configured agent-facing resources. Origin Trial support: Optionally sends a WebMCP Origin Trial token as an Origin-Trial header and HTML meta tag for Chrome 149+ production testing. Current browser API support: Registers page tools with document.modelContext, keeps a compatibility fallback for older navigator.modelContext builds, and can expose tools to configured secure cross-origin iframe hosts. Content signals: Adds optional headers and robots.txt directives for automated content-use preferences. Read-only tools can be exposed publicly. State-changing tools require the normal WordPress REST nonce and current-user context. Public agent endpoints include simple transient-based rate limiting to reduce accidental repeated load. Built for… Publishers and content sites If your site contains articles, guides, documentation or resources, the plugin helps compatible agents discover the right content and request a cleaner text version for analysis. Agencies and developers If you manage WordPress sites for clients, the plugin provides a structured way to expose public content, menus, media and selected business actions without building a custom agent API for each project. Businesses using forms If Contact Form 7 or custom frontend forms are part of your conversion flow, the plugin can describe form fields and purposes so authenticated browser-agent tests can work with structured input. AI visibility workflows If you are testing how AI clients understand a site, BeeClear WebMCP AI Visibility gives you manifest, Markdown, OpenAPI and discovery-file outputs from one admin-controlled plugin. Admin controls In wp-admin, go to BeeClear WebMCP to: Enable or disable the integration. Add a Chrome WebMCP Origin Trial token for production testing. Configure secure origins that may discover tools when this site is embedded in an iframe with allow="tools". Choose which public post types are exposed. Enable or disable content, navigation, media, form and custom-function tool groups. Configure agent discovery documents and content-signal preferences. Detect existing /llms.txt and /llms-full.txt files from another plugin or static file. Independently decide whether WebMCP should generate /llms.txt or /llms-full.txt fallback output. Preview the generated agent-manifest.txt, agents-manifest.txt and agents.txt policy files. Add optional trusted issuer hints and site-specific x- capability tokens. Describe Contact Form 7 fields and form purposes. Disable selected Contact Form 7 forms from WebMCP visibility. Define custom forms with CSS selectors and field metadata. Define custom functions that proxy to same-site REST endpoints. Run quick checks for the manifest, discovery files and enabled tools. Additional resources BeeClear website WordPress REST API documentation Translations BeeClear WebMCP AI Visibility is prepared for translation with the beeclear-webmcp-ai-visibility text domain. The source translation template is included in languages/beeclear-webmcp-ai-visibility.pot. Plugin interface strings and readme strings should be translated through translate.wordpress.org after the plugin is imported into the WordPress.org Plugin Directory. Reviewed translations approved as Current by a Project Translation Editor or General Translation Editor are distributed to sites automatically as WordPress.org language packs. Before each release, run scripts/update-translations.sh from the plugin directory to refresh the POT file, merge existing PO files, compile MO files and generate JavaScript translation JSON files when PO files are present. If you maintain a translation outside translate.wordpress.org, use the POT file as the source, review all machine-assisted output with a fluent human translator, and import the resulting PO file into the matching locale and subproject on translate.wordpress.org. External services This plugin does not send data to third-party external services by default. The plugin may send same-site HTTP requests to the WordPress site where it is installed. These requests are used to detect whether local discovery files such as /llms.txt or /llms-full.txt already exist, and to call administrator-configured custom REST functions. Custom REST functions are restricted to same-site endpoints or relative paths; external URLs are rejected. Administrators can optionally enter DID values for trusted VC issuers or agent identities. Those values are published as policy hints in agent-manifest.txt; the plugin does not contact those identifiers, send data to them, or verify them cryptographically. Administrators can optionally enter secure HTTPS origins for cross-origin WebMCP iframe testing. When a matching embedding page delegates allow="tools", the browser may expose this site’s registered WebMCP tool metadata and allow tool execution to that configured origin. The plugin does not contact those origins by itself. Administrators can optionally enter a Chrome WebMCP Origin Trial token. The plugin publishes that token as an Origin-Trial HTTP header and an HTML meta tag; it does not send the token to Google or any other external service.