Title: iAmAI Connector
Author: iAmAI
Published: 2026년 7월 5일
Last modified: 2026년 9월 17일
---
플러그인 검색
# iAmAI Connector
작성자: [iAmAI](https://profiles.wordpress.org/15iamai/)
[다운로드](https://downloads.wordpress.org/plugin/iamai-connector.1.9.32.zip)
* [세부사항](https://ko.wordpress.org/plugins/iamai-connector/#description)
* [평가](https://ko.wordpress.org/plugins/iamai-connector/#reviews)
* [설치](https://ko.wordpress.org/plugins/iamai-connector/#installation)
* [개발](https://ko.wordpress.org/plugins/iamai-connector/#developers)
[지원](https://wordpress.org/support/plugin/iamai-connector/)
## 설명
iAmAI Connector links your WordPress / WooCommerce store to the iAmAI service (https://
www.iam-ai.co.il) — 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.
**This plugin requires a paid iAmAI subscription.** 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/#price
**What the plugin does:**
* Writes a meta title, meta description and focus keyphrase for every product,
page and post — real search terms with measured Hebrew demand, not the product
title rewritten.
* Image alt text, FAQ blocks, breadcrumbs and Product schema (JSON-LD) for your
catalogue.
* Product page depth: an answer-first summary, a specification table, who it’s
for / less suitable for, a comparison with similar products from the same store
and visible questions & answers — every sentence grounded in the product’s own
data, approved by the store before it shows. The Product schema is completed
with the product’s visible attributes, weight and dimensions.
* Works with NO SEO plugin installed: iAmAI stores the fields itself and renders
them into the page head.
* 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.
* 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.
* Product screen shows what iAmAI wrote for that product and what it looked like
before, without an extra page load.
* Manual-edit guard: every write is preceded by a live read of the field. If you
edited it by hand, iAmAI leaves it alone.
* Monthly Hebrew articles for your blog, each waiting for your approval before
it is published.
* Monthly progress report by email, and a Reports screen inside wp-admin with every
month’s report and history.
* IndexNow: every title or description iAmAI writes, and every product, post or
page you publish, is pushed to Bing the moment it changes — and through Bing’s
index to ChatGPT’s web search. (Google does not take IndexNow; this does not
affect Google.)
* Reversible: every change records its previous value; disconnecting restores what
was there before.
* Product feed for AI shopping (OpenAI Agentic Commerce format): the catalogue
is served at /wp-json/iamai/v1/acp-feed — 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.
* Google Merchant Center feed: the same catalogue as an RSS 2.0 product feed at/
iamai-gmc-feed.xml (off by default; switch it on under Settings › AI search channels
and paste the URL into Merchant Center as a scheduled fetch). One item per simple
product and per variation (grouped by item_group_id), live price, sale price
and dates, availability, brand, GTIN/MPN, category path, gallery images, specifications
from visible attributes, colour/size/material/gender/age group, flat or free
shipping for the store’s country. Titles and descriptions iAmAI wrote are declared
as AI-generated (structured_title / structured_description), next to your own
text. Google fetches the feed from your site; the plugin sends nothing.
* WordPress 7.x Abilities API: iAmAI’s capabilities (store status, read/write a
product’s SEO fields, monthly reports, IndexNow, snapshot and review-request
status) 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.
* Snapshot & restore: a versioned copy of every product, post and page (title,
body, excerpt, slug, featured image and its alt text, and every SEO-plugin, page-
builder and iAmAI field) is taken when you connect, weekly after that, and before
each write. The שחזור screen compares any item with its copy and restores it —
SEO fields only or everything — or restores the whole site. Items you edited
after the copy are skipped unless you say otherwise. The copies survive uninstall
by default.
* Post-purchase review requests (off by default): a few days after a WooCommerce
order is completed, the customer gets one email from your own site listing up
to three products they bought, each with a button to the review form with their
name and email already filled in, asking for one concrete sentence about how
they used the product — the descriptive text AI shopping engines and Google’s
review snippets read. At most one email per customer per 30 days, an optional
single reminder, an unsubscribe link in every email, never sent to someone who
already reviewed. Ratings feed the Product schema’s aggregateRating automatically.
**How it works:**
1. Install and activate the plugin.
2. 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.
3. The wizard runs the first scan and shows what it found.
4. 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.
The connection is built on standard WordPress Application Passwords (available since
WP 5.6). You can revoke access at any time from **Users Profile Application Passwords**,
or by clicking “Disconnect” inside the plugin’s settings page.
#### עברית
iAmAI Connector מחבר את חנות ה-WordPress / WooCommerce שלכם לשירות iAmAI, שכותב
ומחיל עבורכם את עבודת ה-SEO ואת ההתאמה לכלי AI, מוצר אחרי מוצר.
**התוסף דורש מנוי iAmAI בתשלום.** ההתקנה והסריקה הראשונה חינם; הכתיבה לאתר מתחילה
עם מנוי פעיל.
**מה התוסף עושה:**
* כותב כותרת SEO, תיאור מטא וביטוי מפתח לכל מוצר, עמוד ופוסט. ביטויים אמיתיים עם
ביקוש נמדד בעברית, לא הכותרת של המוצר בניסוח אחר.
* טקסט חלופי לתמונות, בלוקי שאלות ותשובות, פירורי לחם וסכמת מוצר (JSON-LD).
* העמקת עמוד מוצר: תקציר שעונה קודם, טבלת מפרט, למי זה מתאים / למי פחות, השוואה
למוצרים דומים מאותה חנות ושאלות ותשובות גלויות. כל משפט מבוסס על הנתונים של המוצר
עצמו, ומאושר על ידי החנות לפני שהוא מוצג. סכמת המוצר מושלמת עם המאפיינים הגלויים,
המשקל והמידות של המוצר.
* עובד גם בלי שום תוסף SEO: iAmAI שומר את השדות בעצמו ומציג אותם ב-head של העמוד.
* בלי תגיות כפולות כשיש תוסף SEO: Yoast, Rank Math, All in One SEO, SEOPress, Slim
SEO ו-The SEO Framework מזוהים והערכים נכתבים לשדות של התוסף עצמו.
* אשף התקנה עם סריקה אמיתית: איפה אתם בגוגל, מי מתחרה בכם על אותם חיפושים, ומה
ChatGPT, Gemini ו-Claude יודעים על המותג שלכם.
* מסך המוצר מציג מה iAmAI כתב ומה היה שם לפני, בלי טעינה נוספת.
* שומר עריכות ידניות: כל כתיבה מתחילה בקריאה חיה של השדה. אם ערכתם אותו ידנית,
המערכת לא נוגעת בו.
* מאמרים חודשיים בעברית לבלוג, כל אחד ממתין לאישורכם לפני פרסום.
* דוח התקדמות חודשי במייל, ומסך “דוחות” בתוך wp-admin עם כל הדוחות וההיסטוריה.
* IndexNow: כל כותרת או תיאור שהמערכת כותבת, וכל מוצר, פוסט או עמוד שאתם מפרסמים,
נשלחים ל-Bing ברגע השינוי, ודרך האינדקס של Bing לחיפוש של ChatGPT. (גוגל לא משתמשת
ב-IndexNow; זה לא משפיע על גוגל.)
* הפיך: כל שינוי שומר את הערך הקודם, וניתוק מחזיר את מה שהיה.
* פיד מוצרים לקניות ב-AI (פורמט Agentic Commerce של OpenAI): הקטלוג מוגש ב-/wp-
json/iamai/v1/acp-feed, רק מוצרים מפורסמים וגלויים עם מחיר, עם התיאור הקריא ל-
AI של iAmAI ומחיר ומלאי חיים. גילוי בלבד, בלי תשלום מחוץ לאתר. מוכן להגשה ביום
שתוכנית הסוחרים נפתחת בישראל.
* פיד ל-Google Merchant Center: אותו קטלוג כפיד מוצרים RSS 2.0 בכתובת /iamai-gmc-
feed.xml (כבוי כברירת מחדל; מפעילים בהגדרות › ערוצי חיפוש AI ומדביקים את הכתובת
ב-Merchant Center כ-URL מתוזמן). פריט לכל מוצר פשוט ולכל וריאציה (מקובצות לפי
item_group_id), מחיר חי, מחיר מבצע ותאריכים, זמינות, מותג, GTIN/MPN, נתיב קטגוריה,
תמונות גלריה, מפרט מהמאפיינים הגלויים, צבע/מידה/חומר/מגדר/קבוצת גיל, ומשלוח קבוע
או חינם למדינת החנות. כותרת ותיאור שהמערכת כתבה מסומנים לגוגל כתוכן AI (structured_title/
structured_description), לצד הטקסט שלכם. גוגל מושכת את הפיד מהאתר שלכם; התוסף
לא שולח כלום.
* Abilities API של וורדפרס 7: היכולות של iAmAI (מצב החנות, קריאה וכתיבה של שדות
SEO לפריט, הדוחות החודשיים, IndexNow, מצב הגיבויים ובקשות הביקורת) רשומות כיכולות,
כך שסוכן AI משלכם יכול לגלות ולהפעיל אותן דרך ה-MCP של האתר. דורש מנהל; לא פעיל
בגרסאות ישנות.
* גיבוי ושחזור: עותק מגורסה של כל מוצר, פוסט ועמוד (כותרת, גוף, תקציר, כתובת, תמונה
ראשית והטקסט החלופי שלה, וכל שדה של תוסף SEO, בונה עמודים ו-iAmAI) נלקח בחיבור,
כל שבוע אחרי, ולפני כל כתיבה. מסך “שחזור” משווה כל פריט לעותק שלו ומחזיר אותו,
שדות SEO בלבד או הכל, או מחזיר את כל האתר. פריטים שערכתם אחרי העותק מדולגים אלא
אם תבקשו אחרת. העותקים נשארים גם אחרי הסרת התוסף, כברירת מחדל.
* בקשת ביקורת אחרי רכישה (כבוי כברירת מחדל): כמה ימים אחרי שהזמנת WooCommerce הושלמה,
הלקוח מקבל מייל אחד מהאתר שלכם עם עד שלושה מוצרים שקנה, לכל אחד כפתור לטופס הביקורת
עם השם והמייל כבר מלאים, ובקשה למשפט אחד קונקרטי על איך השתמש במוצר — הטקסט התיאורי
שמנועי הקניות ב-AI וקטעי הביקורת של גוגל קוראים. לכל היותר מייל אחד ללקוח ב-30
יום, תזכורת אחת אופציונלית, קישור הסרה בכל מייל, ולא נשלח למי שכבר כתב ביקורת.
הדירוגים נכנסים אוטומטית ל-aggregateRating בסכמת המוצר.
**איך זה עובד:**
1. מתקינים ומפעילים את התוסף.
2. אשף ההתקנה מחבר את האתר: התוסף יוצר Application Password ושולח ל-iAmAI.
3. האשף מריץ סריקה ראשונה ומציג את הממצאים.
4. מפעילים מנוי. מכאן המערכת מייצרת ומחילה שיפורים בקצב חודשי מדוד, ואתם עוקבים אחרי
כל שינוי במסך iAmAI בתוך wp-admin.
החיבור משתמש ב-Application Passwords הסטנדרטיים של WordPress; ניתן לבטל את הגישה
בכל רגע מ-Users Profile Application Passwords או דרך “ניתוק” בהגדרות התוסף.
### Third-Party Services
This plugin connects your WordPress site to the iAmAI service (an external third-
party SaaS at **https://www.iam-ai.co.il**) and exchanges data with it. The plugin
will not function without an iAmAI account.
The following calls are made to the iAmAI backend:
**1. On Connect (one-time, from the setup wizard)**
* Endpoint: `POST https://www.iam-ai.co.il/api/integrations/wordpress?action=install`
* 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.
* Purpose: provision your store inside iAmAI and let iAmAI write SEO updates back
via the REST API.
**2. During the setup wizard scan (one-time, admin-initiated)**
* Endpoints: `POST https://www.iam-ai.co.il/api/scan?action=wizard-start`, `GET
https://www.iam-ai.co.il/api/scan?action=status&id=…`, `POST https://www.iam-
ai.co.il/api/integrations/wordpress?action=claim_ticket`
* Data sent: store ID, API token, and the site URL.
* Purpose: run the first scan (Google positions, competitors, AI-engine mentions)
and hand the admin over to their iAmAI account without a second login.
**3. On Disconnect / Deactivate / Uninstall (one-time per event)**
* Endpoint: `POST https://www.iam-ai.co.il/api/integrations/wordpress` (action `
disconnect` or `plugin_event`).
* Data sent: store ID, API token, event type (`disconnect`, `deactivated`, or `
uninstalled`), site URL, plugin version.
* Purpose: let iAmAI reflect your status immediately instead of waiting for the
next health check.
**4. On admin visits to the plugin’s screens (cached, admin only)**
* Endpoints: `GET https://www.iam-ai.co.il/api/integrations/wordpress?action=status
|dashboard|articles|reports|product_keywords&store_id=…&token=…`, `POST …?action
=brand_update`, `GET https://www.iam-ai.co.il/llms.txt?store=…`
* Data sent: store ID and API token; for `brand_update`, the brand profile fields
the admin edited on the settings screen; for `product_keywords`, the post ID
being viewed.
* 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.
**5. On page render of singular posts/pages (server-side, cached 1 hour)**
* Endpoints: `GET https://www.iam-ai.co.il/api/seo/faq-public?store_id=…`, `GET
https://www.iam-ai.co.il/api/seo/breadcrumb-public?store_id=…&path=…`, `GET https://
www.iam-ai.co.il/api/seo/sections-public?store_id=…&post_id=…`
* Data sent: store ID, the requested URL path / post ID.
* Purpose: fetch the applied FAQ, breadcrumb and content-section entries and inject`
FAQPage` / `BreadcrumbList` Schema.org JSON-LD and the approved content blocks.
**6. On every WooCommerce product page (server-side, cached 1 hour per product)**
* Endpoint: `GET https://www.iam-ai.co.il/api/seo/product-schema-public?store_id
=…&path=…`
* Data sent: store ID and the product URL path.
* Purpose: fetch and inject `Product` Schema.org JSON-LD and social preview meta
tags.
**7. On every storefront page view (visitor side, async, non-blocking)**
* Script loaded: `https://www.iam-ai.co.il/pixel.js?sid=…&platform=wordpress`
* Beacon endpoint: `POST https://www.iam-ai.co.il/api/v1/p-signal`
* Data sent: page URL, referrer, anonymous visit identifier, and basic interaction
events (page views, add-to-cart on WooCommerce loop buttons).
* The pixel **does not** load for logged-in administrators (`manage_options` capability),
and it does not load on admin, login, or AJAX pages.
* Purpose: analytics that iAmAI uses to score which optimizations are working.
**8. IndexNow (server-side, after a write or a publish)**
* Endpoint: `POST https://api.indexnow.org/indexnow` (an open protocol operated
by Microsoft Bing, shared with Yandex, Seznam and Naver; terms: https://www.indexnow.
org/)
* 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 `https://
/.txt`.
* 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.
**9. Product feeds served FROM your site (no outbound call)**
* URLs: `https:///iamai-gmc-feed.xml` (Google Merchant Center, RSS 2.0)
and `https:///wp-json/iamai/v1/acp-feed` (OpenAI Agentic Commerce,
JSON). The Merchant Center feed is off by default.
* Data served: the public catalogue as the storefront already shows it — published,
visible, priced products: name, description, URL, images, price, availability,
brand, GTIN/SKU, category, visible attributes, shipping rate, and the iAmAI-written
title/description marked as AI-generated.
* The plugin does **not** send this data anywhere. Google fetches the feed only
after you paste its URL into your own Merchant Center account (Products › Add
products › Add feed › Scheduled fetch); the fetch is governed by Google’s terms(
https://support.google.com/merchants/answer/160173). Turn the switch off and
the URL answers 404.
**Backend site writes**
iAmAI’s backend uses the WordPress REST API (authenticated with the Application
Password created at connect) to write back into your site:
* `POST /wp-json/iamai/v1/seo-fields` — 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.
* `POST /wp-json/iamai/v1/gsc-verification` — sets a Google Search Console verification
token that the plugin injects into `` via the standard `google-site-verification`
meta tag.
* `POST /wp-json/iamai/v1/snapshot` (and `GET …/snapshot/runs`, `…/snapshot/run`,`…/
snapshot/items`, `…/snapshot/diff`, `…/snapshot/export`, `POST …/snapshot/restore`,`…/
snapshot/restore-all`) — takes a versioned copy of the items iAmAI is about to
write, and lets the backend read, export or restore those copies on your behalf.
Copies are stored in two tables on your own site (`iamai_snapshots`, `iamai_snapshot_runs`);
nothing is uploaded unless the export endpoint is called.
* Standard `wp/v2` and `wc/v3` endpoints — image alt text, internal links appended
to content, and article drafts (articles are created as drafts and published
only after you approve them).
**Post-purchase review requests (no third-party service involved)**
The review-request emails are sent by your own WordPress installation (`wp_mail`,
through WooCommerce’s email template when WooCommerce is active) to your own customers,
using the billing email on the order. Nothing about the order, the customer or the
email is sent to iAmAI or to any other external service. The feature is off until…
## 스크린샷
[⌊The iAmAI dashboard inside wp-admin: three gauges about the work — optimisation
coverage, AI readiness and site health — each listing the named checks it is made
of.⌉⌊The iAmAI dashboard inside wp-admin: three gauges about the work — optimisation
coverage, AI readiness and site health — each listing the named checks it is made
of.⌉[
The iAmAI dashboard inside wp-admin: three gauges about the work — optimisation
coverage, AI readiness and site health — each listing the named checks it is made
of.
[⌊"What was fixed": every product with its SEO title and meta description before
and after, as applied to the live site.⌉⌊"What was fixed": every product with its
SEO title and meta description before and after, as applied to the live site.⌉[
“What was fixed”: every product with its SEO title and meta description before and
after, as applied to the live site.
[⌊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.⌉⌊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.⌉[
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.
[⌊Articles: what is being written, what waits for your approval, what was published.⌉⌊
Articles: what is being written, what waits for your approval, what was published
.⌉[
Articles: what is being written, what waits for your approval, what was published.
[⌊AI crawlers that visited this month (GPTBot, ClaudeBot, PerplexityBot, Meta AI),
counted on your own site, plus the running totals.⌉⌊AI crawlers that visited this
month (GPTBot, ClaudeBot, PerplexityBot, Meta AI), counted on your own site, plus
the running totals.⌉[
AI crawlers that visited this month (GPTBot, ClaudeBot, PerplexityBot, Meta AI),
counted on your own site, plus the running totals.
## 설치
1. Install from the WordPress.org plugin directory, or upload the ZIP via **Plugins
Add New Upload Plugin**.
2. Activate the plugin. The setup wizard opens.
3. Follow the wizard: connect, scan, review the findings, activate a subscription.
The connection is immediate. The plugin creates an Application Password named “iAmAI
Connector” under the admin user and sends it to the iAmAI server.
## FAQ
### Is the plugin safe?
Yes. The connection uses standard WordPress Application Passwords. You can revoke
access at any time from **Users Profile Application Passwords**, or by clicking“
Disconnect” inside the plugin.
### Will it overwrite SEO I wrote myself?
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.
### I already use Yoast / Rank Math / AIOSEO. Do I get duplicate tags?
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.
### What data is sent to iAmAI?
See the dedicated **Third-Party Services** 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).
### Can I undo what iAmAI wrote?
Yes. The plugin keeps a versioned copy of every product, post and page: the first
copy is taken when you connect (before iAmAI writes anything), a full copy runs
weekly, and iAmAI’s backend takes a copy of an item right before it writes to it.
Open **iAmAI שחזור**, find the item, click “השוואה” to see the copy next to the
live values, and restore either the SEO fields only (title, description, keyphrase,
image alt text — for every SEO plugin) or everything (body, excerpt, slug and all
captured fields). A whole-site restore is on the same screen. An item you edited
yourself after the copy was taken is skipped unless you tick “also items edited
after the backup”. The last three versions per item, everything from the last 90
days and the very first copy are kept; the tables survive uninstall unless you untick
that on the screen.
### What happens when I disconnect?
* The plugin deletes the Application Password from WordPress.
* The plugin notifies iAmAI; iAmAI stops writing to the site.
* 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.
### What happens when I uninstall the plugin?
* All plugin options, transients and `_iamai_*` post meta are removed, and the
Application Passwords the plugin created are revoked.
* The snapshot tables (`iamai_snapshots`, `iamai_snapshot_runs`) are kept, so the
backup outlives the plugin — unless you unticked “keep snapshots on uninstall”
on the שחזור screen, in which case they are dropped.
* The Google Search Console verification meta tag persists as standard WordPress
data.
### Do I need a paid iAmAI account?
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.
### Where are the iAmAI Terms of Service and Privacy Policy?
* Terms: https://www.iam-ai.co.il/terms
* Privacy: https://www.iam-ai.co.il/privacy
## 후기
이 플러그인에 대한 평가가 없습니다.
## 기여자 & 개발자
“iAmAI Connector”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에
기여하였습니다.
기여자
* [ iAmAI ](https://profiles.wordpress.org/15iamai/)
[자국어로 “iAmAI Connector”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/iamai-connector)
### 개발에 관심이 있으십니까?
[코드 탐색하기](https://plugins.trac.wordpress.org/browser/iamai-connector/)는,
[SVN 저장소](https://plugins.svn.wordpress.org/iamai-connector/)를 확인하시거나,
[개발 기록](https://plugins.trac.wordpress.org/log/iamai-connector/)을 [RSS](https://plugins.trac.wordpress.org/log/iamai-connector/?limit=100&mode=stop_on_copy&format=rss)
로 구독하세요.
## 변경이력
#### 1.9.32
* Fix: the AI-crawler check reported a block that did not exist. WooCommerce writes`
Disallow: /*?add-to-cart=` into every store’s robots.txt, and the matcher tested
only the part of the pattern before the `*` — which is `/`, so every path matched
and every engine came back “blocked”. Measured on a store whose robots.txt explicitly
allows all of them: the screen named eight blocked engines and sent the merchant
to re-configure a firewall that was fine. Both halves of the check, in the plugin
and on the server, now apply the documented glob rules and are held to the same
behaviour by tests.
* New screen: מנועי AI. The crawler-access verdict, the outside check, the robots
declaration, Bing verification, the plain-text alternate and the filtered-url
control moved off the settings page onto a screen of their own. They are a diagnosis,
not settings, and the settings page had grown past the point where anything could
be found on it.
* Fix: a scheduled monthly article that failed its quality gates emailed the merchant“
we received your change request and it needs a manual review” — about a request
they never made. The executor passes every row it drains through the revision
path, and the email was gated on that path rather than on whether a customer
had actually asked for a change. It is now gated on the request itself; the article
is still parked and flagged either way.
* Articles screen: a scheduled slot no longer reads “ללא כותרת”. It has no topic
yet by design — the topic is chosen at writing time so it can avoid what was
already written this month — and the row now says it is waiting its turn.
* Reports: the month in progress now shows the AI-mention rate from the latest
weekly scan instead of “לא נמדד” — technically true of a monthly review that
does not exist yet, and read by the merchant as “nobody is measuring this”.
#### 1.9.31
* New: a plain-text version of every page, at its own url and announced in the
head. AI crawlers do not run JavaScript, so a theme that renders the price, the
stock state or the description on the client serves them an empty shell. The
text version carries the live price, availability, SKU, specification list, description,
customer reviews and the store’s questions. It is served to anyone who asks for
it and states nothing the page itself does not — serving crawlers different content
at the same url is cloaking, and this deliberately is not that.
* New: filtered-navigation control. Five filters with four values each is 1,024
urls per category, every one of them a near-duplicate competing with the category
page and eating the crawl budget the products need. Filtered, sorted and price-
banded urls now carry noindex plus a canonical to the clean category; a single
filter on an attribute the merchant marks as worth indexing stays indexable.
When Yoast or Rank Math is installed the plugin changes THEIR canonical rather
than printing a second one.
* New: customer reviews on the page, not behind a tab. Up to three real approved
reviews render server-side under the product description with the verified-purchase
mark, and the reviews themselves — not only the average — go into the product
schema. Nothing is summarised, translated or selected for positivity: newest
first, exactly as customers wrote them.
* New: “what AI says about you”. When an answer engine states something about the
business that contradicts the identity sheet — a wrong founding year or city,
a wrong phone, a claim that the store closed — the dashboard shows it with the
sentence it came from. Silence is never reported as a contradiction.
* New: the questions the store is absent from. The visibility scan now records,
per buyer question, which names the engines recommended instead, so the screen
shows work to do rather than one percentage.
* New: an English-language brand kit for Hebrew stores, alongside the Hebrew one.
An audit of 950 Israeli companies found that publishing only in Hebrew is itself
a citation penalty; the same facts, the same gates, in the language the engines
have a corpus in.
* Product screen: each product now shows which blocks are actually live on its
page — depth block, problem-aware block, reviews, product schema, the text version—
read from what the site is currently serving.
* Content: Hebrew product copy is now checked for the words a buyer actually types.
A professional term left in English where Hebrew has a common one (“side-by-side”
instead of “מקרר אמריקאי”), or a sentence that mixes scripts, is rejected and
rewritten — mixed-script sentences are handled badly by the retrieval layer that
decides whether a model sees the page at all.
#### 1.9.30
* New: AI crawler access. A new panel (הגדרות › גישת מנועי AI לאתר) shows, engine
by engine, whether ChatGPT, Perplexity, Claude, Meta AI, Bing and Google are
allowed to fetch the site, reads the site’s real robots.txt rather than assuming,
and warns when WordPress itself is set to discourage search engines. iAmAI also
fetches the store from outside once a week as each crawler and reports what it
actually received, which is the only way to see a Cloudflare or firewall block:
that request never reaches WordPress. A store whose crawlers are turned away
gets a warning at the top of the dashboard, because nothing else the plugin does
can work until it is fixed. Explicit Allow lines can be published to robots.txt;
the separate consent switch for AI training crawlers is off unless the merchant
turns it on.
* New: Bing Webmaster Tools verification (meta tag and a virtual /BingSiteAuth.
xml, no file access needed). ChatGPT’s web answers are discovered through Bing’s
index, and this is the only place a merchant can see whether the store is in
it. The screen says first that a verified Google Search Console property can
simply be imported.
* Fix: the monthly report screen (דוחות) worked for nobody. It has been asking
the server for an action that was never implemented, so every merchant saw “לא
הצלחנו לקרוא את הדוחות”. The endpoint now returns each month’s applied changes
by type, the score at the start and end of the month, the keyword verdicts and
the AI-mention rate — plus the month in progress, so a new store sees what has
been written so far instead of an empty screen.
* Brand identity: every profile field now says where to find the link (which button
in Google Business Profile, the page URL and not a post, the channel and not
a video), and the missing-links box reads as a numbered task list instead of
a list of complaints.
* Fix: the product feed at /iamai-gmc-feed.xml was served empty. The pretty URL
was handled before WooCommerce registers the product post type, so the feed’s
own query matched nothing while the REST route returned every product. Merchants
who gave Google Merchant Center the pretty URL were submitting an empty feed.
* Dashboard: the screen now opens with the latest items and keeps the rest behind
a “show the earlier items” toggle. On a store with dozens of optimized items
the page opened thousands of pixels long and pushed everything else below the
fold. Nothing was removed — the full list is one click away.
#### 1.9.29
* New: brand identity. One place (הגדרות › זהות המותג) for the store’s legal name,
founding year, address, phone, logo and its profiles on Google Business Profile,
Facebook, Instagram, YouTube, TikTok, LinkedIn and Wikidata; the plugin emits
one Organization node from it — the same node the product and feed data point
at — so search engines and AI assistants see one consistent business rather than
several. Missing profiles are listed with one line each on why they matter. Nothing
is invented and every URL is checked against the network it claims to be.
* New: product page depth. An applied pdp_depth_block — answer-first summary, specification
table, who it’s for / less suitable for, a comparison with similar products from
the same store and visible questions & answers — is appended under the product
description, every sentence grounded in the product’s own data and approved by
the store before it shows. Structural HTML only (headings, table, lists, details/
summary, links), a few lines of CSS printed only where the block renders, RTL-
safe; skipped when the merchant pasted the block into the description themselves.
Applying a field clears the block’s cache so a fresh apply shows at once. The
product schema now also lists the product’s visible attributes (additionalProperty,
plus color/material/size), weight and dimensions in the store’s units; nothing
is invented. Reports name the type; iamai/product-seo reports pdp_block_applied.
* New: merchant-listing completeness. The product schema is completed at render
time from live WooCommerce data: current price and stock, priceValidUntil, SKU
and GTIN, brand, gallery images, real review ratings, the store’s flat-rate or
free shipping for its home country, and a return policy with a configurable window(
הגדרות › ערוצי חיפוש AI, default 14 days). Nothing is invented; a field the store
cannot answer is left out.
* Performance: the front-end fetches (FAQ, breadcrumbs, product schema, problem-
aware section) no longer block a shopper’s page while a cache refreshes. A stale
value is served and refreshed in the background through WP-Cron; only the very
first request for a page fetches inline, with a two-second cap.
* Fix: the FAQPage structured data is printed only where the questions are visible.
The FAQ is now rendered on the front page (or wherever the new [iamai_faq] shortcode
is placed) as accessible details/summary markup, and the JSON-LD follows it.
It used to be printed invisibly on every post, page and product.
* Security: the store token is sent in a request header, never in the URL. Disconnect
revokes the Application Password of the user it was created for, not of whoever
pressed the button.
* Fix: the analytics pixel now really skips administrators and previews, as the
documentation always claimed.
* Fix: the ACP product feed lists the price the shopper sees (tax rules applied),
never a negative stock count, answers 404 for pages past the end instead of caching
every requested page number, and respects the new on/off switch under הגדרות ›
ערוצי חיפוש AI.
* Fix: an IndexNow submission is marked as sent only after it actually left the
site; a transport failure no longer locks the URL out for twelve hours.
* Fix: one list of SEO plugins for every “is an SEO plugin active” check (SEOPress,
Slim SEO and The SEO Framework were only recognised by half the plugin).
* Fix: applying a title or description also clears our own schema/breadcrumb cache
for that URL, so the new values show at once rather than an hour later.
* New: הגדרות › ערוצי חיפוש AI — a health lamp for the IndexNow key file, the ACP
feed switch and the FAQ shortcode.
* New: a Google Merchant Center product feed at /iamai-gmc-feed.xml (also /wp-json/
iamai/v1/gmc-feed.xml; RSS 2.0 with the g: namespace, 500 products per page,
cached 15 minutes, 404 past the last page). Off by default; the switch, the URL
to copy, a three-step how-to and a health line (items, last generation) live
under הגדרות › ערוצי חיפוש AI. Simple products and every visible variation (item_group_id),
live and sale price with dates, availability, brand, validated GTIN or MPN (identifier_exists
no otherwise), product_type from the category path, up to 10 gallery images,
product_highlight from the short description’s bullets or the approved “best
for” list, product_detail from visible attributes, color/size/material/gender/
age_group when an attribute matches, flat or free shipping for the base country,
is_bundle no. google_product_category only from a merchant mapping (never guessed).
iAmAI’s title and description go in structured_title / structured_description
as trained_algorithmic_media; the merchant’s own stay in title / description.
Uninstall removes the option; a read-only iamai/gmc-feed-status ability reports
enabled, url and items.
* New: גיבוי ושחזור. A versioned copy of every product, post and page — title,
body, excerpt, slug, featured image and alt text, and every SEO-plugin, page-
builder and iAmAI field — taken on connect, weekly, and by the backend before
each write; only stored when something changed. The new שחזור screen shows the
last run, finds an item, compares it with its copy and restores it (SEO fields
only or everything) or restores the whole site; items edited after the copy are
skipped unless forced. REST routes under iamai/v1/snapshot* (take, list, diff,
restore, gzip export) for the backend, and an iamai/snapshot-status ability.
Retention: last 3 versions per item, everything from 90 days, and the first copy
forever. The tables are kept on uninstall by default.
* Fix: signed deltas on the Reports screen read correctly inside Hebrew sentences.
* New: post-purchase review requests (הגדרות › ערוצי חיפוש AI, off by default).
When a WooCommerce order is completed, one WP-Cron event is queued per order
and, N days later (default 7, 2–30), the customer gets one email from the store’s
own WordPress — WooCommerce’s email wrapper when available — listing up to three
products from the order with a “write a review” button that lands on the product’s
review form with name and email pre-filled, and asks for one concrete sentence
about how they used the product (usage-based reviews are what ChatGPT Shopping
ranks on and what earns Google review snippets). Guards: one email per customer
per 30 days, skipped when the customer already reviewed any product in the order,
skipped for opted-out customers; an optional single reminder after 7 more days;
an unsubscribe link in every email (order meta, user meta and a site-wide hashed
list); the order is marked as requested only after wp_mail succeeded. Reviews
written from a request are flagged (_iamai_from_request) so the settings row
can show requests sent this month against reviews received; a test email to the
current administrator; Hebrew by default, English when the site locale or the
brand’s content language is English; iamai/reviews-status ability (read-only).
Nothing leaves the site.
* Cleanup: uninstall removes every transient and scheduled event the plugin creates.
* Fix: the first-run wizard redirect is no longer consumed by a background request
before the administrator sees it; connecting again after an interrupted connect
no longer fails on a leftover application password; disconnecting clears the
deep-scan pointer; a site that moved domain now says so instead of “sync failed”;
disconnecting keeps the subscription attached to the store on the server, so
reconnecting restores it.
* Fix: the AI-crawler counter is buffered per day and folded hourly instead of
rewriting an option on every bot hit; a failed adoption-ticket request is remembered
for two minutes instead of retried on every admin page; the IndexNow key file
answers HEAD requests, trailing slashes and subdirectory installs; the site insight
is primed in the background right after connecting so the first dashboard open
is fast.
#### 1.9.28
* 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.
* 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.
* Fix: the Reports screen names schema, breadcrumb and FAQ work in Hebrew instead
of showing internal keys.
#### 1.9.23
* 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.
* New: the dashboard shows how many IndexNow submissions went out this month.
* New: דוחות. 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.
#### 1.9.21
* New: a focus keyphrase for every product and post — real search terms with measured
Hebrew demand, chosen for the product, not its title rewritten. Primary keyphrase
first, secondary set after it is applied.
* 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.
* Fix: an approved article appears in the list immediately, without a manual refresh.
* Fix: the article approval link opened an address that no longer existed; every
actionable article now carries its own signed review link.
* Fix: articles that stopped in the quality check are no longer shown to the merchant;
they stay in iAmAI’s records for review.
* Fix: the article’s cover image is attached to the article in the same step it
is created.
* Fix: the monthly report addresses the merchant by their brand name, not their
domain.
* Change: writes are paced per month by plan, with a weekly rate derived from it—
full catalogue coverage within about three months, no bursts against the host.
#### 1.9.17
This release covers everything built since 1.1.7. The plugin stopped being a
reporting
connector and became the part of iAmAI that writes to your site.
* New: automatic SEO and AEO for WooCommerce. Titles, descriptions, image alt
text, FAQ blocks, breadcrumbs and product schema are generated for your catalogue
and applied for you.
* New: works with no SEO plugin at all. iAmAI stores the meta itself and renders
it into the page head, so a store with no Yoast still gets proper titles and
descriptions.
* New: no duplicate tags when you DO run an SEO plugin. Yoast, Rank Math, All in
One SEO, SEOPress, Slim SEO and The SEO Framework are detected, and iAmAI feeds
its values through that plugin instead of emitting a second set of tags.
* New: setup wizard. The scan checks where you rank on Google, which shops
compete
with you, and what ChatGPT, Gemini and Claude know about your brand.
* New: product screen shows what iAmAI wrote for that product and what it looked
like before, with no extra page load.
* New: articles, internal links and problem-aware content sections, each behind
its own approval.
* Change: nothing is written to your site without a live read first. If you edited
a field by hand, iAmAI leaves it alone instead of overwriting you.
* Change: every applied change is reversible, and disconnecting restores what was
there before.
* Fix: keyword and meta fields belonging to an SEO plugin you have removed are
no
longer read as live values.
* Fix: descriptions are cut at a sentence boundary and never mid-word.
* i18n: Hebrew and English throughout.
#### 1.9.4
* 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.
* 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 — nothing moves on a timer. The “לתוצאות” button stays available
the whole time.
* New: “מה מצאנו” shows those results under the three gauges — 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.
* Change: this first scan is also your starting point. Everything iAmAI reports
later as an improvement is measured against it.
#### 1.9.3
* Fix: the product panel announced “בוצעה אופטימיזציה” after the plugin was removed
and installed again. The panel reads its state from post meta, and uninstall
had never cleared any — 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.
* Fix: a product panel showing “אופטימיזציה חלקית” 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 — it is real and it is on the
site — but it no longer counts someone else’s work as ours.
* UI: the dashboard, activation, articles and settings screens now share the setup
wizard’s surface — same card shape, same accent, and the same navy brand header.
Finishing setup no longer drops you onto a plain admin page.
* Change: the status bar is two separate signals. “מחובר” says the site and iAmAI
can talk; the subscription state says whether anyone is actually working on the
store. The old single “מחובר ועובד” was shown to stores with no active subscription,
where nothing was running.
* Change: a store whose connection has broken no longer shows an active subscription
beside the error — while the connection is down nothing is being optimised, whatever
the subscription says.
* Copy: the activation screen names the annual plan alongside the monthly one.
#### 1.9.2
* Fix: uninstalling now revokes the Application Passwords the plugin created. Removing
the plugin used to leave a working credential behind on the site — one per reconnect,
all still valid.
* 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.
* Fix: uninstall reported plugin version “1.1.7” to the service regardless of the
build installed — the version guard it sat behind could never pass, because WordPress
runs uninstall.php without loading the plugin.
* 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.
* 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.
* 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.
* UI: RTL button order on the final step — the primary action now lands where a
Hebrew line ends.
* 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.
#### 1.9.1
* Change: the dashboard and “מה מצב החנות” were the same screen at two lengths
and are now merged, with the full catalogue list and filter chips. The old address
still works — it redirects.
* New: מאמרים. 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.
* New: הגדרות is now account details, subscription, connections and brand profile,
instead of five diagnostics and a disconnect button.
* 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 —
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.
#### 1.9.0
* UI: complete admin redesign. One design system across every screen — dashboard,
store state, activation, settings, setup and the product panel now share one
stylesheet, one header and one connection indicator.
* New: setup wizard (welcome > connect > scan > findings > activate) shown once
on activation, instead of dropping a new merchant onto an empty dashboard.
* New: dashboard shows three half-circle gauges about the WORK — optimisation coverage,
AI readiness, site health — 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.
* 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.
* New: optional AI-crawler counter — how many times GPTBot, ClaudeBot, PerplexityBot
and Meta AI fetched pages this month, counted on your own site.
* New: the product panel shows the full keyword set (primary, secondary, entities),
not just the single keyphrase.
* Change: coverage now reads Yoast / Rank Math / AIOSEO fields too, so a store
with hand-written SEO is no longer reported as empty.
* Change: activation screen no longer renders plan cards or prices; one button
opens the pricing page on iam-ai.co.il. Billing logic untouched.
* Change: Store ID, account and sync details moved from the front screen to Settings.
* Change: the product panel no longer lists missing schema fields (brand, price,
rating) as failures — those are catalogue facts, not defects.
* Fix: the free fix always failed with “store not connected” on a correctly connected
store — it read an option name (`iamai_store_token`) that nothing ever wrote.
* 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.
* Fix: the connection indicator never shows a green tick when the status check
failed — an unreachable server gets its own “could not check” state.
#### 1.1.7
* Compatibility: Tested up to WordPress 7.0.
* Fix: pixel script now registered via wp_enqueue_script() / wp_add_inline_script()
instead of direct echo, per WordPress coding standards.
* Fix: wp_parse_url() replaces parse_url() in breadcrumb and product-schema injectors.
* Fix: wp_json_encode() in JSON-LD and inline-script output now includes JSON_HEX_TAG
| JSON_HEX_APOS | JSON_HEX_QUOT flags.
* Fix: wp_unslash() added before REQUEST_URI usage in breadcrumb and product-schema
injectors.
* Fix: missing /* translators: */ comments added for plural-capable i18n strings.
* Fix: _n() singular forms now include the %d placeholder for full translator compatibility.
* Fix: uninstall.php version references updated to 1.1.7.
#### 1.1.6
* 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 — so a shared product link shows a cover-image card on
WhatsApp/Facebook/Twitter. The backend supplies these as a generic `meta_tags`
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.
#### 1.1.5
* 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.
* Readme: stable_tag synchronized to the plugin version (was 1.1.3 while plugin
shipped 1.1.4).
* Readme: Tested up to bumped to 6.7. Tags reduced to 5 (`automation` dropped as
redundant with `seo`+`optimization`).
* Security: dropped `JSON_UNESCAPED_SLASHES` from the FAQ, Breadcrumb, and Product
schema JSON-LD encoders so `` cannot break out of the inline `