Headlines and rich text
Headline and Rich Text elements are translated inside the boxes you placed, with your fonts, colors and sections unchanged. Your design stays pixel for pixel where you put it.
Built your page in Hebrew and now need it in English, Russian, French or Arabic? SiteTran translates your one Pagewiz page as it loads, from the headline to the thank-you message, with AI and your own translators. No duplicate page per language.
Driving growth for companies with millions of users
Your Widget Code has three lines. The two script lines go in the page's Scripts & Styles. The third line, a div, goes in an HTML Code element, so you can drag the language dropdown exactly where you want it.
Sign up free, add your page's address, select its original language, such as Hebrew, and pick the languages to translate into. SiteTran gives you your Widget Code.
In your Pagewiz dashboard, hover over the page and click Design. Open Page Settings, then Scripts & Styles, then JS, and add a new script. Set Script Location to Head, name it SiteTran Widget, paste the two script lines and click Apply.
From Add New Element, drag an HTML Code element to where the dropdown should appear, such as beside your phone number. Paste the div line, click Apply, then Save. Open Preview or your live page and pick a language.
<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 widget draws the dropdown inside the div, and without it no dropdown appears.
Simplified illustration. Pagewiz's screens may look slightly different in your account.
Pagewiz's Scripts window notes that code must be wrapped in <script> tags, and its help center says the HTML part of a widget belongs in an HTML Code element. So the scripts go in Scripts & Styles and the div goes on the canvas.
Pagewiz places elements exactly where you drop them, so the HTML Code element decides where the dropdown appears. Next to the phone number in your top section works well. To float it in a corner of the window instead, set Positioning to Fixed on window on the Dropdown Style page.
Positioning the Language Dropdown →Our screenshot guide shows the two script lines in Scripts & Styles. If you set it up that way and see no dropdown, add an HTML Code element with the div line, click Apply and Save.
SiteTran translates what Pagewiz renders in the browser and keeps watching the page, so messages that only appear after a click are translated when they appear.
Headline and Rich Text elements are translated inside the boxes you placed, with your fonts, colors and sections unchanged. Your design stays pixel for pixel where you put it.
Button labels are translated, and links keep working. Buttons that jump to a section with a link such as #SECTION4 scroll as before with the default URL Type.
Field labels, placeholders, dropdown and multiple-choice options, checkbox text and the submit button are translated. What visitors type reaches your Pagewiz Leads as typed.
Error tooltips such as "Please fill in a valid phone number" and the thank-you message box appear only after a submit. SiteTran translates them when they appear.
The Page Meta Title, Page Meta Description and Facebook share title and description from Pagewiz's SEO & Plugins settings switch with the visitor's language.
Numbers stay as they are, and names you add to the Glossary, such as your brand or project, are kept as written in every language. Your offer reads the same everywhere.
Pagewiz builds a mobile design, an A/B variant, a thank-you page and each step of a multi-step form as its own page. SiteTran translates every page that has the code, so check each one before you launch in a new language.
The page your ads point to. Start here.
divA separate 540px page connected under Mobile › Connect your Mobile Design. Place the dropdown again for the narrow layout.
Pagewiz describes variants as independent pages that share one URL. Check each variant's Scripts & Styles.
divIf your form redirects to another Pagewiz page, that page needs the code too, or visitors return to the original language after they convert.
Pagewiz builds each step as its own page on the same domain, so the visitor's language carries from step to step once every step has the code.
Tick Add to script library when you add the SiteTran script, then use Add from library on every other page. Edit it once and every linked page updates. On plans without it, paste the same two lines into each page. The div is always added per page with an HTML Code element.
Many Pagewiz pages are designed in Hebrew first, for audiences that also read Russian, French, English or Arabic. SiteTran handles both directions from one page.
Pagewiz sets a page to RTL or LTR under Size & Direction. When a visitor switches from Hebrew to Russian, SiteTran switches the text direction to left-to-right, and back again for Hebrew or Arabic.
Pagewiz positions each element at a fixed spot. Translated text fills the same boxes, and Russian or French often runs longer than Hebrew, so check headlines and buttons in each language.
In SiteTran, open Languages, click Manage for a language and add CSS Styles for that language's pages, for example a smaller headline for Russian. Nothing changes in Pagewiz.
Prefer to keep the page right-to-left in every language? Add sitetran.update_direction = false; to your Widget Code. Updating CSS Styles by Language and Page →
SiteTran translates the text shown in the visitor's browser, so your Pagewiz form, lead list, notification emails, webhooks and Zapier connections keep working exactly as they do today.
Validation tooltips and the thank-you box only exist after a submit, so send one test lead per language. SiteTran then picks those messages up as phrases you can translate.
By default, SiteTran switches each visitor to their browser language when it's on your page, and remembers their choice. When a Russian-language ad or WhatsApp message should always open the Russian version, set URL Type to Use Hash on the Dropdown Style page and end the link with #ru.
Using anchor links? If your buttons jump to sections with links like #SECTION4, keep the default URL Type on that page, and visitors' browsers still pick their language.
Pagewiz doesn't have a translation feature, so the choices are a duplicate page per language, a free browser-translation widget, a translation script or proxy service, or SiteTran.
| A page per languageDuplicate in Pagewiz | Free translate widgetFor example GTranslate Free | Translation servicesFor example Localize, Crowdin | SiteTranScripts & Styles + HTML Code | |
|---|---|---|---|---|
| How it works | Duplicate the page, retype every element in the new language and set its direction under Size & Direction. | A script machine-translates the page in the visitor's browser. | A script added in Scripts & Styles. Translations are managed in the service's dashboard. | SiteTran translates your page as it renders and adds a language dropdown you place yourself. |
| Updating content | Repeat each change, price or date on every copy, plus each copy's mobile design. | Automatic, with no way to correct a translation. | New text is detected on the pages you visit and sent for translation. | New text is discovered as visitors view it; translate it with AI, people or both. |
| Campaigns, leads and A/B tests | A separate URL, statistics, leads list and A/B test for each language. | One page and one leads list. | One page and one leads list. | One page, one leads list and one A/B test, with per-language links if you want them. |
| Who translates | You, or anyone with access to your Pagewiz account. | Google's machine translation only. Translations aren't stored. | Machine translation and your team or the service's translators, depending on plan. | DeepL, Google Translate and OpenAI, plus translators and reviewers per language, with unlimited teammates. |
| Right-to-left | Set per page in Size & Direction. | Depends on the widget. | Depends on the service. | Direction switches with the language, with per-language CSS for fine-tuning. |
| Language URLs | Each copy has its own URL. | None. URLs don't change and translations aren't indexed. | Varies by service and plan. | Same URL by default, with translated meta tags. Language URLs through the Static Translation API. |
Pagewiz details are from its help center and pricing page. Localize publishes a Pagewiz setup guide, and Crowdin lists a Pagewiz app that is now part of its Website Translator. Details are from their own websites, checked October 20, 2026. For a single campaign in one extra language that won't change, a duplicate page can be a reasonable choice.
Start with machine translation for speed, then have a native speaker check the headline, the offer and the button. You decide what goes live.
Get suggestions for any phrase, or translate new phrases automatically. You choose whether they're approved automatically or reviewed first.
Invite a Russian-speaking salesperson, an agency client or a professional translator for each language, and choose who can approve. Turn on AI Translation Review for a second opinion.
Keep your brand and project names as written in the Glossary, set Translation Rules that AI translation follows, such as the formal "вы" in Russian and "vous" in French, 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 page.
Most Pagewiz pages get their visitors from ads, email and social links, where a translated page at the same address is all you need. If organic search in each language matters too, you can add language URLs.
When a visitor switches language, the meta title and description you set in Pagewiz's SEO & Plugins switch with it, along with the rest of the page.
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:
Language URLs are served by a small proxy or edge worker on your own domain, in front of Pagewiz. If your page uses Pagewiz's Robots tag with NOINDEX, as many ad landing pages do, you can skip this step.
Talk to us about Pagewiz SEOYour page stays on Pagewiz. A small proxy or edge worker on your domain answers requests for language addresses, asks SiteTran for the translated page and returns it, with the original passed straight through.
/ru/, the proxy calls the API with the original page's URL and a language code and returns the translated HTML. Each call is one Static API request, so cache the results.sitetran.static_url_language_code_lookup so the dropdown links to your language URLs and hreflang tags are added. Refresh cached pages after you publish new translations.Our Pagewiz integration guide shows each screen from opening Design to previewing the dropdown. Add the div line in an HTML Code element as shown on this page.
Most Pagewiz setup problems come down to the missing div, a page that doesn't have the code yet, or longer text in a fixed-size box.
<div id="sitetran_translate_element"></div>, and that the two script lines are in Scripts & Styles › JS.?sitetran=on to your URL.div where it fits the 540px layout, then Save.div.#SECTION4 are read as a language. Switch back to the default for pages with anchor links.Every plan includes unlimited languages and teammates, so adding Arabic next to Russian never means another page to build or 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
Can't find your answer? Our team is happy to help with your Pagewiz setup.
Email supportAdd three lines, save, and let every visitor your campaign reaches read your offer in their own language. One page to edit, one leads list, every language kept in step. Start free and upgrade only when you grow.