Translate Duda sites without touching the templates

Duda has no API for native language versions, so Lingvit serves them for you. Point a language subdomain at Lingvit for search-indexable pages, add one script tag in Head HTML for the in-page language switcher, or do both.

Get started View all integrations

What gets translated

Every page of a Duda site, including dynamic pages and collections

Navigation, buttons, forms and footer text

Meta descriptions, Open Graph tags and image alt text on language subdomains

Translated URLs and hreflang on language subdomains

Sites in an agency portfolio, one connection each

Setup guide

1
Create a Lingvit project
Sign up at app.lingvit.com and create a project for the site. Choose the languages you want to offer.
2
Serve languages on subdomains (recommended for SEO)
In the Lingvit dashboard open Integrations → Domains and add fr.yoursite.com for French (one entry per language). At your DNS provider create a CNAME for each subdomain pointing at the target shown in the dashboard. The subdomain turns Active within minutes, with its own TLS certificate.
```
fr.yoursite.com.   CNAME   dns.lingvit.com.
```
3
Add the language switcher in Head HTML
In the Duda editor open SEO & Settings → Head HTML and paste your project's script tag from the dashboard. Republish the site. Visitors get a language switcher; on a language subdomain the script simply keeps the choice in sync.
```
<script src="https://cdn.lingvit.com/widget.bundle.js?v=1" data-widget-key="lng_wpk_…" async></script>
```
4
Publish and review
Translations appear in the Lingvit dashboard as pages are visited. Edit any of them; edits are pinned and never overwritten by a re-translation.

Need the full platform overview? Browse the use case guides →

Frequently asked questions

Why subdomains rather than Duda's own multilingual feature?

Duda's built-in multilingual duplicates the site and machine-translates it once, without translating SEO metadata and without a way to sync later edits. A Lingvit language subdomain is rendered from the live site on every request, so it never drifts, and it carries translated metadata, translated URLs and hreflang.

Does this work for sites on an agency account?

Yes. Each site gets its own Lingvit project and its own DNS records. Nothing is installed on the Duda account itself, and nothing changes in the site's templates.

Will I appear in the Duda App Store?

A listing is in preparation. Until then the two steps above are the supported setup and work on every Duda plan that allows Head HTML.

Do I need to republish after every content change?

No. Language subdomains read the published site live, and the script translates in the browser. Only the Head HTML step itself needs one republish.

Setup guide

Create a Lingvit project

Serve languages on subdomains (recommended for SEO)

In the Lingvit dashboard open Integrations → Domains and add fr.yoursite.com for French (one entry per language). At your DNS provider create a CNAME for each subdomain pointing at the target shown in the dashboard. The subdomain turns Active within minutes, with its own TLS certificate.

fr.yoursite.com.   CNAME   dns.lingvit.com.

Add the language switcher in Head HTML

In the Duda editor open SEO & Settings → Head HTML and paste your project's script tag from the dashboard. Republish the site. Visitors get a language switcher; on a language subdomain the script simply keeps the choice in sync.

<script src="https://cdn.lingvit.com/widget.bundle.js?v=1" data-widget-key="lng_wpk_…" async></script>

Publish and review

Translations appear in the Lingvit dashboard as pages are visited. Edit any of them; edits are pinned and never overwritten by a re-translation.

Frequently asked questions

Why subdomains rather than Duda's own multilingual feature?

Does this work for sites on an agency account?

Yes. Each site gets its own Lingvit project and its own DNS records. Nothing is installed on the Duda account itself, and nothing changes in the site's templates.

Will I appear in the Duda App Store?

A listing is in preparation. Until then the two steps above are the supported setup and work on every Duda plan that allows Head HTML.

Do I need to republish after every content change?

No. Language subdomains read the published site live, and the script translates in the browser. Only the Head HTML step itself needs one republish.

Translate Duda sites without touching the templates

What gets translated

Setup guide

Frequently asked questions

Start translating your Duda site

Translate Duda sites without touching the templates

What gets translated

Setup guide

Frequently asked questions

Start translating your Duda site