ConveyThis

Webflow Localize now handles most multilingual work natively: AI translation of on-canvas text and Collection items, per-locale SEO settings, automatic hreflang tags, and locale subdirectories. One gap stayed open. Localize does not support Ecommerce Site plan features, so products, categories, and pages cannot be localized on a store.

ConveyThis fills that gap with script-based translation that runs on top of the published site, whatever is on it. One tag in your head code translates every page, adds a language switcher, and serves each language from its own indexable URL.

This suits Webflow Ecommerce stores that Localize cannot reach, agencies running one translation account across several client domains, and teams that need a longer language list than the Localize add-on tiers cover. Developers can drive both platforms' APIs into a custom localization pipeline.

How to integrate ConveyThis with Webflow

What is ConveyThis? ConveyThis is a website translation platform that adds machine translation and a customizable language switcher to an existing site, with multilingual SEO handled automatically. It supports 210 languages and runs on Webflow, WordPress, Shopify, Squarespace, Wix, and any JavaScript site. You manage translations from a dashboard with a visual editor, a text editor, a glossary, and an option to order human translation. It meters usage in machine-translated words, starting at 5,000 words and one language on the free tier, with paid tiers adding languages, domains, and word allowance.

Before wiring anything up, work out which side of the line your site sits on. Webflow Localize now does AI translation of text elements and Collection items, per-locale SEO fields, and automatic hreflang in both the page head and the sitemap, as a Site plan add-on from $9 per month for up to three locales. Off Ecommerce, that native path produces content that lives in Webflow and renders from Webflow, and a script overlay cannot match it for editing or for indexing. ConveyThis earns its place where Localize will not run at all, where you need more languages than the add-on tiers cover, or where a client site has to go multilingual this week without touching the build.

The ConveyThis and Webflow combination has three working paths. The MCP servers on both sides let an agent check translation coverage and write site changes from your editor. The ConveyThis JavaScript snippet handles site-wide translation, the switcher, and multilingual SEO with no code beyond one tag. The Webflow and ConveyThis APIs give you control over translating pages and CMS items into Webflow locales, and require server-side development. Most sites run the snippet alone; the API path matters when translations need to live inside Webflow itself.

Connect the ConveyThis and Webflow MCP servers

Both platforms ship an MCP server, and between them they cover the two halves of a multilingual Webflow site: what still needs translating, and what needs changing on the site. Install the snippet first, because ConveyThis has nothing to report until it is running.

The ConveyThis MCP server is read-only. Query-only keys let an agent read projects, languages, translated strings, glossary terms, and word usage, and they cannot publish pages, edit live copy, delete translations, or change billing. It is a Streamable HTTP endpoint that works with any client accepting bearer tokens, with per-client configs for Claude Code, Cursor, VS Code, Cline, Windsurf, and MCP Inspector.

The Webflow MCP server writes. An agent can read and update existing CMS items and static content in secondary locales, manage site and page custom code, and update meta titles and descriptions across pages, all inside your existing Webflow permissions and roles, and the site activity log records every change it makes. One documented limit matters here: the server cannot create new localized CMS items, only read and update ones that already exist.

Pairing the two means you can ask which pages are still untranslated and then fix the Webflow side in the same session, without exporting a CSV or opening two dashboards.

Add the ConveyThis snippet to your site's head code

The JavaScript snippet is the official ConveyThis integration path for Webflow. You paste one script tag into your site's head code, and every published page becomes translatable with no changes to layouts or classes. The snippet needs custom code access, so the site needs a paid Site plan or a paid Workspace plan; the free Starter plan leaves out custom code in head and body tags. Each custom code section holds up to 50,000 characters, far more than one script tag needs.

To set up the integration:

1. Create a ConveyThis account, select Webflow as your website technology, enter your domain, and choose target languages.
2. Copy the generated snippet: <script src="//cdn.conveythis.com/javascript/conveythis.js?api_key=YOUR_API_KEY"></script>
3. In Webflow, open Site settings > Custom code, paste the snippet into the Head code section, and save.
4. Publish the site and refresh the live page. The language switcher appears at the bottom right within a few minutes.

Once the snippet is live, these features run without further code:

• Site-wide machine translation: ConveyThis translates page content on load, including AJAX responses and DOM updates as they happen.
• Language URLs and hreflang: Each language gets its own subdirectory or subdomain URL, with hreflang tags and translated meta titles and descriptions.
• Switcher customization: Colors, flags, position, and custom CSS all change from the ConveyThis dashboard without touching your Webflow build.
• Visitor redirection: Visitors land on the language their browser prefers rather than the default locale.
• Editing and glossary control: A visual editor and a glossary let you correct machine output and lock brand terms across every language.

Content that other JavaScript injects into the page may escape translation, so check any script-rendered sections before launch.

Place the language switcher in your navigation

The switcher defaults to the bottom right of every page. Placement matters when that default badge sits awkwardly against your design or covers a fixed element. The positioning guide shows how to attach it to any element with an ID, including your navbar.

To move the switcher:

1. In Webflow, give the target element an ID, for example menu.
2. In the ConveyThis dashboard, go to Domains > your domain > General Settings > Settings > Positioning.
3. Set the position type to Custom and enter the element ID without the # symbol, so menu rather than #menu.

The switcher then renders inside that element on the live site, and you can style the surrounding container in Webflow like any other nav item.

Build with the Webflow and ConveyThis APIs

For programmatic control, translate content with the ConveyThis REST API and write the results into localized pages and CMS items with the Webflow Data API v2. This path requires server-side development and a server of your own to run it on.

Four pieces make up the pipeline:

• ConveyThis translation endpoint: The ConveyThis API translates arrays of text segments, reports API status, and confirms whether a language pair is supported.
• Webflow localization endpoints: The Data API v2 localization endpoints read and write page and Collection content per locale.
• Webflow webhooks: Webhooks fire events such as collection_item_changed and site_publish, so translation runs when content changes.
• Authentication: ConveyThis takes an api_key in the JSON request body, while the Data API uses OAuth scopes such as pages:write and cms:write.

Nothing about this loop is prebuilt: any automation between the two platforms is code you write and host yourself.

Translate static pages into secondary locales

The page localization endpoints read a page's DOM and write translated content into secondary locales. Choose this path when translations need to live inside Webflow locales rather than in an overlay. The primary locale stays editable only in Webflow.

To translate a static page:

1. Call GET /v2/sites/{site_id} and read the locales object; each secondary locale returns its identifier as id, which you pass as the localeId to the page endpoints.
2. Fetch page content with GET /v2/pages/{page_id}/dom and extract the text nodes.
3. Send those strings to POST https://api.conveythis.com/translate/ with api_key, referrer, target_language, and segments in the body.
4. Write results back with POST /v2/pages/{page_id}/dom and pass the secondary locale's localeId. Each request accepts up to 1,000 nodes.
5. Update localized SEO metadata with PUT /v2/pages/{page_id}.

The DOM endpoint returns content only for static pages; Collection template pages come back empty.

Localize CMS items

The CMS localization endpoints let you read and update Collection items per locale, so translated blog posts and product descriptions live inside your Webflow CMS collections.

To localize CMS content:

1. Get the target locale's cmsLocaleId from GET /v2/sites/{site_id}.
2. List items with GET /v2/collections/{collection_id}/items and pass the cmsLocaleId.
3. Translate the text values in fieldData through POST https://api.conveythis.com/translate/.
4. Update items with PATCH /v2/collections/{collection_id}/items and include cmsLocaleId in the body, then publish with POST /v2/collections/{collection_id}/items/publish.

Adding a secondary locale to an existing CMS item happens in the Webflow CMS panel, because that action is not supported through the API.

Automate translation on content changes

For automation, register Webflow webhooks with POST /v2/sites/{site_id}/webhooks. ConveyThis documents no webhooks of its own, so Webflow drives the loop.

To build the loop:

1. Register a collection_item_changed or site_publish webhook pointing at your server.
2. When the event fires, read changed text from the payload's fieldData, or fetch it with GET /v2/pages/{page_id}/dom.
3. Submit the strings to POST https://api.conveythis.com/translate/ and write results back to the matching locale.

The collection_item_deleted payload carries the item's id, collectionId, and cmsLocaleId, so you can tell which item and locale went away and clear the matching translation.

Inject the snippet across multiple sites

Agencies managing several client sites can push the ConveyThis script tag programmatically instead of opening each site's settings, using the site custom code endpoint.

To deploy at scale:

1. Authorize your app with the custom_code:write scope.
2. Call PUT /v2/sites/{site_id}/custom_code with the ConveyThis script tag for each site.
3. Publish each site so the change goes live.

One ConveyThis account can cover several client domains on the higher plans, which fits this multi-client workflow.

What you can build with the ConveyThis Webflow integration

Integrating ConveyThis with Webflow gives you a multilingual site from a single Webflow project, with no duplicated pages and no separate build per language. The builds below are the ones where the overlay approach still beats the native path.

Four patterns come up most often:

• Multilingual Webflow Ecommerce stores: Translate product titles, descriptions, category pages, and checkout on a store that Webflow Localize cannot localize at all.
• Bilingual regional sites: Serve English at the root and French from a /fr/ subdirectory in one project, with the switcher docked in your navbar instead of floating in the corner.
• Language coverage past the add-on tiers: Publish into more languages than the Localize plans cover, which matters on support and documentation sites where breadth beats per-locale polish.
• Multi-client agency rollouts: Run several client domains from one ConveyThis account and push the script tag through the custom code API rather than opening each site's settings.

See how to apply custom code through the Data API to script that last one across a whole client portfolio.