Multilingual websites

Question 1

Is it easy to make a multilingual site?

Accepted Answer

Yes. Pick the languages in the wizard and Blanca's Builder generates routes, hreflang tags and translated content automatically.

Question 2

How many languages does the platform support?

Accepted Answer

24 manually translated UI languages today. Generated sites can support far more — any language your AI provider can write well.

Question 3

What is hreflang and why do I need it?

Accepted Answer

hreflang tells search engines which language and region each page targets. Blanca's Builder emits correct hreflang and x-default automatically across the site.

Question 4

Should I use subdirectories, subdomains or different domains?

Accepted Answer

Subdirectories (/es/, /fr/) are easiest and inherit domain authority. Subdomains and ccTLDs make sense when each market has separate teams or distinct branding.

Question 5

Is auto-translation good enough for production?

Accepted Answer

Modern LLMs deliver near-human quality for marketing copy. We still recommend a one-pass review for high-stakes pages (pricing, legal) by a native speaker.

Question 6

Are right-to-left languages supported?

Accepted Answer

Yes. Arabic, Hebrew and Urdu render right-to-left with mirrored layouts. The platform itself ships in Arabic with full RTL support.

Question 7

Does the site include a language switcher?

Accepted Answer

Yes. A header switcher is generated by default. Each option links to the corresponding URL with hreflang annotations.

Question 8

How do I translate blog posts and CMS content?

Accepted Answer

Each entry has per-language fields. Translate manually or click 'Translate with AI' to draft and edit. Drafts only publish when you mark them ready.

Question 9

What is hreflang x-default?

Accepted Answer

x-default points search engines at the fallback page for languages you do not target. Usually the English version, served when nothing else matches.

Question 10

Does the site auto-redirect visitors by language?

Accepted Answer

Optional. The first visit can be redirected based on Accept-Language. After that the user's choice is remembered. Google requires a way to reach every language directly.

Question 11

Should I translate images with text in them?

Accepted Answer

Yes if the text matters. Keep text out of images when possible and use HTML overlays so each language renders without re-exporting graphics.

Question 12

Can I show different currencies per language?

Accepted Answer

Yes. Settings, Localisation lets you bind a currency to each locale. Prices format with the correct symbol, separator and tax rules.

Question 13

Are dates and numbers formatted per locale?

Accepted Answer

Yes. Every component uses the Intl APIs with the user's locale. Dates, numbers, percentages and currencies render correctly without extra code.

Question 14

Are SEO tags translated per language?

Accepted Answer

Yes. Title, description, OpenGraph and JSON-LD are generated per locale from the translated content.

Question 15

Does Blanca's Builder remember my translation choices?

Accepted Answer

Yes. The Memory Bank stores brand-specific glossary entries. The Coach uses them so terminology stays consistent across pages and updates.

Question 16

What is the zero-fallback policy?

Accepted Answer

Every visible string in the platform UI must be translated 100% in every supported language. There are no English fallbacks; missing keys are treated as bugs.

Question 17

How do I add a new language to my generated site?

Accepted Answer

Settings, Languages, Add language. Existing pages are queued for translation; the new language appears in the switcher when ready.

Question 18

Does each language cost extra?

Accepted Answer

No extra hosting cost. AI translation usage is metered if you use Managed AI; manual translation is free.

Question 19

Is a multilingual site treated as duplicate content?

Accepted Answer

No, when hreflang is correct. Search engines understand that /en/about and /es/about are language variants, not duplicates.

Question 20

Does the launch checklist verify translations?

Accepted Answer

Yes. The build fails launch if any visible string is missing in any language. You cannot publish a half-translated site by accident.