SITEORIGIN PAGE BUILDER
Translate SiteOrigin pages without rebuilding the layout.
REEID Translate Pro processes supported SiteOrigin widget content while preserving the original builder structure.
BUILDER-AWARE WORKFLOW
Keep SiteOrigin responsible for the page layout.
REEID handles supported visitor-facing content while SiteOrigin continues controlling rows, widgets and presentation.
✓ Original structure remains controlled by SiteOrigin Page Builder
✓ Supported visitor-facing content remains editable
✓ Frontend presentation can be reviewed before launch
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 structured workflow.
REEID processes supported visitor-facing content while the original product remains responsible for its structure and functionality.
STEP 1
Build the source page
Create the original page with SiteOrigin rows, widgets and supported content fields.
STEP 2
Choose a target language
Select the language and translation settings through the REEID workflow.
STEP 3
Generate the language version
REEID processes supported visitor-facing widget fields.
STEP 4
Review and publish
Verify content, layout and frontend presentation before publication.
SUPPORTED CONTENT
Translate supported content without replacing SiteOrigin Page Builder.
The compatibility workflow targets approved visitor-facing fields 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
Separate translatable content from product configuration.
DEFINITION
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.
PRACTICAL LIMITATIONS
Know what should be tested before launch.
Compatibility can vary when extensions, dynamic content or third-party modules introduce additional storage and rendering behavior.
Compatibility check 1
Third-party widgets may use unsupported storage formats.
Compatibility check 2
Dynamic output and shortcode-generated content require separate testing.
Compatibility check 3
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.
Does REEID rebuild the SiteOrigin layout?
No. SiteOrigin remains responsible for rows, widgets and layout configuration.
Are third-party SiteOrigin widgets automatically supported?
Not necessarily. Third-party widgets should be tested individually.
BUILDER-AWARE TRANSLATION
Translate SiteOrigin content without rebuilding the page.
REEID Translate Pro preserves the existing SiteOrigin workflow while adding editable language versions.
Third-party widgets may require separate verification.