SITEORIGIN
SiteOrigin and REEID Translate Compatibility Guide
SiteOrigin translation support is verified by REEID for 3 visitor-facing content surfaces.
VERIFIED COMPATIBILITY
Keep SiteOrigin responsible for the page layout.
REEID manages supported multilingual content and language relationships while SiteOrigin remains responsible for builder structure, presentation and configuration.
VERIFIED COMPATIBILITY
This integration has been tested and verified by REEID.
STRUCTURED
Supported visitor-facing fields are processed without replacing SiteOrigin builder structure.
EDITABLE
Generated language versions remain available for normal WordPress review and refinement.
PRACTICAL WORKFLOW
Translation workflow
01 · Build the source page
Create the original page with SiteOrigin structure 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 fields while preserving the original builder structure.
04 · Review and publish
Verify content, layout and frontend presentation before publication.
SUPPORTED CONTENT
Translation scope
Text widgets
Translate supported visitor-facing text stored in SiteOrigin widget data.
Headings
Translate supported titles and headings without replacing their widget configuration.
Button labels
Translate supported calls to action while retaining destinations and styling.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Build responsive column-based content using a drag-and-drop page builder interface.
- Work with standard WordPress widgets.
- Insert a Page Builder Layout into the Block Editor using the SiteOrigin Layout Block.
- Support live editing to see content and edit widgets in real time.
- Provide a History Browser to roll forward and back through changes.
- Generate code for the created layouts (no coding required).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
SiteOrigin structure and translatable content remain separate.
Builder structure and configuration remain controlled by SiteOrigin while REEID targets supported visitor-facing fields.
Third-party widgets, dynamic output and additional builder extensions may require separate compatibility testing.
LIMITATIONS & QA
Verification notes
- Third-party widgets may use unsupported storage formats and require separate compatibility testing
- Dynamic output and shortcode-generated content require separate testing.
- Translated pages should receive frontend and responsive QA.
COMMON QUESTIONS
SiteOrigin and REEID Translate FAQ.
Does REEID Translate support SiteOrigin?
Yes. REEID Translate Pro includes tested compatibility for supported visitor-facing content created with SiteOrigin.
Does REEID rebuild the SiteOrigin layout?
No. SiteOrigin remains responsible for layout and builder configuration while REEID translates supported content.
Are third-party SiteOrigin widgets automatically supported?
Not necessarily. Third-party widgets and extensions can use separate storage paths and should be verified independently.
RELATED GUIDES
Continue through the compatibility library.
WORDPRESS PAGE BUILDERS
Translate SiteOrigin content without rebuilding the page.
REEID Translate Pro adds multilingual content workflows while your page builder remains responsible for structure and presentation.
SiteOrigin remains responsible for layout, widgets and builder configuration.