Email MK Tools

A Bilingual Site on systeme.io: What Needs a Second Copy

Selling in two languages on systeme.io: page versions, the blog and course that hold one language each, tagging contacts by language, and where Free ends.

Plenty of small businesses sell in two languages, and the question they bring to systeme.io is simple: can one account run the business in both?

The answer depends on which part of the business you mean. systeme.io's website builder handles a second language as a version of each page. Its website article says it plainly: "The Websites feature supports multilingual structures." The rest of the account works differently. A blog has one language setting. So does a course. And the email side sorts people by tags, not by language.

So a second language costs you two different things. On the website it's a second version of each page, inside the same site. Everywhere else it's a second copy of the whole asset: another blog, another course, another tag, another welcome sequence. This guide goes through each part in that order and counts the copies, because the copies, not the pages, decide your plan. Where the documentation stops short, I flag it and give you the check to run.

How each part holds a language

Part of the accountHow it handles language (help center)What a second language takes
WebsiteLanguages added in Settings, then Languages; each page gets a language-specific versionA second version of each page, in the same website
BlogOne language setting per blog, in Blog settingsA second blog
CourseOne language per course, set in the course settingsA second course
ContactsA Language field on every contactA way to tell your forms which language a contact chose
EmailsNewsletters and campaigns go to contacts by tagA tag per language, and a sequence per language

Read the table from the top down. The website is the one place where a second language is cheap: no new asset, just page versions. Every row below it doubles something. If your business is a website and a contact form, you're nearly done. If it's a blog, a course and a welcome sequence, a second language means a second set of all three.

Page versions: the website's second language

The multilingual setup lives in the Websites feature, under Sites, then Websites. Your main language is chosen when you create the website. To add more, open the website, go to the Settings tab, then Languages, and add the languages you want. The website article is explicit that this comes first: "You must first add the languages you want to support in Settings → Languages before they can appear here."

Then build the second version of each page. Build the website in your main language first. For each page, open the three-dot menu, then Settings, and on the Languages tab click Duplicate language-specific versions of this page. The dropdown at the top of the Pages tab switches between languages, and from there you edit the new version by hand.

Editing by hand is the whole job. Switching the dropdown, the article says, "does not translate content automatically". The duplicate is a copy in your first language until you rewrite it.

The plan table lists Languages per website as 2 on the free plan. A bilingual site fits Free; a third language doesn't.

What the website article doesn't describe is what a visitor sees: the address a language version lives at, and whether the site shows a language switcher on its own. Before you send traffic to the second language, open both versions from outside your account and check the addresses. If your menu doesn't offer a way across, add a link to the other language's home page yourself.

A form and a tag per language

The website's Form element has an Actions tab, and its In-editor automations can add a tag, subscribe someone to a campaign or send an email when the form is submitted. That tag is how the rest of your account will know which language a subscriber chose.

Every contact in systeme.io carries a Language field. The add-contact article lists it as one of two mandatory fields, with the email address, when you add a contact by hand. What it doesn't say is whether a website form fills that field in from the page's language. Rather than rely on it, tag by language on the form itself: a tag such as fr on the French version's form and en on the English one.

Because the second version starts as a copy, open the form on the duplicated page and check its Actions tab. If the copy still adds the first language's tag, change it there. It's the one edit that keeps your list sorted.

This is the first place the free plan feels tight. Free allows one tag. Two languages need two.

One blog per language, if search matters

A blog is created under Sites, then Blogs, and the blog article lists its settings as the blog's "name, domain, URL path, and language". One setting, one language.

If you want to publish articles in both languages, that's two blogs, each with its own language, its own posts and its own URL path. The free plan includes one blog. You could post in both languages on a single blog, but the blog itself would still be labeled with one.

This matters more than it looks if search traffic is part of the plan. The sitemap article says your domain's sitemap covers funnels and blogs, and that "Other assets (like Websites) will be supported in future updates." So for articles you want found in both languages, the blog is the part of systeme.io that reaches the sitemap today, and the website isn't.

One course per language, for the student dashboard

A course has a language too. The student dashboard article says you can change it in the course settings, and explains where it shows. Students see your other courses in the Explore tab of their dashboard, and "The Explore tab only displays courses that match the language of the student's profile." Its example: a student whose profile is set to French "will not see your English courses."

So a course taught in two languages is best built as two courses, each set to its own language, each with its own sales page. That way a French student browsing the dashboard finds the French one. The free plan includes one course.

One part of the course doesn't change with your choices. The email that gives a new student their login is fixed. The course access article says it can't be modified: it's "the same template sent to all of our customers." The help page doesn't say which language that template is sent in, so enroll yourself in the second-language course and look at what arrives.

That check isn't hypothetical. Bom Baxx, a seller with German buyers, wrote on Trustpilot in January 2024 that his customers were "properly tagged as German in the system" yet still received English emails, such as a resent course-access email: "Since we cannot change the text of this email, my German customers receive English emails." systeme.io replied that it was working on an issue with one of the emails. That was in 2024, and I can't tell from the help center whether it's fixed, which is why the test enrollment belongs on your list.

I don't expect the template itself to open up soon. The access-email article was last revised in December 2025, nearly two years after that review, and it still answers "This is currently not possible" before defending the email as it stands: "It works perfectly, and the most important thing is that our customers are able to access their courses easily." That reads as a settled position. Plan the second-language welcome as a separate email of your own, sent by a rule on the language tag, next to the fixed one.

Emails sorted by tag, one set per language

systeme.io's email side doesn't sort by language. It sorts by tag. With a tag per language in place, each language gets:

  • Its own welcome sequence. One campaign for the English tag, one for the French tag, which the form's in-editor automation can subscribe people to. Free allows one email campaign.
  • Newsletters sent by tag. systeme.io's newsletter article describes choosing a newsletter's audience "by including or excluding specific tags", so write one per language and send each to its own tag.
  • Its own confirmation email, if you can get one. Double opt-in is switched on per form, and the confirmation email is edited in one place, under your profile picture, Settings and Emails, in the section headed Double opt-in. The double opt-in article doesn't mention a version per language. If you run double opt-in on both forms, write that email in both languages, one after the other, or test whether the contact's Language field changes it.

A visitor's check of both languages

Before you promote the second language, check it as a visitor would. Both versions of the website's home page should load, at addresses you're happy to share. A test sign-up on each form should land with the right tag, and the welcome email for each tag should arrive in the right language. If you have a course in each language, a test student set to the second language should see that course under Explore.

Free holds the bilingual website; Startup holds the second copies

PlanLanguages per websiteBlogsCoursesTagsEmail campaignsCost
Free21111$0
StartupNo cap listed551010$17 monthly, $170 yearly

For a two-language business, the website on its own fits Free, two languages and all. The first thing outside the website that needs a second copy doesn't. A language tag on each form is two tags, a welcome sequence for each language is two campaigns, a blog in each language is two blogs, and a course in each language is two courses. Each of those is one more than Free allows.

The upgrade moment, then, is the day the second language starts bringing its own buyers. A French-speaking reader who lands on an English welcome sequence is a reader you've half lost, and keeping them means the second tag and the second campaign first, then a blog or course if those sell in that language too. Startup covers all four with room to spare: $17 a month, or $170 billed once for the year ($14.17 a month spread over twelve), and it lists no cap on languages per website. That matters more than it sounds. Natalia M., an animal therapist who moved her WordPress site to systeme.io, rated the move 5.0 on Capterra in July 2025 and noted that it took longer than expected because "my site is fairly large and available in three languages." A third language is past Free's two. The bilingual website itself runs on Free; when the second welcome sequence goes in, Startup is the plan for it.

If the course is the core of what you sell, students count against your contacts, and a second-language course adds to them; my plan guide for course creators goes through that count. For the first funnel in each language, see my guide to delivering a free download on systeme.io.

When one language and a translated page are enough

If almost all of your buyers read one language comfortably, a single-language business with one translated page, an "about" or a contact page in the second language, may serve them better than a second copy of everything. That fits Free: two languages on one website, and one of everything else. The second copies earn their keep when the second language brings its own buyers: its own search traffic, its own list, its own course sales.

Support is a separate question from the product. One Capterra reviewer, catherine G., a consultant in health and wellness whose four-star review from September 2025 is written in Italian, said she'd have preferred migration help in a language other than English: "avrei voluto poter comunicare in italiano o francese" (she'd have liked to communicate in Italian or French). If you'd want help in your second language, ask before you buy.

FAQ

Does systeme.io translate my pages? No translation is documented. The website article says switching languages "does not translate content automatically", and each page version is edited by hand.

How many languages can one systeme.io website have? The plan table lists 2 per website on the free plan, with no cap listed on Startup and above. The language count is rarely what moves you off Free, though. Each language needs its own welcome email, tag and campaign, and those counts run out first. A third language is past Free's two, and so is a second welcome sequence.

Can one systeme.io blog or course be in two languages? Each has a single language setting, per the blog and student dashboard articles. You can write in two languages inside one, but for a dashboard that shows students the right course, and a blog labeled correctly, use one per language.

Will my systeme.io site switch languages for visitors automatically? The help center doesn't say. It doesn't describe a language switcher or the address each version lives at, so check both versions from outside your account and add a link between them if needed.

Does the systeme.io sitemap include my website pages in both languages? Not yet, by systeme.io's account. The sitemap article says it covers funnels and blogs, and that websites will be supported in future updates.

What language is the course access email sent in? The help center doesn't say, and the template can't be edited. Enroll yourself in the second-language course and see what arrives.

About the author: Tess Morrow is the editorial pen name of the Email MK Tools research team. We haven't set up a bilingual site in a live systeme.io account; every step here is the help center's. More about Tess.

Sources

Read on October 9, 2026, from systeme.io's help center:

Also: systeme.io pricing, monthly and yearly; Capterra, Systeme.io reviews and Trustpilot, systeme.io reviews, both read October 9, 2026.

More on systeme.io