The No-BS Guide to Multilingual Squarespace Sites (2026 Edition): Native vs. Weglot vs. The "Hard Way"

By Gediminas | Founder of UOGAweb & Squarespace Circle Gold Member

The Ultimate Guide to Multilingual Squarespace Websites 2026

Here’s the short answer: Squarespace still has no built-in translation feature in 2026. You have three real options — the Weglot extension (from ~€15/month, the right call for most businesses), the manual method (free, full control, painful to maintain), or a Google Translate widget (please don’t). Whichever you pick, the SEO layer — hreflang tags, indexable translated pages, one clean URL structure — decides whether your second language brings you customers or quietly hurts your rankings.

That’s the whole guide in one paragraph. The rest is the detail that makes it actually work.

Fully updated July 2026 — every price and platform fact below was re-verified this month.

I’m not writing this from other people’s tutorials. My own studio site runs in English and Lithuanian on the exact stack described in Part 4, and I run the same Weglot setup on client builds — the physiotherapy studio Kartu su kūnu is one of them. I’ve done it the manual way too. Both scars and results below.

While Shopify and Wix shipped native translation tools years ago, Squarespace never did. For years the honest options were hacky code, duplicated pages, and hoping Google would cope.

Good news: in 2026 the options are solid. Bad news: you can still wreck your SEO by picking the wrong one.

Part 1: The "Big Three" Options (And Why One Probably Sucks for You)

Let’s cut through the marketing fluff. You only have three real paths.

Option A: The "Official" Extension (Weglot)

• The Vibe: "I have a budget and I value my sanity."

• The Cost: Free under 2,000 words; real plans start at €15/mo for 10,000 words and one language, €29/mo for three languages (July 2026 prices — plans change, check their pricing page).

• The Reality: It’s an external layer that sits on top of your site. It translates content automatically but lets you edit it manually.

• My Take: Use this if you are a business. If you sell products or services, the time you save is worth 10x the monthly fee.

Option B: The "Manual" Workaround (DIY)

• The Vibe: "I am a control freak and I refuse to pay subscriptions."

• The Cost: €0 (but costs you ~20 hours of life).

• The Reality: You physically duplicate every page (/home becomes /lt/pradzia). You use custom code to hide navigation menus.

• My Take: Use this for Portfolios or simple 5-page sites. It gives you ultimate design freedom (e.g., a totally different layout for Lithuanian users), but it’s a nightmare to maintain for large sites.

Option C: Google Translate Widget (The "Ugly" Way)

• The Vibe: "I don't care about my brand image."

• The Cost: Free.

• The Reality: You embed a script. A nasty toolbar appears. It translates "Home" to "House" and "Book Now" to "Book Immediately".

• My Take:Never do this. It looks cheap. It breaks your design. It provides ZERO SEO benefit because Google doesn't index the translated dynamic content. Just don't.

Left side: A beautiful custom language switcher. Right side: The ugly Google Translate dropdown bar.

Part 2: The Weglot Strategy (How to Do It Like a Pro)

Most people just install Weglot and leave it. That’s why their sites look "generic." Here is how we customize it for high-end clients.

1. The Setup (Don't mess this up)

Go to your Squarespace Settings > Extensions > Search "Weglot". Connect it. It will ask for your API key. Once connected, it automatically detects your content.

The Critical Step: Go to your Weglot Dashboard > Project Settings. Ensure "Auto-Switch" is OFF. Wait, what? Yes. Auto-switch sounds nice ("It detects the user is from Lithuania and shows Lithuanian!"). But in reality, it causes a "flash of content" where the user sees English for 0.5 seconds before it snaps to Lithuanian. It feels buggy. Let the user choose their language.

2. Styling the Switcher (The "Gold Member" Code)

By default, the switcher is a floating button at the bottom right. It covers your "Scroll to Top" button or your Chat widget. It’s annoying.

We move it to the Header Navigation using CSS.

Copy this into Design > Custom CSS:

CSS

/* UOGAweb PRO TIP: Move Weglot to Header */
.weglot-container {
    position: absolute;
    top: 25px; /* Adjust based on your logo height */
    right: 5vw;
    z-index: 1000;
}

/* Typography Polish */
.wg-li a {
    font-family: 'aktiv-grotesk', sans-serif; /* CHANGE THIS to your site font */
    font-weight: 500;
    letter-spacing: 0.05em;
    text-transform: uppercase;
    color: #1a1a1a !important;
}

/* Active Language State */
.wg-current {
    border-bottom: 2px solid #000; /* Underline the active language */
    padding-bottom: 2px;
}

UOGAweb website’s header showing the clean "EN | LT" switcher integrated perfectly next to the navigation.

3. The "Visual Editor" Rule

AI translation has gotten scary good (thanks, DeepL). But it still fails on nuance.

• Example: In English, a button says "Get in Touch".

• AI Translation: "Gaukite prisilietimą" (Lithuanian literal translation).

• Correct: "Susisiekite".

Rule: Never launch without a human review. Open the Weglot "Visual Editor", click on your headlines, and rewrite them to sound human.

Part 3: The Manual Method (For the Brave)

Okay, so you want to save the monthly fee and have total control. I respect the hustle. I built my first agency site this way. It took me three days, but the SEO result was incredible.

Here is the exact architecture you need.

Step 1: The "Two-Site" Illusion

You aren't building one site. You are building two sites under one roof.

1. Create a Folder in Pages called "MAIN-EN".

2. Create a Folder in Pages called "MAIN-LT".

3. Drag your English pages into MAIN-EN.

4. Duplicate them, translate the text, and drag them into MAIN-LT.

SEO WARNING: Look at the URL Slug. Squarespace often defaults to /home-1. Change it immediately to /lt/pradzia. The /lt/ prefix is vital for tracking.

Folder structure clearly pointing to "English" and "Lithuanian" folders.

Step 2: The Navigation Nightmare (Solved)

If you just leave it like this, your header will show: HOME ABOUT CONTACT PRADZIA APIE KONTAKTAI It looks like a mess.

You need to tell Squarespace: "When I am on an English page, hide the Lithuanian links."

We use Page Header Code Injection for this. (You’ll need a plan that includes code injection — on Squarespace’s 2026 lineup that’s Core and up.) Go to the Settings (Gear Icon) of your "MAIN-EN" folder (yes, the folder itself has settings). Go to Advanced. Paste this:

HTML

<style>
  /* Hide LT Folder Links when inside EN */
  .header-nav-item:nth-child(n+4) { display: none !important; } 
  /* Adjust "n+4" based on how many links you have. */
</style>

Then do the reverse for the LT folder. Note: This is "brittle" code. If you rearrange your menu, you break the code. Be careful.

Step 3: The Mobile Menu Trap

This is where 99% of tutorials fail you. They give you code for the desktop menu, but when you open your phone, the "Burger Menu" still shows ALL links.

You need to target the mobile class specifically:

CSS

/* Mobile Menu Specific Hiding */
.header-menu-nav-item a[href*="/lt/"] {
    display: none;
}

Place this in Custom CSS, wrapped in a body class targeting your English pages.

Part 4: Advanced SEO (How to Rank #1 Globally)

This is the secret sauce. This is the part clients actually pay a specialist for — not the translation itself, the search plumbing underneath it.

The Hreflang Tag

Google is smart, but it won’t guess your intent. Without hreflang it can treat your language versions as competing duplicates — indexing the wrong one, folding them together, or showing English pages to Lithuanian searchers. There’s no formal “duplicate content penalty”, but the practical result feels like one: the right page stops showing up.

You must explicitly map the relationship.

The Code Snippet (Put this in every page header):

HTML

<link rel="alternate" hreflang="en" href="https://uogaweb.com/en/services" />
<link rel="alternate" hreflang="lt" href="https://uogaweb.com/lt/paslaugos" />
<link rel="alternate" hreflang="x-default" href="https://uogaweb.com/en/services" />

What is x-default? It tells Google: "If a user comes from a country where we don't have a specific language (e.g., Japan), show them the English version." Without this, Google might randomly show your Lithuanian page to a user in Tokyo.

This site runs exactly that pattern — reciprocal en↔lt tags on every page, pointing between uogaweb.com and lt.uogaweb.com. If you use Weglot, it generates hreflang for you automatically; go manual and these tags are yours to maintain forever. Budget for that honestly.

Google Search Console "International Targeting" report showing the hreflang tags highlighted.

Part 5: E-commerce & The "Currency Problem"

Here is the hard truth Squarespace doesn't advertise: You cannot sell in multiple currencies natively. Even if you translate your site to Lithuanian, the checkout will still show € (EUR) (which is fine for us) or $ (USD). You cannot show Dollars to Americans and Euros to Europeans automatically.

The Workaround:

1. Stick to one currency (EUR). Most international shoppers are used to it.

2. Add a Currency Converter Widget. There are plugins (like Elfsight) that show an approximate price in USD below the EUR price.

3. The Checkout Page Language. Even with Weglot, the checkout page (where they enter credit card info) is locked by Squarespace security. It allows some translation, but often reverts to the "Site Language".

   • Tip: Set your main Site Language to English. It’s better for a Lithuanian to see English checkout than for an American to see Lithuanian checkout (they will panic and think it's a scam).

Conclusion: Which Path is Yours?

I wrote this guide because I was tired of seeing businesses fail globally because of bad technical decisions.

Choose Weglot if:

• You have more than 10 pages.

• You run an online store.

• You value your time at more than €2/hour.

• Verdict: It’s the "Business" choice.

Choose Manual if:

• You are a portfolio artist (photographer, architect).

• You need "Pixel Perfect" control over each language.

• You have zero budget but unlimited coffee.

• Verdict: It’s the "Designer" choice.

Multilingual Squarespace FAQ (the questions I actually get)

Does Squarespace support multiple languages natively?

No. As of mid-2026 there is still no built-in translation feature. The official paths are the Weglot extension or a manual multi-page setup — both covered above. If Squarespace ever ships a native feature, this guide gets updated the same week.

How much does a multilingual Squarespace site really cost?

With Weglot: your normal Squarespace plan plus Weglot’s subscription — free under 2,000 words, €15/month for 10,000 words and one extra language, €29/month for three (July 2026 prices; check their page). The manual method costs nothing monthly, but budget 15–20 hours to build and double the maintenance forever.

Do the translated pages actually get indexed by Google?

Yes — that’s the point of doing it properly. Weglot serves each language on its own URLs (a subdomain — lt.uogaweb.com for this site) with hreflang tags and a multilingual sitemap, so every language competes in search on its own. A JavaScript widget that swaps text in the browser gives Google nothing to index — which is why I keep telling people to avoid that route.

Can I translate the Squarespace checkout?

Only partly. The checkout runs on Squarespace’s secure system and mostly follows the site language — Weglot can translate some of it, but expect the final payment screens to stay in your main language. For stores selling internationally I set the site language to English: a Lithuanian shopper handles an English checkout far better than the reverse.

Can Squarespace sell in more than one currency?

No — one currency per store, full stop (confirmed on Squarespace’s own docs, July 2026). Translation doesn’t change that. Pick your main market’s currency and, if needed, show approximate conversions with a third-party widget.

Is Weglot worth it for a small site?

Under 2,000 words you can run the free plan, so try it. Beyond that: if the site earns money in a second language — bookings, sales, enquiries — €15/month pays for itself with one extra customer. If it’s a hobby site, the manual method or a single translated landing page may be all you need. For service businesses — salons are the ones I write about most — the bilingual version is often the best-value marketing you already own.

Still feeling overwhelmed? I get it. This stuff is technical. One missing semicolon in the code can break your mobile menu.

This is routine work for me — I’m a Squarespace Circle Gold member, my own site runs bilingual, and multilingual setups are one of the things I’m hired for most. You can see real builds in my portfolio and how I work on the services page.

If you’d rather skip the headache: 👉 Book a free strategy call — 15 minutes, and you’ll leave knowing which of the three paths fits your site, whether you hire me or not.

Author Bio

Gediminas is the founder of UOGAweb and a Squarespace Expert based in Vilnius. When he isn't debugging CSS for international brands, he's probably sailing or complaining about bad UX design on some social platforms.