SiteTran
Formsite forms & surveys One Custom Code item

Translate your Formsite forms and surveys into 187+ languages

Let every respondent read your questions, choices and instructions in their own language, while all the answers land in one Formsite results table. No copy of the form per language, no merging spreadsheets afterwards.

  • Free plan, no card needed
  • Answers saved as entered
  • AI + human translation
187+languages, including right-to-left
~4 minto add to a form in the Form Editor
1form and results table for every language
$0to start on the Free plan

Driving growth for companies with millions of users

Alignment Neil Patel Exomonitor Cyfe Instructified
Before you start

On Formsite, the code lives inside the form

Formsite has no form-wide setting for scripts. Code is added as a Custom Code item, which is part of the form like any question. Three things follow from that.

Every form page

One Custom Code item per page

Each page of a multi-page form loads on its own, so add the Widget Code after every Page Break. The respondent's language carries over from page to page.

Form Editor›Formatting Items›Custom Code
Embedded forms too

The code goes in the form, not your website

An embedded Formsite form runs in an iframe from formsite.com. With the Widget Code inside the form, it translates itself wherever it's shown, on formsite.com or on your website.

Share›Embed Code
Success page too

Use a Custom success page

To translate your thank-you page as well, use a Custom format Success Page and paste the Widget Code into its HTML with the text editor turned off.

Form Settings›Success Pages
  1. Page 1Consent and introCustom Code item at the top.Translated
  2. Page 2Survey questionsSame Custom Code item after the Page Break.Translated
  3. Page 3About youSame Custom Code item again.Translated
  4. Formsite pageOrder Summary, loginGenerated by Formsite, using your Custom Text wording.Test in each language
  5. LastSuccess PageCustom format with the Widget Code in its HTML.Translated
How it works

Add SiteTran to a Formsite form in three steps

These steps match the current Formsite Form Editor, with its Build, Style and Rules panels.

1

Create your SiteTran site

Sign up free, add your form's address and pick your languages. SiteTran gives you your Widget Code, which adds the language dropdown to your form.

2

Add a Custom Code item

In Formsite, click Edit on your form. In the Build panel, open Formatting Items and drag Custom Code to the top of the form. Paste all three lines into Code and click Save. Repeat on each page.

Form Editor›Build›Formatting Items›Custom Code
3

Translate and go live

Click View Form, choose a language and walk through every page. SiteTran discovers your text as it appears. Translate it with AI, your own translators, or both, then publish.

What the Widget Code looks like
<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.

Put the dropdown at the top

By default the dropdown floats in the bottom-left corner. In SiteTran's Dropdown Style, choose Relative positioning and it sits exactly where your Custom Code item is, so respondents see it before the first question.

Positioning the Language Dropdown on your Site →

Copy it to every page quickly

Hover the Custom Code item and use Copy, then drag the copy below each Page Break. For several forms, the Copy From Other Form item block brings items in from a form you've already set up.

Not the Header/Footer

Formsite's Header/Footer repeats on every page, which sounds ideal, but Formsite says its text editor doesn't allow most script tags. Custom Code items are the supported place for scripts.

Built for surveys

Respondents read their language. Your results stay comparable.

A multilingual survey is only useful if every answer can be analyzed together. SiteTran changes what respondents see and leaves what they submit alone.

Translated for respondents

Everything on the form page

SiteTran watches each page as it loads and as it changes, so text that appears later is translated too.

  • Questions, Heading and Description Text items, help text and consent statements
  • Radio, checkbox and dropdown choices, matrix rows and scale columns, ranking and rating rows
  • Required-field notes and validation messages as they appear
  • Previous, Next and Submit buttons and the page progress text
  • Placeholders, image alt text and the labels screen readers use, plus the page's lang attribute
Left exactly as submitted

Everything that goes into Results

Formsite records multiple-choice answers by choice, not by the words on screen, so a translated label never changes your data.

  • Typed answers are saved exactly as typed, in whatever language the respondent used
  • Choices are stored as the choices you wrote, in your form's language
  • Hidden Fields and pre-populated values are not touched
Results Wellbeing survey
#Safe at nightOne changeLang
1041AgreeMore evening bus routesen
1042AgreeMás luz en el parquees
Optional

Record the language of each response

Want to compare answers by language, or reply in the respondent's language? Store the language code in a Formsite Hidden Field, like the Lang column above.

  1. Add a Hidden Field and set its default value to your form's language code, such as en.
  2. Find the field's input id in your browser's inspector. Formsite uses ids like RESULT_TextField-7.
  3. Use the Widget Code shown here, with your site ID and field id, in the Custom Code item on the page that holds the Hidden Field.
Frontend API - Widget Initialization Options →
Widget Code with language capture
<script>
var sitetran = {
  site_id: your_site_id,
  language_change_function: function (language_code) {
    var f = document.getElementById('RESULT_TextField-7');
    if (f) f.value = language_code;
  }
};
</script>
<script src="//c.sitetran.com/widget/v3.js"></script>
<div id="sitetran_translate_element"></div>

Test one response per language and check the Results table before you launch.

Embedded forms

Your form is on your website? The code still goes in the form.

Formsite's embed code creates an iframe that loads your form from formsite.com. Browsers keep pages from different domains apart, so like every website translator, SiteTran works from inside the form: add the Widget Code there and the form translates itself wherever it's embedded.

  • Put the Widget Code in the form itself

    Add the Custom Code items in the Form Editor as shown above. The embedded form then translates itself and shows its own language dropdown inside the frame.

  • The form picks its language on its own

    The form detects each visitor's browser language and opens in it, and visitors can switch any time with the form's own dropdown.

  • Already using SiteTran on your website?

    Use a separate SiteTran site for your forms in the same team, and turn on Shared Resources so your forms reuse the website's Glossary, Similar Phrases and Translation Rules.

Built for Formsite

How SiteTran handles each Formsite feature

Formsite forms do a lot more than collect names. Here's what happens with rules, piping, order forms, notifications and the rest.

Translated as shown

Rules and branching

Item and page Rules keep working as you built them. Items that Rules show or hide are translated when they appear, and skipped pages are simply never shown.

Use variables

Piping and reference numbers

A question such as "Thanks, [pipe:3]. How was your visit?" shows a different name to every respondent. Turn it into one phrase with a {{variable}}, and use Automatic Number Variables for reference numbers and scores.

Adding Variables to Phrases →
Translated on your form

Order forms and payments

Product names, pricing items, coupon messages and running totals on your form pages are translated, so respondents know exactly what they're ordering before they pay.

One per language

Notification emails

With the response language in a Hidden Field, create one confirmation Notification per language in Formsite and use its Conditional logic, so every respondent gets an email in their language.

Works together

Custom Text

Formsite's Custom Text page sets one wording for built-in labels and messages. Write those in your form's main language, and SiteTran translates them on your form pages like any other text.

Keep it private

Personal data on review pages

Piped answers and success pages can show names and contact details. Wrap pipe codes in an element with the notranslate class, or turn off Public Phrase Discovery so respondents' details never become phrases.

Prevent User's Personal Data from Being Translated →
Who translates Formsite forms

Forms people need to understand to answer well

When someone can't read a question, they skip it, guess, or give up. A form in their own language gets more complete and more accurate answers.

Research and community surveys

Keep one questionnaire and one dataset. Lock your agreement scale in the Glossary so "Somewhat agree" is worded the same way in every question and every wave.

Event and program registration

Let international attendees, parents or volunteers register in their language, with one attendee list and one inventory count for every session.

Clinic and service intake

Have a native-speaking reviewer approve consent and medical wording before it goes live. Formsite no longer offers its HIPAA service to new customers, so check your compliance needs first.

HR and employee surveys

Run one engagement survey or job application for a multilingual workforce, and record each response's language to spot gaps between teams.

Compare your options

Every way to offer a Formsite form in more than one language

Formsite doesn't have a language switcher of its own. Its help articles describe copying the form per language, showing items by language with Rules, or adding a Google Translate dropdown. Here's how those compare with SiteTran.

A copy per languageFormsite's suggested method Google Translate dropdownPasted into Custom Code SiteTranCustom Code item per page
How it works Copy the form, retype every question and choice, translate the system text on Custom Text, and send people to the right copy with a chooser form and Rules. Google's website translator machine-translates the page when a visitor picks a language. SiteTran shows your approved translations on the one form you already have.
Your results A separate results table per copy, to export and merge before analysis. One table. One table. Choices are stored as written, typed answers as typed.
Changing a question Edit every copy, and keep their Rules, Notifications and Success Pages in sync by hand. Translated again automatically. The changed text shows up in SiteTran ready to translate, or is translated automatically if you turn that on.
Quality control Whatever you type. Machine translation only, with no way to correct a wording. Machine translation from DeepL, Google or OpenAI, with reviewers, approval, Glossary and Translation Rules.
Availability Uses up a form slot per language on your Formsite plan. Google has reduced support for the widget and points businesses to its paid Cloud Translation API. Free plan to start. Unlimited languages and teammates on every plan.

Thinking about switching form builders?

Some builders have form languages built in. Jotform's Form Languages setting adds translations of each field and its warning messages, with optional browser-language detection. Typeform offers multi-language forms with AI translation on some paid plans, for a set list of languages. Both mean rebuilding your Formsite forms, Rules and integrations elsewhere.

What about Weglot, ConveyThis and similar tools?

We found no Formsite guide from Weglot, ConveyThis, Bablic, Localize, Linguise or GTranslate. Like SiteTran, any of them would run inside the form itself. Weglot's plans include a fixed word allowance and 1 to 20 languages.

Formsite methods are from Formsite's help center and blog. Jotform, Typeform and Weglot details are from their own help and pricing pages, checked October 20, 2026. A copy per language still suits a form that needs very different content in each language.

Translation quality

Questions that mean the same thing in every language

In a survey, a small change in wording changes the answer. Start with machine translation, then have a fluent reviewer approve the questions that matter.

  • Machine translation from DeepL, Google and OpenAI

    Get suggestions for any phrase, or translate new phrases automatically. You choose whether they're approved automatically or reviewed first.

  • Translators and reviewers per language

    Invite a bilingual colleague or a professional translator for each language, and choose who can approve. Turn on AI Translation Review for a second opinion.

  • Glossary, rules and translation memory

    Fix the wording of your rating scale and program names in the Glossary, set Translation Rules that AI translation follows, such as formal "usted" in Spanish, and reuse past work with Similar Phrases.

  • A language dropdown that fits your form

    Choose from three dropdown types, with or without flags, and add your own CSS. Respondents are switched to their browser language automatically.

Translate your Formsite forms into 187+ languages

SpanishChinese (Simplified)VietnameseTagalogArabicFrenchKoreanRussianHaitian CreolePortuguese (Brazil)SomaliUkrainianHindiGermanJapaneseHebrew+ 170 more
Search and sharing

What about SEO for translated forms?

Most forms are reached through a link, an email or your website, not from search results. Here's what SiteTran translates on the form, and where language URLs make sense.

Included as soon as you install

Titles, link previews and accessibility

When a respondent switches language, more than the visible text changes.

  • The browser tab title of the form page
  • Meta descriptions and Open Graph tags when they're present
  • Image alt text, placeholders and ARIA labels
  • The page's lang attribute, so screen readers use the right voice
Where language URLs belong

Rank the page that holds the form

A Formsite form keeps one address on formsite.com for every language, which is ideal for sharing links. If search traffic matters, translate the page on your own website that embeds or links to the form, and give it language URLs.

fs8.formsite.com/…/indexOne URL, every language
yourorg.org/es/registerYour site, indexable

For indexable language URLs on your own website, SiteTran's Static Translation API returns translated HTML for an address you serve, or use the SiteTran WordPress plugin if your site runs on WordPress.

Talk to us about your setup

Want the walkthrough with screenshots?

Our Formsite integration guide shows each screen, from copying your Widget Code to viewing your translated form. Remember to keep all three lines of the code and add it to every page.

Read the guide
Troubleshooting

Formsite translation not working? Check these first

Most Formsite setup problems come down to a page without the code, or code that's on your website instead of in the form.

1The dropdown is only on the first page

  1. Each form page needs its own Custom Code item. Add one below every Page Break.
  2. Check that each one has all three lines, including the div.
  3. Click View Form and go through every page, not just the first.

2My embedded form isn't translated

  1. Check the Widget Code is in the form's Custom Code items, not only on your website.
  2. Look for the dropdown inside the form's frame. It's separate from any dropdown on your website.
  3. Open the form's own link from the Share page to test it outside your website.

3No dropdown appears at all

  1. Look in the bottom-left corner. That's where the dropdown sits unless you've set Relative positioning.
  2. In SiteTran, make sure the language is both Active and Live. If Hide All Widgets On Site (dev mode) is on, add ?sitetran=on to your form's URL.
  3. If you used the Header/Footer, move the code into a Custom Code item.
My Language Isn’t Showing Up in the Language Dropdown →

4Some text is still in the original language

  1. SiteTran discovers text when it's shown. Trigger your validation messages, Rules and every page, including the success page, yourself.
  2. A translation appears only after it's approved and published. To translate new text automatically, turn on Machine Translation Auto Translate.
  3. For the thank-you page, use a Custom format Success Page with the Widget Code in its HTML.
Translating Dynamic Content →

5My changes aren't showing yet

  1. After you approve and publish, translation data can take up to 30 seconds to update.
  2. A browser can keep translation data cached for up to 10 minutes.
  3. Try a hard refresh or a private window.
My New Translations or Changes Aren’t Appearing on my Website →

6Respondents' names are showing up as phrases

  1. Piped answers become part of the question text. Use {{variables}} for them.
  2. On a Custom success page, wrap pipe codes in <span class="notranslate">.
  3. For forms that show personal data back to respondents, turn off Public Phrase Discovery.
Skip HTML from Being Translated or Discovered →
Pricing

Simple pricing that grows with your forms

Every plan includes unlimited languages and teammates, so adding a sixth language to your survey never means a bigger plan. Start free and upgrade when your response volume grows.

Free

$0

For small sites and testing

  • 7K words in site
  • 3K translated pageviews / month
  • 7K machine translations

Starter

$3/mo

For sites with moderate translation needs

  • 30K words in site
  • 15K translated pageviews / month
  • 30K machine translations
Growing sites

Pro

$35/mo

For larger sites or several smaller ones

  • 90K words in site
  • 45K translated pageviews / month
  • 90K machine translations

Business

$75/mo

For large-scale international sites

  • 250K words in site
  • 125K translated pageviews / month
  • 250K machine translations
Annual billing: 2 months free · Enterprise plans for 1M+ words See all features
FAQ

Formsite translation questions

Have another question? Our team is happy to help with your Formsite setup.

Email support
How do I add SiteTran to a Formsite form?
Create a free SiteTran site and copy your Widget Code. In Formsite, edit your form, open Formatting Items in the Build panel and drag a Custom Code item to the top of the form. Paste all three lines into Code, click Save, then click View Form and pick a language from the dropdown.
My form has several pages. Do I need the code on each one?
Yes. Each page of a Formsite form loads on its own, and a Custom Code item only runs on the page it sits on. Add a Custom Code item with the same Widget Code after each Page Break, ideally at the top of every page. The respondent's language is remembered from one page to the next.
Can I put the code in the form's Header/Footer instead?
We don't recommend it. The Header/Footer repeats on every form page, but Formsite says its text editor does not allow most script tags. Custom Code items are Formsite's supported place for scripts, so use one per page.
My form is embedded on my website. Where does the code go?
Inside the form, as a Custom Code item. Formsite's embed code shows your form in an iframe loaded from formsite.com, so, as with every website translation tool, the code belongs in the form itself. With the Widget Code in the form, the embedded form shows its own language dropdown and translates itself wherever it is shown.
Are the answers people submit translated?
No. SiteTran only changes the text respondents see. What they type is submitted exactly as typed, and Formsite records multiple-choice answers by choice, so a Spanish respondent who ticks De acuerdo is stored as the Agree choice you wrote. All responses land in one results table.
Can I see which language each response was given in?
Yes, with a few lines of code. Add a Hidden Field to your form with your original language code as its default value, then use SiteTran's language_change_function option to copy the current language code into that field. Each result then records the language it was answered in.
Is the success page translated?
Yes, when the Widget Code is on it. In Form Settings, Success Pages, create a page with the Custom format, uncheck enable text editor and paste the Widget Code at the bottom of the page HTML.
Does SiteTran translate error messages and the Next and Submit buttons?
Yes. Validation messages, required-field notes, the progress text and the Previous, Next and Submit buttons are translated when they appear, along with placeholders and the labels screen readers use.
What about order forms and payments?
Product names, pricing labels, coupon messages and running totals on your form pages are translated. Like every website translation tool, the payment step follows your processor's own language settings, such as Stripe's or PayPal's. Test the Order Summary page in each language before launch.
Can I send confirmation emails in each respondent's language?
Yes. Notifications are emails sent by Formsite, so record each response's language in a Hidden Field, write one confirmation Notification per language, and use its Conditional logic so each respondent gets the right one.
Doesn't Formsite already support other languages?
Formsite lets you change a form's built-in labels and messages on its Custom Text page, which sets one language per form. For more than one language, Formsite suggests copying the form for each language or showing items by language with Rules. SiteTran keeps a single form and adds the languages on top.
Do I need a paid Formsite plan?
Not for the translation itself. Custom Code is a standard Formatting Item, and Formsite's plan comparison does not list it as a paid feature. Your Formsite plan still sets how many results each form can collect, and payments and Notifications need paid Formsite plans.
Can one SiteTran site cover all of my forms?
Yes. Paste the same Widget Code into every form you want translated, and their phrases are managed together, so shared text such as consent statements and rating scales is translated once. The words across all of those forms count toward the site's plan.
Can I test translations before respondents see them?
Yes. A language stays hidden from respondents until you set it to Live. You can also turn on Hide All Widgets On Site (dev mode) under Settings, then Publishing, and add ?sitetran=on to your form's URL to preview the language dropdown yourself.
Is there a free plan?
Yes. The Free plan includes 7,000 words in your site, 3,000 translated pageviews per month and 7,000 machine translations, with unlimited languages and teammates. Paid plans raise those limits and start at $3 per month. Compare plans.
What happens if I go over my plan's limits?
You will be prompted to upgrade or buy additional credits. Your existing translations remain intact, and new translations are paused until you upgrade.

Hear from everyone you're asking

Add one Custom Code item per page, pick your languages, and let every respondent answer in the language they think in. Start on the Free plan and upgrade only when you grow.

Start translating free Book a call Free plan · Unlimited languages and teammates