Translating a Squarespace Site Into Italian and Portuguese Without Rebuilding It
Yes: Squarespace has no built-in translation, but Weglot (7.1 only) or a per-language tool can add Italian and Portuguese URLs without a rebuild.
Yes, but not with a built-in setting: Squarespace has no native translation feature as of 2026. Without a rebuild, the realistic options are the Weglot integration that Squarespace documents, which is officially available only on site version 7.1, or a per-language translation tool such as Lantis, which is installed by pasting one line of code.
Key takeaways:
- Squarespace has no built-in translation, so Italian and Portuguese pages must come from an add-on, a translation tool or manual duplication of every page.
- Weglot's official Squarespace integration works only on version 7.1, so check your site version before anything else.
- Weglot's paid Starter plan covers 10,000 translated words for one language. A 9,000-word site in two languages needs 18,000 words, which is more than that allowance.
- Lantis charges €2.50 per language per month for 2 to 9 languages and includes 500,000 words per language, so Italian and Portuguese cost €5 per month.
Why can't Squarespace translate my content by itself?
Squarespace has no setting that translates the text you write. A designer guide from UOGAweb says so directly:

"Squarespace still has no built-in translation feature in 2026."
In July 2025, a moderator on the Squarespace community forum said Squarespace had made no official announcement about a native, comprehensive multilingual feature.
The confusion usually comes from the site-language setting. According to Squarespace's help page, it changes the built-in text visitors see, such as dates, form field labels and navigation controls. The UOGAweb guide lists Italian and Portuguese among the available site languages, but the list only controls that interface text. Your pages, product descriptions and blog posts stay in Spanish, so Google has no Italian or Portuguese content to show.
What does Google need to show Italian and Portuguese pages?
Google needs a separate, fully translated page for each language, and it needs to be able to connect those pages. Google's documentation on localized versions says that if you have several versions of a page for different languages, you should tell Google about the variations. It also notes that Google might still find alternate language versions without any action on your part. Its guidance on multi-regional sites advises locale-specific URLs for a whole site or a single page. In practice, that means an Italian address and a Portuguese address for each page, not one address that changes language in the browser.
Duplicate content is the usual worry. According to Google's documentation, localized versions count as duplicates only if the main content of the page remains untranslated. A fully translated Italian page next to its Spanish original is not treated that way. Lantis has a longer explanation in its guide to duplicate content and translations.
The annotations that link the versions are called hreflang. A third-party hreflang guide says the relationships must be reciprocal: if the Spanish page points to the Italian one, the Italian page must point back. The same guide notes that Bing does not use hreflang and relies on other signals, such as Content-Language HTTP headers and geolocation data, so results can differ between search engines.
These requirements give you four questions to ask of any route:
- URLs: does each language get its own address?
- Annotations: are hreflang tags added and kept reciprocal?
- Coverage: is the whole page translated, including menus and footer?
- Effort: what happens each time you edit a page?
How does the official Weglot integration work on Squarespace?
Squarespace's help center documents Weglot as its integration for generating translated versions of a site in several languages. The limit is the site version: the page states that the integration is currently only available for version 7.1. If your site is on version 7.0, the same page says you can manually create a multilingual site, so there is no official automatic path for that version.
On addresses, the Weglot guide on Squarespace Circle says each translated language gets its own subdirectory or subdomain, which Google recommends for crawling those pages. That meets the first criterion above.
Weglot's free tier is the cheapest way to try the route, but it does not reach two languages: according to Squarespace's help page, Weglot is free for one language and up to 2,000 words. Beyond that, a pricing calculator based on Weglot's pricing page lists the Starter plan at €15 per month or €150 per year for 10,000 translated words and one language. Standard plans are priced in euros and exclude VAT. The sources consulted do not give prices for plans above Starter, so the cost of a two-language Weglot plan cannot be stated here.
The word allowance multiplies by the number of destination languages. The same calculator shows that a 9,000-word site needs 18,000 translated words for two destination languages. For Italian and Portuguese, you would count your Spanish word total twice before picking a plan.
If you sell online, test the purchase flow in each language before you announce the new versions.
For a version 7.1 site that wants the integration Squarespace itself documents, Weglot is the straightforward choice, especially for a small site. The cost to model is the word count multiplied by two languages.
What does the manual route involve?
The manual route needs no add-on, but it means more work. As SQSPThemes explains, you duplicate your original pages, translate the text yourself and link between the language versions. This is also the route Squarespace's help page describes for sites on version 7.0.
Its cost is time. Every new page and every later edit has to be made in each language, and nothing keeps the versions in sync for you. For a small site that rarely changes, that can be acceptable. For a shop or a blog, the maintenance adds up.
The language switcher is the fragile part. A guide from Square It Up warns that the hand-coded switch method can break when Squarespace changes its source code, which could expose all the language pages in the menu. If you go this way, plan to check the switcher after Squarespace updates.
Do translation widgets and language switchers help with SEO?
A guide from Squarespell describes a widget that writes the translated text into the page in real time. The mechanism is documented, but it suggests the page address does not change, and Google needs a distinct address for each language. The Square It Up guide goes further: its comparison table rates the Google Translate widget route as "Not indexed by Google."
A widget can still help visitors read a page in their own language. If your goal is for Google to show Italian and Portuguese results, it does not meet the URL criterion.
How does Lantis fit a Squarespace site?
Lantis translates websites with AI and gives each language its own URL, with hreflang tags and sitemaps generated automatically. It is installed by pasting one line of code, without changing DNS or touching the design. Lantis lists Framer, Webflow, Shopify and WordPress by name and says it works on any website. Squarespace does not document it as an integration, unlike Weglot, and the sources consulted do not detail how it performs on Squarespace specifically or give SEO results for it there.
On the same criteria used above, Lantis is designed to give each language its own address with hreflang. For coverage and effort, it offers these tools:
- Translation engine: Gemini by default, with Claude, DeepL or DeepSeek as alternatives.
- Corrections: a visual editor to fix translations, plus a custom glossary per language.
- Control: exclusion of specific pages or blocks.
- Reporting: analytics on the languages your visitors use.
Lantis includes 500,000 words per language and more than 60 languages. Extra words (+500,000) cost a one-time €1. It charges only for active languages, with no limit on websites or visitors. There is no lock-in, and Lantis refunds in full within 14 days of each payment. The Agency plan, for people who manage client sites, costs €49 per month for up to 20 websites and up to 5 languages per site.
What does each route cost for Italian and Portuguese?
The table applies the same attributes to each option. Weglot's figures come from Squarespace's help page and the pricing calculator cited above; Lantis's figures are its own.
| Route | Cost for two extra languages | Words included | Installation |
|---|---|---|---|
| Manual duplication | No add-on fee; your time for each translation and edit | Not applicable | Built by hand in Squarespace |
| Lantis | €5 per month (2 × €2.50) | 500,000 per language | One line of code; not a documented Squarespace integration |
Lantis's allowance is much larger per language, though the sources consulted do not give a word-count method for Lantis. Lantis's per-language pricing is €3 per month for one language, €2.50 per language for 2 to 9 languages and €2 per language for 10 or more.
Each route suits a different case. Lantis suits a site that wants per-language pricing and a visual editor, and it works outside Squarespace's documented integrations.
What should you check after launch?
Whichever route you choose, verify the result before you expect Google to show it:
- Reciprocal links: every language page should link to its equivalents, and each link should be reciprocal, as hreflang requires.
- Self-referencing tags: each page should include an hreflang tag pointing to its own language version.
- Template text: menus, footer, cookie notice and form labels should be translated too, since untranslated main content can make a page look like a duplicate.
- Indexing: in Search Console, confirm that the Italian and Portuguese URLs are discovered and that no language version is missing from the sitemap. Lantis's Search Console guide for multilingual sites walks through this step.
- Overall review: Lantis also publishes a checklist for multilingual SEO that you can run against any of the routes.
Next steps
- Open your Squarespace site settings and confirm whether the site runs on version 7.1 or 7.0, because that decides whether the official Weglot integration is available.
- Count the words on your Spanish site and multiply by two to get the translated word total for Italian and Portuguese.
- List the pages that matter most for search and decide whether you need all of them translated or only a subset.
- Test your checkout and contact forms in each language after launch, and check the Italian and Portuguese URLs in Search Console.
- For background on the costs and limits of each approach, Lantis's guide to AI versus manual translation is one more reading option.
Frequently asked questions
Can I translate only some pages of my Squarespace site and leave the rest in Spanish?
Yes, with the manual route you choose which pages to duplicate and translate. Lantis lets you exclude pages or blocks from translation. Untranslated pages simply stay in Spanish.
Will translated pages hurt my Spanish SEO through duplicate content?
Not if the pages are fully translated. Google states that localized versions count as duplicates only if the main content remains untranslated. Pages with Spanish text under an Italian menu are the ones to avoid.
Do I need to change my Squarespace domain or DNS to add translated URLs?
Lantis does not require DNS changes: you paste one line of code and each language gets its own URL. With Weglot, each language gets its own subdirectory or subdomain.
Is there a free option that works for two extra languages?
Weglot's free tier covers one language and up to 2,000 words, so it does not reach two. Manual duplication has no add-on fee but costs your time. Lantis starts at €3 per month for one language and refunds in full within 14 days of each payment.
Can I edit AI translations myself before they go live?
With Lantis, yes: a visual editor lets you correct translations, and a glossary per language keeps terms consistent. With manual duplication, you write every translation yourself, so you control all of it.
Sources
- Multilingual Squarespace: Weglot vs Manual (2026 Guide) — UOGAweb
- Creating a multilingual site with Weglot
- Multi language translation and page settings inside Squarespace? — Squarespace Forum
- Changing your account and site language
- Localized Versions of your Pages
- Managing Multi-Regional and Multilingual Sites
- hreflang Tags: The Complete Implementation Guide for Multilingual SEO
- Translate a Squarespace Website With Weglot — Squarespace Circle
- Weglot Pricing Calculator: Plans, Costs and Squarespace Checks
- How to create a multilingual website on Squarespace — SQSPThemes
- How to Make Your Squarespace Website Multilingual — Square It Up
- How to Add a Language Switch to Your Squarespace Website — Squarespell
Pon tu web en varios idiomas hoy.
Una línea de código. SEO real por idioma. Traducción con IA. Sin tarjeta para empezar.