Lionrapid Translation

Lionrapid Translation translates your site’s content on the server, before the page reaches the browser. Visitors never see a flash of untranslated text, and search engines index the translated pages.

The plugin is managed from your Lionrapid dashboard: languages, switcher style, excluded paths and server-side rendering sync to the plugin automatically. In WordPress you only enter your site key.

Key features

• Server-side translation: the page’s HTML is translated before delivery, so search engines see the translated content directly.
• Formatting kept: inline formatting such as <b> and <a> survives translation.
• Managed from the dashboard: source and target languages, the switcher and excluded paths come from your Lionrapid project. Changes are pushed to the site immediately, with a 5-minute check as a safety net.
• Gutenberg blocks: a translation block, a language switcher block and an inline translation editor.
• Language switcher: three styles (floating, buttons, flags), added to every page automatically or placed where you want it with the block.
• Language URLs: addresses like /de/, /es/ and /fi/ lead visitors to the right language.
• SEO: hreflang tags, translated meta descriptions and canonical URLs.
• New text is collected: text that appears on the live site is sent to your dashboard for translation in the background (wp_cron).

Required external service

This plugin requires a Lionrapid account. It connects to the Lionrapid service at the address shown under Settings → Lionrapid (https://app.lionrapid.com by default).

When activated and configured with a site key, the plugin sends:

• Translation requests (page content blocks) → server for translation lookup
• New keys discovered on the live site → server for translation queue
• Configuration sync requests → server for current project settings

Server endpoints called:

• GET /api/integrations/config?domain={your-site-domain} — fetches project config
• GET /api/integrations/translations/{locale}/{namespace} — fetches translations
• POST /api/integrations/sync/... — pushes newly discovered keys

When your settings hold a publishable key (pk_), your visitors’ browsers also call the Lionrapid service directly, at the API address your Lionrapid project gives (https://app.lionrapid.com by default):

• to load the translations and language settings for the page they are viewing;
• to report text on the page that has no translation yet, so it appears in your dashboard.

Like any web request, these calls show the service the visitor’s IP address and browser details. The plugin adds no tracking or analytics. Login and account pages excluded on the dashboard never report text. Without a publishable key, the browser loads translations from your own site instead and calls no Lionrapid address.

The plugin also adds two REST endpoints to your site:

• POST /wp-json/lionrapid/v1/resync: your Lionrapid dashboard calls it to push configuration changes immediately. It is authenticated with the key stored in your plugin settings.
• GET /wp-json/lionrapid/v1/api/integrations/translations/{locale}/{namespace}: public and read-only. It serves your site’s translations to the visitor’s browser, so the browser never needs a key.

Lionrapid’s terms of service: https://www.lionrapid.com/terms. Privacy policy: https://www.lionrapid.com/privacy.

Without a site key

Until you enter a site key, the plugin calls no external service. It does start preparing your pages for translation as soon as it is active (language links and markers in the HTML), so activate it once your Lionrapid account is ready.