The Visual Editor is a dedicated translation workspace that shows the original content and the translation side by side on one screen. It is designed for translators and content managers who want to work through content segment by segment — paragraph by paragraph, heading by heading — with full context visible at all times. Instead of switching between two browser tabs (one for the English post, one for the Spanish translation), you see everything in a single, organized interface.
The Visual Editor is especially valuable for long or complex pages where losing your place is easy, for pages with many custom fields that need individual attention, and for situations where you want to use AI translation on specific segments rather than the entire post at once.
When to use the Visual Editor vs. the regular editor
| Situation | Recommended tool |
|---|---|
| Translating a long blog post or page (1,000+ words) | Visual Editor — keeps you oriented in long content |
| Translating a post with many ACF custom fields | Visual Editor — shows the ACF fields in a structured layout |
| Quick edit to one paragraph of an existing translation | Regular WordPress editor — faster for small changes |
| Translating a short post (under 300 words) | Regular editor — less overhead for simple tasks |
| First-time translators who want a guided experience | Visual Editor — the segment-by-segment layout is intuitive |
Step-by-step: Translating a blog post in the Visual Editor
- Go to Lang Forge > Translations > Visual Editor in the WordPress admin menu
- At the top of the page, use the search dropdown to find the source post. Start typing the post title and select it from the results
- Select the target language from the language dropdown next to the search field
- Click Load. If a translation already exists, it loads into the right panel. If not, the right panel starts empty, and the translation is created as a draft the first time you save
- The screen splits into two panels. The left panel shows the original content as read-only segments — each paragraph, heading, list item, and blockquote appears as a distinct segment, in the order of the blocks of the original. A block with no text of its own, such as an image without a caption, is not a segment. The right panel shows corresponding editable fields for the translation
- Click any segment on the right panel to activate its editing field. A cursor appears and you can start typing
- For each segment, you have several options:
– Copy from Original — click this button to paste the original text into the field as a starting point that you then modify
– AI Translate — click the AI icon on that specific segment to have the AI translate just that one piece (starts at 1 credit)
- As you translate each segment, it is marked with a green checkmark. Untranslated segments remain highlighted in light yellow so you can easily see what is left
- Work through all segments from top to bottom. Use Tab to jump to the next segment or Shift + Tab to go back to the previous one
- Below the main content segments, you will find any translatable custom fields grouped by field group. Expand repeater field groups to translate each row
- When finished, click Save All. A translation that the editor creates starts as a draft, and saving does not change the status of a translation that exists, so publish it from its own post screen when it is ready
Keyboard shortcuts for faster translation
| Shortcut | Action |
|---|---|
| Tab | Jump to the next segment |
| Shift + Tab | Jump to the previous segment |
| Ctrl + S (Cmd + S on Mac) | Save All: save the translation at once |
Real-world example: Translating a “Spa Services” page segment by segment
A resort website has a “Spa Services” page with 15 sections: an introduction paragraph, 10 service descriptions (each with a heading and paragraph), a pricing note, a booking call-to-action, and two ACF fields (“Opening Hours” and “Booking Phone Number”). In the Visual Editor, the translator sees all 15 content segments on the left and corresponding fields on the right. She uses AI Translate on the factual service descriptions (since they describe massage types and durations — straightforward content), manually translates the marketing-heavy introduction and call-to-action, and copies the Opening Hours as-is since the resort uses the same hours for all languages. The phone number field is replaced with the international-format number.
How custom fields appear in the Visual Editor
Below the main content area, the Visual Editor displays the translatable fields of the ACF field groups on the post (Field Forge fields are not shown in this editor). Fields are grouped by their field group name and labeled clearly. Text fields, textarea fields, and WYSIWYG fields all have editable translation fields. Repeater fields appear as expandable accordion sections — click to open them and translate each row individually.
Running an AI Quality Check on your translation
Once you have translated all segments (manually, with AI, or both), the Visual Editor can run an AI Quality Check to catch issues you might have missed. Click the QA Check button in the toolbar at the top of the page. Lang Forge sends the original and the translation to the AI, which returns a 0–100 score and a list of specific issues grouped by type: missing content, meaning changes, tone or style mismatches, and grammar or spelling errors.
Each issue in the list is anchored to a specific segment and includes:
- A short explanation of what is wrong (e.g., “The translation of ‘free shipping worldwide’ omits ‘worldwide'”)
- The problem segment highlighted in the right panel
- A Fix button that replaces the problem segment with an AI-suggested improvement
Click Fix on any issue to accept the AI’s suggestion. The Visual Editor updates the affected field in place — the new text appears immediately in the right panel and the editor is marked as unsaved. Review the change, edit further if needed, and click Save All when you are ready.
For the rare case where the problem lives in a field the Visual Editor does not render on screen (for example, the SEO excerpt or a hidden custom field), the fix is still applied to the post on the server, and a small Reload editor link appears next to the issue. Click it to refresh the editor and see the updated field.
> Tip: Each QA run consumes AI credits (applying a fix does not). For short posts this is negligible; for very long posts, consider running QA once at the end of translation rather than after every small change.
> Good to know: If the AI returns a suggestion that is essentially identical to your current translation (same text after ignoring formatting and whitespace), Lang Forge filters it out automatically — you will not see “ghost” issues without a real difference to apply.
What happens on the Free plan
The Visual Editor menu item is visible on the Free plan, but clicking it shows an informational landing page that explains the feature and invites you to upgrade to PRO. The basic translation workflow (using the + Create button of the Language metabox in the post editor) remains fully available on the Free plan.
> Tip: Use the AI Translate button on individual segments that contain straightforward, factual content (like product specifications or step-by-step instructions), and manually translate segments that need a creative touch (like marketing headlines, calls to action, or culturally sensitive content).
> Good to know: The Visual Editor saves your work about 5 seconds after you stop typing in a segment, and Ctrl + S (Cmd + S on Mac) saves at once. If your browser closes unexpectedly after a save, your work is preserved and will be there when you return.
> Good to know: When you typed nothing in the content and the translation already has content, a Save All does not write the content, and a title or an excerpt that you did not change stays as the translation has it. A row that you did not touch shows the text of the translation, not the text of the original.
> Good to know: The rows follow the blocks of the original. A block that is built differently in the translation (it was edited in the block editor, or the original changed after it was translated) has its row switched off, with a line under it that says to change that block in the block editor, and a notice above the rows says how many rows are switched off. Save All keeps those blocks as they are. When the translation has more blocks than the original, a notice says so, and the extra blocks stay where they are when you save.
> Good to know: A Save All takes off the “Content Changed” mark of a translation when it writes the content and every block of the original has its place in the translation after the save. A Save All in which you typed nothing in the content leaves the mark when the translation already has content, because it does not write the content. Click Mark as Current in the Language metabox when you have checked that the translation is up to date. A page whose editor shows no rows of the content (it has only custom fields or Elementor settings there) has no content to write: a Save All there takes the mark off. The save that the editor makes by itself 5 seconds after you stop typing, and the save that follows AI Translate, go the same way as Save All.
> Important: The Visual Editor creates a real WordPress post for the translation. Everything you do here is the same as editing a post directly — the Visual Editor is simply a more translator-friendly interface for the same underlying content.
[Screenshot: The Visual Editor showing the original English content in the left panel and editable Spanish translation fields in the right panel, with AI Translate buttons on each segment]
—