Deepglot turns one WordPress site into a multilingual experience without duplicating posts or rebuilding pages. It translates the rendered output, keeps your source content in place, and serves visitors language-specific pages with the SEO signals search engines expect.

A Deepglot account and API key are required. Connect a hosted project at https://deepglot.ai or use a compatible self-hosted Deepglot service.

Publish in more languages from one WordPress site

Translate visible text, metadata, accessibility attributes, and JSON-LD structured data.
Keep the original posts and pages as the single source of truth.
Rewrite internal links and translated URL slugs with path-prefix or subdomain routing.
Translate supported WooCommerce email subjects, headings, and HTML content when enabled.

Build multilingual SEO into every page

Add reciprocal canonical, hreflang, and x-default links.
Publish a dedicated multilingual sitemap with alternate-language entries.
Redirect stale translated slugs to their current localized URLs.
Serve cached translations to crawlers without spending fresh translation quota.

Put the language switcher where it belongs

Add Deepglot through a shortcode, block, widget, navigation menu, theme action, or automatic placement. Choose a list or dropdown, labels or ISO codes, flag styles, language order, device visibility, and inline or floating positioning. Multiple independent switcher instances let different parts of the site use different presentations.

Keep the visitor experience responsive

Deepglot stores translations locally. Uncached text is queued for an immediately due background WP-Cron job, so ordinary page requests do not wait for a slow translation provider. After warming succeeds, Deepglot purges affected URLs in WP Rocket, W3 Total Cache, LiteSpeed Cache, and WP Super Cache.

For AJAX, infinite-scroll, and other content added after page load, an optional same-origin REST flow can translate new text without exposing the API key to the browser.

Stay in control

Exclude URLs, selectors, or regular-expression patterns from translation. Use synchronized translated slugs and manual translations from the Deepglot project. Enable browser-language redirects, search, AMP, dynamic content, and WooCommerce email translation only when they fit your site.

Deepglot is GPL-licensed. Development source and reproducible release build instructions are available at https://github.com/ostheimer/deepglot.

External services

By default, this plugin connects to the Deepglot service at https://deepglot.ai/api/. A compatible self-hosted API base URL can be selected in the settings.

For translation requests, the plugin sends the configured API key, text fragments from rendered pages, source and target language codes, the requested page URL, and a bot-classification code. It sends these requests when uncached content needs translation or when an administrator tests the connection. Dynamic translation requests first pass through the site’s same-origin WordPress REST endpoint, so the API key is not exposed to browsers.

Settings synchronization sends the configured API key, site URL, routing mode, source and target languages, domain mappings, and the feature flags for automatic redirect, email translation, search translation, AMP translation, and dynamic translation.

Runtime refresh sends the configured API key and receives URL and selector exclusions, regular-expression exclusions, and translated URL-slug mappings. The plugin can also request the public supported-languages list without an API key.

Starting the Visual Editor verifies its token through the project-scoped editor-sessions/verify endpoint. Saving a manual translation sends the token, original and translated text, source and target language codes, and the request URL to the project-scoped manual-translations endpoint.

Deepglot returns translated text, language and quota status, and the synchronized project configuration described above. Review the service policies before enabling the hosted service: