Generate a live translated preview, estimate localization effort, and launch multilingual pages without changing your codebase.
Smartcat’s website translator makes your existing site multilingual without engineering work. One JavaScript snippet renders translated pages live.
Your team reviews them on the real page in a visual in-context editor before anything goes live.
Every new locale used to mean an engineering ticket: duplicate the templates, wire up the routing, rebuild the nav.
Then the site changed on Tuesday and the Spanish version fell three releases behind.
Same work, five steps, your team in control.
From URL to live markets
1
Paste your URL into the preview widget above and see your site translated before you commit.
2
Pick your pages and markets — crawl the whole site, import your sitemap, or hand-pick URLs.
3
Get the AI draft — Smartcat translates every page and applies your terminology automatically.
4
Review on the live layout — check translations in place in the visual in-context editor, on staging or production, solo or with your team. Promote each market when it's ready.
5
Publish and forget — later changes are detected and translated automatically, and only net-new words are metered.
Only if search engines can crawl and index the translated pages — which is where most quick fixes fail.
The old Google Translate widget translated pages in the visitor's browser only: Google never indexed those translations, and it has since deprecated the widget for new sites.
Here is how Smartcat handles the three things that decide whether a translated site ranks.
2
Serving Modes: Readable, Then Findable
Default — the JS snippet: translations render in the visitor's browser. Fastest way to go live, and all a staging, internal or non-public site needs.
Optional — the SEO Proxy path, enabled separately, is the mode that serves crawlers.
The snippet makes your site readable in 280+ languages; the proxy path makes it findable. Both run from the same translations, and most teams want both.
Auto
Reciprocal Hreflang, Generated for You
Hreflang is generated by default, whatever URL or proxy setup you choose — including the reciprocal return links hand-built implementations usually miss.
Translated titles, meta descriptions and Open Graph tags come with it, so your French search result reads in French — and so does the share preview.
3
URL Structures to Choose From
A subdirectory (yoursite.com/fr/), a subdomain (fr.yoursite.com), or a Smartcat proxy hostname — plus default snippet mode, which leaves your URLs untouched.
Smartcat never touches your DNS or your web server.
The accuracy and quality of translations noticeably improved over the four months of using Smartcat’s AI translation capabilities. Consistency in brand and product terminology across translations is a notable benefit.
”Explore Case Study →
Proxies are a legitimate architecture — they solved this problem first, and Smartcat uses a proxy layer too. The difference is where it sits.
Your Visitors’ Traffic Never Routes Through Us
Translations are fetched browser-side, with no server-to-server hop and no Smartcat proxy in front of your visitors.
The optional SEO Proxy path covers crawler and SEO delivery only; staging, intranet and gated sites never touch it. Your pages stay served by your own infrastructure, under your own DNS, hosting and CDN.
Where This Falls Short — Honestly
• Content behind a login is not picked up by page translation alone
• Text baked into images needs the image translator
• App UI strings belong in a software localization workflow
• If your site is mostly application, talk to us before you wire anything up
If your content lives in a CMS, translate it at the source instead — content pushes to Smartcat and translations come back into native locale pages, with updates syncing automatically.
Ready-made integrations cover the most widely used platforms, including WordPress, Drupal, Contentful, Adobe Experience Manager, Sitecore, Webflow, Wix and Squarespace. See all integrations.
Keep multilingual WordPress pages current with live updates, preserved approvals, and less repeat localization work.
Extend the same market-ready workflow to help content and support journeys that shape the customer experience.
Launch localized Wix experiences faster while keeping content, layout, and approvals aligned across markets.
Trigger website localization from Contentful and push only net-new changes through translation, review, and publish.
Localize product content with fewer repeat cycles by translating only updated catalog data.
Run staged multilingual Drupal launches with centralized review and automatic reuse of approved translations.
Publish multilingual Ghost content faster with live-ready copy and preserved editorial decisions.
Test and ship multilingual landing pages quickly while keeping campaign approvals and updates in sync.
Localize landing pages for each market and keep test variants moving without restarting review from zero.
Keep multilingual Weebly pages aligned with your source site while Smartcat applies only the changes that matter.
Maintain design integrity and search-ready copy while launching Squarespace content for more markets.
Move Webflow pages from source update to staged multilingual launch with faster approvals and less manual rework.
Launch multilingual acquisition pages faster and keep localized variants aligned with campaign changes.
Move from design-led websites to live localized experiences with reusable approvals and less manual cleanup.
Localize storefront pages and product updates while protecting approved commerce content and SEO structure.
Keep global storefront content current by translating only new changes and pushing launches faster across regions.
76% of consumers prefer purchasing products with information in their own language (CSA Research, survey of 8,709 consumers in 29 countries).
Smartcat fits teams that need multilingual launch speed, reviewer control, predictable cost on a living site, and infrastructure that stays under their own DNS, hosting and CDN.
for ease of setup, on G2
for ease of use, on G2
enterprise brands trust Smartcat
languages available as a source or a target
Paste your URL and see your site translated in the live preview, before you commit.
One snippet to go live, automatic hreflang and translated metadata, and an optional SEO Proxy path when you want those pages indexed.
The rate is the ordinary one: 1 Smartword ≈ 1 source word, per target language, with no website surcharge and no multiplier. What differs is what gets counted.
Website translation meters unique content fragments — titles, paragraphs, buttons, navigation, footer, hero — counting each once and reusing it everywhere it appears through the Smartwords cache. Your nav, your footer and the “Book a demo” button repeated across 400 pages are paid for once, not 400 times.
For contrast:
2–3 days
Turnaround, Down From 10
for Smith+Nephew, down from 10 days with their previous providers.
Up to 70%
Lower Localization Costs
for Stanley Black & Decker while maintaining quality and scaling output.
31 hours
Saved Every Month
for Babbel teams managing multilingual content operations.
Paste your URL, see your site translated in the live preview, and launch the markets that are ready. Free for 15 days with 15,000 Smartwords, no credit card.
A 1:1 walkthrough with a specialist on your actual website, no commitment — your CMS, your staging flow, your reviewer model, and whether you want the SEO Proxy path from day one.
Smartcat's Website Translator translates a whole site in three moves:
No rebuild, replatform or code changes are required, and unchanged pages are left untouched on later updates.
It is a website translation agent that translates your site and serves the translated pages to visitors automatically.
AI Coworkers translate net-new content, apply your terminology, and preserve translations your team has already approved instead of re-processing them.
Point Smartcat at the site and select English as the target language — the Website Translator translates the discovered pages and renders them live.
On each sync only net-new and modified content is translated, so an English version stays current without anyone re-translating pages that did not change.
No. The default mode is a JavaScript snippet that renders translations in the visitor's browser — added as a script tag or through Google Tag Manager, with no DNS work.
An optional SEO Proxy path can be enabled separately and serves crawlers only; it is never in your visitors' request path, unlike full-proxy translation tools. Internal and staging sites do not need it.
Yes, with Smartcat's SEO delivery enabled. It generates hreflang tags automatically and translates title tags, meta descriptions and Open Graph tags.
Crawler-visible translated URLs are served through the optional SEO Proxy path — the snippet alone renders for visitors in the browser, so enable SEO delivery when organic visibility matters.
Three options: a subdirectory (yoursite.com/fr/), a subdomain (fr.yoursite.com), or a proxy hostname.
Smartcat never touches your DNS or servers.
Any CMS — the JavaScript snippet is platform-agnostic and can also be deployed through Google Tag Manager.
Smartcat additionally offers ready-made integrations for the most widely used platforms, including WordPress, Drupal, Contentful, Adobe Experience Manager, Sitecore, Webflow, Wix, and Squarespace.
See all website translation integrations.
Accuracy comes from combining AI translation with your own assets — translation memory reuses approved wording and your glossary is applied automatically.
High-value pages route through the Smartcat Editor, where in-house reviewers or Marketplace linguists approve or refine each translation — and approved segments stay approved on later syncs.
No. Smartcat charges for net-new content — unchanged pages and approved translations are preserved rather than reprocessed, so recurring cost tracks how much your site actually changes.
A free trial includes 15,000 Smartwords over 15 days with full access to Smartcat's translation capabilities.