Lingvit
  • Squarespace
  • Wix
  • No-Code

Squarespace and Wix multilingual: how to translate your no-code site (2026)

7 min read

Squarespace and Wix are two of the most popular no-code website builders — but their multilingual stories are very different, and neither gives you truly automatic translation out of the box. Here's what each platform offers and how to fill the gap with a custom code injection.

Squarespace's multilingual options

Squarespace has no built-in multilingual support. There is no native feature for managing multiple language versions of your site inside the Squarespace editor. The workarounds available without third-party tools are:

  • Duplicate pages per language. Create a copy of every page, manually translate the content, and link a language switcher to the duplicated pages. Slow to set up, harder to maintain as content changes.
  • Separate Squarespace site per language. Some businesses run a separate Squarespace project for each language. This doubles (or quintuples) your subscription cost and makes content updates twice as painful.

A notable exception: Squarespace Commerce supports multiple currencies, but this is billing infrastructure — it does not translate any content on the page.

Wix's multilingual options

Wix is significantly ahead of Squarespace here. Wix Multilingual is a free feature available in the Wix dashboard that gives you a proper multilingual workflow:

  • Create language versions of any page and manage them in a side-by-side editor showing the original and translated content together
  • Each language gets its own URL structure managed by Wix (typically /fr/page or a subdomain)
  • A language switcher widget can be added directly to your Wix site from the editor

However, Wix Multilingual has a critical limitation: translation is manual. You type every translation yourself in the side-by-side editor. Wix does offer a machine translation add-on (paid), but it requires you to trigger translation per page and still leaves you managing the output in the editor.

The problem with both approaches

Squarespace: no native solution

Without a custom code solution, Squarespace multilingual means manually duplicating pages. Every content update — a pricing change, a new blog post, a product description — requires updating every language version by hand. This simply doesn't scale for sites with active content.

Wix Multilingual: manual translation at scale

Wix Multilingual is a real solution for small sites with stable content. For larger sites — or any site where content changes regularly — the manual translation overhead becomes the bottleneck. Publishing a new blog post means returning to the editor to manually translate it in every active language.

Neither platform gives you truly automatic translation — where new content is translated and published immediately, without manual intervention, for every language you've configured.

Adding Lingvit via custom code injection

Both Squarespace and Wix allow you to inject custom HTML and JavaScript into your site. This is how you add a script-tag translation solution without needing to rebuild anything.

Squarespace

  1. Create a Lingvit project

    Sign up at app.lingvit.com, create a new project, enter your Squarespace site's domain, and select your target languages. Copy the script tag from project settings.

  2. Open Code Injection in Squarespace

    In your Squarespace dashboard: go to Settings → Advanced → Code Injection. Scroll to the Footer section (labelled “Footer” — this injects before the closing </body> tag).

  3. Paste the script tag and save

    Paste the Lingvit script tag into the Footer Code Injection field and click Save. The script is now live on all published pages — no per-page steps needed.

Note: Squarespace's Code Injection works on published sites only — the script will not appear in the visual editor preview mode.

Wix

Wix requires Velo (formerly Corvid) — Wix's developer platform — to inject scripts.

  1. Enable Velo in the Wix editor

    In the Wix editor: click Dev Mode → Enable Velo in the top bar. This activates developer tools including the site.js file.

  2. Use a Custom HTML Embed widget

    In the Wix editor: Add → Embed → Custom HTML. Paste your Lingvit script tag into the HTML embed. Position it at the bottom of the page. This approach works without Velo and is simpler for non-developers.

  3. Publish your Wix site

    Publish the site. Lingvit will begin translating on the first visitor request for each language and cache results for subsequent visitors.

What Lingvit translates on no-code sites

Lingvit works at the rendered DOM level — it translates whatever text the browser actually displays on the page, regardless of how the site was built.

Supporting data for Squarespace and Wix Multilingual: How to Translate Your No-Code Site (2026), table 1 of 2
Content typeTranslated?
Headings and body textYes
Navigation linksYes
Button labelsYes
Footer textYes
Wix Stores product names and descriptionsYes (rendered to DOM)
Images and videoNot translated (alt text is)

Scroll horizontally to view every column.

SEO considerations

Runtime translation and multilingual SEO are separate concerns. For search visibility, use the locale publishing features provided by Squarespace, Wix, or another routing layer:

  • Platform-owned hreflang tags

    Configure hreflang in the platform that renders your crawlable locale URLs. General Lingvit runtime translation does not inject those tags at launch.

  • URL routing per language

    Use your platform to publish locale URLs such as /fr/ or /de/. Confirm the rendered language, canonical, and reciprocal hreflang before requesting indexing.

  • Translated meta titles and descriptions

    Page <title> and meta description are translated for each language, so search results in the target market show the correct localised snippet.

Important note for Squarespace users: the custom code injection is only active on the published version of your site. Test your multilingual setup on the live domain, not in the Squarespace editor preview.

Wix Multilingual vs Lingvit

Supporting data for Squarespace and Wix Multilingual: How to Translate Your No-Code Site (2026), table 2 of 2
FactorWix MultilingualLingvit
Translation methodManual (type each translation in editor)Automatic + overrides
New content handlingManual update required per pageTranslated automatically on first request
Per-language CMS entriesYes (full Wix CMS integration)No (operates on rendered HTML)
Setup timeHours to daysGuided script setup
CostFree (MT add-on is paid)Monthly or annual plans with word capacity and monthly generation

Scroll horizontally to view every column.

Choose Wix Multilingual if you want translations fully inside the Wix editor with per-language CMS entries and editorial control over every string before publishing.

Choose Lingvit if you want automatic translation with zero manual work per page — every page translates automatically, including new content published after setup.

Frequently asked questions

Does Lingvit work with Squarespace templates?

Yes. Lingvit works at the DOM level on the published site, not inside the Squarespace editor. It translates whatever text is rendered in the visitor's browser regardless of which Squarespace template you use — headings, body copy, button labels, navigation, and footer text are all captured.

Does it work with Wix Stores or Wix ecommerce?

Lingvit can translate eligible Wix Stores content rendered in the page, including product and cart text. Verify the checkout flow before publishing; hosted or restricted steps require Wix's localization features.

Does adding Lingvit affect Squarespace or Wix SEO rankings?

Lingvit runtime translation does not create separate indexable locale URLs or hreflang at launch. If multilingual search visibility is required, use the platform's server-rendered locale URLs and metadata, then validate the result in your search tools.