Visual Editor

The visual editor gives you a live, clickable preview of your site where you can translate text directly in place. Instead of working from a list of strings, you see exactly how the page looks and click on any piece of text to translate it.

Opening the Visual Editor

There are two ways to open the editor:

1. From the dashboard — click the editor icon in any page’s row. The visual editor opens with that page already loaded.
2. From the frontend admin bar — while browsing your site as a logged-in administrator, you’ll see an Omnalingo → Translate Page button in the admin bar. Clicking it opens the visual editor for the page you’re currently viewing.

Note

The visual editor is available to administrators. If you need to give a translator access, assign them the Omnalingo Translator role in WordPress user settings.

Editor Layout

When the editor opens, you’ll see:

• The page preview (main area) — a live rendering of your page with all translatable strings highlighted. Click any highlighted element to select it.
• The sidebar (right side) — shows the selected string, its current translation, and controls for editing or generating a translation with AI.
• The toolbar (top) — language selector, save button, and access to the AI chatbot panel.

Translating a String

1. Click on any highlighted text in the page preview. The string appears in the sidebar.

2. Type your translation in the input field. For simple text, this is a plain text box. For strings that contain formatting (bold, links, line breaks), a rich text editor appears automatically.

3. Your translation appears live in the page preview as you type, so you can see how it looks in context.

4. Translations are saved automatically as you type. You can also click Save in the toolbar to save everything at once.

AI-Assisted Translation

For each string, you can generate an AI translation suggestion instead of typing manually:

1. Select a string by clicking it in the page preview.

2. Click Generate (or the AI icon) in the sidebar.

3. Omnalingo sends the string to its AI translation service and returns a suggestion.

4. Review the suggestion. Accept it as-is, edit it, or discard it and type your own.

AI suggestions require a connected API key. You can set this up under Omnalingo → Settings → API.

Switching Languages

Use the language selector in the toolbar to switch between your active target languages. The page preview updates to show translations for the selected language, and the sidebar inputs show that language’s current translations.

Keyboard shortcut: Alt + Down to move to the next language, Alt + Up to move to the previous one.

Navigating Between Strings

To move through strings without clicking in the preview:

• Press Tab to jump to the next string in the sidebar list.
• Press Shift + Tab to go to the previous string.

String Status Badges

Each string in the sidebar shows a small status badge:

Badge	Meaning
Empty circle	Not yet translated
AI icon	Translated by AI — not manually reviewed
Checkmark	Saved by a human editor
Warning	Flagged for review — the source text may have changed since this translation was saved

Strings flagged for review show a yellow banner with the previous source text alongside the current text, so you can see exactly what changed and update the translation if needed.

Different String Types

The sidebar input adapts to the type of string you’ve selected:

• Plain text — a simple text input.
• HTML content — a rich text editor (bold, italic, links are preserved).
• Image alt text or ARIA labels — a plain text input labelled with the attribute name.
• Images — two fields: one to replace the image source with a localized version, one for the alt text.
• Page title and meta tags — dedicated inputs for the <title> tag, meta description, and Open Graph fields.
• Select menus — each dropdown option is shown separately so you can translate the display labels.
• URL slugs — see Slug Translation (Pro only).

What the Visual Editor Can and Can’t Translate

The visual editor captures text that is present in the page’s initial HTML. Most content on standard WordPress pages and WooCommerce stores — including content loaded dynamically by blocks and AJAX responses — is also detected automatically as it appears.

There are some situations where content may not be clickable in the preview:

• Content that requires a user action to trigger (for example, text inside a modal that only opens when a button is clicked) may not be visible until you interact with the preview.
• Very dynamic content driven by JavaScript frameworks may occasionally need a page reload inside the editor before it becomes selectable.

In cases where you can’t click a string directly, you can still find it in the sidebar string list and translate it there.

Previously Found Strings

At the bottom of the sidebar, you may see a Previously Found section. These are strings that were on the page in a past scan but are no longer present — for example, text that was deleted or rewritten.

Previously found strings are not clickable in the preview (the text no longer exists on the page). You can:

• Delete the string if the old content is gone for good. This removes the string and its translations from all languages.
• Leave it if you want to review it before deciding.

See Orphan Management for more detail on how Omnalingo handles changed content.