AEOMATIC
AEOmatic — AI SEO, llms.txt & Schema Markup translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what AEOmatic — AI SEO, llms.txt & Schema Markup does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Generates and serves AI-oriented metadata endpoints: a spec-compliant `/llms.txt` Markdown index at the site root and a `/llms-full.txt` endpoint that returns extracted published body text (cached and capped by default).
- Produces JSON-LD structured data across 22 page-level schema types plus additional types (e.g., Organization, Person/Author, Breadcrumb, WebSite with SearchAction, VideoObject, Speakable), with a visual JSON-LD editor and live preview.
- Performs server-side content extraction from multiple sources (Gutenberg/Classic Editor and major page builders like Elementor/Divi/Beaver Builder/Bricks/Oxygen/WPBakery, plus ACF text/textarea/wysiwyg/repeater/flexible-content fields) and uses that single extraction for downstream schema generation and audits.
- Implements AI crawler access control and reporting: per-bot Allow/Disallow toggles that update `robots.txt` for a set of recognized AI crawlers, and an internal server-side crawler log recording bot name, requested URL, user-agent, HTTP status, and timestamp (no IP/cookies/referrers/human visitor data).
- Provides WooCommerce Product schema auto-fill for product fields (price, availability, SKU, brand, ratings, sale dates) including variable products via AggregateOffer min/max range.
- Adds optional AI discovery HTTP headers and a `Link: rel="ai-context"` pointer to `llms.txt` (configurable and described as proposed conventions).
- Includes a live verification panel that fetches only the plugin’s own public outputs from the site (e.g., `/llms.txt`, `robots.txt`, and latest post schema) and shows what is actually being served to administrators only; it also links to Google Rich Results Test for the latest post.
Distinctive features
Generates and serves AI-oriented metadata endpoints: a spec-compliant `/llms.txt` Markdown index at the site root and a `/llms-full.txt` endpoint that returns extracted published body text (cached and capped by default). Produces JSON-LD structured data across 22 page-level schema types plus additional types (e.g., Organization, Person/Author, Breadcrumb, WebSite with SearchAction, VideoObject, Speakable), with a visual JSON-LD editor and live preview. Performs server-side content extraction from multiple sources (Gutenberg/Classic Editor and major page builders like Elementor/Divi/Beaver Builder/Bricks/Oxygen/WPBakery, plus ACF text/textarea/wysiwyg/repeater/flexible-content fields) and uses that single extraction for downstream schema generation and audits. Implements AI crawler access control and reporting: per-bot Allow/Disallow toggles that update `robots.txt` for a set of recognized AI crawlers, and an internal server-side crawler log recording bot name, requested URL, user-agent, HTTP status, and timestamp (no IP/cookies/referrers/human visitor data). Provides WooCommerce Product schema auto-fill for product fields (price, availability, SKU, brand, ratings, sale dates) including variable products via AggregateOffer min/max range. Adds optional AI discovery HTTP headers and a `Link: rel="ai-context"` pointer to `llms.txt` (configurable and described as proposed conventions). Includes a live verification panel that fetches only the plugin’s own public outputs from the site (e.g., `/llms.txt`, `robots.txt`, and latest post schema) and shows what is actually being served to administrators only; it also links to Google Rich Results Test for the latest post.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what AEOmatic — AI SEO, llms.txt & Schema Markup does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AEOmatic — AI SEO, llms.txt & Schema Markup and REEID Translate FAQ.
Does the current evidence establish translation scope for AEOmatic — AI SEO, llms.txt & Schema Markup?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.