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:

1. Use Weglot, Squarespace’s recommended multilingual integration

2. Manually create separate pages for each language

3. 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

En Squarespace, ve a:

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

  • Servicios

  • Contacto

• 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:

1. Create a homepage or landing page that lets visitors choose their language.

2. Create a navigation dropdown for each language.

3. Duplicate your main pages for each language.

4. Translate the duplicated pages.

5. Add links between matching language pages when needed.

6. Check all buttons, forms, navigation links, footer links, and SEO titles.

7. 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.

What Actually Changes When You Shift from Freelancer to Studio (And What You Need Before You Hire Your Second Person)

You're solo right now. You've been building your web design business long enough that the work is steady, the clients are good, the pricing is moving in the right direction. You're starting to feel the edges of solo — too much work to do alone, too many opportunities you're turning down, too many late nights because you're the only one who can do any of it.

So you're thinking about the shift. From freelancer to studio. You're asking what it takes.

Most advice on this shift focuses on three things: hiring, pricing, and positioning. All three matter. But there's a fourth thing — quieter, less talked about, and the one that most often breaks studios in their first year.

It's the operational shift. The structural rebuild that has to happen inside your business before you can actually grow beyond yourself. And most people try to do it after their first hire, which is backwards.

This piece is about what that shift actually requires, why the order matters, and what you need in place before you bring on your second person.

What solo hides that studio exposes

When you're solo, your business is carried by a lot of invisible operational work that you don't think of as work.

You carry client details in your head. You know without thinking that the Acme Corp logo files live in the Acme folder, that their point of contact prefers phone calls over email, that their invoice goes to accounting@ not info@, that they asked last month to be CC'd on any subcontractor emails. Multiply this by every active client. You know all of it, and you know it fluently.

You remember follow-ups because you saw the email. The lead from three weeks ago who asked about timing — you saw their email, you clocked it, you'll respond when you get a chance. The chance comes. Or it doesn't. But the system is: you saw it, you'll get to it.

Your processes live in "how you've always done it." Your onboarding isn't documented — it's the sequence of things you do when a new client signs, and you do them from muscle memory. Your review process isn't written down — it's the series of checks you run before delivering, which you do because you've learned the hard way what happens when you skip them.

Your priorities live in your gut. You know what's most important this week. You don't need to write it down, because you're the one doing all of it, and you can feel where the pressure is.

All of this works. It works for one reason: you are the system. Every piece of operational information is stored in one place — you — and accessed by one person — also you. There's no transfer problem. There's no lookup problem. There's no "where is that file" problem, because you're the file.

This is the part solo hides. Because the operational infrastructure of your business is entirely internal, you don't perceive it as infrastructure. It just feels like how you work.

The moment you hire someone, everything you'd been carrying internally has to become externalizable. And most of it isn't.

What happens the day your second person starts

Let's be concrete about what breaks.

Day one, your new hire starts. They need to know where your current projects stand. You spend two hours walking them through each project, realizing as you talk that most of the information is in your head and not written anywhere.

Day three, a new lead comes in. Your hire asks how follow-up usually works in your business. You realize you don't have a follow-up process — you just remember to follow up. So you write one on the spot. It's okay, but it's not as good as it would be if you'd designed it thoughtfully.

Day seven, your hire asks where the brand guidelines live for the client they're helping on. You tell them. It's in your Google Drive, in a folder nested inside another folder, named something that made sense to you three years ago but doesn't to them. They spend fifteen minutes finding it. They ask if you can move it somewhere obvious. You say you will. You don't.

Day fourteen, a client asks your hire a question. Your hire doesn't know the answer. They ask you. You know it. You answer the client yourself because it's faster. Your hire learns that when clients ask hard questions, you'll handle it. This is the start of the pattern where you're still doing client work and managing a team member, which is how you end up doing more work after hiring, not less.

Day thirty, you notice you've been spending most of your time on meetings, explanations, and course-corrections. Your hire is doing good work on the things you've walked them through. Anything you haven't walked them through, they're doing approximately, or they're asking you. Your actual output — the design work you used to do — has dropped.

This pattern is almost universal for studios that hire before they systematize. It's not a failure of the hire. It's a failure of the studio to have an operational backbone for the hire to work inside.

The real sequence

The sequence most studios follow is: hire → struggle → systematize.

This is the hard way. You've already taken on a salary. You're already paying someone to wait while you build the systems they need to be useful. You're rebuilding the plane while flying it, with two people now on the plane.

The better sequence is: systematize → hire → scale.

You build the operational backend before you bring anyone in. When your new hire starts, there's already a project management system they can see. There's already a place where client details live that isn't inside your head. There's already a documented onboarding process, a follow-up rhythm, a resource library, a priority structure.

Day one, your hire looks at the dashboard and sees where every project stands. Day three, they handle a new lead using the existing follow-up process. Day seven, they find the brand guidelines in the obvious place. Day fourteen, they answer a client question themselves because the information exists somewhere besides your head. Day thirty, you notice your own output has increased because the hire is multiplying your capacity instead of extracting your attention.

This is what a proper operational backend does. It converts a hire from a drain on your time into an amplifier of your capacity.

What you actually need before hiring

Here's the pre-hire checklist most studio owners don't realize they need until it's too late:

A project management structure that doesn't depend on your memory. Every active project visible in one place. Status, timeline, responsible party, next action, client-facing and internal views. When a team member joins, they can see the entire operational picture of the studio at a glance without asking you.

Client information that lives in one place. For each client: brand assets, communication history, contracts, project history, preferences, points of contact. Findable in under thirty seconds by someone who isn't you.

Lead and follow-up tracking that isn't in your inbox. A simple CRM — even a lightweight one — that captures new inquiries, tracks each one through your sales process, and surfaces follow-ups at the right time. This is the thing that prevents leads from dying because you got busy.

Documented processes for anything recurring. Onboarding, offboarding, proposal creation, project kickoff, delivery, invoicing, follow-up cadences. Not exhaustive. Just the recurring operational moves, written down once, referenceable forever.

A resource library. SOPs, templates, scripts, checklists, commonly used assets. The place where "how do we usually do this?" has an answer that isn't you.

Goals and priorities that live outside your head. Annual and quarterly goals broken down to the week. So the studio works toward something specific instead of just responding to whatever's loudest.

A central dashboard. One view that shows everything above in summary. So planning the week takes fifteen minutes, not two hours of piecing things together.

If this list looks like a lot, that's the point. This is what you've been carrying internally as a solo practitioner. It all exists already, in your head. The pre-hire work is making it external.

Why most studios don't do this in the right order

Two reasons.

One: it's hard to see the operational work you're doing when it's invisible. You don't notice you're the operating system until you're trying to transfer the operating system to someone else and realizing there's no file to hand over.

Two: building a proper operational backend from scratch takes 3 to 6 months of careful design work, and most solo designers planning a hire don't have 3 to 6 months to spend on backend design. So they hire, figure it out on the fly, and eat the first-year cost of doing it in the wrong order.

This is why pre-built operational systems designed specifically for web design studios matter. Not generic templates. Not blank Notion workspaces. A complete, shaped-for-studios operating system you can populate with your existing data, ready to run when your second person arrives.

The Web Design Studio Notion HQ is one of these. Joy and Reyna built it inside Hello-World Studio as they were making their own shift from solo to boutique studio — the backend they wished they'd had on the day of their first hire, refined over months of use, released as a product. It covers every area in the checklist above, pre-designed and pre-connected.

If you're planning your shift from freelance to studio, the HQ is the thing to have in place before the hire, not after.

One more thing worth saying

There's a version of growth that doesn't require hiring anyone. Some solo designers grow revenue by raising prices, tightening their niche, productizing, and staying a team of one. That's a real path. It's often a better path than hiring, depending on the person and the business.

But if you've decided you want a studio — more than one person, shared capacity, collective output — then the operational shift is non-negotiable. You can't grow past yourself without building infrastructure that isn't yourself.

The hire comes second. The structure comes first. That's the order.

Learn more about the Web Design Studio Notion HQ →

---

Related reading: It Works Until It Doesn't: The Operational Crisis Every Studio Eventually Hits — the anchor piece on what happens when small studios try to run on structure they never explicitly built.

Why Web Design Studios Hit an Operational Wall Around 2–5 People (And How to Get Past It)

There's a point in a web design studio's growth where the work is good, the clients are happy, the pipeline is healthy — and the inside of the studio is quietly falling apart.

You can feel it before you can name it. Follow-ups slipping. Details getting missed. A project runs longer than it should because nobody caught that it was slipping until it had already slipped. A lead goes cold because it was in someone's inbox and that someone got busy. A team member asks where a client's brand guidelines are and you realize you don't know either.

If you've felt this, you've hit the wall most small web design studios hit somewhere between two and five people.

It's a predictable wall. It arrives at a predictable size. And most studios cross it reactively — noticing it only once they're already in the middle of the operational breakdown — rather than preparing for it.

This is a piece about why the wall exists, what causes it, and what it actually takes to get past it. Skip the sections that don't apply to you.

Why the wall arrives at 2–5 people

When you were solo, your head was the operating system.

Every lead, every client detail, every project status, every deadline, every SOP, every follow-up — all of it lived in your memory, your inbox, your notes app, and the tabs you keep open. You didn't have a system. You were the system. And that worked, because the data was all in one place: you.

When you added a second person, a strange thing happened. The studio looked bigger but felt heavier.

This is because the second person doesn't just add capacity. They add a new demand: information has to be extractable from your head. Things you knew instinctively — where this client's assets live, what the plan is for Tuesday, what you told the lead on the intro call — now need to be communicable. Every time your colleague needs to know something, they either have to ask you (which means you're still the bottleneck) or find it in whatever notes, docs, or tools you've set up (which means the notes, docs, and tools need to be findable and current).

Most two-person studios survive this by overcommunicating. You sync a lot. You Slack each other constantly. You meet every morning. You keep calling the shots, and your colleague checks in with you before most decisions. It feels collaborative. It's actually still centralized — just with one person asking the center (you) a lot of questions.

Then the studio adds a third person, or takes on a larger project, or hires a contractor, or brings on a retainer client with ongoing deliverables. And the model breaks.

A third person can't get all their information from you. Neither can a second person when you're also managing a busy project. The informal "just ask" system stops scaling the moment more than one person at a time needs information you're holding.

This is the wall. It isn't about headcount alone. It's about the moment when the studio's operational information exceeds what any single person — usually you — can hold and distribute in real time.

What the wall feels like

The symptoms are specific enough that most studio owners recognize them immediately:

The dropped follow-up. A lead emails asking about timing. You see it, plan to respond when you have a moment, and then don't. Three weeks later you remember — if you remember. This happens not because you're disorganized, but because the follow-up lives in your inbox, which is also where 200 other things live, and there's no system that surfaces it at the right time.

The buried project detail. A client mentions offhand that they want the testimonials in a specific order. You note it somewhere. Two weeks later the designer asks about testimonial order. You know it's written down. You can't find it. You spend 20 minutes searching Slack, email, and Notion before giving up and asking the client again — which costs you credibility you didn't need to spend.

The "where is that file" moment. A team member asks where a client's logo files are. The answer is somewhere across Dropbox, Figma, Google Drive, and maybe an email attachment from three months ago. You end up hunting for it yourself because explaining the location would take longer than just finding it. Multiply this by a dozen times per week.

The proposal that went out late. You meant to send it Monday. Monday got busy. Tuesday you forgot. Wednesday you remembered but couldn't find the template. Thursday you finally sent it. The client had already talked to someone else by Friday.

The Sunday dread. You sit down Sunday evening to look at the week ahead and realize you don't actually know where half the projects stand. You spend two hours piecing it together from Slack, emails, and memory. The week starts already behind.

These aren't individual mistakes. They're the same structural problem expressing itself in different places. The studio is running on an operating system — your head — that has exceeded its capacity.

What studios try (and why it keeps not working)

At the wall, studio owners usually reach for one of four responses. Each seems reasonable. Each falls short for a specific, diagnosable reason.

Trying harder. More lists. More reminders. More discipline. This works for about two weeks, which is long enough to convince yourself the problem was your attention and not your structure. Then a busy client period hits, your attention gets pulled, and the whole structure — which depended entirely on your attention — collapses. Discipline is not scalable. It can keep a solo operator running. It cannot run a two- or three-person studio.

Adopting a project management tool. Asana, Notion, ClickUp, Monday — pick one. The studio adopts it enthusiastically for a few weeks, then quietly abandons it when real work returns. This happens because the tool is a blank container. Setting it up the right way for a web design studio requires designing an operating system, and designing an operating system while running a studio is a second full-time job. Most studios can't sustain that, so the tool becomes another tab nobody opens.

Hiring a virtual assistant or operations person. This feels like the right move — "I need someone to run the admin." But the VA or ops person walks into a studio with no documented system and is expected to create order out of memory. They can't. Either they spend six months building the system the studio needed before they arrived (in which case you've just paid someone to do the hardest part of your operational work), or they try to bring order to whatever currently exists (in which case the disorder just gets professionally managed instead of solved).

Building it yourself. Some studio owners take a weekend — or a quarter — and try to design their own operating system in Notion or Airtable. A few succeed. Most don't, because designing an operational backend is a specific skill, and doing it while running client work is structurally difficult. The ones who succeed often build something rigid, tied to their specific workflow at that specific moment, and then struggle to adapt it when the studio grows or the workflow shifts.

The common thread: every response treats the wall as a problem of effort, tools, or personnel. None of them treat it as a problem of structure — which is what it actually is.

What actually gets you past the wall

Getting past the wall requires one thing: the studio's operational information has to move out of your head and into a system that lives outside any one person.

Not a tool. A structure. The tool is where the structure is stored. The structure is the thing that matters.

A proper web design studio operating system has roughly seven core areas:

1. Project management — where every project lives, what stage each is in, who's responsible for what, what's due when, and what the client sees vs. what stays internal.

2. Client management — a place where each client's brand assets, communications, contracts, and project history live in one findable spot.

3. Lead tracking — a simple CRM that captures new inquiries, tracks where each one is in the pipeline, and surfaces follow-ups at the right time so nothing goes cold because you got busy.

4. Resource library — SOPs, checklists, templates, scripts, and internal tools, organized so that the next time someone asks "how do we usually handle this?" the answer exists somewhere other than your memory.

5. Marketing and content planning — a place where your content calendar, social posts, newsletter, and marketing efforts live, so the studio's visibility doesn't disappear every time client work gets intense.

6. Goals and planning — annual and quarterly goals connected to weekly priorities, so the studio is working toward something specific rather than just responding to the loudest incoming request.

7. A central dashboard — one place where all of the above is visible at a glance, so Sunday evening planning takes ten minutes instead of two hours.

When all seven of these exist in a single, connected system, the studio stops running on memory. Follow-ups surface themselves. Project status is visible without asking. New team members have somewhere to learn from. You stop being the bottleneck — not because you stopped caring about the work, but because the work stopped depending on your recall.

This is the shift. And it doesn't happen by trying harder, switching tools, or hiring help. It happens when the operating system gets built.

Why most studios don't build this themselves

Because it takes 3 to 6 months of careful design work, and most studio owners don't have 3 to 6 months of careful design work to spare.

The bottleneck isn't skill. Plenty of designers could build an excellent operating system in Notion or Airtable if they had the time. The bottleneck is that the studio is already running, clients are already active, deadlines are already real — and stepping out of that for long enough to design a backend is something the studio structurally can't afford. This is the paradox of the wall: the studios that need an operating system the most are the ones least able to stop and build one.

This is why pre-built operating systems designed specifically for web design studios exist. Not generic "agency templates." Not blank Notion workspaces. Full operational backends, designed by people who already spent the 6–12 months figuring out what a web design studio actually needs, ready for you to populate with your own data.

The Web Design Studio Notion HQ is one of these. Joy and Reyna built it inside Hello-World Studio — not as a product at first, but as the backend their own two-person studio needed to function past the wall. They refined it over months of real operations, released it as a product, and it's now the operating system several other small studios run on.

It includes the seven areas listed above, pre-designed, pre-connected, ready to receive your projects, clients, leads, and SOPs on day one. What takes most studios months to design and build is already designed and built.

If you recognize yourself in this piece

The wall doesn't go away by waiting. The symptoms compound. Dropped follow-ups become lost leads. Lost leads become revenue shortfalls. Revenue shortfalls become pressure to take worse projects. Worse projects become burnout. Burnout becomes "maybe I should go back to being solo."

Most studios that shrink back to solo don't shrink because they couldn't find enough work. They shrink because they couldn't find enough structure — and the operational weight became heavier than the capacity gain was worth.

The wall is the point where structure has to become explicit. Past the wall, studios that build or adopt a real operating system keep growing. Studios that don't, either stall or contract.

If any of this reads like your Tuesday, the HQ was built for this exact moment. Take a look.

Related reading: It Works Until It Doesn't: The Operational Crisis Every Studio Eventually Hits — the anchor piece on the operational breakdown pattern every small studio eventually encounters.