New Multilingual SEO audits and regional language routing are now included. See what changed
Integrations

Keep your website stack. Add a translation layer.

The WordPress connector works with rendered HTML, your SEO output and established cache tools. More platform connectors will use the same central API.

W
Available

WordPress

Native PHP connector for scanning, caching, routing, rendering, analytics and SEO.

Setup guide
WC
Compatible

WooCommerce

Translate products, categories, interface strings, metadata and store navigation.

Compatibility details
F
Compatible

WordPress Forms

Translate labels, placeholders, buttons, notices and rendered form content.

Compatibility details
S
Planned

Shopify

Connector-neutral API foundation prepared for a Shopify storefront adapter.

Connector roadmap
WF
Planned

Webflow

Future site adapter using the same content, revision and SEO APIs.

Connector roadmap
L
Planned

Laravel

Future PHP package for Blade applications and server-side language routing.

Connector roadmap
JS
Planned

HTML & JavaScript

Future adapter for framework-free and JavaScript-rendered websites.

Connector roadmap
A clear connector boundary

Your website stays responsible for delivery.

The connector handles authentication, scanning, extraction, hashing, synchronization, caching, routing, rendering and change detection.

A central operating layer

Laravel manages translation intelligence.

The platform owns providers, AI polishing, memory, glossaries, review, usage, licensing, billing, analytics and SEO records.

Need another platform?

The API already separates translation logic from website code.

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