How to create a multilingual website on Squarespace
Creating a multilingual Squarespace website is possible, but the right setup depends on how much control you need, how much content you have, and whether SEO matters for each language.
There are three main ways to do it:
Use Weglot, Squarespace’s recommended multilingual integration
Manually create separate pages for each language
Use custom code or an older third-party multilingual plugin
For most Squarespace 7.1 sites, Weglot is the simplest option. For smaller sites, or sites where you already have your translations written, the manual method can also work. For more custom setups, you may need a plugin or developer.
Let’s walk through the options.
First: Squarespace Site Language Is Not the Same as a Multilingual Website
Squarespace has a site language setting, but this does not translate your whole website.
Changing your site language affects built-in Squarespace text, such as form labels, dates, navigation labels, checkout text, and other system-generated text. It does not automatically translate the text you wrote inside text blocks, page titles, blog posts, product descriptions, categories, tags, or custom content.
If you want more context on what Squarespace supports natively, read: Which Languages Does Squarespace Support?
So if you want your actual website content to appear in multiple languages, you need a multilingual setup.
Option 1: Use Weglot
Weglot is Squarespace’s recommended multilingual solution for Squarespace 7.1 websites.
It automatically detects your site content, creates translated versions of your pages, adds a language switcher, and gives you a dashboard where you can review and edit translations.
This is usually the best option if:
You want the fastest setup
You have a lot of pages or blog posts
SEO matters in each language
You want a language switcher in your site header
You want to manage translations from one place
You do not want to manually duplicate every page on your site
Weglot is especially useful when the website is active and likely to keep changing. If you publish new blog posts, update service pages, change product descriptions, or edit your navigation often, managing everything manually can become a lot of work.
With Weglot, you are paying for convenience, automation, translation management, and multilingual SEO support.
You can start here: Try Weglot for Squarespace
How to Add Weglot to Squarespace
In Squarespace, go to:
Settings → Site Languages → Multilingual
From there, connect Weglot, create or log into your Weglot account, select your original language, and choose the language or languages you want to add.
Once connected, Weglot adds a language switcher to your site and creates translated versions of your content. You can then review and edit those translations inside the Weglot dashboard.
You should still review the translations before treating the site as finished. Automatic translation can get you moving quickly, but brand voice, idioms, service names, product names, and local context often need a human pass.
For the official setup instructions, see Squarespace’s guide: Creating a multilingual site with Weglot
You can also review Weglot’s own Squarespace setup guide here: Weglot Squarespace Integration Setup
Important Weglot Limitations
Weglot is the cleanest option for many Squarespace users, but it is not magic.
Some parts of Squarespace may not translate through the integration, including certain third-party blocks, Acuity Scheduling, Email Campaigns, and member/customer account login screens.
You should also check pricing before you commit. Weglot pricing depends on word count, number of languages, and feature needs. A small brochure site may fit comfortably into a lower plan. A large blog, shop, or content-heavy site may need a paid plan.
Before you translate a large site, it is worth checking your word count. Weglot has a free word count tool here: Weglot Website Word Count
Option 2: Manually Create Pages for Each Language
The manual method means creating separate versions of your pages for each language.
For example, your navigation might have one dropdown for English and another dropdown for Spanish. Under each dropdown, you create matching pages:
English
Home
About
Services
Contact
Español
Inicio
Sobre nosotros
Servicios
Contacto
You can duplicate your original pages, translate the text yourself, and then link between the language versions.
This can work well for small sites.
It is usually a good fit if:
Your site only has a few pages
You already have human translations
You do not update the site very often
You do not want another monthly tool
You are comfortable managing duplicate pages
The main advantage is control. You decide exactly what each page says in each language.
The main drawback is maintenance. Every time you update a page in one language, you need to remember to update the matching page in the other language. On a five-page site, that may be fine. On a fifty-page site with blog posts, products, forms, and landing pages, it can become messy fast.
Squarespace has an official guide for this method here: Manually creating a multilingual site
Manual Multilingual Setup in Squarespace
A simple manual setup looks like this:
Create a homepage or landing page that lets visitors choose their language.
Create a navigation dropdown for each language.
Duplicate your main pages for each language.
Translate the duplicated pages.
Add links between matching language pages when needed.
Check all buttons, forms, navigation links, footer links, and SEO titles.
Update both language versions whenever you make future edits.
This method gives you control, but it does not give you the same automatic multilingual SEO structure that a dedicated multilingual tool can provide.
Option 3: Use Custom Code or an Older Multilingual Plugin
Before Weglot became the main Squarespace recommendation, a lot of multilingual Squarespace setups relied on CSS, scripts, duplicated content, or third-party tools.
These options may still make sense in certain cases, but I would not start there unless you have a specific reason.
CSS-only multilingual setups can be clever, but they are easy to make fragile. You may end up hiding and showing content instead of creating clean language-specific pages. That can create maintenance, accessibility, and SEO concerns.
A plugin or custom code setup may be worth considering if:
You have a very specific design requirement
You want a one-time setup instead of an ongoing translation platform
You already have all translations written
You are working with a developer who understands Squarespace
You do not need the same automation Weglot provides
For most site owners, I would compare Weglot and the manual method first.
Which Multilingual Squarespace Option Should You Choose?
Here is the simplest way to think about it.
Use Weglot if you want the easiest setup, automatic translation, translation management, a language switcher, and better multilingual SEO support.
Use the manual method if your site is small, your content does not change often, and you already have translated copy for each language.
Use custom code or a plugin if you have a specific design or technical requirement that Weglot and the manual method do not solve.
My Recommendation
For most Squarespace 7.1 websites, I would start with Weglot.
It is the most straightforward path, and it is the direction Squarespace points users toward for multilingual sites. It is especially useful for businesses with more than a few pages, content that changes often, or any serious need to appear in search results across multiple languages.
For a small, mostly static website, the manual page duplication method can still be perfectly fine. It takes more care, but it avoids another monthly tool and gives you full control over the translated content.
The main thing is to avoid choosing based only on setup cost.
A multilingual website is not just a translation project. It is a maintenance project. Before you choose a method, ask yourself who will update the second language version three months from now, six months from now, and a year from now.
That answer usually makes the right option obvious.
If you want the easiest path, start here: Try Weglot for Squarespace
Squarespace Multilingual Website FAQs
Does Squarespace support multilingual websites?
Yes, but Squarespace does not have a full native multilingual content manager built into the editor. You can use Weglot, manually create separate language pages, or use a custom/plugin solution.
Does changing the Squarespace site language translate my website?
No. Changing your site language only affects built-in Squarespace text. It does not translate the custom text you added to pages, blog posts, products, or other content areas.
What is the easiest way to make a Squarespace site multilingual?
For most Squarespace 7.1 sites, Weglot is the easiest option. It connects inside Squarespace, adds a language switcher, detects your content, and gives you a translation dashboard.
Can I create a multilingual Squarespace site for free?
You can manually create duplicate pages for each language without paying for a translation tool. This works best for small sites with limited content. You will still need to write or provide the translations yourself.
Is Weglot better than manually duplicating pages?
Weglot is usually better for larger sites, active sites, SEO-focused sites, and sites that need easier translation management. Manual duplication can be better for small, static sites where you want full control and do not want another monthly service.
Is Weglot good for Squarespace SEO?
Weglot is designed to support multilingual SEO by creating language-specific versions of your content and helping search engines understand the translated pages. If SEO is important in multiple languages, Weglot is usually easier than trying to manage everything manually.
Can I use different currencies for different languages in Squarespace?
Squarespace sites can only sell in one currency at a time. If you need different currencies for different markets, you may need separate sites or a more complex ecommerce setup.
Should I use CSS to create a bilingual Squarespace site?
CSS-only multilingual setups can work in some cases, but I would not recommend them as the first option for most site owners. They can be harder to maintain and may create SEO or accessibility issues if not handled carefully.