Most bilingual website examples are one site with a translation layer bolted on, the same URL, the text swapped by a plugin, nothing separate for Google to index. Del Cielo a la Tierra is not that. It is two full sites inside one installation: every page exists twice, at its own URL, crawled and indexed independently, with its own navigation and its own capture flow.
37 pages, live, built on WordPress and Divi with no paid translation plugin at any point.
A translated site says the right words and sounds like nobody
A website in two languages is not the same product as a website translated into two languages, and the clients who matter most can tell.
The documented before-state, three problems:
- No digital presence at the level of the work itself, so credibility had to be rebuilt in every conversation
- No email capture at all, every visit that left was a contact lost permanently
- Two language audiences served by one generic version, so neither felt addressed
Enquiries arrived by direct referral only, which caps growth at the size of the referral network.
The reason automatic translation was rejected is on the record and it is not about accuracy: it translates words, not editorial decisions. A personal brand may need an informal register with French clients and a more formal one in Spanish. No tool makes that call.
What was built
Two versions that are not mirror images of each other, and that asymmetry is the proof.
37 pages are live, confirmed through the WordPress API in July 2026, split 17 in Spanish and 20 in French. A translated site has identical page counts by definition. These do not, because each version was written for its own audience and stopped where that audience stopped needing pages.
The build, layer by layer:
- Parallel-page architecture. Each service has its Spanish page and its French equivalent, with their own slugs. WordPress multilingual without plugin, because at two languages a paid translation layer buys nothing the structure does not already give.
- 5 service pages per language, two of them carrying published prices, plus 10 blog articles: five in each language.
- 4 capture points: an embedded form at the end of every service page, an exit intent popup carrying the same offer, two dedicated newsletter landing pages (
newsletter-es,newsletter-fr), and a separate form with its own offer on the classes page. - 2 different lead magnets by entry intent: a downloadable guide on the service pages, a free introductory class on the classes page. The buy-ready visitor and the curious visitor are not asked for the same thing.
- 2 independent automation flows in MailerLite, one per language. The WordPress MailerLite integration tags the subscriber at the moment of capture, so a visitor arriving from the French version enters the French sequence and never receives a Spanish email.
The segmentation happening at capture rather than during a later cleanup is the part that makes this maintainable by one person who is not a marketer.
This is the digital infrastructure engineering line, on a two-language site.
What the same setup costs on a closed platform
The advertised platform fee is never the cost. The second language and the email automation each arrive as their own subscription.
The Squarespace vs WordPress cost comparison, as researched in July 2026:
- Squarespace Core at $23/month ($276/year), plus Weglot from $17/month ($204/year) because Squarespace has no real bilingual support, plus MailerLite Comfort from $12/month ($144/year) because Squarespace Email Campaigns is significantly more limited for automations. Documented total: $624/year in subscriptions.
- Wix Core at $29/month ($348/year) plus MailerLite at $12/month ($144/year). Documented total: $492/year minimum: and the word minimum is in the source, because the same paragraph states that serious editorial content also needs a translation third party on top. The Wix multilingual cost is a translation-credit allowance, not a bilingual site.
- Neither platform offers conditional flows per language, and neither delivers a lead magnet natively, that path needs a connector such as Zapier or Make, which is another subscription and another point of failure.
The delivered stack is Divi at $89/year, plus hosting.
No savings figure is published on this page, on purpose. The hosting cost is not documented, so the WordPress-side total is incomplete; and the Wix total is incomplete in the source itself by its own admission. Both alternatives’ totals are quoted exactly as researched. Subtracting them would produce a number that looks precise and is not.
Frequently asked questions
Do I need a translation plugin to run a website in two languages?
No. At two languages a parallel-page architecture works without any paid translation layer: each page has its own equivalent in the second language, with its own slug and its own text. A translation manager starts to pay for itself from three languages upward.
What is the difference between translating a site and writing a version per language?
A translation reproduces the words; a separate version reproduces the decisions. Register, page order and which pages exist at all can differ per audience, which is why most multilingual website examples that work are not mirror images of each other.
How does a subscriber end up in the right language sequence?
The subscriber is tagged by language at the moment of capture, not sorted afterwards. The form they used determines which automation flow they enter, so the two audiences never receive each other's emails.
What does a two-language site cost per year on Squarespace or Wix?
As researched in July 2026: Squarespace Core plus Weglot plus a separate email tool totals $624/year in subscriptions, and Wix Core plus a separate email tool totals $492/year minimum, before the translation third party that serious editorial content still requires.
Two languages, one system
The build is the same shape for any language pair: two editorial versions, capture on every entry point, one automation flow per audience.
Tell me which two languages, and which of the two your best clients read.