Public Beta: 9 builders supported

Switch WordPress page builders in seconds, not weeks.

One API translates content across Elementor, Divi, Bricks, Gutenberg, and 5 more builders. Keep your design, change your engine.

No plugins required. Works with WP REST API (5.6+). Free tier included.

POST /api/translate-and-publish
source_builder: "elementor"
target_builder: "bricks"
post_id: 4821, auto_publish: true
200 OK in 28ms
blocks_translated: 47
published: true

Supports all 9 major WordPress builders

D
A
WPB
B
The Problem

Switching builders costs 40+ hours. We fixed that.

Every widget, layout, and section manually rebuilt. That is 2 full days of work per page minimum. Translation Bridge compresses that to 30 seconds.

40+
Hours saved per migration
30s
Average translation time
9
Builders supported
Before: 40 hours of manual rebuilding. After: 30 seconds with Translation Bridge.
How It Works

Three steps. One API call.

No plugins to install. No page builder accounts required on the target. Just an HTTP request.

How Translation Bridge works: flow diagram showing builder JSON to API to WordPress
01
step

Send your content

POST your page builder JSON or HTML to /translate. Include source builder, target builder, and optionally override which engine to use.

02
step

Translation Bridge processes it

The API detects your source format, selects the optimal engine (PHP for speed, Python for lossless precision), and translates every block.

03
step

Auto-publish to WordPress

The translated content is injected directly into WordPress via REST API. Your page goes live: same design, new engine, no manual editing.

All 9 Builders

Every direction. Every builder.

72 conversion paths. Any builder can be your source or target. No dead ends. Switch freely in any direction.

All 9 WordPress page builders supported: Elementor, Divi, Bricks, Gutenberg, Bootstrap 5, Avada, WPBakery, Beaver Builder, Oxygen
Bootstrap 5
Elementor
D
Divi
A
Avada
Bricks
WPB
WPBakery
B
Beaver Builder
Gutenberg
Oxygen

All 9 builders supported as source and target. Elementor source additionally gets the lossless Python engine with 100% metadata preservation.

API Demo

One request. Any direction.

The translate-and-publish endpoint handles content extraction, format translation, and WordPress injection in a single call.

POST /translate-and-publish
Translate Elementor to Bricks
"wp_url": "https://yoursite.com"
"source_builder": "elementor"
"target_builder": "bricks"
"post_id": 4821
"engine": "python"
"auto_publish": true
Response200 OK: 28ms
Translation complete
"status": "success"
"source_builder": "elementor"
"target_builder": "bricks"
"blocks_translated": 47
"metadata_preserved": true
"published": true
Translation Bridge API architecture: how the system connects source and target builders
Features

Built for production. Ready today.

Everything you need to migrate entire WordPress sites across builders: safely, fast, and at scale.

Translate Any Builder

All 9 builders as source and target. 72 unique conversion paths. No constraints on direction.

Auto-Publish to WP

Translated content is injected directly into WordPress via REST API and published live. No copy-paste required.

WP REST Integration

Uses WordPress Application Passwords for secure REST API access. No plugins to install on the target site.

100% Metadata Preserved

SEO title, meta description, open graph tags, schema, post slug, categories: all retained with the Python engine.

Self-Hostable

Run the API on your own server. No per-call fees or external dependencies. Deploy to any VPS or cloud provider.

Dual Engine

PHP engine: under 30ms. Python engine: lossless precision with full metadata fidelity. You choose per request.

Pricing

Simple pricing. No surprises.

Start free. Scale when you need it. Self-host for unlimited volume with the Enterprise plan.

Free

$0/mo

Try it on your own server. No time limit, no credit card.

Run Your First Translation Free
  • 50 translations / month
  • PHP engine (fast)
  • All 9 builders
  • WP REST auto-publish
  • Community support
Most Popular

Pro

$49/mo

For freelancers and solo agencies running regular migrations.

Unlock Pro Power
  • 1,000 translations / month
  • PHP + Python engines
  • 100% metadata preservation
  • Priority queue
  • Email support
  • API key management

Agency

$199/mo

For agencies handling migrations across multiple client sites.

Run Your Agency on Auto
  • 10,000 translations / month
  • Both engines
  • Bulk migration endpoint
  • Webhook callbacks
  • Priority support
  • White-label option

Enterprise

Custom

Self-hosted, unlimited volume, SLA-backed, custom integrations.

Let's Talk Scale
  • Unlimited translations
  • Self-hosted deployment
  • SLA guarantee
  • Custom engine config
  • Dedicated support
  • Source code license
The Team

Built by people who know WordPress.

No VC funding. No pivot risk. Two builders who got tired of spending days on migrations that should take seconds.

Cory Hubbell

Cory Hubbell

Original Creator

Cory built the original engines: the core translation logic that maps page builder formats bidirectionally across 9 systems.

Mike Merlino

Mike Merlino

Productized and Deployed

Mike productized, deployed, and is taking it to market. Translation Bridge is now live, self-hostable, and available to agencies.

FAQ

Frequently Asked Questions

Still unsure? Email mike@merlinomarketing.com

  • All 9: Elementor, Divi, Avada, Bricks, WPBakery, Beaver Builder, Gutenberg, Oxygen, and Bootstrap 5. Every builder can be source or target: 72 unique conversion paths with no dead ends.

  • No plugins. Translation Bridge uses the WordPress REST API with Application Passwords (built into WP 5.6+). You authenticate once, then fire API calls from anywhere.

  • The PHP engine is optimized for speed: under 30ms per translation. The Python engine is lossless: it preserves 100% of your metadata (SEO title, description, schema, open graph, slugs, categories). Choose per-request based on what matters for that translation.

  • Yes, when using the Python engine. All meta fields, Yoast/RankMath data, schema markup, canonical URLs, and post slugs are preserved. The PHP engine focuses on content structure and is faster but less metadata-aware.

  • Yes. The Enterprise plan includes a full self-hosted deployment. You run it on your own server: no per-call fees, no external API dependencies, unlimited volume. Source code license included.

  • When auto_publish is true, the translated content is immediately published to WordPress as a new post (or overwrites the target post ID if specified). When false, it is saved as a draft for review. The translated post ID is always returned in the response.

  • Yes. Translation Bridge is deployed and in active use. The PHP engine has processed thousands of pages. The Python engine is in active beta. The API is self-hostable, meaning your usage is completely in your control.

  • The engine maps to the closest semantic equivalent. If no match exists, the content is wrapped in a fallback HTML block and flagged in the response with a warnings array. Nothing is silently dropped.

Get Your API Key Now

Get early API access. Free tier included, no credit card required. We will email your key within 24 hours.

No spam. Unsubscribe any time. Free tier ships with 50 translations per month.