WORDPRESS CLASSIC EDITOR
Translate Classic Editor content without replacing the workflow.
REEID translates standard WordPress titles, body content, excerpts and slugs while keeping the familiar Classic Editor workflow available to your team.
CLASSIC CONTENT MODEL
Simple editing stays simple.
REEID works with the standard content stored by WordPress instead of introducing another page-building system.
✓ Title, body, excerpt and slug
✓ Separate linked language versions
✓ Editable translation drafts
PRO
Dedicated Classic Editor translation is built into REEID Translate Pro.
1
The original WordPress post remains the central source.
EDITABLE
Generated language versions can be reviewed before publication.
PRACTICAL WORKFLOW
Translate the content through a familiar WordPress process.
The source post remains intact while REEID creates or updates a linked language version for review.
STEP 1
Write the source post
Create the title, body content and excerpt with the standard WordPress editor.
STEP 2
Choose a language
Select the target language and the available REEID translation settings.
STEP 3
Generate the translation
REEID translates the supported content fields and prepares the language version.
STEP 4
Review and publish
Edit the translated post where necessary and publish it intentionally.
SUPPORTED CONTENT
Translate the standard fields visitors actually read.
REEID handles the main WordPress content fields used by Classic Editor posts and pages.
Post title
Translate the visitor-facing title while retaining the relationship to the original post.
VISITOR-FACING CONTENT
Body content
Translate the standard HTML content stored in the WordPress post body.
VISITOR-FACING CONTENT
Excerpt
Translate the post excerpt used by themes, archives and other supported displays.
SUPPORTING CONTENT
Language slug
Create a language-specific URL slug from the translated title while respecting WordPress uniqueness rules.
LANGUAGE URL
CONTENT BOUNDARY
Classic Editor content can contain both visible text and functional markup.
REEID translates supported visitor-facing content while preserving the surrounding HTML structure as part of the WordPress post.
Shortcodes, embedded applications, custom fields and plugin-owned metadata should be tested separately because they can introduce their own storage and rendering rules.
TRANSLATION OPTIONS
Classic Editor translation is built into REEID Translate Pro.
Translate through REEID Cloud Assist while keeping the familiar WordPress editing and review workflow.
01
Dedicated Classic workflow
REEID detects standard Classic Editor content and translates the title, body, excerpt and language slug through the Pro workflow.
02
Cloud Assist transport
Managed translation transport keeps the translation workflow connected to REEID without requiring a separate provider setup on each website.
CLEAR RESPONSIBILITIES
Standard content is predictable. Extensions require verification.
Classic Editor itself is straightforward, but plugins can add shortcodes, custom fields and proprietary content that live outside the standard post body.
Shortcodes should be tested
The shortcode itself may control content, output or external data that should remain functional.
Custom fields are separate
Plugin-owned metadata is not automatically equivalent to standard Classic Editor body content.
Functional markup remains functional
Links, embeds, scripts and structured HTML should be reviewed after translation.
Human review remains valuable
Translation quality, terminology and context should be checked before publication.
COMMON QUESTIONS
Classic Editor and REEID Translate FAQ
Answers about supported fields, separate language versions and Classic Editor compatibility.
Does REEID Translate support Classic Editor?
Yes. REEID Translate Pro includes dedicated Classic Editor content translation.
Which Classic Editor fields are translated?
REEID can translate the post title, standard body content, excerpt and language-specific slug.
Does REEID modify the original post?
No. A separate language version is created or updated and linked to the original through the REEID translation relationship.
Can I edit the translated post afterward?
Yes. The translated version remains a normal editable WordPress post or page.
Are HTML formatting and links preserved?
REEID processes the standard post content while retaining its surrounding HTML structure. The result should still be reviewed before publication.
Are shortcodes translated automatically?
Shortcodes can contain functional instructions or plugin-controlled output. Their compatibility should be tested individually.
Are custom fields included?
Not automatically. Custom fields and plugin-owned metadata use separate storage and require explicit support or a dedicated workflow.
Is Classic Editor support included in REEID Translate Pro?
Yes. Classic Editor translation is part of the Pro compatibility workflow.
How is Classic Editor translation delivered?
REEID Translate Pro uses Cloud Assist as its managed translation transport while retaining the familiar Classic Editor content workflow.
FAMILIAR WORDPRESS WORKFLOW
Translate Classic Editor content without rebuilding the website.
REEID works with the standard WordPress content model while keeping every generated language version editable.
Shortcodes, custom fields and plugin-owned data may require separate compatibility testing.