Localizer.co

How to integrate Localizer with Webflow

What is Localizer? Localizer is a hosted translation service that reads the pages of a site you already run, stores the text it finds, and serves translated versions back through a single line of JavaScript. Translations can come from machine translation, from your own team working in its visual editor, or from paid human translators. Its published plans start at a free tier with 1 language and 2,000 words, move to a startup tier from $35 per month covering up to 5 languages and 1,000,000 words, and reach an enterprise tier from $250 per month.

Before you install anything, work out how much of this job Webflow already does for you. Webflow Localize is a native localization product that translates on-canvas text and Collection items, keeps separate SEO fields per locale, and publishes each locale to its own subdirectory. That covers most of what a translation overlay used to be hired for, so the honest case for a third-party script is narrower than it was, and worth stating precisely.

The order below reflects that. Start by weighing native Localize against an overlay, because the answer decides whether you need Localizer at all. If you do, installing the snippet is one paste into your site's head code. Teams running several locales at volume then hand the repetitive work to the Webflow API and MCP server.

Weigh native Localize against a script overlay

Webflow Localize handles the core of multilingual publishing inside the product you already build and publish from, which removes the main reason teams used to reach for an overlay. Here is what you get natively before any third-party tool enters the picture.

• Translation that matches your source tone: Webflow's automated translation reads the tone and formality of your primary locale and reproduces it in the target language, and you can set that per target language.
• CMS as well as canvas: Text elements, links, buttons and forms translate on the canvas, while Collection content translates a whole item at a time or field by field.
• Terminology you control: A custom translation glossary pins how brand names, product names and other repeated terms come out in each language.
• SEO fields per locale: Every locale gets its own page settings, and Webflow writes hreflang into the page head and into the auto-generated sitemap without you configuring it.
• Cost: Localize add-on pricing is $9 per month for Essential, covering 1 to 3 locales, and $29 per month for Advanced, covering up to 10, both sold as Site plan add-ons. You can preview Localize for free on any plan and pay only when you publish.

That leaves one documented gap, and it is the reason this page still has a job. Localize does not support Ecommerce Site plan features, so products, categories and pages cannot be localized when both are enabled. If you run a Webflow Ecommerce store that has to read in more than one language, a script layer sitting above the rendered page is still the practical answer, and Localizer is one of those. ConveyThis works the same way.

Be deliberate about the SEO consequence, because the two setups are not the same shape. A natively localized Webflow site publishes each locale as a subdirectory under your existing domain, with Webflow generating the hreflang signals for it. Localizer's feature page says it serves content for a language under a different domain or subdomain with localized meta tags, which is the vendor describing its own product rather than anything measured here. Both arrangements can be indexed. What you are really choosing is where your translated URLs live, so choose it on purpose instead of inheriting it from whichever tool you install first.

Add the Localizer snippet to Webflow's head code

Installation is a single paste with no build step. Localizer publishes a Webflow-specific snippet that queues itself behind Webflow's own script loader and skips execution while the site is open in the Editor.

<script>
var Webflow = Webflow || [];
Webflow.push(function () {
  if (!window.WebflowEditor) {
    $.ajax({
      type: 'GET',
      url: '//secure.localizer.co/Replacer/?siteId=000000000',
      dataType: 'script',
      cache: true
    });
  }
});
</script>

To add it to your site:

1. Copy the snippet from your Localizer dashboard and swap the placeholder site ID for yours.
2. Open Site settings in Webflow and go to the Custom code tab.
3. Paste it into the head code field.
4. Save your changes, then publish the site.

Two details in that snippet decide whether it behaves. Webflow.push defers the request until Webflow's script queue is ready, and the window.WebflowEditor check stops the translation layer from rewriting text underneath someone editing content. The request itself uses jQuery's $.ajax, so confirm jQuery is present on your published site rather than assuming it. Localizer's Webflow walkthrough also carries a 2016 update date, so read its menu names as a rough guide and follow the labels currently in Webflow.

Manage locales with the Webflow API and MCP server

Localizer does not document a public API on its site, so anything you automate around this integration happens on the Webflow side. The Webflow API covers the rest of the surface, and its localization endpoints read and write CMS items per locale, which is what you need when translated content has to arrive from a pipeline rather than a person.

The Webflow MCP server puts the same work in plain language for an agent. It reads and updates existing CMS items and static content in secondary locales, and Webflow documents that it cannot create new localized CMS items, so plan for the item to exist before an agent translates it rather than discovering that mid-run.

Set the guardrails up before you point an agent at a multilingual site. Agent instructions can reference the site's own locales, so the rules you write apply per language. Anything an agent does stays inside your existing permissions and roles, and the site activity log records what changed, which is how you audit a translation pass that touched every locale at once.

What you can build with the Localizer Webflow integration

This combination earns its place where Webflow's native localization stops, or where you want a language live before you commit to building it properly. Four uses come up repeatedly.

• Multilingual Ecommerce storefronts: Serve a Webflow Ecommerce catalogue in several languages by translating the rendered page, which is the one case native Localize does not cover.
• Fast market tests: Put a landing page into a new language in an afternoon to find out whether demand is real, before paying for a locale you build properly.
• Translated support hubs: Keep a large, frequently changing help library readable in other languages by letting new content get picked up automatically instead of queued for a manual pass.
• Region-specific pricing and messaging: Pair currency conversion and language triggers with per-locale copy so numbers and offers read correctly for each audience.

If your translation layer needs to go on at publish time rather than by hand, see how to apply custom code via API across your Webflow pages.