Writes a physical root llms.txt so crawlers stop seeing HTTP 404 on hosts that do not route .txt files through WordPress. Update, then open any wp-admin page once (or regenerate llms.txt in Settings).<\/p>","1.2.3":"
Author URI is the company site; Plugin URI is omitted so the two headers are not identical.<\/p>","1.2.2":"
WordPress.org review hardening: sanitized admin input, enqueued admin CSS, and documented the optional Venuex AI service.<\/p>","1.2.1":"
Prefix cleanup for WordPress.org uniqueness requirements.<\/p>","1.2.0":"
Official name is now Venuex AI Connector. Updating \/llms.txt via REST requires an Administrator Application Password (manage_options).<\/p>","1.1.0":"
Adds root \/llms.txt for AI search visibility. Reactivate or visit Settings \u2192 Permalinks \u2192 Save once if \/llms.txt 404s after update.<\/p>","1.0.0":"
Initial public release. Activate on sites connected to Venuex AI that use Elementor or Yoast.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3647431,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3647431,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3647431,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3647431,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.3","1.2.4"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[76538,239487,23853,186,2227],"plugin_category":[55],"plugin_contributors":[275717],"plugin_business_model":[],"class_list":["post-351274","plugin","type-plugin","status-publish","hentry","plugin_tags-elementor","plugin_tags-llms","plugin_tags-rest-api","plugin_tags-seo","plugin_tags-yoast","plugin_category-seo-and-marketing","plugin_contributors-venuexai","plugin_committers-venuexai"],"banners":{"banner":"https:\/\/ps.w.org\/venuex-ai-connector\/assets\/banner-772x250.png?rev=3647431","banner_2x":"https:\/\/ps.w.org\/venuex-ai-connector\/assets\/banner-1544x500.png?rev=3647431","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/venuex-ai-connector\/assets\/icon-128x128.png?rev=3647431","icon_2x":"https:\/\/ps.w.org\/venuex-ai-connector\/assets\/icon-256x256.png?rev=3647431","generated":false},"screenshots":[],"raw_content":"\n
Venuex AI Connector<\/strong> is the official WordPress plugin for Venuex AI<\/a>. It exposes the post meta fields the Venuex AI Growth Agent needs so it can make approved content and SEO changes on your site through the WordPress REST API.<\/p>\n\n This plugin is not affiliated with WordPress\u2019s built-in AI Connectors screen. It does not register AI providers or send prompts to third-party model APIs. It only unlocks the WordPress REST fields Venuex AI needs on your site.<\/p>\n\n This plugin is not affiliated with Elementor or Yoast. Those product names are used only to describe optional compatibility.<\/p>\n\n Without this plugin (or an equivalent snippet), WordPress accepts writes to Elementor and Yoast meta with a success response and silently discards them<\/strong>. The agent then cannot update Elementor-built pages or set SEO titles and descriptions.<\/p>\n\n This plugin can be used on its own. It registers REST meta locally and serves If you also use Venuex AI<\/a>, you connect the site from the Venuex dashboard with a WordPress Application Password. Venuex AI then calls this site\u2019s REST API to apply changes you approve. That optional service is provided by VenueX:<\/p>\n\n Businesses that connect their WordPress site to Venuex AI and use Elementor and\/or Yoast SEO. Install once, keep it active while Venuex AI is connected.<\/p>\n\n Only if your pages are built with Elementor. The plugin still registers the meta keys either way; non-Elementor sites simply do not use Only if you want Venuex AI to write SEO titles and descriptions. The keys are registered regardless so they work as soon as Yoast is installed.<\/p><\/dd>\n No. The plugin still registers REST meta and serves Functionally yes for meta registration. The plugin is the supported, updateable way to do it \u2014 versioned, uninstallable, and with a status screen.<\/p><\/dd>\n Yes. Deactivating or deleting the plugin immediately removes REST access to those meta keys. Existing page content is unchanged. Deleting the plugin also removes the stored No. This plugin does not contact Venuex servers. It only registers WordPress meta and exposes local REST routes on your site. If you connect the site from Venuex AI, that service will call your site using the Application Password you provide. See the Venuex Terms of Service<\/a> and Privacy Policy<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\nVenuex AI service<\/h4>\n\n
\/llms.txt<\/code> from your WordPress site. It does not<\/strong> phone home or send data to Venuex.<\/p>\n\n\n
What it enables<\/h4>\n\n
\n
_elementor_data<\/code>) so additive content (FAQs, sections) actually appears on the live page<\/li>\n\/llms.txt<\/code><\/strong> file (Markdown, text\/plain<\/code>) so AI-visibility audits stop flagging a missing file. On hosts that do not send .txt<\/code> URLs through WordPress, the plugin also writes a physical llms.txt<\/code> in the site web root.<\/li>\n\/wp-json\/venuex-ai\/v1\/status<\/code>) so Venuex AI can verify the connector is active<\/li>\n<\/ul>\n\nWho should install this<\/h4>\n\n
Security<\/h4>\n\n
\n
show_in_rest<\/code> and an auth_callback<\/code> that requires edit_post<\/code> on that post<\/li>\n\/llms.txt<\/code> option (REST POST or Settings screen) requires manage_options<\/code><\/li>\nedit_posts<\/code><\/li>\nRequirements<\/h4>\n\n
\n
\n
venuex-ai-connector<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the zip via Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n\n
Do I need Elementor installed?<\/h3><\/dt>\n
_elementor_data<\/code>.<\/p><\/dd>\nDo I need Yoast SEO?<\/h3><\/dt>\n
Do I need a Venuex AI account?<\/h3><\/dt>\n
\/llms.txt<\/code> without one. Connecting to Venuex AI is optional and is done in the Venuex dashboard, not inside this plugin.<\/p><\/dd>\nIs this the same as pasting a WPCode snippet?<\/h3><\/dt>\n
Can I remove it later?<\/h3><\/dt>\n
\/llms.txt<\/code> option and the physical root llms.txt<\/code> file this plugin created.<\/p><\/dd>\nDoes it send data to Venuex AI?<\/h3><\/dt>\n
1.2.4<\/h4>\n\n
\n
llms.txt<\/code> in the WordPress web root so hosts that 404 \/llms.txt<\/code> before PHP still return HTTP 200.<\/li>\n1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
\/llms.txt<\/code> as text\/plain<\/code> Markdown at the site root.<\/li>\nGET\/POST \/wp-json\/venuex-ai\/v1\/llms-txt<\/code> so Venuex AI can read or update the body.<\/li>\n1.0.0<\/h4>\n\n
\n
_elementor_data<\/code>, _yoast_wpseo_title<\/code>, and _yoast_wpseo_metadesc<\/code> for page<\/code> and post<\/code>.<\/li>\nGET \/wp-json\/venuex-ai\/v1\/status<\/code> health endpoint.<\/li>\n