IAMAI CONNECTOR
iAmAI Connector compatibility with REEID Translate
iAmAI Connector compatibility with REEID Translate is being evaluated from available plugin evidence. Generates and manages a WordPress Application Password for authenticated communication with the iAmAI backend; supports revocation via Users → Profile → Application Passwords and a plugin “Disconnect” action. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for iAmAI Connector.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
iAmAI Connector is documented in the SEO category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How iAmAI Connector compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Generates and manages a WordPress Application Password for authenticated communication with the iAmAI backend; supports revocation via Users → Profile → Application Passwords and a plugin “Disconnect” action.
- Performs an initial setup wizard scan by calling iAmAI scan endpoints (wizard-start, status polling, and claim-ticket) and then provisions the store inside iAmAI.
- Writes SEO fields back to the site via WordPress REST API, including meta title, meta description, and focus keyphrase for posts/pages/products (stored as standard postmeta and mirrored into the active SEO plugin’s own fields when detected).
- Injects Schema.org JSON-LD and related SEO blocks on page render by fetching cached FAQ, breadcrumb, and content-section data from iAmAI and outputting FAQPage/BreadcrumbList schema and approved content blocks.
- Injects WooCommerce Product schema (JSON-LD) and social preview meta tags on product page views by fetching product-schema data from iAmAI (server-side, cached).
- Supports Google Search Console verification by setting a verification token via a REST endpoint and injecting it into the page using the standard google-site-verification meta tag.
- Implements visitor-side analytics via a storefront pixel (pixel.js) and a beacon endpoint, excluding logged-in administrators and not loading on admin/login/AJAX pages.
- Uses IndexNow to notify Bing (and other IndexNow participants) of changed public URLs after writes/publishes, generating an ownership key served at https:///.txt; does not participate with Google.
CONTENT BOUNDARY
iAmAI Connector capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
iAmAI Connector and REEID Translate FAQ.
What does iAmAI Connector do according to the available plugin evidence?
iAmAI Connector has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for iAmAI Connector?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for iAmAI Connector?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate iAmAI Connector in a multilingual WordPress workflow.
REEID documents iAmAI Connector functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.