SITEORIGIN PAGE BUILDER
Translate SiteOrigin pages without rebuilding the layout.
REEID Translate Pro detects SiteOrigin content, translates supported widget fields and reinjects the translated text into a separate language version while preserving the surrounding page-builder structure.
BUILDER-AWARE TRANSLATION
Translate widget content—not the builder itself.
REEID works with SiteOrigin’s stored widget data instead of flattening the page into generic text.
✓ Automatic SiteOrigin detection
✓ Path-based widget extraction
✓ Translated builder data reinjection
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 content through a builder-aware workflow.
REEID identifies the page-builder source, extracts approved visitor-facing fields and prepares a linked language version without replacing the original layout.
STEP 1
Build the source page
Create the original page with SiteOrigin rows, widgets and supported content fields.
STEP 2
Choose the language
Select the target language and translation settings inside REEID Translate Pro.
STEP 3
Translate supported fields
REEID processes approved text paths while retaining the surrounding widget configuration.
STEP 4
Review and publish
Inspect the generated SiteOrigin page, refine the language and publish intentionally.
SUPPORTED CONTENT PATHS
Translate supported text inside SiteOrigin widgets.
REEID uses explicit field rules instead of assuming that every value stored by a widget should be translated.
Headlines
Translate supported headline, subheadline and title fields used by SiteOrigin widgets.
VISITOR-FACING CONTENT
Text content
Process supported text, feature descriptions and other approved content fields.
VISITOR-FACING CONTENT
Button labels
Translate supported button text while preserving the surrounding button configuration.
INTERFACE CONTENT
Form messages
Translate supported labels, submit text, success messages and validation messages.
FORM CONTENT
CONTENT BOUNDARY
SiteOrigin builder data contains both visible content and structural configuration.
REEID translates only approved visitor-facing paths and reinjects the resulting text into a copy of the original SiteOrigin widget structure.
Custom widgets and third-party SiteOrigin extensions can introduce additional fields that require explicit compatibility rules and testing.
STRUCTURE PRESERVATION
The page remains a SiteOrigin page after translation.
REEID stores translated builder data on the linked language version and can render the translated SiteOrigin structure into the WordPress content field.
01
Builder detection
REEID identifies SiteOrigin through its stored page-builder metadata before selecting the translation adapter.
02
Selective extraction
Only strings matching approved SiteOrigin content paths are sent through the translation workflow.
03
Safe reinjection
Translated strings are written back into the corresponding widget paths without replacing unrelated configuration.
04
Separate language version
The translated page receives its own title, excerpt, slug, content and SiteOrigin builder data.
SINGLE AND BULK TRANSLATION
Use the same SiteOrigin adapter across individual and bulk workflows.
REEID Translate Pro supports translating one SiteOrigin page directly or processing supported SiteOrigin pages through the bulk translation workflow.
A
Single-page workflow
Translate, review and publish one SiteOrigin page directly from its editing workflow.
B
Bulk workflow
Process multiple supported SiteOrigin pages while preserving their individual builder structures.
COMPATIBILITY BOUNDARIES
Builder-aware translation still requires explicit field support.
SiteOrigin compatibility is based on known content paths. Third-party widgets and mixed-builder pages should be verified before large-scale publication.
Supported paths are explicit
REEID translates approved widget fields instead of changing every string stored in the builder data.
Custom widgets need testing
Third-party extensions may store text under field paths not covered by the standard SiteOrigin rules.
Mixed builders are protected
REEID detects conflicting editor signals and can block unsafe translation rather than risk damaging the layout.
Review remains part of publishing
Widget output, forms, links and responsive behavior should be checked before the translated page goes live.
COMMON QUESTIONS
SiteOrigin and REEID Translate Pro FAQ
Answers about builder detection, supported widgets, structure preservation and bulk translation.
Does REEID Translate Pro support SiteOrigin Page Builder?
Yes. REEID Translate Pro includes a dedicated SiteOrigin adapter for supported builder content.
How does REEID detect a SiteOrigin page?
REEID checks the page’s stored SiteOrigin builder metadata before selecting the SiteOrigin translation workflow.
Does translation flatten the page into plain HTML?
No. The translated language version receives translated SiteOrigin builder data as well as rendered WordPress content.
Which SiteOrigin widget fields are supported?
Supported paths include common titles, headlines, text, feature content, button labels and selected form labels and messages. Coverage depends on the widget and its stored field structure.
Are all third-party SiteOrigin widgets supported automatically?
No. Third-party widgets can introduce proprietary fields that require dedicated compatibility rules and testing.
Are titles, excerpts and slugs translated?
Yes. The SiteOrigin workflow can translate the page title and excerpt and generate a language-specific slug.
Can SiteOrigin pages be translated in bulk?
Yes. REEID Translate Pro includes SiteOrigin handling in its supported bulk translation workflow.
What happens if a page contains data from multiple builders?
REEID checks for mixed-builder signals and can block the translation to protect the page structure until the correct editor context is confirmed.
Can the translated page be edited afterward?
Yes. The generated language version remains an editable WordPress page with its translated SiteOrigin data attached.
SITEORIGIN COMPATIBILITY
Translate SiteOrigin pages without abandoning SiteOrigin.
REEID Translate Pro processes supported widget content while preserving the builder data your website already depends on.
Third-party and custom widgets may require dedicated compatibility testing.