WordPress
Native PHP connector for scanning, caching, routing, rendering, analytics and SEO.
Setup guide →The WordPress connector works with rendered HTML, your SEO output and established cache tools. More platform connectors will use the same central API.
Native PHP connector for scanning, caching, routing, rendering, analytics and SEO.
Setup guide →Translate products, categories, interface strings, metadata and store navigation.
Compatibility details →Extract visible Elementor content and refresh translations after editor saves.
Compatibility details →Translate labels, placeholders, buttons, notices and rendered form content.
Compatibility details →Read and localize titles, descriptions, Open Graph fields and canonical output.
Compatibility details →Synchronize SEO fields and preserve language-specific canonical URLs.
Compatibility details →Purge page cache after a translation revision changes.
Compatibility details →Coordinate local translated pages with LiteSpeed cache invalidation.
Compatibility details →Flush cached language pages when synchronized translations change.
Compatibility details →Keep translated delivery aligned with the active page cache.
Compatibility details →Connector-neutral API foundation prepared for a Shopify storefront adapter.
Connector roadmapFuture site adapter using the same content, revision and SEO APIs.
Connector roadmapFuture PHP package for Blade applications and server-side language routing.
Connector roadmapFuture adapter for framework-free and JavaScript-rendered websites.
Connector roadmapThe connector handles authentication, scanning, extraction, hashing, synchronization, caching, routing, rendering and change detection.
The platform owns providers, AI polishing, memory, glossaries, review, usage, licensing, billing, analytics and SEO records.
Shopify, Webflow, Laravel and general HTML adapters can share authentication, content-event, revision, analytics and SEO endpoints without copying business logic.
Read the architecture guide →