{"id":333896,"date":"2026-07-05T10:35:31","date_gmt":"2026-07-05T10:35:31","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/iamai-connector\/"},"modified":"2026-09-10T07:04:03","modified_gmt":"2026-09-10T07:04:03","slug":"iamai-connector","status":"publish","type":"plugin","link":"https:\/\/bre.wordpress.org\/plugins\/iamai-connector\/","author":23525252,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.9.28","stable_tag":"1.9.28","tested":"7.0.4","requires":"5.6","requires_php":"7.4","requires_plugins":null,"header_name":"iAmAI Connector","header_author":"iAmAI","header_description":"\u05d7\u05d9\u05d1\u05d5\u05e8 \u05d4\u05d7\u05e0\u05d5\u05ea \u05dc-iAmAI \u05dc\u05d0\u05d5\u05e4\u05d8\u05d9\u05de\u05d9\u05d6\u05e6\u05d9\u05d4 \u05d0\u05d5\u05d8\u05d5\u05de\u05d8\u05d9\u05ea \u05e9\u05dc SEO, AEO \u05d5\u05e0\u05e8\u05d0\u05d5\u05ea \u05d1-AI. Connect your store to iAmAI for automated SEO, AEO, and AI visibility optimization.","assets_banners_color":"d5e9fd","last_updated":"2026-09-10 07:04:03","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/www.iam-ai.co.il","rating":0,"author_block_rating":0,"active_installs":0,"downloads":218,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.1.7":{"tag":"1.1.7","author":"15iamai","date":"2026-06-30 16:48:07","revision":3591767},"1.9.21":{"tag":"1.9.21","author":"15iamai","date":"2026-09-09 20:08:50","revision":3688953},"1.9.23":{"tag":"1.9.23","author":"15iamai","date":"2026-09-09 21:11:37","revision":3689009},"1.9.28":{"tag":"1.9.28","author":"15iamai","date":"2026-09-10 07:04:03","revision":3689429}},"upgrade_notice":{"1.9.21":"<p>Major update from 1.1.7: the plugin now writes the SEO work to your site (titles, descriptions, keyphrases, alt text, schema), with a setup wizard, a product-level before\/after view, articles with approval, and a manual-edit guard. Requires an active iAmAI subscription for writes. Recommended for every connected store.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.gif":{"filename":"icon-128x128.gif","revision":3688953,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.gif":{"filename":"icon-256x256.gif","revision":3688953,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3688953,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3688953,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.7","1.9.21","1.9.23","1.9.28"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3688953,"resolution":"1","location":"assets","locale":"","width":1388,"height":675},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3688953,"resolution":"2","location":"assets","locale":"","width":1388,"height":675},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3688953,"resolution":"3","location":"assets","locale":"","width":1078,"height":649},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3688953,"resolution":"4","location":"assets","locale":"","width":1388,"height":675},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3688953,"resolution":"5","location":"assets","locale":"","width":1388,"height":675}},"screenshots":{"1":"The iAmAI dashboard inside wp-admin: three gauges about the work \u2014 optimisation coverage, AI readiness and site health \u2014 each listing the named checks it is made of.","2":"\"What was fixed\": every product with its SEO title and meta description before and after, as applied to the live site.","3":"The product screen: what iAmAI wrote for this product, what it looked like before, and a per-field edit that tells the system to leave that field alone.","4":"Articles: what is being written, what waits for your approval, what was published.","5":"AI crawlers that visited this month (GPTBot, ClaudeBot, PerplexityBot, Meta AI), counted on your own site, plus the running totals."}},"plugin_section":[],"plugin_tags":[244526,2353,5777,186,286],"plugin_category":[52,55],"plugin_contributors":[269621],"plugin_business_model":[],"class_list":["post-333896","plugin","type-plugin","status-publish","hentry","plugin_tags-aeo","plugin_tags-ai","plugin_tags-meta-description","plugin_tags-seo","plugin_tags-woocommerce","plugin_category-performance","plugin_category-seo-and-marketing","plugin_contributors-15iamai","plugin_committers-15iamai"],"banners":{"banner":"https:\/\/ps.w.org\/iamai-connector\/assets\/banner-772x250.png?rev=3688953","banner_2x":"https:\/\/ps.w.org\/iamai-connector\/assets\/banner-1544x500.png?rev=3688953","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/iamai-connector\/assets\/icon-128x128.gif?rev=3688953","icon_2x":"https:\/\/ps.w.org\/iamai-connector\/assets\/icon-256x256.gif?rev=3688953","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/iamai-connector\/assets\/screenshot-1.png?rev=3688953","caption":"The iAmAI dashboard inside wp-admin: three gauges about the work \u2014 optimisation coverage, AI readiness and site health \u2014 each listing the named checks it is made of."},{"src":"https:\/\/ps.w.org\/iamai-connector\/assets\/screenshot-2.png?rev=3688953","caption":"\"What was fixed\": every product with its SEO title and meta description before and after, as applied to the live site."},{"src":"https:\/\/ps.w.org\/iamai-connector\/assets\/screenshot-3.png?rev=3688953","caption":"The product screen: what iAmAI wrote for this product, what it looked like before, and a per-field edit that tells the system to leave that field alone."},{"src":"https:\/\/ps.w.org\/iamai-connector\/assets\/screenshot-4.png?rev=3688953","caption":"Articles: what is being written, what waits for your approval, what was published."},{"src":"https:\/\/ps.w.org\/iamai-connector\/assets\/screenshot-5.png?rev=3688953","caption":"AI crawlers that visited this month (GPTBot, ClaudeBot, PerplexityBot, Meta AI), counted on your own site, plus the running totals."}],"raw_content":"<!--section=description-->\n<p>iAmAI Connector links your WordPress \/ WooCommerce store to the iAmAI service (https:\/\/www.iam-ai.co.il) \u2014 an external SaaS platform that writes and applies on-page SEO and AI-readiness improvements to your catalogue, product by product, so you do not have to.<\/p>\n\n<p><strong>This plugin requires a paid iAmAI subscription.<\/strong> Installing the plugin and running the first scan is free; writing to your site starts with an active subscription. Plans and prices: https:\/\/www.iam-ai.co.il\/payment\/<\/p>\n\n<p><strong>What the plugin does:<\/strong><\/p>\n\n<ul>\n<li>Writes a meta title, meta description and focus keyphrase for every product, page and post \u2014 real search terms with measured Hebrew demand, not the product title rewritten.<\/li>\n<li>Image alt text, FAQ blocks, breadcrumbs and Product schema (JSON-LD) for your catalogue.<\/li>\n<li>Works with NO SEO plugin installed: iAmAI stores the fields itself and renders them into the page head.<\/li>\n<li>No duplicate tags when you DO run one: Yoast, Rank Math, All in One SEO, SEOPress, Slim SEO and The SEO Framework are detected and iAmAI feeds its values through that plugin's own fields.<\/li>\n<li>Setup wizard with a real scan: where you rank on Google, which shops compete with you on the same searches, and what ChatGPT, Gemini and Claude know about your brand.<\/li>\n<li>Product screen shows what iAmAI wrote for that product and what it looked like before, without an extra page load.<\/li>\n<li>Manual-edit guard: every write is preceded by a live read of the field. If you edited it by hand, iAmAI leaves it alone.<\/li>\n<li>Monthly Hebrew articles for your blog, each waiting for your approval before it is published.<\/li>\n<li>Monthly progress report by email, and a Reports screen inside wp-admin with every month's report and history.<\/li>\n<li>IndexNow: every title or description iAmAI writes, and every product, post or page you publish, is pushed to Bing the moment it changes \u2014 and through Bing's index to ChatGPT's web search. (Google does not take IndexNow; this does not affect Google.)<\/li>\n<li>Reversible: every change records its previous value; disconnecting restores what was there before.<\/li>\n<li>Product feed for AI shopping (OpenAI Agentic Commerce format): the catalogue is served at \/wp-json\/iamai\/v1\/acp-feed \u2014 published, visible, priced products only, with iAmAI's AI-readable description, live price and stock. Discovery only, no off-site checkout. Ready to submit the day the merchant program opens for your country.<\/li>\n<li>WordPress 7.x Abilities API: iAmAI's capabilities (store status, read\/write a product's SEO fields, monthly reports, IndexNow) are registered as abilities, so your own AI agent can discover and use them through the site's MCP endpoint. Requires an administrator; inert on older WordPress.<\/li>\n<\/ul>\n\n<p><strong>How it works:<\/strong><\/p>\n\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>The setup wizard connects the site. The plugin creates a WordPress Application Password and sends it to iAmAI so iAmAI can scan and update your site.<\/li>\n<li>The wizard runs the first scan and shows what it found.<\/li>\n<li>Activate a subscription. iAmAI then generates and applies improvements to your catalogue at a paced monthly rate, and you follow every change from the iAmAI screen inside wp-admin.<\/li>\n<\/ol>\n\n<p>The connection is built on standard WordPress Application Passwords (available since WP 5.6). You can revoke access at any time from <strong>Users \u2192 Profile \u2192 Application Passwords<\/strong>, or by clicking \"Disconnect\" inside the plugin's settings page.<\/p>\n\n<h4>\u05e2\u05d1\u05e8\u05d9\u05ea<\/h4>\n\n<p>iAmAI Connector \u05de\u05d7\u05d1\u05e8 \u05d0\u05ea \u05d7\u05e0\u05d5\u05ea \u05d4-WordPress \/ WooCommerce \u05e9\u05dc\u05db\u05dd \u05dc\u05e9\u05d9\u05e8\u05d5\u05ea iAmAI, \u05e9\u05db\u05d5\u05ea\u05d1 \u05d5\u05de\u05d7\u05d9\u05dc \u05e2\u05d1\u05d5\u05e8\u05db\u05dd \u05d0\u05ea \u05e2\u05d1\u05d5\u05d3\u05ea \u05d4-SEO \u05d5\u05d0\u05ea \u05d4\u05d4\u05ea\u05d0\u05de\u05d4 \u05dc\u05db\u05dc\u05d9 AI, \u05de\u05d5\u05e6\u05e8 \u05d0\u05d7\u05e8\u05d9 \u05de\u05d5\u05e6\u05e8.<\/p>\n\n<p><strong>\u05d4\u05ea\u05d5\u05e1\u05e3 \u05d3\u05d5\u05e8\u05e9 \u05de\u05e0\u05d5\u05d9 iAmAI \u05d1\u05ea\u05e9\u05dc\u05d5\u05dd.<\/strong> \u05d4\u05d4\u05ea\u05e7\u05e0\u05d4 \u05d5\u05d4\u05e1\u05e8\u05d9\u05e7\u05d4 \u05d4\u05e8\u05d0\u05e9\u05d5\u05e0\u05d4 \u05d7\u05d9\u05e0\u05dd; \u05d4\u05db\u05ea\u05d9\u05d1\u05d4 \u05dc\u05d0\u05ea\u05e8 \u05de\u05ea\u05d7\u05d9\u05dc\u05d4 \u05e2\u05dd \u05de\u05e0\u05d5\u05d9 \u05e4\u05e2\u05d9\u05dc.<\/p>\n\n<p><strong>\u05de\u05d4 \u05d4\u05ea\u05d5\u05e1\u05e3 \u05e2\u05d5\u05e9\u05d4:<\/strong><\/p>\n\n<ul>\n<li>\u05db\u05d5\u05ea\u05d1 \u05db\u05d5\u05ea\u05e8\u05ea SEO, \u05ea\u05d9\u05d0\u05d5\u05e8 \u05de\u05d8\u05d0 \u05d5\u05d1\u05d9\u05d8\u05d5\u05d9 \u05de\u05e4\u05ea\u05d7 \u05dc\u05db\u05dc \u05de\u05d5\u05e6\u05e8, \u05e2\u05de\u05d5\u05d3 \u05d5\u05e4\u05d5\u05e1\u05d8. \u05d1\u05d9\u05d8\u05d5\u05d9\u05d9\u05dd \u05d0\u05de\u05d9\u05ea\u05d9\u05d9\u05dd \u05e2\u05dd \u05d1\u05d9\u05e7\u05d5\u05e9 \u05e0\u05de\u05d3\u05d3 \u05d1\u05e2\u05d1\u05e8\u05d9\u05ea, \u05dc\u05d0 \u05d4\u05db\u05d5\u05ea\u05e8\u05ea \u05e9\u05dc \u05d4\u05de\u05d5\u05e6\u05e8 \u05d1\u05e0\u05d9\u05e1\u05d5\u05d7 \u05d0\u05d7\u05e8.<\/li>\n<li>\u05d8\u05e7\u05e1\u05d8 \u05d7\u05dc\u05d5\u05e4\u05d9 \u05dc\u05ea\u05de\u05d5\u05e0\u05d5\u05ea, \u05d1\u05dc\u05d5\u05e7\u05d9 \u05e9\u05d0\u05dc\u05d5\u05ea \u05d5\u05ea\u05e9\u05d5\u05d1\u05d5\u05ea, \u05e4\u05d9\u05e8\u05d5\u05e8\u05d9 \u05dc\u05d7\u05dd \u05d5\u05e1\u05db\u05de\u05ea \u05de\u05d5\u05e6\u05e8 (JSON-LD).<\/li>\n<li>\u05e2\u05d5\u05d1\u05d3 \u05d2\u05dd \u05d1\u05dc\u05d9 \u05e9\u05d5\u05dd \u05ea\u05d5\u05e1\u05e3 SEO: iAmAI \u05e9\u05d5\u05de\u05e8 \u05d0\u05ea \u05d4\u05e9\u05d3\u05d5\u05ea \u05d1\u05e2\u05e6\u05de\u05d5 \u05d5\u05de\u05e6\u05d9\u05d2 \u05d0\u05d5\u05ea\u05dd \u05d1-head \u05e9\u05dc \u05d4\u05e2\u05de\u05d5\u05d3.<\/li>\n<li>\u05d1\u05dc\u05d9 \u05ea\u05d2\u05d9\u05d5\u05ea \u05db\u05e4\u05d5\u05dc\u05d5\u05ea \u05db\u05e9\u05d9\u05e9 \u05ea\u05d5\u05e1\u05e3 SEO: Yoast, Rank Math, All in One SEO, SEOPress, Slim SEO \u05d5-The SEO Framework \u05de\u05d6\u05d5\u05d4\u05d9\u05dd \u05d5\u05d4\u05e2\u05e8\u05db\u05d9\u05dd \u05e0\u05db\u05ea\u05d1\u05d9\u05dd \u05dc\u05e9\u05d3\u05d5\u05ea \u05e9\u05dc \u05d4\u05ea\u05d5\u05e1\u05e3 \u05e2\u05e6\u05de\u05d5.<\/li>\n<li>\u05d0\u05e9\u05e3 \u05d4\u05ea\u05e7\u05e0\u05d4 \u05e2\u05dd \u05e1\u05e8\u05d9\u05e7\u05d4 \u05d0\u05de\u05d9\u05ea\u05d9\u05ea: \u05d0\u05d9\u05e4\u05d4 \u05d0\u05ea\u05dd \u05d1\u05d2\u05d5\u05d2\u05dc, \u05de\u05d9 \u05de\u05ea\u05d7\u05e8\u05d4 \u05d1\u05db\u05dd \u05e2\u05dc \u05d0\u05d5\u05ea\u05dd \u05d7\u05d9\u05e4\u05d5\u05e9\u05d9\u05dd, \u05d5\u05de\u05d4 ChatGPT, Gemini \u05d5-Claude \u05d9\u05d5\u05d3\u05e2\u05d9\u05dd \u05e2\u05dc \u05d4\u05de\u05d5\u05ea\u05d2 \u05e9\u05dc\u05db\u05dd.<\/li>\n<li>\u05de\u05e1\u05da \u05d4\u05de\u05d5\u05e6\u05e8 \u05de\u05e6\u05d9\u05d2 \u05de\u05d4 iAmAI \u05db\u05ea\u05d1 \u05d5\u05de\u05d4 \u05d4\u05d9\u05d4 \u05e9\u05dd \u05dc\u05e4\u05e0\u05d9, \u05d1\u05dc\u05d9 \u05d8\u05e2\u05d9\u05e0\u05d4 \u05e0\u05d5\u05e1\u05e4\u05ea.<\/li>\n<li>\u05e9\u05d5\u05de\u05e8 \u05e2\u05e8\u05d9\u05db\u05d5\u05ea \u05d9\u05d3\u05e0\u05d9\u05d5\u05ea: \u05db\u05dc \u05db\u05ea\u05d9\u05d1\u05d4 \u05de\u05ea\u05d7\u05d9\u05dc\u05d4 \u05d1\u05e7\u05e8\u05d9\u05d0\u05d4 \u05d7\u05d9\u05d4 \u05e9\u05dc \u05d4\u05e9\u05d3\u05d4. \u05d0\u05dd \u05e2\u05e8\u05db\u05ea\u05dd \u05d0\u05d5\u05ea\u05d5 \u05d9\u05d3\u05e0\u05d9\u05ea, \u05d4\u05de\u05e2\u05e8\u05db\u05ea \u05dc\u05d0 \u05e0\u05d5\u05d2\u05e2\u05ea \u05d1\u05d5.<\/li>\n<li>\u05de\u05d0\u05de\u05e8\u05d9\u05dd \u05d7\u05d5\u05d3\u05e9\u05d9\u05d9\u05dd \u05d1\u05e2\u05d1\u05e8\u05d9\u05ea \u05dc\u05d1\u05dc\u05d5\u05d2, \u05db\u05dc \u05d0\u05d7\u05d3 \u05de\u05de\u05ea\u05d9\u05df \u05dc\u05d0\u05d9\u05e9\u05d5\u05e8\u05db\u05dd \u05dc\u05e4\u05e0\u05d9 \u05e4\u05e8\u05e1\u05d5\u05dd.<\/li>\n<li>\u05d3\u05d5\u05d7 \u05d4\u05ea\u05e7\u05d3\u05de\u05d5\u05ea \u05d7\u05d5\u05d3\u05e9\u05d9 \u05d1\u05de\u05d9\u05d9\u05dc, \u05d5\u05de\u05e1\u05da \"\u05d3\u05d5\u05d7\u05d5\u05ea\" \u05d1\u05ea\u05d5\u05da wp-admin \u05e2\u05dd \u05db\u05dc \u05d4\u05d3\u05d5\u05d7\u05d5\u05ea \u05d5\u05d4\u05d4\u05d9\u05e1\u05d8\u05d5\u05e8\u05d9\u05d4.<\/li>\n<li>IndexNow: \u05db\u05dc \u05db\u05d5\u05ea\u05e8\u05ea \u05d0\u05d5 \u05ea\u05d9\u05d0\u05d5\u05e8 \u05e9\u05d4\u05de\u05e2\u05e8\u05db\u05ea \u05db\u05d5\u05ea\u05d1\u05ea, \u05d5\u05db\u05dc \u05de\u05d5\u05e6\u05e8, \u05e4\u05d5\u05e1\u05d8 \u05d0\u05d5 \u05e2\u05de\u05d5\u05d3 \u05e9\u05d0\u05ea\u05dd \u05de\u05e4\u05e8\u05e1\u05de\u05d9\u05dd, \u05e0\u05e9\u05dc\u05d7\u05d9\u05dd \u05dc-Bing \u05d1\u05e8\u05d2\u05e2 \u05d4\u05e9\u05d9\u05e0\u05d5\u05d9, \u05d5\u05d3\u05e8\u05da \u05d4\u05d0\u05d9\u05e0\u05d3\u05e7\u05e1 \u05e9\u05dc Bing \u05dc\u05d7\u05d9\u05e4\u05d5\u05e9 \u05e9\u05dc ChatGPT. (\u05d2\u05d5\u05d2\u05dc \u05dc\u05d0 \u05de\u05e9\u05ea\u05de\u05e9\u05ea \u05d1-IndexNow; \u05d6\u05d4 \u05dc\u05d0 \u05de\u05e9\u05e4\u05d9\u05e2 \u05e2\u05dc \u05d2\u05d5\u05d2\u05dc.)<\/li>\n<li>\u05d4\u05e4\u05d9\u05da: \u05db\u05dc \u05e9\u05d9\u05e0\u05d5\u05d9 \u05e9\u05d5\u05de\u05e8 \u05d0\u05ea \u05d4\u05e2\u05e8\u05da \u05d4\u05e7\u05d5\u05d3\u05dd, \u05d5\u05e0\u05d9\u05ea\u05d5\u05e7 \u05de\u05d7\u05d6\u05d9\u05e8 \u05d0\u05ea \u05de\u05d4 \u05e9\u05d4\u05d9\u05d4.<\/li>\n<li>\u05e4\u05d9\u05d3 \u05de\u05d5\u05e6\u05e8\u05d9\u05dd \u05dc\u05e7\u05e0\u05d9\u05d5\u05ea \u05d1-AI (\u05e4\u05d5\u05e8\u05de\u05d8 Agentic Commerce \u05e9\u05dc OpenAI): \u05d4\u05e7\u05d8\u05dc\u05d5\u05d2 \u05de\u05d5\u05d2\u05e9 \u05d1-\/wp-json\/iamai\/v1\/acp-feed, \u05e8\u05e7 \u05de\u05d5\u05e6\u05e8\u05d9\u05dd \u05de\u05e4\u05d5\u05e8\u05e1\u05de\u05d9\u05dd \u05d5\u05d2\u05dc\u05d5\u05d9\u05d9\u05dd \u05e2\u05dd \u05de\u05d7\u05d9\u05e8, \u05e2\u05dd \u05d4\u05ea\u05d9\u05d0\u05d5\u05e8 \u05d4\u05e7\u05e8\u05d9\u05d0 \u05dc-AI \u05e9\u05dc iAmAI \u05d5\u05de\u05d7\u05d9\u05e8 \u05d5\u05de\u05dc\u05d0\u05d9 \u05d7\u05d9\u05d9\u05dd. \u05d2\u05d9\u05dc\u05d5\u05d9 \u05d1\u05dc\u05d1\u05d3, \u05d1\u05dc\u05d9 \u05ea\u05e9\u05dc\u05d5\u05dd \u05de\u05d7\u05d5\u05e5 \u05dc\u05d0\u05ea\u05e8. \u05de\u05d5\u05db\u05df \u05dc\u05d4\u05d2\u05e9\u05d4 \u05d1\u05d9\u05d5\u05dd \u05e9\u05ea\u05d5\u05db\u05e0\u05d9\u05ea \u05d4\u05e1\u05d5\u05d7\u05e8\u05d9\u05dd \u05e0\u05e4\u05ea\u05d7\u05ea \u05d1\u05d9\u05e9\u05e8\u05d0\u05dc.<\/li>\n<li>Abilities API \u05e9\u05dc \u05d5\u05d5\u05e8\u05d3\u05e4\u05e8\u05e1 7: \u05d4\u05d9\u05db\u05d5\u05dc\u05d5\u05ea \u05e9\u05dc iAmAI (\u05de\u05e6\u05d1 \u05d4\u05d7\u05e0\u05d5\u05ea, \u05e7\u05e8\u05d9\u05d0\u05d4 \u05d5\u05db\u05ea\u05d9\u05d1\u05d4 \u05e9\u05dc \u05e9\u05d3\u05d5\u05ea SEO \u05dc\u05e4\u05e8\u05d9\u05d8, \u05d4\u05d3\u05d5\u05d7\u05d5\u05ea \u05d4\u05d7\u05d5\u05d3\u05e9\u05d9\u05d9\u05dd, IndexNow) \u05e8\u05e9\u05d5\u05de\u05d5\u05ea \u05db\u05d9\u05db\u05d5\u05dc\u05d5\u05ea, \u05db\u05da \u05e9\u05e1\u05d5\u05db\u05df AI \u05de\u05e9\u05dc\u05db\u05dd \u05d9\u05db\u05d5\u05dc \u05dc\u05d2\u05dc\u05d5\u05ea \u05d5\u05dc\u05d4\u05e4\u05e2\u05d9\u05dc \u05d0\u05d5\u05ea\u05df \u05d3\u05e8\u05da \u05d4-MCP \u05e9\u05dc \u05d4\u05d0\u05ea\u05e8. \u05d3\u05d5\u05e8\u05e9 \u05de\u05e0\u05d4\u05dc; \u05dc\u05d0 \u05e4\u05e2\u05d9\u05dc \u05d1\u05d2\u05e8\u05e1\u05d0\u05d5\u05ea \u05d9\u05e9\u05e0\u05d5\u05ea.<\/li>\n<\/ul>\n\n<p><strong>\u05d0\u05d9\u05da \u05d6\u05d4 \u05e2\u05d5\u05d1\u05d3:<\/strong><\/p>\n\n<ol>\n<li>\u05de\u05ea\u05e7\u05d9\u05e0\u05d9\u05dd \u05d5\u05de\u05e4\u05e2\u05d9\u05dc\u05d9\u05dd \u05d0\u05ea \u05d4\u05ea\u05d5\u05e1\u05e3.<\/li>\n<li>\u05d0\u05e9\u05e3 \u05d4\u05d4\u05ea\u05e7\u05e0\u05d4 \u05de\u05d7\u05d1\u05e8 \u05d0\u05ea \u05d4\u05d0\u05ea\u05e8: \u05d4\u05ea\u05d5\u05e1\u05e3 \u05d9\u05d5\u05e6\u05e8 Application Password \u05d5\u05e9\u05d5\u05dc\u05d7 \u05dc-iAmAI.<\/li>\n<li>\u05d4\u05d0\u05e9\u05e3 \u05de\u05e8\u05d9\u05e5 \u05e1\u05e8\u05d9\u05e7\u05d4 \u05e8\u05d0\u05e9\u05d5\u05e0\u05d4 \u05d5\u05de\u05e6\u05d9\u05d2 \u05d0\u05ea \u05d4\u05de\u05de\u05e6\u05d0\u05d9\u05dd.<\/li>\n<li>\u05de\u05e4\u05e2\u05d9\u05dc\u05d9\u05dd \u05de\u05e0\u05d5\u05d9. \u05de\u05db\u05d0\u05df \u05d4\u05de\u05e2\u05e8\u05db\u05ea \u05de\u05d9\u05d9\u05e6\u05e8\u05ea \u05d5\u05de\u05d7\u05d9\u05dc\u05d4 \u05e9\u05d9\u05e4\u05d5\u05e8\u05d9\u05dd \u05d1\u05e7\u05e6\u05d1 \u05d7\u05d5\u05d3\u05e9\u05d9 \u05de\u05d3\u05d5\u05d3, \u05d5\u05d0\u05ea\u05dd \u05e2\u05d5\u05e7\u05d1\u05d9\u05dd \u05d0\u05d7\u05e8\u05d9 \u05db\u05dc \u05e9\u05d9\u05e0\u05d5\u05d9 \u05d1\u05de\u05e1\u05da iAmAI \u05d1\u05ea\u05d5\u05da wp-admin.<\/li>\n<\/ol>\n\n<p>\u05d4\u05d7\u05d9\u05d1\u05d5\u05e8 \u05de\u05e9\u05ea\u05de\u05e9 \u05d1-Application Passwords \u05d4\u05e1\u05d8\u05e0\u05d3\u05e8\u05d8\u05d9\u05d9\u05dd \u05e9\u05dc WordPress; \u05e0\u05d9\u05ea\u05df \u05dc\u05d1\u05d8\u05dc \u05d0\u05ea \u05d4\u05d2\u05d9\u05e9\u05d4 \u05d1\u05db\u05dc \u05e8\u05d2\u05e2 \u05de-Users \u2192 Profile \u2192 Application Passwords \u05d0\u05d5 \u05d3\u05e8\u05da \"\u05e0\u05d9\u05ea\u05d5\u05e7\" \u05d1\u05d4\u05d2\u05d3\u05e8\u05d5\u05ea \u05d4\u05ea\u05d5\u05e1\u05e3.<\/p>\n\n<h3>Third-Party Services<\/h3>\n\n<p>This plugin connects your WordPress site to the iAmAI service (an external third-party SaaS at <strong>https:\/\/www.iam-ai.co.il<\/strong>) and exchanges data with it. The plugin will not function without an iAmAI account.<\/p>\n\n<p>The following calls are made to the iAmAI backend:<\/p>\n\n<p><strong>1. On Connect (one-time, from the setup wizard)<\/strong><\/p>\n\n<ul>\n<li>Endpoint: <code>POST https:\/\/www.iam-ai.co.il\/api\/integrations\/wordpress?action=install<\/code><\/li>\n<li>Data sent: site URL, site name, admin username, admin email, a WordPress Application Password (stored encrypted on the iAmAI side using AES-256-GCM), WordPress version, WooCommerce installed flag, plugin version.<\/li>\n<li>Purpose: provision your store inside iAmAI and let iAmAI write SEO updates back via the REST API.<\/li>\n<\/ul>\n\n<p><strong>2. During the setup wizard scan (one-time, admin-initiated)<\/strong><\/p>\n\n<ul>\n<li>Endpoints: <code>POST https:\/\/www.iam-ai.co.il\/api\/scan?action=wizard-start<\/code>, <code>GET https:\/\/www.iam-ai.co.il\/api\/scan?action=status&amp;id=\u2026<\/code>, <code>POST https:\/\/www.iam-ai.co.il\/api\/integrations\/wordpress?action=claim_ticket<\/code><\/li>\n<li>Data sent: store ID, API token, and the site URL.<\/li>\n<li>Purpose: run the first scan (Google positions, competitors, AI-engine mentions) and hand the admin over to their iAmAI account without a second login.<\/li>\n<\/ul>\n\n<p><strong>3. On Disconnect \/ Deactivate \/ Uninstall (one-time per event)<\/strong><\/p>\n\n<ul>\n<li>Endpoint: <code>POST https:\/\/www.iam-ai.co.il\/api\/integrations\/wordpress<\/code> (action <code>disconnect<\/code> or <code>plugin_event<\/code>).<\/li>\n<li>Data sent: store ID, API token, event type (<code>disconnect<\/code>, <code>deactivated<\/code>, or <code>uninstalled<\/code>), site URL, plugin version.<\/li>\n<li>Purpose: let iAmAI reflect your status immediately instead of waiting for the next health check.<\/li>\n<\/ul>\n\n<p><strong>4. On admin visits to the plugin's screens (cached, admin only)<\/strong><\/p>\n\n<ul>\n<li>Endpoints: <code>GET https:\/\/www.iam-ai.co.il\/api\/integrations\/wordpress?action=status|dashboard|articles|reports|product_keywords&amp;store_id=\u2026&amp;token=\u2026<\/code>, <code>POST \u2026?action=brand_update<\/code>, <code>GET https:\/\/www.iam-ai.co.il\/llms.txt?store=\u2026<\/code><\/li>\n<li>Data sent: store ID and API token; for <code>brand_update<\/code>, the brand profile fields the admin edited on the settings screen; for <code>product_keywords<\/code>, the post ID being viewed.<\/li>\n<li>Purpose: render the dashboard (what was fixed, what is queued, AI-crawler visits), the articles list, the monthly reports, the keyword set on a product screen, and the brand profile.<\/li>\n<\/ul>\n\n<p><strong>5. On page render of singular posts\/pages (server-side, cached 1 hour)<\/strong><\/p>\n\n<ul>\n<li>Endpoints: <code>GET https:\/\/www.iam-ai.co.il\/api\/seo\/faq-public?store_id=\u2026<\/code>, <code>GET https:\/\/www.iam-ai.co.il\/api\/seo\/breadcrumb-public?store_id=\u2026&amp;path=\u2026<\/code>, <code>GET https:\/\/www.iam-ai.co.il\/api\/seo\/sections-public?store_id=\u2026&amp;post_id=\u2026<\/code><\/li>\n<li>Data sent: store ID, the requested URL path \/ post ID.<\/li>\n<li>Purpose: fetch the applied FAQ, breadcrumb and content-section entries and inject <code>FAQPage<\/code> \/ <code>BreadcrumbList<\/code> Schema.org JSON-LD and the approved content blocks.<\/li>\n<\/ul>\n\n<p><strong>6. On every WooCommerce product page (server-side, cached 1 hour per product)<\/strong><\/p>\n\n<ul>\n<li>Endpoint: <code>GET https:\/\/www.iam-ai.co.il\/api\/seo\/product-schema-public?store_id=\u2026&amp;path=\u2026<\/code><\/li>\n<li>Data sent: store ID and the product URL path.<\/li>\n<li>Purpose: fetch and inject <code>Product<\/code> Schema.org JSON-LD and social preview meta tags.<\/li>\n<\/ul>\n\n<p><strong>7. On every storefront page view (visitor side, async, non-blocking)<\/strong><\/p>\n\n<ul>\n<li>Script loaded: <code>https:\/\/www.iam-ai.co.il\/pixel.js?sid=\u2026&amp;platform=wordpress<\/code><\/li>\n<li>Beacon endpoint: <code>POST https:\/\/www.iam-ai.co.il\/api\/v1\/p-signal<\/code><\/li>\n<li>Data sent: page URL, referrer, anonymous visit identifier, and basic interaction events (page views, add-to-cart on WooCommerce loop buttons).<\/li>\n<li>The pixel <strong>does not<\/strong> load for logged-in administrators (<code>manage_options<\/code> capability), and it does not load on admin, login, or AJAX pages.<\/li>\n<li>Purpose: analytics that iAmAI uses to score which optimizations are working.<\/li>\n<\/ul>\n\n<p><strong>8. IndexNow (server-side, after a write or a publish)<\/strong><\/p>\n\n<ul>\n<li>Endpoint: <code>POST https:\/\/api.indexnow.org\/indexnow<\/code> (an open protocol operated by Microsoft Bing, shared with Yandex, Seznam and Naver; terms: https:\/\/www.indexnow.org\/)<\/li>\n<li>Data sent: your site's hostname, the public URL of the page that just changed, and a 32-character ownership key the plugin generates and serves at <code>https:\/\/&lt;your-site&gt;\/&lt;key&gt;.txt<\/code>.<\/li>\n<li>Purpose: ask those search engines to re-fetch the changed page now instead of on their next crawl. Sent only for published, public pages, at most once per URL per 12 hours, and never when the site's \"discourage search engines\" setting is on. Google does not participate in IndexNow.<\/li>\n<\/ul>\n\n<p><strong>Backend \u2192 site writes<\/strong><\/p>\n\n<p>iAmAI's backend uses the WordPress REST API (authenticated with the Application Password created at connect) to write back into your site:<\/p>\n\n<ul>\n<li><code>POST \/wp-json\/iamai\/v1\/seo-fields<\/code> \u2014 sets meta title, meta description and focus keyphrase on individual posts (stored as standard postmeta; mirrored into the active SEO plugin's own fields when one is present), together with the previous value for the before\/after view.<\/li>\n<li><code>POST \/wp-json\/iamai\/v1\/gsc-verification<\/code> \u2014 sets a Google Search Console verification token that the plugin injects into <code>&lt;head&gt;<\/code> via the standard <code>google-site-verification<\/code> meta tag.<\/li>\n<li>Standard <code>wp\/v2<\/code> and <code>wc\/v3<\/code> endpoints \u2014 image alt text, internal links appended to content, and article drafts (articles are created as drafts and published only after you approve them).<\/li>\n<\/ul>\n\n<p><strong>Terms and Privacy<\/strong><\/p>\n\n<ul>\n<li>iAmAI Terms of Service: https:\/\/www.iam-ai.co.il\/terms<\/li>\n<li>iAmAI Privacy Policy: https:\/\/www.iam-ai.co.il\/privacy<\/li>\n<\/ul>\n\n<p>Visitor tracking through the storefront pixel is anonymous, but as the site operator you remain responsible for any disclosures and consent required under GDPR \/ CCPA \/ local law. The iAmAI Privacy Policy describes the data iAmAI receives and how it is stored.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install from the WordPress.org plugin directory, or upload the ZIP via <strong>Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n<li>Activate the plugin. The setup wizard opens.<\/li>\n<li>Follow the wizard: connect, scan, review the findings, activate a subscription.<\/li>\n<\/ol>\n\n<p>The connection is immediate. The plugin creates an Application Password named \"iAmAI Connector\" under the admin user and sends it to the iAmAI server.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20the%20plugin%20safe%3F\"><h3>Is the plugin safe?<\/h3><\/dt>\n<dd><p>Yes. The connection uses standard WordPress Application Passwords. You can revoke access at any time from <strong>Users \u2192 Profile \u2192 Application Passwords<\/strong>, or by clicking \"Disconnect\" inside the plugin.<\/p><\/dd>\n<dt id=\"will%20it%20overwrite%20seo%20i%20wrote%20myself%3F\"><h3>Will it overwrite SEO I wrote myself?<\/h3><\/dt>\n<dd><p>No. Before writing any field iAmAI reads its live value. A field that no longer matches what iAmAI last saw is treated as your edit and left alone. You can also mark a single field on a product as \"mine\" from the product screen.<\/p><\/dd>\n<dt id=\"i%20already%20use%20yoast%20%2F%20rank%20math%20%2F%20aioseo.%20do%20i%20get%20duplicate%20tags%3F\"><h3>I already use Yoast \/ Rank Math \/ AIOSEO. Do I get duplicate tags?<\/h3><\/dt>\n<dd><p>No. When a supported SEO plugin is active, iAmAI writes its values into that plugin's own fields and emits no tags of its own.<\/p><\/dd>\n<dt id=\"what%20data%20is%20sent%20to%20iamai%3F\"><h3>What data is sent to iAmAI?<\/h3><\/dt>\n<dd><p>See the dedicated <strong>Third-Party Services<\/strong> section above for the complete list. In short: on connect, the site URL + name, admin username + email, an Application Password (encrypted at rest on the iAmAI side) and the WordPress \/ WooCommerce versions; on page render, cached fetches of FAQ \/ breadcrumb \/ product schema markup; on every visitor pageview, an anonymous analytics pixel (logged-in admins excluded).<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20disconnect%3F\"><h3>What happens when I disconnect?<\/h3><\/dt>\n<dd><ul>\n<li>The plugin deletes the Application Password from WordPress.<\/li>\n<li>The plugin notifies iAmAI; iAmAI stops writing to the site.<\/li>\n<li>Values iAmAI wrote into your posts are restored to what was there before where a previous value was recorded; the fields remain standard postmeta you can edit.<\/li>\n<\/ul><\/dd>\n<dt id=\"what%20happens%20when%20i%20uninstall%20the%20plugin%3F\"><h3>What happens when I uninstall the plugin?<\/h3><\/dt>\n<dd><ul>\n<li>All plugin options, transients and <code>_iamai_*<\/code> post meta are removed, and the Application Passwords the plugin created are revoked.<\/li>\n<li>The Google Search Console verification meta tag persists as standard WordPress data.<\/li>\n<\/ul><\/dd>\n<dt id=\"do%20i%20need%20a%20paid%20iamai%20account%3F\"><h3>Do I need a paid iAmAI account?<\/h3><\/dt>\n<dd><p>Yes, for the plugin to write to your site. Installing, connecting and running the first scan is free. Without an active subscription the plugin reports and does not write.<\/p><\/dd>\n<dt id=\"where%20are%20the%20iamai%20terms%20of%20service%20and%20privacy%20policy%3F\"><h3>Where are the iAmAI Terms of Service and Privacy Policy?<\/h3><\/dt>\n<dd><ul>\n<li>Terms: https:\/\/www.iam-ai.co.il\/terms<\/li>\n<li>Privacy: https:\/\/www.iam-ai.co.il\/privacy<\/li>\n<\/ul><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.9.28<\/h4>\n\n<ul>\n<li>New: an OpenAI Agentic Commerce product feed at \/wp-json\/iamai\/v1\/acp-feed (JSON, 500 items per page, cached 15 minutes). Published, visible, priced products with an image only; iAmAI's meta description as the product description; live price, stock and availability from WooCommerce; enable_checkout is false. Discovery only.<\/li>\n<li>New: WordPress Abilities API. Five abilities under iamai\/ (store-status, product-seo, set-product-seo, monthly-reports, indexnow-submit), administrator-only, exposed as MCP tools on WordPress 7.1+. A write through an ability is recorded as the merchant's own edit, so the automation leaves that field alone afterwards.<\/li>\n<li>Fix: the Reports screen names schema, breadcrumb and FAQ work in Hebrew instead of showing internal keys.<\/li>\n<\/ul>\n\n<h4>1.9.23<\/h4>\n\n<ul>\n<li>New: IndexNow. Every SEO write and every publish pings Bing (and through Bing, ChatGPT's web search) so the engine reads the new title and description, not the old one. Deduped per URL, non-blocking, off on sites that discourage search engines. Google does not take IndexNow and nothing here claims it does.<\/li>\n<li>New: the dashboard shows how many IndexNow submissions went out this month.<\/li>\n<li>New: \u05d3\u05d5\u05d7\u05d5\u05ea. The monthly report is now readable inside wp-admin, every month the store has, with what was applied by type, the keyword verdicts, the AI-mention rate and the site score. A month with no measurement says so instead of showing a zero. Until now the email was the only copy.<\/li>\n<\/ul>\n\n<h4>1.9.21<\/h4>\n\n<ul>\n<li>New: a focus keyphrase for every product and post \u2014 real search terms with measured Hebrew demand, chosen for the product, not its title rewritten. Primary keyphrase first, secondary set after it is applied.<\/li>\n<li>Fix: the product screen could never reach \"optimised\" on a store with no SEO plugin, because it required a keyphrase field that such stores never had. It now asks for a keyphrase only where a keyphrase has a home.<\/li>\n<li>Fix: an approved article appears in the list immediately, without a manual refresh.<\/li>\n<li>Fix: the article approval link opened an address that no longer existed; every actionable article now carries its own signed review link.<\/li>\n<li>Fix: articles that stopped in the quality check are no longer shown to the merchant; they stay in iAmAI's records for review.<\/li>\n<li>Fix: the article's cover image is attached to the article in the same step it is created.<\/li>\n<li>Fix: the monthly report addresses the merchant by their brand name, not their domain.<\/li>\n<li>Change: writes are paced per month by plan, with a weekly rate derived from it \u2014 full catalogue coverage within about three months, no bursts against the host.<\/li>\n<\/ul>\n\n<h4>1.9.17<\/h4>\n\n<p>This release covers everything built since 1.1.7. The plugin stopped being a\nreporting connector and became the part of iAmAI that writes to your site.<\/p>\n\n<ul>\n<li>New: automatic SEO and AEO for WooCommerce. Titles, descriptions, image alt\ntext, FAQ blocks, breadcrumbs and product schema are generated for your\ncatalogue and applied for you.<\/li>\n<li>New: works with no SEO plugin at all. iAmAI stores the meta itself and renders\nit into the page head, so a store with no Yoast still gets proper titles and\ndescriptions.<\/li>\n<li>New: no duplicate tags when you DO run an SEO plugin. Yoast, Rank Math, All in\nOne SEO, SEOPress, Slim SEO and The SEO Framework are detected, and iAmAI feeds\nits values through that plugin instead of emitting a second set of tags.<\/li>\n<li>New: setup wizard. The scan checks where you rank on Google, which shops\ncompete with you, and what ChatGPT, Gemini and Claude know about your brand.<\/li>\n<li>New: product screen shows what iAmAI wrote for that product and what it looked\nlike before, with no extra page load.<\/li>\n<li>New: articles, internal links and problem-aware content sections, each behind\nits own approval.<\/li>\n<li>Change: nothing is written to your site without a live read first. If you edited\na field by hand, iAmAI leaves it alone instead of overwriting you.<\/li>\n<li>Change: every applied change is reversible, and disconnecting restores what was\nthere before.<\/li>\n<li>Fix: keyword and meta fields belonging to an SEO plugin you have removed are no\nlonger read as live values.<\/li>\n<li>Fix: descriptions are cut at a sentence boundary and never mid-word.<\/li>\n<li>i18n: Hebrew and English throughout.<\/li>\n<\/ul>\n\n<h4>1.9.4<\/h4>\n\n<ul>\n<li>New: the setup wizard's scan step now runs the full iAmAI check on your store, not only the local read of your catalogue. It looks up where you rank on Google, finds the shops competing with you on the same searches, and asks ChatGPT, Gemini and Claude what they know about your brand.<\/li>\n<li>New: that scan takes between one and three minutes, and the scan step now shows what is actually happening while it runs. Each line ticks when that stage really finishes on our side \u2014 nothing moves on a timer. The \"\u05dc\u05ea\u05d5\u05e6\u05d0\u05d5\u05ea\" button stays available the whole time.<\/li>\n<li>New: \"\u05de\u05d4 \u05de\u05e6\u05d0\u05e0\u05d5\" shows those results under the three gauges \u2014 your Google positions, the competitors ahead of you, and how often each AI engine mentioned you. A section we could not measure is left out rather than shown as a zero.<\/li>\n<li>Change: this first scan is also your starting point. Everything iAmAI reports later as an improvement is measured against it.<\/li>\n<\/ul>\n\n<h4>1.9.3<\/h4>\n\n<ul>\n<li>Fix: the product panel announced \"\u05d1\u05d5\u05e6\u05e2\u05d4 \u05d0\u05d5\u05e4\u05d8\u05d9\u05de\u05d9\u05d6\u05e6\u05d9\u05d4\" after the plugin was removed and installed again. The panel reads its state from post meta, and uninstall had never cleared any \u2014 so a fresh install on a site that once ran iAmAI claimed work it had not done, with a date from before the removal. Uninstall now clears every iAmAI field from post meta as well.<\/li>\n<li>Fix: a product panel showing \"\u05d0\u05d5\u05e4\u05d8\u05d9\u05de\u05d9\u05d6\u05e6\u05d9\u05d4 \u05d7\u05dc\u05e7\u05d9\u05ea\" for a keyphrase the merchant typed into Yoast, Rank Math or AIOSEO themselves, on a product iAmAI had never touched. The panel still reports the keyphrase \u2014 it is real and it is on the site \u2014 but it no longer counts someone else's work as ours.<\/li>\n<li>UI: the dashboard, activation, articles and settings screens now share the setup wizard's surface \u2014 same card shape, same accent, and the same navy brand header. Finishing setup no longer drops you onto a plain admin page.<\/li>\n<li>Change: the status bar is two separate signals. \"\u05de\u05d7\u05d5\u05d1\u05e8\" says the site and iAmAI can talk; the subscription state says whether anyone is actually working on the store. The old single \"\u05de\u05d7\u05d5\u05d1\u05e8 \u05d5\u05e2\u05d5\u05d1\u05d3\" was shown to stores with no active subscription, where nothing was running.<\/li>\n<li>Change: a store whose connection has broken no longer shows an active subscription beside the error \u2014 while the connection is down nothing is being optimised, whatever the subscription says.<\/li>\n<li>Copy: the activation screen names the annual plan alongside the monthly one.<\/li>\n<\/ul>\n\n<h4>1.9.2<\/h4>\n\n<ul>\n<li>Fix: uninstalling now revokes the Application Passwords the plugin created. Removing the plugin used to leave a working credential behind on the site \u2014 one per reconnect, all still valid.<\/li>\n<li>Fix: the uninstall sweep now removes transients with a dynamic name (per-post AI views, keyword sets, cached status), which the old named deletes could not reach. Multisite included.<\/li>\n<li>Fix: uninstall reported plugin version \"1.1.7\" to the service regardless of the build installed \u2014 the version guard it sat behind could never pass, because WordPress runs uninstall.php without loading the plugin.<\/li>\n<li>UI: the setup wizard is one visual family across all five screens. Welcome, scan and activate open on a navy stage; connect gets a lighter surface of the same shape; findings keeps its gauges and widens to fit them. Previously the flow read as two different products.<\/li>\n<li>UI: the step rail is a five-column grid instead of nine free-floating children, so it can no longer wrap into an unassembled row at narrow widths.<\/li>\n<li>UI: the wizard card is capped and centred rather than stretched to the full admin width, with a clearer type scale and one primary action per screen.<\/li>\n<li>UI: RTL button order on the final step \u2014 the primary action now lands where a Hebrew line ends.<\/li>\n<li>Fix: the \"connect\" screen rendered navy text on a navy panel; its style modifier was defined before the base rule it was meant to override.<\/li>\n<\/ul>\n\n<h4>1.9.1<\/h4>\n\n<ul>\n<li>Change: the dashboard and \"\u05de\u05d4 \u05de\u05e6\u05d1 \u05d4\u05d7\u05e0\u05d5\u05ea\" were the same screen at two lengths and are now merged, with the full catalogue list and filter chips. The old address still works \u2014 it redirects.<\/li>\n<li>New: \u05de\u05d0\u05de\u05e8\u05d9\u05dd. The article pipeline had been writing drafts and quality flags with no way to see either from wp-admin, including the ones waiting on merchant approval. Stopped articles show the reason and the exact quote that tripped it.<\/li>\n<li>New: \u05d4\u05d2\u05d3\u05e8\u05d5\u05ea is now account details, subscription, connections and brand profile, instead of five diagnostics and a disconnect button.<\/li>\n<li>New: per-field edit in the product panel. Editing one of the three SEO fields tells the system to stop overwriting that field and carry on with the rest \u2014 narrower and more honest than the whole-product opt-out it replaces. Withheld on AIOSEO stores, where the guard cannot read the field it would need to protect.<\/li>\n<\/ul>\n\n<h4>1.9.0<\/h4>\n\n<ul>\n<li>UI: complete admin redesign. One design system across every screen \u2014 dashboard, store state, activation, settings, setup and the product panel now share one stylesheet, one header and one connection indicator.<\/li>\n<li>New: setup wizard (welcome &gt; connect &gt; scan &gt; findings &gt; activate) shown once on activation, instead of dropping a new merchant onto an empty dashboard.<\/li>\n<li>New: dashboard shows three half-circle gauges about the WORK \u2014 optimisation coverage, AI readiness, site health \u2014 each listing the named checks it is made of. Deliberately NO Google-ranking gauge: we do the optimisation work, we do not control the ranking.<\/li>\n<li>New: the plugin now behaves differently before and after payment. Subscribers see \"what was fixed\" (with before\/after) and \"what's queued\", and no manual \"fix now\" controls.<\/li>\n<li>New: optional AI-crawler counter \u2014 how many times GPTBot, ClaudeBot, PerplexityBot and Meta AI fetched pages this month, counted on your own site.<\/li>\n<li>New: the product panel shows the full keyword set (primary, secondary, entities), not just the single keyphrase.<\/li>\n<li>Change: coverage now reads Yoast \/ Rank Math \/ AIOSEO fields too, so a store with hand-written SEO is no longer reported as empty.<\/li>\n<li>Change: activation screen no longer renders plan cards or prices; one button opens the pricing page on iam-ai.co.il. Billing logic untouched.<\/li>\n<li>Change: Store ID, account and sync details moved from the front screen to Settings.<\/li>\n<li>Change: the product panel no longer lists missing schema fields (brand, price, rating) as failures \u2014 those are catalogue facts, not defects.<\/li>\n<li>Fix: the free fix always failed with \"store not connected\" on a correctly connected store \u2014 it read an option name (<code>iamai_store_token<\/code>) that nothing ever wrote.<\/li>\n<li>Fix: \"this document did not come from us, try refreshing\" no longer appears when the schema loaded successfully; it now appears only when no Product schema is found on the page.<\/li>\n<li>Fix: the connection indicator never shows a green tick when the status check failed \u2014 an unreachable server gets its own \"could not check\" state.<\/li>\n<\/ul>\n\n<h4>1.1.7<\/h4>\n\n<ul>\n<li>Compatibility: Tested up to WordPress 7.0.<\/li>\n<li>Fix: pixel script now registered via wp_enqueue_script() \/ wp_add_inline_script() instead of direct echo, per WordPress coding standards.<\/li>\n<li>Fix: wp_parse_url() replaces parse_url() in breadcrumb and product-schema injectors.<\/li>\n<li>Fix: wp_json_encode() in JSON-LD and inline-script output now includes JSON_HEX_TAG | JSON_HEX_APOS | JSON_HEX_QUOT flags.<\/li>\n<li>Fix: wp_unslash() added before REQUEST_URI usage in breadcrumb and product-schema injectors.<\/li>\n<li>Fix: missing \/* translators: *\/ comments added for plural-capable i18n strings.<\/li>\n<li>Fix: _n() singular forms now include the %d placeholder for full translator compatibility.<\/li>\n<li>Fix: uninstall.php version references updated to 1.1.7.<\/li>\n<\/ul>\n\n<h4>1.1.6<\/h4>\n\n<ul>\n<li>New: product pages now render og:image + twitter:image (main product image, same source as the Product JSON-LD) plus twitter:card=summary_large_image, og:url, og:type, og:site_name \u2014 so a shared product link shows a cover-image card on WhatsApp\/Facebook\/Twitter. The backend supplies these as a generic <code>meta_tags<\/code> list (single source of truth); the plugin renders them verbatim, so future meta changes need no plugin update. Skipped when an SEO plugin (Yoast\/RankMath\/AIOSEO) is active, which emits its own og:image.<\/li>\n<\/ul>\n\n<h4>1.1.5<\/h4>\n\n<ul>\n<li>Readme: full External Services disclosure section (listing every endpoint the plugin contacts, what data is sent, when, and why), per WordPress.org submission guideline 6\/7.<\/li>\n<li>Readme: stable_tag synchronized to the plugin version (was 1.1.3 while plugin shipped 1.1.4).<\/li>\n<li>Readme: Tested up to bumped to 6.7. Tags reduced to 5 (<code>automation<\/code> dropped as redundant with <code>seo<\/code>+<code>optimization<\/code>).<\/li>\n<li>Security: dropped <code>JSON_UNESCAPED_SLASHES<\/code> from the FAQ, Breadcrumb, and Product schema JSON-LD encoders so <code>&lt;\/script&gt;<\/code> cannot break out of the inline <code>&lt;script type=\"application\/ld+json\"&gt;<\/code> block.<\/li>\n<\/ul>\n\n<h4>1.1.4<\/h4>\n\n<ul>\n<li>New: deactivation webhook \u2014 fires a <code>plugin_event<\/code> POST to the iAmAI backend so the dashboard can show \"deactivated\" immediately. Sibling to the existing uninstall webhook. Best-effort with a 5s timeout; deactivation never fails because of an HTTP error.<\/li>\n<\/ul>\n\n<h4>1.1.3<\/h4>\n\n<ul>\n<li>Layout: force RTL anchoring on the header (\"iAmAI Connector\" + logo + sub now cluster on the right edge instead of centering \u2014 fixes inheritance break when a WP-admin parent forces dir=\"ltr\").<\/li>\n<li>Visual: replaced the stylised stroke-only \"globe\" mark with the official WordPress logo (Simple Icons, MIT) rendered in canonical brand blue (#21759B), sized to match the iAmAI icon (30px). The \"Connected\" card's WP\u2194iAmAI viz now reads as the real brand instead of a generic icon.<\/li>\n<\/ul>\n\n<h4>1.1.2<\/h4>\n\n<ul>\n<li>Layout: unified right-aligned (RTL-natural) text alignment across both connection states. The disconnected hero CTA no longer center-aligns, matching the connected state's data cards. WordPress\u2194iAmAI viz and first-connect modal stay centered as graphics.<\/li>\n<li>New: dashboard CTA is now context-aware. When the server reports the store no longer exists (HTTP 401\/403\/404 from \/status), the \"\u05e4\u05ea\u05d7\u05d5 \u05d3\u05e9\u05d1\u05d5\u05e8\u05d3\" button changes to \"\u05d4\u05e9\u05dc\u05d9\u05de\u05d5 \u05d4\u05e8\u05e9\u05de\u05d4 \u05d1-iAmAI\" and routes to \/v3\/start\/ instead of a broken dashboard URL. Transient failures (5xx, network) keep the normal dashboard CTA.<\/li>\n<li>Internal: fetch_status() now exposes the HTTP status of the underlying API call so the UI can distinguish broken-connection errors from transient ones.<\/li>\n<\/ul>\n\n<h4>1.1.1<\/h4>\n\n<ul>\n<li>Fix: \"\u05d4\u05de\u05e2\u05e8\u05db\u05ea \u05d4\u05d5\u05e4\u05e2\u05dc\u05d4 \u05d1\u05d4\u05e6\u05dc\u05d7\u05d4\" popup was stuck visible after first connect \u2014 the modal CSS used <code>display: flex<\/code> at higher specificity than the browser's <code>[hidden] { display: none }<\/code> UA rule, so the <code>hidden<\/code> attribute had no visible effect. Added an explicit <code>.iamai-modal[hidden] { display: none }<\/code> override and a defensive <code>modal.hidden = true<\/code> right before the reload.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>New: Connection Center admin UI \u2014 clean Stripe-Connect-style layout with status strip, 4 cards (connection, sync status, what's happening, help) and a small disconnect.<\/li>\n<li>New: One-shot \"\u05d4\u05de\u05e2\u05e8\u05db\u05ea \u05d4\u05d5\u05e4\u05e2\u05dc\u05d4 \u05d1\u05d4\u05e6\u05dc\u05d7\u05d4\" popup on first connect, reminding merchants to return to the iAmAI tab.<\/li>\n<li>New: Live status panel \u2014 products count, last-sync time, pending recommendations \u2014 fetched from iAmAI server with a 60s cache + manual refresh button.<\/li>\n<li>Visual: removed marketing bullets, large floating robot, and gradient text. Added a compact WordPress\u2194iAmAI connection visualization on the connected card.<\/li>\n<li>CSS: rewrote with scoped specificity (<code>.iamai-connection-center<\/code>) \u2014 zero !important rules, cleaner overrides over WP admin defaults.<\/li>\n<li>Internal: status fetch wrapper (IAmAI_Connect::fetch_status) with transient cache; new iamai_refresh_status AJAX endpoint.<\/li>\n<\/ul>\n\n<h4>1.0.3 \u2013 1.0.9<\/h4>\n\n<ul>\n<li>Plugin namespace <code>\/wp-json\/iamai\/v1\/seo-fields<\/code> (meta_title \/ meta_description \/ focus_keyword), with cache purge for LiteSpeed\/WP Rocket\/W3TC\/Super Cache\/Hummingbird (1.0.9)<\/li>\n<li>Native title + OG + Twitter override across Yoast \/ RankMath \/ AIOSEO (1.0.9)<\/li>\n<li><code>\/wp-json\/iamai\/v1\/gsc-verification<\/code> REST + auto-injected <code>&lt;meta name=\"google-site-verification\"&gt;<\/code> (1.0.8)<\/li>\n<li>Product Schema.org JSON-LD on WooCommerce product pages (1.0.7)<\/li>\n<li>Breadcrumb JSON-LD injector per path (1.0.6)<\/li>\n<li>Async pixel injector with WooCommerce loop add-to-cart enrichment (1.0.5)<\/li>\n<li>FAQ JSON-LD injector with 1h transient cache (1.0.3)<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>Fix: \"\u05e4\u05ea\u05d7 \u05d3\u05e9\u05d1\u05d5\u05e8\u05d3\" link now correctly carries store_id + token query params (was building incorrectly in 1.0.1)<\/li>\n<li>Defensive: falls back gracefully if store_id or api_token are missing from options<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Dashboard magic-link: \"\u05e4\u05ea\u05d7 \u05d3\u05e9\u05d1\u05d5\u05e8\u05d3\" now opens iAmAI dashboard scoped to this store<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release<\/li>\n<li>Connect\/disconnect flow via Application Passwords<\/li>\n<li>Hebrew + English support<\/li>\n<\/ul>","raw_excerpt":"Automatic on-page SEO and AI-readiness for WooCommerce stores, in Hebrew. Connects your store to the iAmAI service, which writes and applies the work  &hellip;","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/333896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=333896"}],"author":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/15iamai"}],"wp:attachment":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=333896"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=333896"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=333896"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=333896"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=333896"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=333896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}