All 58 languages, in every tier
Tiers are sized by how much content you have, never by how many languages you want. The full set of 58 is translated on every tier.
Website translation
Your website in 58 languages
We translate your pages, posts, metadata and URL slugs into 58 languages, and serve each one on its own indexable URL with correct hreflang. Every language is included in every tier — the words are bought up front, so there is no per-language charge to add later. You decide which languages your visitors are shown, and switching one on takes effect immediately.
What it is
Website Translation is a pipeline rather than a one-off job. It reads your site and translates every visitor-facing string — page copy, post bodies, meta titles and descriptions, image alt text, breadcrumb labels and the URL slugs themselves — then publishes each language as a real, crawlable version of your site.
It is an SEO product as much as a translation product. Each language lives at its own URL, carries hreflang annotations pointing back to every sibling version, and appears in a per-locale sitemap, so a search engine can index your Spanish or Japanese pages exactly as readily as your English ones.
What you get
One pipeline, wired into the content lifecycle, covering the parts of a site that translation tools usually leave in English.
Translated, then served on your terms
Translating and serving are two separate things: everything is translated, and you choose which languages visitors actually see. Turning one on is instant, with no new order and no re-run.
Translated URL slugs
Each locale gets its own readable, keyword-carrying path rather than an English slug with a language prefix bolted on. Visitors and crawlers both see a native URL.
Metadata, not just body copy
Meta titles and descriptions, OpenGraph and social cards, JSON-LD schema text, image alt text and breadcrumb labels are all translated alongside the page.
Incremental re-translation
Edit a page and only the strings that actually changed are re-translated, automatically. Everything else is served from a content-hash cache, so a typo fix does not re-run your whole site.
hreflang and per-locale sitemaps
Every published language is annotated with hreflang links to its siblings and listed in its own sitemap, so search engines can discover and attribute each version correctly.
How it works
Three steps, and only the first one asks anything of you.
Connect your site
We crawl your content and count the words, which is what determines your tier. Nothing on your live site changes at this stage.
Translate everything
The pipeline translates every string into all 58 languages, including metadata and slugs, and caches each result against a hash of its source text.
Choose what visitors see
Publish the languages you want from your dashboard, in any order and at any time. Each one goes live on its own URL with hreflang and a sitemap entry already in place.
Pricing
One subscription per site, tiered by word count — a small site, a content-heavy site, and a large shop or enterprise site. Every tier includes all 58 languages, so the only question is how much content you have, not how far you want to reach.
Site Translation — Standard site
$19.00/month
Site Translation — Large or complex site
$59.00/month
Site Translation — Shop or enterprise site
$199.00/month
Tiers are sized by the number of translatable words on the site. There is no per-language charge and no charge for switching a language on.
Why buy it here
Most translation products bill per language, which quietly turns reaching a new market into a purchasing decision. We translate the whole set up front and let you publish on judgement rather than on budget — try a market, watch the traffic, keep it or hide it again.
The parts that decide whether a translated page ranks are the parts most tools skip: the slug, the meta description, the schema text, the hreflang graph and the sitemap. Those are handled here as a matter of course, and they stay in step automatically as you edit the source.
Do I pay per language?
No. Every tier includes all 58 languages, and pricing is set by the amount of content on the site instead. Switching a language on or off costs nothing and changes nothing about your subscription.
What is the difference between a language being translated and being served?
Translated means the words exist, stored and cached against your content. Served means visitors and search engines can reach that version at its own URL. Everything is translated; you decide what is served, and a language you have not published is simply not visible.
Will search engines index the translated pages?
That is the design. Each published language is server-rendered at its own URL, annotated with hreflang tags linking it to every sibling version, and listed in a per-locale sitemap. Crawlers see distinct, indexable pages rather than one page with a client-side language switcher.
What happens when I edit a page after it has been translated?
The changed strings are marked stale and re-translated automatically; untouched strings are served from cache. A small edit costs a small amount of work, so your translations do not drift behind your source content while you wait for a manual re-run.
Are the URLs translated too, or just the page content?
The slugs are translated as well, so each locale gets a native path rather than an English one behind a language code. Meta titles, meta descriptions, OpenGraph tags, JSON-LD schema text, alt text and breadcrumb labels are translated with the page.
How do I know which tier I need?
Tiers are set by translatable word count across the site: a brochure site, a content-heavy publisher, and a large shop or enterprise estate. We count your words when you connect the site, so you can see which tier applies before you commit.
Publish in every market you want
Connect a site, see its word count and tier, and publish your first additional language the same day. The other 57 are already translated and waiting behind a switch.
Get started