SITEORIGIN PAGE BUILDER
Translate SiteOrigin pages without rebuilding the layout.
REEID Translate Pro translates supported visitor-facing SiteOrigin content while preserving the page structure and builder workflow you already use.
BUILDER-AWARE WORKFLOW
Translate the content. Keep SiteOrigin in control of the layout.
REEID targets supported visitor-facing fields for translation. SiteOrigin continues to control rows, columns, widgets, styling and page presentation.
COMPATIBILITY AT A GLANCE
SiteOrigin Page Builder + REEID Translate.
PRO
Dedicated SiteOrigin compatibility is built into REEID Translate Pro.
STRUCTURED
Supported widget fields are collected from SiteOrigin builder data.
EDITABLE
Generated language versions remain available for review and refinement.
PRACTICAL WORKFLOW
Translate SiteOrigin Page Builder content through a controlled workflow.
REEID processes supported visitor-facing content while SiteOrigin Page Builder remains responsible for its structure and functionality.
01
Build the source page
Create the original page with SiteOrigin rows, widgets and supported content fields.
02
Choose a target language
Select the language and translation settings through the REEID workflow.
03
Generate the language version
REEID processes supported visitor-facing widget fields.
04
Review and publish
Verify content, layout and frontend presentation before publication.
WHAT GETS TRANSLATED
Translate supported content without replacing SiteOrigin Page Builder.
The compatibility layer targets approved visitor-facing content while leaving structural and functional configuration intact.
Text widgets
Translate supported visitor-facing text stored in SiteOrigin widget data.
Headings
Process supported titles and headings without replacing their widget configuration.
Button labels
Translate supported calls to action while retaining their destinations and styling.
CONTENT BOUNDARY
Translate the content. Preserve the product.
WHAT REMAINS CONTROLLED BY SiteOrigin Page Builder
SiteOrigin structure and translatable content remain separate.
Rows, columns and widget configuration remain controlled by SiteOrigin while REEID targets approved visitor-facing fields.
Third-party SiteOrigin widgets require separate compatibility testing.
LIMITATIONS & QA
Know what should be checked before launch.
Extensions, custom modules and dynamic content can introduce additional compatibility boundaries.
01
Compatibility boundary
Third-party widgets may use unsupported storage formats.
02
Extension check
Dynamic output and shortcode-generated content require separate testing.
03
Frontend QA
Every translated page should receive frontend and responsive QA.
COMMON QUESTIONS
SiteOrigin Page Builder and REEID Translate FAQ.
Answers about compatibility, supported content and practical testing.
Does REEID Translate support SiteOrigin Page Builder?
Yes. REEID Translate Pro includes dedicated SiteOrigin compatibility for supported visitor-facing content.
Does REEID rebuild the SiteOrigin layout?
No. SiteOrigin remains responsible for rows, columns, widgets and layout configuration while REEID handles supported translatable content.
Are third-party SiteOrigin widgets automatically supported?
Not necessarily. Third-party and custom widgets can store content differently and should be tested individually.
What should be checked before publishing translated pages?
Review translated text, dynamic output, responsive layouts and any third-party widgets on the frontend before launch.
RELATED GUIDES
Continue through the REEID compatibility library.
BLOCK EDITING
Gutenberg
Translate supported core blocks while preserving their hierarchy.
CLASSIC CONTENT
Classic Editor
Translate standard WordPress post fields through a familiar workflow.
SYSTEM DESIGN
Architecture
Understand how source content and language versions fit together.
BUILDER-AWARE TRANSLATION
Translate SiteOrigin content without rebuilding the page.
REEID Translate Pro preserves your existing SiteOrigin layouts and workflow while creating editable language versions of supported visitor-facing content.
Third-party and custom widgets may require separate compatibility testing.