Websites That Speak Your Customers’ Languages

A multilingual Squarespace website is one site that serves each visitor in their own language — with search engines indexing every language version separately, so you get found in each market you serve. That is what I build: design, translation setup, and the technical SEO layer that makes both languages actually rank. This site you’re reading runs exactly that setup — switch it to Lithuanian in the header, and you’re looking at the proof.

300+ AI-assistant citations in 3 months · Squarespace Circle Gold since 2024 · 12 published builds · Bilingual EN/LT

Proof you can open, not promises

Multilingual SEO is easy to claim and hard to fake. Here is what the setup looks like when it works — starting with the site you are on.

uogaweb.com — the living case study

English + Lithuanian · one Squarespace site

Every page you see here exists in two languages on separate, indexable URLs with hand-maintained hreflang pairs. The result: the Lithuanian and English pages rank independently for their own queries, and this site’s multilingual content earned 300+ citations from AI assistants (Copilot, Perplexity) in the three months to August 2026 — measured in Bing Webmaster Tools, with nearly half arriving through one multilingual guide.

Open the Lithuanian version ↗ · Read the technical guide →

Vandens lelija studija

Beauty & wellness studio · Vilnius

A calm, premium build that quietly sells: ritual menu, gift-voucher e-commerce and a booking enquiry in one place — the kind of polish your second language deserves too.

Open the site ↗ · Case study →

Grožio salonas „Edita“

Beauty salon · Kaunas

Full service catalogue, gift vouchers and Google reviews (4.7★, 75+) displayed right on the site — trust built before the first call.

Open the site ↗

All 12 published builds → Salons, restaurants, physiotherapy, tattoo studios, sailing and personal brands.

Who this is for

Service businesses whose customers don’t all speak one language: salons and clinics with international clients, restaurants in tourist areas, studios serving expat communities, professionals selling across borders. If half your Instagram messages arrive in another language — or you keep answering the same questions in two languages — your website should be doing that work for you. A single-language site quietly turns those visitors away, and you never see it happen in any report.

What a properly multilingual site includes

  • One site, not two. You edit content once; the translation layer keeps every language in sync. No duplicate site to maintain, no second subscription to forget.

  • Separately indexable language versions. Each language lives on its own URLs, so Google can rank the Lithuanian pages in Lithuania and the English pages in the UK — at the same time.

  • Correct hreflang tags. The invisible plumbing that tells search engines which version to show to whom. Most DIY multilingual sites get this wrong and compete against themselves.

  • Translated titles and meta descriptions. The text people see in Google results. Most “translated” sites forget these — the page is bilingual but its search listing never is, so the second language stays invisible.

  • A language switcher visitors actually find, in the header where they expect it.

  • Hand-polished translations on the pages that sell. Machine translation is good enough for a blog archive; it is not good enough for the page where someone decides to pay you. Money pages must read as written, not converted.

How the setup works — the exact steps

The same six steps run on my own site and on client builds. Most “multilingual” setups skip half of them — that is why the second language never ranks.

  1. Language architecture first. Decide what gets translated and what deliberately stays in one language — pricing pages, local-only offers, hand-written landing pages. Deciding what NOT to translate is part of the architecture.

  2. Connect the translation layer. Weglot on a language subdomain with clean URLs — every language version becomes a real page search engines can crawl, not a browser-side swap.

  3. Add hreflang pairs at the source. Each translated page gets its pair declared on the origin site, so Google always knows which version belongs to which market.

  4. Translate the search listings. Titles and meta descriptions in every language — the text people actually see in Google results.

  5. Hand-polish the pages that sell. Money pages get a native rewrite (Lithuanian I do natively) and are pinned so machine translation never overwrites them.

  6. Verify and index. The language version goes into Google Search Console and Bing Webmaster Tools, indexing is requested, and rankings are tracked per language from day one.

The mistakes that keep multilingual sites invisible

  • JavaScript-only translation widgets. The page translates in the browser, but there are no separate URLs for Google to index — so the second language simply doesn’t exist in search.

  • Untranslated metadata. The body is translated, the search listing isn’t. Clicks never come.

  • Auto-redirecting visitors by IP. Feels clever, breaks crawling and annoys people who wanted the other language.

  • Translating everything blindly. Some pages should stay in one language on purpose — machine-translating a hand-written sales page usually makes it worse in both languages.

Why me

I run my own business in two languages, so I build this for myself first and my clients second. Squarespace Circle Gold member (partner since 2024), 12 published builds, bilingual EN/LT — and I maintain the hreflang map across every translated page of this site by hand, which is how I know exactly where the platform fights you. My written guide on this setup is one of the most-referenced Squarespace multilingual resources online — and the numbers above show it. A guide can’t build your site, though; that’s what this page is for. Read the full technical guide or browse the live builds.

Pricing

Multilingual builds start at £800 (Showcase tier plus full language setup). The translation service itself is billed by Weglot — a small monthly cost that depends on word count, and I’ll tell you exactly which plan you need before you commit, so there are no surprises. Already have a Squarespace site? Adding a second language properly is a fixed-scope project: audit, setup, hreflang, metadata, polish — ask and I’ll quote it after a quick look. Every build includes three months of care, then plans from £35/month if you want me to keep maintaining it.

Frequently asked questions

Does Squarespace support multiple languages natively?

Not fully — that’s why the setup matters. Done wrong, Google only ever sees one language. Done properly with a translation layer, each language version is separately indexable.

Does Weglot work with Squarespace?

Yes — Weglot is the standard translation layer for Squarespace. Set up on a language subdomain, it serves every language as real, crawlable pages. I configure it end to end, including the parts the default setup skips.

Do I need hreflang tags on Squarespace?

If you serve more than one language, yes. Squarespace does not generate hreflang for translated versions by itself — the pairs have to be added per page, which is exactly what I do, so Google shows the right language to the right market.

Will my site rank in both languages?

Each language version is separately indexable with correct hreflang — that’s the point of doing it properly. Rankings themselves depend on competition and content, as everywhere; the setup removes the technical ceiling.

Can you translate the content?

The tool translates everything automatically; I hand-review the pages that sell. For Lithuanian I do it natively — it reads as written, not converted.

Will the translated version slow my site down?

No. Translations are served as full pages on their own subdomain — not swapped in the browser — so visitors get a normal, fast page in their language.

What does Weglot cost?

From roughly £13/month depending on word count. I size the right plan before you commit.

How long does it take?

Adding a language to an existing Squarespace site: usually one to two weeks including the polish pass. A new bilingual build: three to five weeks from the moment I have your content.

Can I have more than two languages?

Yes — the same architecture scales; each added language mainly affects the translation plan size, not the build.

Will new content translate automatically?

Yes. Publish in your main language and the translation layer picks it up; anything important gets a human pass.

Not sure your current site handles languages correctly?

Run the free check — it takes a minute and shows what search engines actually see. Or write to me directly and I’ll reply within a day.

Run the free website check · Email info@uogaweb.com

Prefer Lithuanian? See Svetainių kūrimas Anglijoje — my Lithuanian-language page for businesses in the UK.

Last updated: 14 August 2026.