iAmAI Connector

Changelog

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 </script> cannot break out of the inline <script type="application/ld+json"> block.

1.1.4

• New: deactivation webhook — fires a plugin_event 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.

1.1.3

• Layout: force RTL anchoring on the header (“iAmAI Connector” + logo + sub now cluster on the right edge instead of centering — fixes inheritance break when a WP-admin parent forces dir=”ltr”).
• 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↔iAmAI viz now reads as the real brand instead of a generic icon.

1.1.2

• 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↔iAmAI viz and first-connect modal stay centered as graphics.
• New: dashboard CTA is now context-aware. When the server reports the store no longer exists (HTTP 401/403/404 from /status), the “פתחו דשבורד” button changes to “השלימו הרשמה ב-iAmAI” and routes to /v3/start/ instead of a broken dashboard URL. Transient failures (5xx, network) keep the normal dashboard CTA.
• Internal: fetch_status() now exposes the HTTP status of the underlying API call so the UI can distinguish broken-connection errors from transient ones.

1.1.1

• Fix: “המערכת הופעלה בהצלחה” popup was stuck visible after first connect — the modal CSS used display: flex at higher specificity than the browser’s [hidden] { display: none } UA rule, so the hidden attribute had no visible effect. Added an explicit .iamai-modal[hidden] { display: none } override and a defensive modal.hidden = true right before the reload.

1.1.0

• New: Connection Center admin UI — clean Stripe-Connect-style layout with status strip, 4 cards (connection, sync status, what’s happening, help) and a small disconnect.
• New: One-shot “המערכת הופעלה בהצלחה” popup on first connect, reminding merchants to return to the iAmAI tab.
• New: Live status panel — products count, last-sync time, pending recommendations — fetched from iAmAI server with a 60s cache + manual refresh button.
• Visual: removed marketing bullets, large floating robot, and gradient text. Added a compact WordPress↔iAmAI connection visualization on the connected card.
• CSS: rewrote with scoped specificity (.iamai-connection-center) — zero …