Quick answer: You don't need a second website to serve a second language. In Faster, languages work as a translation layer over the site you already have: the pages, design, and structure stay singular, and each language adds its own wording on top. Anything not yet translated falls back to your original text — so you can roll languages out page by page, with a switcher in the header that remembers each visitor's choice.
The traditional way to take a small-business website multilingual is quietly ruinous: duplicate the whole site per language, then maintain the copies forever. Update a price on the English site and forget the Spanish one, and you now have two sources of truth disagreeing in public — which is worse than having one language in the first place.
That's why most businesses that should be serving customers in two languages never do it. The work isn't the translation; it's the rebuild and the double maintenance. So Faster takes the duplicate-site model off the table entirely.
One site, with a translation layer on top
In your workspace, a language is not a copy of your website — it's an overlay. There is exactly one set of pages, one design, one navigation, one structure. Each language you add is a set of translated phrases layered over that single site: the heading "Our Services" knows its Spanish wording, its French wording, and shows the right one to the right visitor.
The consequences are exactly the ones the duplicate-site model fails:
- One change, every language. Reorganize a page, change a photo, add a section — done once, reflected everywhere. Only new wording needs translating.
- No structural drift. The Spanish site can't fall behind the English one, because there is no Spanish site — just Spanish words on the same site.
- Adding language three is cheap. The hard work — marking what's translatable — happens once. French after Spanish is just another set of translations.
What translates — and what deliberately doesn't
A good multilingual site is not 100% translated, and that's by design. The line matters:
Everything a visitor reads as interface: headings, paragraphs, buttons, menu items, form labels and placeholder hints, image descriptions, confirmation messages. Even the small things — a search box that says "Buscar..." instead of "Search..." is the difference between translated and localized. Sample formats adapt too: a phone-number hint should look like a local phone number in each language.
Your brand name, your web addresses, product codes and technical identifiers. Translating these breaks trust or breaks links — a visitor on the Spanish site should still find you at the same address, under the same name.
Your content — blog posts, product descriptions, service write-ups — is its own project, with its own editorial judgment. The translation layer handles the frame of the site first, which is what makes a visitor feel at home immediately. Translate the content that earns it, starting with what your second-language customers actually read.
Ask AI to do the sweep — this is the "without rebuilding" part
Marking every visible phrase on every page as translatable used to be the rebuild. Now it's a request: ask the AI to update the page — "make this page available in Spanish and French" — and it walks the page, marks each visible phrase, and produces the translations for review.
Review it like any AI draft — the same drafts-and-approval discipline applies, and translation has its own confidently-wrong failure mode: tone. A massage studio's "Book your escape" and a plumber's "Get it fixed today" should not come back in the same register. If you have a bilingual person on the team or among your regulars, twenty minutes of their judgment on the key pages is the best money in the whole project. Machine translation gets you to reviewable; a native reader gets you to trustworthy.
The fallback rule: never a broken page
The overlay model has one rule that makes the whole rollout safe: anything not yet translated shows your original wording. A missing phrase never produces a blank space or an error — it falls back to English (or whatever your base language is).
That changes the project plan. You don't need a finished translation of the entire site before launching a language — you can ship the homepage and booking page in Spanish this week and let deeper pages follow. Visitors see a fully working site at every step; the worst case is a paragraph that hasn't switched languages yet. Multilingual stops being a big-bang launch and becomes ordinary incremental work, protected by the same checkpoints and safe-publish review as any other site change.
How visitors choose — and how the site remembers
A language switcher sits in your site header — part of your navigation, present on every page. Three details make it feel native rather than bolted on:
- Languages appear in their own names. A Spanish speaker sees "Español," not "Spanish" — you never have to find your language in a list written in someone else's.
- The choice sticks. Pick a language once and the site remembers it for a year — every page, every return visit, no re-selecting.
- The page identifies its language properly behind the scenes, which is what search engines and screen readers use — so accessibility and SEO follow the visitor's actual language, not a site-wide default.
Plugins arrive with their languages included
Here's where the overlay model quietly pays for itself: the interactive parts of your site — booking flows, shop checkout, event pages — come from plugins, and plugins ship with their own translations built in. Activate booking on a bilingual site and the "choose a time" and "booking confirmed" messages already speak both languages.
And when you've customized wording — through the theme editor or your own phrasing of a button — your version wins over the plugin's stock translation. The plugin provides the safety net; your voice takes precedence wherever you've expressed one. Live moments inside those flows are covered too — a "3 spots left" counter updates in the visitor's language, plural forms and all.
A rollout that respects your week
- Pick the language your customers already use with you. The voicemails, the walk-ins, the DMs — that's your evidence, same as choosing a social channel.
- Start with the money pages — homepage, services, booking, contact. The pages from your original launch checklist are the same ones that earn translation first.
- Let AI sweep, then get one native read on tone for those pages.
- Publish behind the safe-launch review, click through the booking flow in the new language yourself, and let the fallback rule carry the long tail.
Key takeaways
- Languages are an overlay on one site: no duplicate site, no structural drift, no double maintenance.
- Interface wording translates: brand names and addresses don't; your content library is a separate, prioritized decision.
- AI does the page sweep and draft translations: one native-speaker review pass on key pages buys the trust.
- Untranslated phrases fall back to your original text: so you can launch a language incrementally, never broken.
- The switcher remembers: each language shows in its own name and the visitor's choice sticks for a year.
- Booking, shop, and other plugin flows ship with translations included: and your custom wording always wins.
Frequently asked questions
Do I need a separate domain or address for each language?
No. One address serves every language — visitors pick their language with the switcher and the site remembers it. There's no second site to register, host, or maintain.
Which languages can I add?
Any language is another translation set on the overlay — there's no fixed menu. Most businesses start with one additional language and add more only when customers ask, since each one deserves a real review pass, not just a machine draft.
Is machine translation good enough for my website?
Good enough to draft, not to vouch. AI translations of interface wording are reliably serviceable; tone on your key sales pages is where a native reader earns their twenty minutes. Draft with AI, review with a human, ship with confidence.
What happens to pages I haven't translated yet?
They display in your original language, fully functional. Visitors never hit a blank or broken page — which is exactly what makes a gradual, page-by-page rollout safe.
Do my blog posts get translated automatically?
No — and you wouldn't want them to be. The translation layer covers your site's frame: navigation, headings, buttons, forms, and flows. Content like posts and product descriptions is an editorial decision; translate the pieces your second-language customers actually read, starting with the ones that drive bookings or sales.
Will a second language hurt my search rankings?
It usually helps. Each page correctly identifies its language to search engines, so your Spanish-speaking customers can find you searching in Spanish — queries your English-only site was invisible to. One site with proper language labeling avoids the duplicate-content problems that plagued the old copy-the-site approach.
If a meaningful slice of your customers lives in another language, the rebuild excuse is gone — the site you already built is one AI sweep and one good review away from speaking to them. Start with the homepage, and say it in their words.