68% of Google searches now end without a click. Your future visitors are AI assistants and agents \u2014 and most WordPress sites are invisible to them.<\/p>\n\n
AI Visibility<\/strong> makes your site readable, quotable and usable by AI systems:<\/p>\n\n Full RTL and Hebrew support.<\/p>\n\n This plugin connects to Google services only when the site administrator explicitly enables the Google Analytics integration (disabled by default):<\/p>\n\n Data sent consists of the event name and its parameters (source, medium, campaign, page URL). No data is ever sent to the plugin author or any other third party. See Google's Privacy Policy<\/a> and Google Analytics Terms of Service<\/a>.<\/p>\n\n\n No. It complements it. AI Visibility skips schema output automatically when a major SEO plugin is active, and adds the AI-specific layers no SEO plugin covers.<\/p><\/dd>\n No. Only published, public content is ever returned. All endpoints are read-only in the free version.<\/p><\/dd>\n No. Activate the plugin and llms.txt, schema, the agent endpoint and bot logging work immediately.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\/wp-json\/focusweb-ai-visibility\/v1\/ask<\/code>) that lets AI agents search your published content, plus registration with the official WordPress Abilities API so MCP clients can discover it.<\/li>\nExternal Services<\/h3>\n\n
\n
\n
Does this replace my SEO plugin?<\/h3><\/dt>\n
Does the agent endpoint expose private content?<\/h3><\/dt>\n
Do I need to configure anything?<\/h3><\/dt>\n
0.8.4<\/h4>\n\n
\n
aiv<\/code> prefix to focuaivi<\/code> had no migration path. This release adds a one-time automatic migration that recovers settings, custom schema overrides, and analytics history from the old names on upgrade. If you already lost data on 0.8.0\u20130.8.3, updating to this version will restore it as long as the old data hasn't been deleted from your database.<\/li>\n<\/ul>\n\n0.8.3<\/h4>\n\n
\n
$table<\/code> in uninstall.php) as $focuaivi_table<\/code>.<\/li>\n<\/ul>\n\n0.8.2<\/h4>\n\n
\n
aiv<\/code>\/AIV<\/code> prefix to focuaivi<\/code>\/FOCUAIVI<\/code> (WordPress.org requires 4+ characters to avoid collisions across the ~100,000 hosted plugins). The REST namespace changed from aiv\/v1<\/code> to focusweb-ai-visibility\/v1<\/code>.<\/li>\nhttps:\/\/focusweb.co.il\/ai-visibility<\/code>), which went through a broken multi-hop redirect (https\u2192http\u2192https) that some crawlers refuse to follow; now points directly at the canonical https:\/\/www.focusweb.co.il\/ai-visibility\/<\/code>.<\/li>\n<\/ul>\n\n0.8.1<\/h4>\n\n
\n
translators:<\/code> comment must sit immediately above the line with the __()<\/code>\/sprintf()<\/code> call, not just earlier in the same statement.<\/li>\n<\/ul>\n\n0.8.0<\/h4>\n\n
\n
<\/script><\/code> breakout risk in JSON-LD output, validated\/canonicalized custom schema JSON before it's ever stored (rather than saving the raw POST string), moved the AI-referral\/gtag front-end script from an inline <script><\/code> tag to a properly enqueued file (wp_enqueue_script<\/code> + wp_localize_script<\/code>), and added a nonce check to the public referral-logging REST route so it can't be trivially forged cross-origin.<\/li>\n<\/ul>\n\n0.7.3<\/h4>\n\n
\n
0.7.2<\/h4>\n\n
\n
…<\/code>) leaking into the output unescaped.<\/li>\n<\/ul>\n\n0.7.1<\/h4>\n\n
\n
0.7.0<\/h4>\n\n
\n
0.6.3<\/h4>\n\n
\n
0.6.2<\/h4>\n\n
\n
0.6.1<\/h4>\n\n
\n
0.6.0<\/h4>\n\n
\n
0.5.0<\/h4>\n\n
\n
0.4.1<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n