Choose how to install
All install paths use the same translations and the same published files. They differ in how the translated page reaches your visitor.
Quickest way to choose: open your site's Install page in the dashboard and pick your platform from the list "Where is your website built?" (WordPress, Shopify, Wix, Squarespace, Webflow, Next.js / React, Nuxt / Astro / other framework, any other site, or "I'm not sure"). The page then shows only the numbered steps for that platform, with your own site key already filled in. Platforms that are not ready yet are marked "Coming soon". The free WordPress plugin file can be downloaded from the same page when your installation includes it.
| Path | Best for | Separate language addresses (/fr/) |
|---|---|---|
| WordPress plugin | WordPress sites | Yes, from the SEO part of the plugin |
| Shopify app | Shopify stores | Yes, Shopify serves its own language addresses |
| Script tag | Wix, Squarespace, Webflow, plain HTML, single-page apps, other platforms | No. One address; text is swapped in the browser |
| Framework kits | Next.js, Nuxt, Astro and static sites you build yourself | Yes, made at build time |
| API and command line | Custom platforms and build pipelines | Your build decides |
How to decide#
- If your platform has a native route (WordPress, Shopify), use it. It is the only route that gives search engines real translated pages without a build step.
- If you build static pages or use Next.js, Nuxt or Astro, use the framework kit. It writes translated copies of your pages at build time.
- If search traffic in other languages matters and your platform has its own multilingual feature with real language addresses, use that feature. Use the script tag only for what it does not cover.
- If visitors already come to your site and you want them to read it in their language, or you need something that works anywhere in minutes, use the script tag.
What is built today#
The WordPress plugin, the Shopify library and theme extension, the framework kits and the script generator exist in the repository and pass their own tests. None of them is published to a store or a package registry yet. Publishing requires the owner's approval: OPEN.
The search-engine behaviour of every path is explained in SEO for translated pages.