Nicepage Hosting
Published from the Online Builder or the desktop app to a nicepage.io address or your own connected domain. Add the code in Nicepage once and publish.
Follow the steps belowNicepage's own Multi-Language feature asks you to switch the editor into each language and retype every heading, button and menu item. SiteTran keeps your one design and translates it as it loads, with AI and your own translators, on Nicepage Hosting or on your own server.
Driving growth for companies with millions of users
Nicepage is a desktop app, an Online Builder and a WordPress and Joomla plugin, and one project can be published four different ways. The right SiteTran setup depends on where your visitors actually load the site.
Published from the Online Builder or the desktop app to a nicepage.io address or your own connected domain. Add the code in Nicepage once and publish.
Follow the steps belowExported as a ZIP, to a folder or over FTP to your own server. Add the code in Nicepage before you export: Nicepage writes it into every exported page, so the next export doesn't wipe it.
Language URLs on your own server →Pages built with the Nicepage plugin or a Nicepage theme are normal WordPress pages. Use the SiteTran WordPress plugin instead: it adds the dropdown for you and can serve /es/ URLs from WordPress.
For a Nicepage template on Joomla, add all three lines of the Widget Code to your Joomla template, as you would on any custom site, so the dropdown loads on every page.
Custom integration guide →The Widget Code has three lines. Nicepage's site-wide head field accepts the two scripts but not the div that draws the dropdown, so the div goes in an HTML element in your header.
Sign up free, add your site's address, select its original language and pick the languages to translate into. SiteTran gives you your Widget Code.
Open Site Settings (the gear icon in the Online Builder), click the HTML tab and paste the two <script> lines into Additional Head HTML. Click Done. Nicepage adds this field to the head of every page.
Select your header, open Add Elements, drop an HTML element where the language dropdown should sit and paste the div into its Code field. Publish or export, then pick a language on your live site.
<script>var sitetran = {site_id: your_site_id};</script> <script src="//c.sitetran.com/widget/v3.js"></script> <div id="sitetran_translate_element"></div>
SiteTran gives you your own ready-to-paste code, with your site ID already in it. The div is where the language dropdown is created, and the widget needs it.
Additional Head HTML only accepts head tags. Nicepage users trying other markup there have reported an error listing the allowed tags: STYLE, BASE, LINK, META, SCRIPT and NOSCRIPT. A div isn't one of them, and it belongs in the visible page anyway.
Nicepage support says HTML comments aren't allowed in the Additional HTML area, and users have seen pasted code disappear after clicking Done because of one. The Widget Code has no comments, so paste it as it is.
The dropdown appears wherever the HTML element sits, so place it beside your menu. To pin it to a corner on every screen size instead, set Positioning to Fixed on window on the Dropdown Style page.
Positioning the Language Dropdown →SiteTran translates whatever Nicepage renders in the browser. It keeps watching the page, so popups, cart items and form messages that appear later are translated when they appear.
Translate your menu items and footer once and they're reused on every page. No Edit Menu dialog per language, and no second menu to keep in sync.
Headings, rich text, buttons, gallery titles, tables, tabs and accordions are translated inside your existing blocks, with the same fonts, spacing and animations.
Modal popups, FAQ answers and the cookie consent text are translated when they open. Nothing has to be duplicated or hidden per language.
Field labels, placeholders, steps, the submit button and the success message are translated. What a visitor types is sent as typed, so a German enquiry arrives in German.
Product lists, product details, Add to Cart and Buy Now buttons, and the cart popup are translated when they render. Prices and currencies stay as you set them.
Image alt text and captions are translated, and you can show a different image or PDF in each language by translating its URL, without duplicating blocks.
Nicepage added Multi-Language sites in version 4.19. You add a Language Element, switch the editor to each language and enter a translation for every text, menu item, form field and SEO title, or run AI Translations on a page.
From Nicepage's Multi-Language Sites and AI Translations documentation and its June 2026 blog post on common multi-language problems, checked October 20, 2026. Using both at once isn't needed: if you switch to SiteTran, remove the extra languages in Site Settings, because Nicepage notes that deleting the Language Element alone only hides the switcher.
People choose Nicepage for free-form, pixel-placed layouts. Translation changes the length and direction of text, so here's how to keep a carefully composed page looking composed.
German and Portuguese labels and headlines often need more room than English, which matters in a hero designed to the pixel. Add CSS for one language, on one page or on every page, from Languages › Manage <Language> in SiteTran. No change to your Nicepage project.
When a visitor picks Arabic, Hebrew or Persian, SiteTran gives translated text the right-to-left direction and updates the page's lang attribute. If a layout should also mirror, such as an image on the other side, add that CSS for the RTL language only.
Give the element a class in Nicepage's Property Panel, then target that class in your SiteTran CSS, so your styles don't depend on generated class names.
A hero image with text on it, or a PDF of your portfolio, can point to a different file for each language. Translate the file's URL in SiteTran like any other phrase. The block stays as it is.
Translating Images or URLs →Studio, project and product names usually stay as they are. Add them to the Glossary so AI and translators keep “Casa do Pátio” as written, or add the notranslate class to an element to skip it completely.
On Nicepage Hosting or an HTML export you have four realistic choices: Nicepage's Multi-Language feature, a free browser-translation widget, a script-based translation service, or SiteTran.
| Nicepage Multi-LanguageBuilt into Nicepage | Free translate widgetFor example GTranslate Free | Translation servicesFor example Weglot | SiteTranSite Settings + HTML element | |
|---|---|---|---|---|
| How it works | A Language Element plus a translation you enter, or generate with AI, for each element in each language. | A script machine-translates each page in the visitor's browser. | A JavaScript snippet in your head code. Translations are managed in the service's dashboard. | SiteTran translates your pages as they render and adds a language dropdown. |
| Nicepage plan | Business or higher. | One that lets you add custom code. | One that lets you add custom code. | One that lets you add custom code and the HTML element. |
| Updating content | Repeat each change in every language mode, then republish. | Automatic, with no way to correct a translation. | New text is detected and translated within a word allowance. | New text is discovered as visitors view it; translate it with AI, people or both. |
| Who translates | Anyone with access to your Nicepage project. | Google's machine translation only. Translations aren't stored. | Machine translation plus team members on higher plans. | DeepL, Google Translate and OpenAI, plus translators and reviewers per language, with unlimited teammates. |
| Languages and limits | Included in the plan. | All languages, machine translation only. | Capped per plan. Weglot Starter: 1 language, 10,000 words, €15 a month. | Unlimited languages on every plan. Free plan: 7K words in site. |
| Language URLs | Handled by Nicepage; its docs don't describe hreflang tags. | None. URLs don't change and the translations aren't indexed. | Subdomains or subdirectories, depending on the plan and setup. | Same URL by default, with translated meta tags. Language URLs through the Static Translation API. |
Nicepage details are from Nicepage's documentation. GTranslate and Weglot details are from their own websites; neither publishes a Nicepage-specific guide. All checked October 20, 2026. For a small site with one extra language that rarely changes, Nicepage's built-in feature can be a fine choice if you're already on Business.
Start with machine translation and refine it with your own team. You decide what gets approved and when it goes live on your Nicepage site.
Get suggestions for any phrase, or translate new phrases automatically. You choose whether they're approved automatically or reviewed first.
Invite a client, a bilingual colleague or a professional translator for each language, and choose who can approve. Turn on AI Translation Review for a second opinion.
Keep project and product names consistent in the Glossary, set Translation Rules that AI translation follows, such as a formal tone in German, and reuse past work with Similar Phrases.
Choose Styled Select, Dropdown List or Bare Select, with or without flags, and add your own CSS so it matches your header. Visitors are switched to their browser language automatically.
Here's what's translated as soon as you install SiteTran, and how to give each language its own indexable address wherever your site is published.
When a visitor switches language, the title and description you set in each page's Page Settings switch with it. You don't fill in a separate SEO tab per language.
lang attribute, updated to the selected languageBy default, every language uses your existing URL and the visitor's choice is remembered. For a separate, indexable page per language, SiteTran's Static Translation API returns translated HTML for an address you serve it from:
With an HTML export on your own hosting, you can serve language URLs yourself. On Nicepage Hosting, a proxy or edge worker in front of your domain serves them.
Talk to us about Nicepage SEOAn exported Nicepage site is plain HTML files, which makes it a good fit for the Static Translation API. SiteTran loads your live original page, applies your published translations and returns the full HTML, which your server can save and serve at a language URL.
/de/. Each call is one Static API request.sitetran.static_url_language_code_lookup for each page so the dropdown links to its language URLs and hreflang tags are added. Regenerate the files after you publish new translations.Our Nicepage integration guide shows the Online Builder, Site Settings and testing your first language in Preview. Remember the third line of your Widget Code: the div goes in an HTML element in your header.
Most Nicepage setup problems come down to where the code was pasted, the HTML element, or publishing.
<!-- --> lines.div there. The field only accepts head tags such as SCRIPT, STYLE and META.<div id="sitetran_translate_element"></div> is in your header. Without it, there's nowhere to draw the dropdown.?sitetran=on to your URL.notranslate class or translate="no" attribute.Every plan includes unlimited languages and teammates, so adding Japanese next to German never means a bigger plan. Start free and upgrade when your traffic grows.
For small sites and testing
For sites with moderate translation needs
For larger sites or several smaller ones
For large-scale international sites
Have another question? Our team is happy to help with your Nicepage setup.
Email supportPaste two script lines, add one HTML element, and let clients from Lisbon to Lyon read your work in their own language. Start on the Free plan and upgrade only when you grow.