ARTIOSYNC FOR ENGINE SEO
ArtioSync for Engine SEO compatibility with REEID Translate
ArtioSync for Engine SEO compatibility with REEID Translate is being evaluated from available plugin evidence. Fetches published articles from the Engine SEO API (GET /v1/articles?format=html) and saves them as WordPress posts. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for ArtioSync for Engine SEO.
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
ArtioSync for Engine SEO is documented in the SEO category with 7 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 ArtioSync for Engine SEO 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
- Fetches published articles from the Engine SEO API (GET /v1/articles?format=html) and saves them as WordPress posts.
- Performs idempotent sync by updating existing posts instead of creating duplicates, using a stable article id stored in post meta.
- Supports automatic hourly synchronization via WP-Cron and manual synchronization via an admin “Sync now” action.
- Imports article images into the WordPress Media Library and sets the first imported image as the featured image.
- Writes meta descriptions for Yoast SEO and Rank Math when either plugin is active.
- Provides a read-only endpoint (GET /api/articles.json) for the Engine SEO panel to determine which posts already exist to avoid duplication.
- Uses HTML content from the Engine SEO API directly for post content (no Markdown conversion on the WordPress side).
CONTENT BOUNDARY
ArtioSync for Engine SEO 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
ArtioSync for Engine SEO and REEID Translate FAQ.
What does ArtioSync for Engine SEO do according to the available plugin evidence?
ArtioSync for Engine SEO has 7 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 ArtioSync for Engine SEO?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for ArtioSync for Engine SEO?
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 ArtioSync for Engine SEO in a multilingual WordPress workflow.
REEID documents ArtioSync for Engine SEO 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.