A website in several languages

Do this

1. Open Settings → Languages.
2. Check which language is the main one. That is the language you write in.
3. Tick the other languages you want in the Languages box. It takes several.
4. Publish.

What happens next: the translations are made the moment you publish, never before, so a half-finished sentence is never shown. Visitors get a language switcher and land on the language their browser asks for. Words that matter you correct afterwards, and the correction stays.

If your customers aren't all Swedish speakers, your website can carry several languages. You write in one language, and SnabbSajt translates the rest.

Which languages

Your website can be in Swedish, English, Polish, German, Danish, Norwegian, Finnish, French, Spanish, Turkish, Arabic or Persian. Pick any combination under Settings → Languages. The SnabbSajt admin itself stays in Swedish, English or Polish, which is separate from what visitors see on your website.

Swedish, English and Polish are hand-written. The text SnabbSajt starts you with in those three languages is written by us. Pick one of the other nine and the website is written in English first, then translated into your language by AI as the website is created. You always read through and change every text yourself afterwards. If the translation cannot run, for example when AI is turned off, the text stays in English until you change it.

Arabic and Persian read right to left. Pick either one and the published website mirrors itself: the menu, the buttons, the forms and the text all start on the right-hand side, the way a reader of those languages expects. The editor canvas mirrors too, so what you are editing is what your visitors get. The SnabbSajt admin around it, meaning the menus, the settings and this help website, stays left to right. Prices, phone numbers and opening hours keep ordinary digits (1 250 kr), not Arabic-Indic ones, because they are Swedish numbers your customers will dial or compare. Your website keeps the typeface you chose for Latin text; Arabic and Persian letters fall back to the reader's own device font, so the shapes are correct and readable but not the same typeface.

Privacy policy, terms and accessibility pages are written in English first and then translated into your website's language, like the rest of your content, so a Turkish website gets Turkish legal pages. That translation uses a few AI credits per page and is redone whenever you regenerate the page. If it cannot run, the page stays readable in English rather than half-translated. These pages are a draft to review, not legal advice, in any language. Adding many languages at once uses more space on each publish; if a language cannot be stored, visitors see your primary language until you publish again with fewer secondary languages or shorter pages.

Your website's language is not the app's language

These are two different settings, and it is worth knowing which is which.

The globe in the top corner of SnabbSajt sets the language you read the app in. It has nothing to do with your website. When you create a website we ask, in its own step, what language your customers read, and that is what gets written and published.

So if you run a Swedish business but prefer the app in Polish, you get a Polish app and a Swedish website, which is what your customers need. New websites are Swedish unless you say otherwise, and you can change it later under Settings → Languages.

Reading your own website in your language

If your website has to be in a language you don't read, you can still check what it says. In the editor, click the globe at the top and switch on Read the page in your language. The page you are looking at is shown in the language the app is set to.

It changes nothing. Your text stays exactly as it is, the website is still written and published in its own language, and visitors see what they saw before. It is a way to read your own page, not a second version of it.

It is free. The first look translates the page; after that, only a sentence you have actually rewritten costs anything, so opening the editor again is instant. If the translation is unavailable, the page simply stays in its own language instead of showing you an error.

You still write in the website's language, and while the reading view is on the page cannot be edited at all - so a translated sentence can never end up in your own text by accident. Switch the reading view off to edit as usual, or open the panel beside the page, which always shows your own words rather than the translation.

How it works

1. Your primary language is the one you write and edit in. It's the website language you set under Settings → Languages.
2. Add the other languages you want in the same place. The Languages box is a multi-select: tick every language you want, not just one. You can also ask the AI assistant in the editor ("can the website be in English too?") and it sets this up for you.
3. Publish. The translations are created at that moment - never before, so a half-finished sentence is never translated and shown.

Visitors get a language switch on the published website and land on the language their browser asks for.

If you change which language is the main one

Your main language is the one on the plain web address. The others sit under a short code, like /en/services. So swapping which language is the main one moves every page: the language you promote loses its code, and the one it replaces gains it.

You do not have to do anything about the old links. When you publish, we send every old address on to its new page automatically, so a link on Google, on your business card or in a post someone shared still opens the right page.

Fixing a translation in the editor

The globe at the top of the editor shows which language you are editing, as SV or EN. Click it, pick another language, and the canvas shows the published translation so you can rewrite any sentence right on the page. The button is tinted while you are in a language other than your primary one, because the difference matters: what you write there saves straight to the published translation, not to your draft. Switch back to the primary language and you are editing the draft as usual again.

If your website has one language the globe is still there, and it takes you to Settings → Languages so you can add one.

Translation runs in the background, after your website has gone live, and it can never hold up or fail a publish. The publish sheet reports the result for each language once it lands: translated, still working, partly translated, or not translated because your AI credits didn't cover it.

Partly translated means the page is live but some of the text is still in your own language. It happens when part of a page can't be translated on the attempt. We try each part twice before giving up, and publishing again picks up what's left.

A developer package can already contain an authored version of every page. In that case publishing uses those words and language-specific addresses without an automatic AI charge. You can review them in the same editor. Translate with AI still works when you explicitly choose it, and later layout or link changes come from the current primary-language draft.

If your credits won't cover a language, the publish sheet says so before you publish, so you can top up first. It's only a heads-up, and you can always publish anyway. What the visitor sees depends on whether that language has ever been translated:

• Never translated: they see your primary language. The page works, it's just not in their language yet.
• Translated on an earlier publish: they keep seeing that older translation. It won't pick up the changes you're publishing now, so if you changed a price or your opening hours, that language will still show the old one until you top up and publish again.

Correcting a translation

Automatic translation gets ordinary sentences right and trade words wrong. Your own service names, product names and local expressions are exactly what it will mangle - so check those.

In the editor

On a multilingual website, the editor top bar shows a language switcher next to Preview. Pick a secondary language to edit that translation on the canvas, in the same place you normally change words. Layout (add, move, delete sections) stays on the primary language; switch back to change structure. If the translation is missing or out of date, a banner asks you to publish or run AI translation first. Canvas text editing unlocks only when that language is ready.

In Settings

Open Settings → Translations (it only shows up when the website has more than one language). Each page shows a status:

• Ready - translated and reviewed.
• Missing - not translated yet. Run Translate with AI first.
• Changed since translating - you edited the original. Translate again, then fine-tune.

Manual fine-tuning opens once a full translation has been saved, so you never edit half a page.

What it costs

Each language costs 5 AI credits per translation run for a small website; a bigger website costs a multiple of that, because there's more to translate. Fixing the words by hand afterwards is free.

Buttons and system text

The part you don't have to think about: buttons and system text like "Send", "Book" and "Read more" come across on their own. Every language version gets its own, at the same time as your own content is translated. So you set the languages in one place and get the whole website in them, not only the words you wrote.

Next steps

• Publish your website - when translations are created.
• Settings - adding languages and reviewing them.
• Edit text - writing the original.

---