Title: BotSpot Author: haavardmk Published: July 31, 2026 Last modified: July 31, 2026 --- Search plugins ![](https://ps.w.org/botspot/assets/banner-772x250.png?rev=3630256) ![](https://ps.w.org/botspot/assets/icon-256x256.png?rev=3630256) # BotSpot By [haavardmk](https://profiles.wordpress.org/haavardmk/) [Download](https://downloads.wordpress.org/plugin/botspot.3.5.14.zip) * [Details](https://wordpress.org/plugins/botspot/#description) * [Reviews](https://wordpress.org/plugins/botspot/#reviews) * [Installation](https://wordpress.org/plugins/botspot/#installation) * [Development](https://wordpress.org/plugins/botspot/#developers) [Support](https://wordpress.org/support/plugin/botspot/) ## Description BotSpot connects your WordPress site to the BotSpot platform. It syncs selected published content to BotSpot and renders the resulting appendix HTML and JSON-LD structured data on your public pages. The plugin is designed for sites that use BotSpot as a software-as-a-service platform for content enrichment and structured data generation. A BotSpot account and access key are required before content can be synced or rendered. Features include: * Sync selected post types, including posts and pages. * Fetch and render appendix HTML from BotSpot. * Emit JSON-LD structured data in the page head. * Choose automatic placement, footer-aware placement, or manual placement with a shortcode. * Add appendix placement with the `[botspot_appendix]` shortcode or the BotSpot Appendix block. * Cache rendered content with WordPress transients. * Retry failed syncs with WP-Cron. * View connection, sync, runtime, and diagnostic information in the WordPress admin. This plugin does not include premium-only WordPress plugin code. Any paid plan or account requirement applies to the external BotSpot service, not to locked code inside the plugin. ### External Services This plugin connects to BotSpot services in order to provide its core functionality. The plugin will not sync site content until a site administrator enters a BotSpot access key and connects the site. Service provider: BotSpot Service URLs used by production builds: * `https://platform.bot.spot` – BotSpot dashboard used to create and manage access keys. * `https://locus-api.bot.spot` – BotSpot API used for site registration, content sync, appendix rendering, JSON-LD rendering, and enrichment webhooks. Terms of service: https://bot.spot/terms Privacy policy: https://bot.spot/privacy Data sent to BotSpot may include: * Site URL, site name, and webhook URL during connection. * Selected published content, including title, content, excerpt, permalink, post type, status, author display name, language, publish/update dates, categories, tags, featured image URL, and existing source JSON-LD during sync. * The current page path, site origin, and API authentication headers when fetching rendered appendix content or JSON-LD. BotSpot may send webhook requests back to the WordPress site to update enrichment status, clear local caches, and push configuration changes. These requests are authenticated with an HMAC signature. ### Privacy Content sync and rendering require an administrator to connect the site with a BotSpot access key. After connection, the plugin can automatically send selected published content to BotSpot when that content is published or updated. After connection, the BotSpot platform may push configuration changes to the plugin via webhook, altering which post types sync or display enriched content. Administrators can review current settings in the Settings tab. These settings are managed in the BotSpot dashboard. Site administrators can view which post types are synced and which post types receive injected output from the plugin settings screen. Disconnecting or removing the access key stops new authenticated API calls from succeeding. The plugin stores BotSpot access credentials and sync metadata in the WordPress database. On uninstall, plugin options and plugin-owned post metadata are removed. The plugin does not add BotSpot attribution links or credits to public pages by default. Service-rendered appendix output may include BotSpot-managed branding or attribution only if that behavior is configured in BotSpot. ### Source and Build The plugin source is distributed as human-readable PHP, JavaScript, and CSS. Runtime PHP dependencies are installed with Composer and prefixed during release builds with Strauss to avoid dependency conflicts in WordPress environments. Production release archives are generated with `./build.sh` or `TARGET=production./ build.sh`. The generated ZIP includes the WordPress.org `readme.txt`, the plugin license, third-party license notices, and the Strauss-prefixed runtime dependency files needed by the plugin. ### Third-Party Licenses This plugin bundles or generates runtime code from the following GPL-compatible packages: * `jaybizzle/crawler-detect` – MIT License. * `monperrus/crawler-user-agents` – MIT License. * Composer autoload/runtime metadata and Strauss-prefixed generated dependency files – see `THIRD-PARTY-LICENSES.txt` in the plugin package. ## Screenshots [⌊Connect tab for entering a BotSpot access key.⌉⌊Connect tab for entering a BotSpot access key.⌉[ Connect tab for entering a BotSpot access key. [⌊Settings tab for content sync and display placement.⌉⌊Settings tab for content sync and display placement.⌉[ Settings tab for content sync and display placement. [⌊Developer tab with connection, sync, cache, and diagnostic tools.⌉⌊Developer tab with connection, sync, cache, and diagnostic tools.⌉[ Developer tab with connection, sync, cache, and diagnostic tools. ## Blocks This plugin provides 2 blocks. * Bspt Appendix * Botspot Wp Appendix ## Installation 1. Upload the `botspot` folder to the `/wp-content/plugins/` directory, or install the plugin from the WordPress Plugin Directory. 2. Activate the plugin through the Plugins screen in WordPress. 3. Open the BotSpot menu in the WordPress admin. 4. Sign in to BotSpot and create an access key. 5. Paste the access key into the Connect tab and click Connect. 6. Review the Settings tab to choose which post types should sync and where output should be rendered. ## FAQ ### Do I need a BotSpot account? Yes. BotSpot is an interface to the BotSpot software-as-a-service platform. An access key is required before content can be synced or rendered. ### Does the plugin send data to an external service? Yes. After an administrator connects the plugin, selected published content and related metadata are sent to BotSpot so the service can process and render appendix content and structured data. See the External Services section for details. ### Can I choose what content is synced? Yes. Content sync settings are managed in the BotSpot dashboard and sync automatically to the plugin. The Settings tab displays the current configuration. By default, posts and pages are selected. ### Can I disable automatic output? Yes. Output settings including appendix HTML, JSON-LD, placement, and post types are managed in the BotSpot dashboard. Changes made there sync automatically to this plugin. ### How do I place the appendix manually? Set placement to Manual placement and add the `[botspot_appendix]` shortcode where the appendix should appear. You can also use the BotSpot Appendix block in the block editor. ### Does this replace my SEO plugin? No. The plugin emits BotSpot JSON-LD as a separate structured data script and is designed to work alongside common SEO plugins. ### What happens if BotSpot is temporarily unavailable? Previously fetched content can be served from WordPress transients while cache entries are still available. Failed sync attempts are logged, and some sync failures are retried with WP-Cron. ### Does this work on WordPress Multisite? Yes. Each subsite connects to BotSpot independently with its own access key. Network administrators cannot configure BotSpot network-wide; each subsite administrator manages their own connection and settings. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “BotSpot” is open source software. The following people have contributed to this plugin. Contributors * [ haavardmk ](https://profiles.wordpress.org/haavardmk/) [Translate “BotSpot” into your language.](https://translate.wordpress.org/projects/wp-plugins/botspot) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/botspot/), check out the [SVN repository](https://plugins.svn.wordpress.org/botspot/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/botspot/) by [RSS](https://plugins.trac.wordpress.org/log/botspot/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 3.5.14 * Escaped all output at the point of output, including the appendix HTML, JSON- LD, diagnostic comments, and admin notices. * Appendix HTML is now filtered before it is escaped, so output added by the `bspt_appendix_html` filter is escaped too. * Replaced the legacy `[botdot_appendix]` shortcode registration with an automatic rewrite to `[bspt_appendix]`, so existing pages keep working without the plugin claiming a shortcode name that lacks its prefix. * Fixed page cache purging for WP Rocket, which was never being triggered, and routed W3 Total Cache purges through its public API so all of its cache modules are cleared. * Fixed a bug where a page using the `[bspt_appendix]` shortcode or BotSpot Appendix block could receive a second, automatically injected appendix. #### 3.5.13 * Fixed two admin notice links that still pointed at the old settings page slug and produced a permissions error. * Synced version metadata across the plugin header, version constant, and readme. #### 3.5.12 * Removed the Plugin URI header so the plugin and author URIs are no longer identical. #### 3.5.11 * Fixed a fatal error on activation caused by a call to a removed webhook secret method. * Guarded the settings tab against a null post type list. #### 3.5.9 * Settings now lock only when the BotSpot dashboard explicitly pushes configuration, not on initial connect. #### 3.5.7 * Fixed hidden settings controls caused by a stale checkbox override. * Webhooks are now always re-registered instead of trusting a cached webhook id. #### 3.5.6 * Fixed the settings page hook and admin CSS selectors after the plugin slug was renamed to “botspot”. #### 3.5.5 * Prefixed all global template variables (bspt_) to satisfy WordPress.org global- namespace guidelines. #### 3.5.4 * Corrected the plugin text domain to match the plugin slug (“botspot”) across all strings. * Renamed the plugin to “BotSpot” and removed the invalid “Network” header for WordPress.org compliance. * Removed the manual load_plugin_textdomain() call (handled automatically for hosted plugins) and updated the “Tested up to” version. #### 3.5.3 * Hardened for WordPress.org review: output escaping, translation text domain, input sanitization, and strict comparisons across admin and public code. * Documented plugin-owned direct database queries and removed stale analytics references from the readme. * Uninstall now removes all plugin options and transients, including platform settings and migration flags. #### 3.5.2 * Version bump for WordPress.org plugin review submission. #### 3.5.1 * Fixed Developer tab badge status checks (Sync timezone, Runtime transient prefix). * Fixed Settings form field selector prefixes. * Removed incomplete server-side analytics feature. * Updated WordPress tested-up-to version to 6.8. #### 3.4.8 * Synced version metadata across plugin header and readme. * Upgraded test harness dependencies to resolve security advisories. #### 3.4.7 * Continued WordPress.org Plugin Directory compliance refinements. * Rebranded user-visible strings from “BotSpot” to “bot.spot”. * Auto-detect WooCommerce and include product post type in sync options. * Relocated analytics section to Developer tab. * Simplified UX by hiding sensitivity setting and defaulting to high. * Settings now only lock when dashboard pushes config, not on initial connect. #### 3.1.1 * Hardened release packaging, metadata, third-party license notices, analytics rendering, JSON-LD output encoding, sync authorization, SSL verification, lifecycle behavior, and uninstall cleanup for WordPress.org submission readiness. #### 3.0.0 * Renamed internal code from botdot-wp to botspot-wp to match BotSpot branding. * File names, class names, constants, hooks, and options now use botspot prefix. * Migration code automatically preserves settings from v2.x installations. * Legacy hook names (botdot_wp_*) remain as aliases for backwards compatibility. * Legacy shortcode [botdot_appendix] remains as alias for [botspot_appendix]. #### 2.9.2 * Current stable release. * Improves push-based content sync and appendix rendering. * Supports JSON-LD output, appendix HTML output, manual placement, block editor placement, caching, diagnostics, and enrichment status updates. #### 2.6.4 * Fixed cache clearing so plugin-owned appendix and JSON-LD transients are removed correctly. * Added external page-cache purge hooks when enrichment updates are received. * Added cache helper actions for site-specific integrations. #### 2.6.3 * Improved force resync behavior for large sites. #### 2.6.2 * Improved Connect flow so access keys can be saved inline. #### 2.5.0 * Changed JSON-LD output to emit BotSpot structured data as a separate peer script. * Improved multilingual language detection for Polylang and WPML. * Improved source JSON-LD cleanup before sync. #### 2.4.0 * Added admin analytics cards for sync health, enrichment lifecycle, and aggregate impressions. * Added local bot classification and scheduled analytics flushing. #### 1.0.1 * Improved sanitization for external HTML. * Re-encoded JSON-LD output before rendering. * Improved error logging and cache handling. #### 1.0.0 * Initial push-based sync and appendix injection release. ## Meta * Version **3.5.14** * Last updated **14 hours ago** * Active installations **Fewer than 10** * WordPress version ** 5.0 or higher ** * Tested up to **7.0.2** * PHP version ** 7.4 or higher ** * Tags * [AI](https://wordpress.org/plugins/tags/ai/)[content](https://wordpress.org/plugins/tags/content/) [schema](https://wordpress.org/plugins/tags/schema/)[seo](https://wordpress.org/plugins/tags/seo/) [structured data](https://wordpress.org/plugins/tags/structured-data/) * [Advanced View](https://wordpress.org/plugins/botspot/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/botspot/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/botspot/reviews/) ## Contributors * [ haavardmk ](https://profiles.wordpress.org/haavardmk/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/botspot/)