Translate a Squarespace website

Squarespace speaks one language.
Your customers speak two.

Squarespace has no built-in way to translate the text you write. Its site language setting changes only its own words, such as checkout and form labels, and only into one language. To translate your site you either duplicate your pages and translate them by hand (any plan, 7.0 or 7.1), connect Weglot, the integration Squarespace’s Help Center recommends (7.1 only, free up to 2,000 words in one language), or add a translation script through Code Injection (Core plan and up). Below: each route step by step, what each one can reach in your cart, checkout and emails, and a word counter for your site.

Compare the routes Count my words
Built-in content translation: none Weglot: 7.1 only Checked 31 Oct 2026

By the Builderify team

Illustration · Not Squarespace’s interface. Your text can switch; checkout takes its language from Squarespace.
01 / The three routes

Does Squarespace support multiple languages?
For its own words, yes. For yours, no.

The site language setting (Site Languages on 7.1, Language & region on 7.0) sets the language of Squarespace’s built-in text: the checkout page, the “Order Confirmed” message, notification emails, form labels such as “First Name” and “Submit”, and date formats. Squarespace says plainly that it doesn’t translate text you add yourself: text blocks, page and post titles, categories or tags. There is one site language per site, from English, French, German, Italian, Korean, Portuguese and Spanish, plus Danish, Dutch, Finnish, Japanese, Norwegian and Swedish on 7.1.

  1. 01
    Any plan · 7.0 and 7.1

    Duplicate your pages

    A second set of pages per language, in its own navigation dropdown, translated by hand. Free, and each page is a real page search engines can index.

    Most work, full control, built-in text stays in one language.

  2. 02
    7.1 only

    Connect Weglot

    Squarespace’s recommended integration, connected from the language settings. It translates automatically, adds a switcher, and with a custom domain gives each language its own subdomain.

    Least work; free up to 2,000 words in one language.

  3. 03
    Core, Plus, Advanced

    Add a script tool

    A translation tool’s script pasted into Code Injection, which swaps the text in the visitor’s browser. Builderify Translations works this way on Squarespace.

    Quick to add; the translations are not separate pages in Google.

Old tutorials embed the Google Translate dropdown through Code Injection. Google ended support for that widget on 1 October 2026; here is how to take it off and what replaces it. For the general method on any platform, including the SEO side, see how to translate a website into Spanish.

02 / Duplicate pages

How to make a bilingual website on Squarespace
by hand, on any plan.

Squarespace’s own article on the manual method describes a language-choice homepage and one navigation dropdown per language, each holding a full copy of your pages. It is the only route on 7.0 sites, and the only one where each translated page is a page you wrote, with its own address and SEO title, that Google can index on its own.

  1. 1

    Finish the site in your first language

    Translating is copying, so every later change has to be made twice. Delete demo pages first.

  2. 2

    Make a language-choice homepage

    Add a blank page, move it to Not linked in the Pages panel and set it as the homepage. It will carry one button per language. A visitor who lands deep in the site never sees it, so keep a language link in the navigation too.

  3. 3

    Add one dropdown per language

    In the main navigation, add a dropdown named for each language, such as English and Español. On 7.0 it is called a folder. Put your existing pages in the first; its first page becomes that language’s landing page.

  4. 4

    Duplicate each page into the second dropdown

    Duplicate every page in the same order and translate the text, the buttons and any form labels you typed yourself. Use the page’s gear icon to give it a translated title.

  5. 5

    Give each copy its own slug

    In the page settings, change the URL slug. Squarespace allows only letters, numbers and dashes, so a slash such as /es/clases isn’t possible; use /es-clases or simply /clases. Slugs must be unique, and cart and checkout are reserved.

  6. 6

    Write the SEO title and description in each language

    Page settings, SEO tab, on every copy. The homepage takes the site-wide SEO description instead, which is one more reason the language-choice page is short.

  7. 7

    Link the homepage buttons and publish

    Point each button at the first page of its language, then open the site in a private window and click through both dropdowns.

Pages panel, after
Main navigation
  • English (dropdown)
    • /classes
    • /teachers
    • /contact
  • Español (dropdown)
    • /es-clases
    • /es-profesores
    • /es-contacto
Not linked
  • / homepage: two buttons

7.1 and 7.0 differ in three places

  • Navigation: dropdowns on 7.1, folders on 7.0. On 7.0 you can also use an index page as one scrolling page per language, or a cover page as the language picker.
  • Site language list: 7.1 offers six more languages for built-in text than 7.0.
  • The way out: Weglot connects only on 7.1, so a 7.0 site is manual or script-based until it moves.

The limits, from Squarespace

  • Built-in text, checkout included, shows in one language for the whole site; so do blog post dates.
  • One currency per store.
  • No separate domain or subdomain per language on one site. A separate site per language allows both, billed as separate sites.

Is a translated copy duplicate content?

No. Google says localized versions are only considered duplicates if the main content stays untranslated. A Spanish page with an English body is the risk; so is translating only the menu and buttons, which Google calls a poor experience.

Will Google find the Spanish pages?

Probably, through your navigation. Google says it may find language versions without help, and recommends telling it with hreflang links. Each version must list itself and every other version, or the links are ignored.

Can I add hreflang on Squarespace?

Only as code. Each page has its own header Code Injection (gear icon, Advanced), which needs the Core plan or above, and every pair of pages needs matching links both ways. On a large site that is a lot of hand-kept code. Weglot’s language subdomains add these tags automatically, which is the setup Squarespace recommends on 7.1.

Should I send Spanish speakers to the Spanish pages automatically?

Google advises against automatic redirection by guessed language. Link the two versions and let people choose.

03 / Weglot

Squarespace multilingual with Weglot:
how the integration works.

Weglot is a separate company with its own account and plans. Squarespace’s Help Center recommends it for 7.1 sites and documents the connection. Your translations live in Weglot: you edit them there, not in Squarespace.

Connect it (7.1)

  1. 1Open Site Languages, and under Multilingual by Weglot click Connect, then Allow.
  2. 2Create a Weglot account, or sign in and create a new project if you already pay for a plan. Squarespace advises against using a free or expired trial account here, as it limits the word count.
  3. 3Choose your original language and the languages to translate into, then Save. A language switcher appears in your header.
  4. 4Open the site in a private window, switch language and browse your pages; that is what generates the translations you then edit through Edit Translations.
  5. 5With a custom domain, click Setup Subdomains and add the CNAME records Weglot shows you, such as es, in your domain’s DNS settings.

What it does, and what it can’t

  • With subdomains, each language gets an address such as es.yourdomain.com, served through the CNAME record that points at Weglot, with hreflang tags added automatically.
  • Translated checkout and error messages, which the manual route can’t do.
  • Customer notification emails in the language the customer browsed in, on by default.
  • Without subdomains, Squarespace says some elements such as error messages may stay untranslated and pages may switch language slightly slower.
  • Not translated: Email Campaigns, Acuity Scheduling, third-party content blocks such as the map, and Member Sites and customer account login screens.
  • Disconnecting it in Extensions doesn’t cancel a paid Weglot plan; you cancel that with Weglot.
Weglot plans, from its pricing page on 31 October 2026
Weglot plan Words Languages Monthly
Free 2,000 1 €0
Starter 10,000 1 €15
Business 50,000 3 €29
Pro 200,000 5 €79
Advanced 1,000,000 10 €299
Extended 5,000,000 20 €699

From Weglot’s pricing page on 31 October 2026, prices before VAT, billed monthly; yearly billing costs ten times the monthly price. Words are unique words across all your languages, so two languages count twice. On the free plan, translations stop showing once you pass the cap; on a paid plan, only new words stop. Translated URLs start at Pro. Squarespace describes a ten-day trial of up to 10,000 words in one language.

04 / A script tool

Translate Squarespace with a script,
through Code Injection.

Any translation tool that installs with a script tag goes in the same place. Code Injection is on the Core, Plus and Advanced plans and some legacy plans; Basic has none. The path is Pages › Custom Code › Code Injection on 7.1 and Settings › Advanced › Code Injection on 7.0. Paste into Header, which goes in the <head> of every page, and save.

Two rules from Squarespace hold for every script: checkout pages don’t support code, so no script runs there, and Squarespace support won’t help with custom code. The same placement is how live chat goes onto Squarespace, and how A/B tests run there.

Builderify Translations on Squarespace

  • One script tag in Header, the same one that carries every other Builderify module
  • Training mode collects your copy as people browse, once per phrase for the whole site
  • You translate in a workbench, per language; AI drafts wait as drafts until you confirm them, unless you choose otherwise
  • 27 languages, with Arabic and Hebrew switched to right-to-left
  • The page title, meta description and share-card tags translated too, with alt text and placeholders (on by default)
  • A link ending in ?lang=es opens the page in Spanish, and the choice is remembered
  • Text that loads after the page has opened is translated as it appears

Know this first

  • Not separate pages in Google. The text is swapped in the visitor’s browser, with no language URLs and no hreflang, so don’t expect the Spanish to be indexed as its own pages. For Spanish pages in search, use the manual route.
  • Checkout runs no custom code, so it stays in your site language.
  • Pages whose address contains cart, checkout, account or order are never read for training, as they can hold a shopper’s details.
  • Squarespace’s emails are sent by Squarespace, not shown in a browser, so a script can’t reach them.
  • Needs Core or above, like every script.

The full module, with every language in its catalogue, is on the Translations page. What a translation project costs across tools, people and plugins is in the website translation cost guide.

05 / Cart, checkout, emails

The parts Squarespace writes for you:
which route reaches each one.

Your text blocks are the easy part. A shop also has a cart, a checkout, form defaults and emails that Squarespace generates, and that is where the routes differ most. If you sell, decide here.

What each translation route can translate on a Squarespace site
Part of the site Duplicate pages Weglot Builderify script
Your text, buttons, menus YesYou write it YesAutomatic, then edit YesOnce approved
SEO title and description YesPer page, SEO tab PartlyNot detailed by Squarespace YesIn the browser only
URL of each language YesYour own slugs YesSubdomain with a custom domain; translated slugs from Pro NoSame address, or a ?lang= link
Form fields you labelled YesRetype on the copy YesSite content YesLabels and placeholders
Built-in form text, dates PartlySite language only PartlyNot detailed by Squarespace PartlyOnly text shown on the page
Cart page PartlySite language only PartlyNot detailed by Squarespace PartlyOnly phrases known from other pages
Checkout PartlySite language only YesTranslated NoNo code runs there
Order and notification emails PartlySite language only YesIn the shopper’s language NoSent by Squarespace
Email Campaigns NoWrite a second campaign NoExcluded NoNot a web page
Third-party blocks, Acuity, member logins PartlyAcuity has its own language setting NoExcluded PartlyNot inside embedded frames

Duplicate pages and Weglot from Squarespace’s Help Center on 31 October 2026; “Not detailed” means its Weglot article doesn’t say either way. Builderify from how its snippet works. “Site language only” means one language for the whole site, set in Site Languages.

A practical split for a bilingual shop on the manual or script route: set the site language to the language most of your buyers check out in, and say on the product pages which language the checkout and receipts use.

06 / Word counter

How many words is your Squarespace site?
Count them before you pick a plan.

Paste a page’s text (select all on the live page, copy, paste), or type a list of pages with their word counts. It shows the words and strings you would translate, checks them against Weglot’s free plan, and estimates Builderify’s page-load credits. Nothing is fetched or sent anywhere.

Weglot cap: 2,000 words in 1 language, from its pricing page on 31 October 2026. Change it if Weglot does.

55
Words
52
Without repeats
9
Strings
52
Words × languages

Measured: 5.8 words per string. Type that into the page list for the rest of the site. 0 pages read, lines without a word count skipped.

Weglot free plan
52 / 2,000

52 words in 1 language: inside Weglot’s free plan of 2,000 words.

Builderify

9 strings to review in the workbench (strings × languages).

3,000 page views use 30 credits a month, inside the 250 free credits.

Starter
$0.00
Growth
$0.00
Pro
$0.00
Business
$0.00
Scale
$0.00

Cost of the credits above the free 250 a month at each one-time pack’s rate (10 credits per 1,000 page loads, from pricing). Not included: AI drafts, which are charged in credits based on what the AI model used.

Words

Every space-separated run with a letter or digit in it. Lines that repeat, such as a menu pasted twice, count once in “without repeats”, because both Weglot and Builderify store a repeated sentence once. In the page list, the words on every page are taken off all but the first page.

Strings

Builderify collects one string per block: a heading, a paragraph, a list item, a button or a link, with any bold text or links inside it kept together. Pasting a page puts each block on its own line, so each different line with a letter in it counts as one. For a page list there is no text to read, so the words are divided by your words per string; paste one page to measure yours.

Languages

Weglot counts words across all your languages, so two languages double the total. Your original language doesn’t count. Text in Chinese, Japanese or Thai has no spaces between words, so this counter undercounts it.

07 / Test it

Check the translated Squarespace site
the way a customer and Google will.

  1. 01

    Browse in a private window

    Logged out, so you see what visitors see. Switch language on three or four pages and on your phone, and look for leftovers in the header, footer and buttons.

  2. 02

    Open a language link directly

    Manual: the Spanish page’s own address. Weglot: the language subdomain. Builderify: any page with ?lang=es on the end. Each should open in Spanish without a click.

  3. 03

    Run a test order

    Add to cart, go to checkout and read every screen and the confirmation email. That shows you which language Squarespace uses for the parts no script reaches.

  4. 04

    Send a form to yourself

    Check the labels, the error message on an empty required field and the thank-you message, in each language.

  5. 05

    Look at the page as Google gets it

    View the page source: text that is still in English there is what a search engine is sure to read. For the manual route, use URL Inspection in Search Console on a Spanish page, and check its hreflang links point both ways.

  6. 06

    Recount after changes

    New pages add words. On Weglot’s free plan, going over the cap stops translations showing; Weglot emails you when you reach it. In Builderify, a sentence you edit comes back as a new string to translate, so the old translation no longer applies to it.

If

You want Spanish pages that rank in Google, and the site is small or on 7.0.

Pick

Duplicate pages. Free on any plan; the work is yours, and checkout stays in one language.

If

You are on 7.1, sell online and want checkout and receipts translated.

Pick

Weglot. Free under 2,000 words in one language; the counter above tells you which plan your site needs.

If

You are on Core or above, want visitors to read the site in their language now, and don’t need the translations in Google.

Pick

A script tool such as Builderify Translations. One snippet, translations you approve, and the same snippet can carry more popups than Squarespace allows or live chat. Coming from WordPress? The GTranslate alternative guide covers indexed translations there.

Builderify starts on 250 free credits a month; packs start at $9 for 1,000 credits, once, and never expire. See pricing.

Questions

Translating Squarespace, before you ask.

Not on its own. The site language setting changes only Squarespace's built-in text, such as checkout, notification emails and form labels, and Squarespace says it doesn't translate text you add yourself. For automatic translation, its Help Center recommends connecting Weglot on version 7.1, or you can add a translation tool's script through Code Injection on the Core plan or above.

For a small site, yes: Weglot's free plan covers one language and 2,000 words, counted across all your languages. On the free plan, translations stop showing once the site goes over that. Its paid plans started at 15 euros a month for 10,000 words in one language on 31 October 2026, and the integration works only on Squarespace 7.1.

Duplicate your pages into a second navigation dropdown (a folder on 7.0), translate each copy, give it its own URL slug and SEO title, and link both languages from a short language-choice homepage. It works on any plan, but Squarespace's built-in text, including checkout, stays in one site language.

Duplicated pages you translate yourself are real pages Google can index, and Google does not treat them as duplicates when the main content is translated. Weglot's language subdomains add hreflang tags for you. Script tools that swap text in the browser, Builderify Translations on Squarespace included, give no separate language URLs, so do not expect those translations to be indexed as their own pages.

Squarespace checkout pages don't run custom code, so no script-based tool reaches them. With duplicated pages, checkout uses your one site language. Squarespace's Help Center says Weglot translates checkout and error messages, and sends customer notification emails in the language the customer browsed in.

Sources

Squarespace’s Help Center, Weglot’s pricing and help pages and Google Search Central, read on 31 October 2026.

← All guides

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.

Start free See what it does