Brand & assets

Building your brand in another language

Published 20 July 2026 Updated 11 August 2026

Your brand's language is the language of the daters you are building for. It does more than translate a few labels: it shapes the content of your public pages so they speak to that audience, and it sets the tone of the community your members join in the app. This guide covers which languages are supported, the three places language is set (your brand, a single page, and many pages at once), what actually changes when you change it, and the one field that trips people up.

Changes to this guide are listed in the Changelog at the bottom.

More than translation: building for your audience

Choosing a language is choosing who your brand is for, and it works on two levels:

Your public pages, the landers. Your starter content is drawn from HubPeople's library for that language, niche and market, so your pages speak to that audience in their own language rather than reading like a translation added on top.
The journey into the app. Your sign-up and login links carry the page's language with them, so someone arriving from a French page continues in French rather than landing on an English form.

In other words, a French brand is not an English brand with French labels. It is a brand built for French-speaking daters, from the first landing page through to the point they join.

The languages we support

Five languages are supported. If your brand is set to anything else, the platform text falls back to English.

Language	Code
English	`en`
Spanish	`es`
Portuguese	`pt`
French	`fr`
German	`de`

French and German are the most recent additions. English, Spanish and Portuguese were already supported.

The three places language is set

Language is set at two levels, and there is a third screen for changing many pages in one go. It is worth understanding the order before you change anything, because they override each other:

Level	Where	What it covers
Your brand	About your brand	Every page, unless that page overrides it.
A single page	That page's Landing tab	Just that page. Wins over the brand setting.
Many pages	Bulk Page Editor, SEO Metadata tab	The same per-page setting, applied to a list of pages at once.

A page with no language of its own follows your brand. Most brands never need a page-level override at all, so if your whole site is in one language, set it on the brand and leave the rest alone.

Setting your brand's language

Open About your brand, click Edit, set Culture, and click Save changes. Culture and Niche are shown as plain text until you click Edit, so if you cannot see a dropdown, that is why. Your niche sits alongside it and is changed the same way. This is the setting that matters most, because everything else inherits from it.

You no longer need to ask your account manager to do this. If you have previously been told the language is fixed once your brand is created, that is no longer the case.

Overriding the language on a single page

Open the page, go to its Landing tab, open Advanced Settings, and set Page Language. Use this when one page needs to speak a different language from the rest of your site, for example a landing page aimed at a different market.

"Reset to default" pins the page, it does not unset it. The button next to Page Language sets that page to whatever your brand's language is at that moment. It does not return the page to following your brand. So if you change your brand's language later, a page you reset earlier keeps the old language and will need changing again. The same is true of saving Advanced Settings at all: if you open that panel to change something else entirely and save, the page is pinned to the language shown in the box. On a single-language brand that makes no visible difference, but it is worth knowing before you change your brand's language later.

Changing the language on many pages at once

Open the Bulk Page Editor and use the Page Language column on the SEO Metadata tab. Tick the pages you want, then either set the language on each row or use the setter panel at the top to apply one language to everything you have ticked. If nothing is ticked, the setter does nothing and Save All stays greyed out.

Read this before saving on a brand that is not in English. Every row arrives with a language already filled in, and pages that have never had one of their own show as English rather than -- None --. So if you tick rows to fix their titles or descriptions and hit Save All, you also pin those pages to English, overriding your brand language. To avoid it, set the Page Language column to -- None -- on the rows you are saving. -- None -- means "leave this field alone", not "go back to following the brand".

Set Lang Code to match. If you do change Page Language here, change the Lang Code column too. The bulk screen does not keep them in step, and a leftover code will describe the page wrongly to browsers and search engines (see the next section).

Lang Code, and when to leave it alone

Next to Page Language you will see a second field called Lang Code. These are not the same thing, and this is the field that most often causes confusion.

Page Language is the one you want. It chooses the language, and everything described in the next section follows from it.
Lang Code is an optional, more precise code that declares the page's language to browsers and search engines, and can carry a regional variant such as en-us or pt-br. It does not translate anything.

When you pick a Page Language on the Landing tab, Lang Code is filled in for you to match. That is the normal case and you can ignore the field entirely. Only set it by hand if you specifically need a regional variant.

If you do set it by hand, keep it in step with the language. Where a Lang Code is present it is what gets reported to browsers and search engines, so a leftover code from a previous language will describe the page wrongly even though the page reads correctly. Note also that choosing a Page Language on the Landing tab overwrites whatever is in Lang Code, so a hand-set regional code such as pt-br will need setting again afterwards.

What actually changes when you change a language

This is the part worth reading before you change anything, because the answer is narrower than most people expect.

What changes: the parts HubPeople provides and keeps up to date for you. The cookie banner, the legal links in your footer (the Legal heading and Terms and Conditions, Privacy Policy, Cookies, Modern Slavery Policy), the "Rated Members" widget label, the "Our Features" heading, and the language the page declares to browsers and search engines. For example, on a brand set to French the cookie banner reads "Nous utilisons des cookies pour améliorer votre expérience. Consultez notre", the accept button reads "Accepter", and the footer legal heading reads "Mentions légales".

What does not change: the words on your pages. Your headings and body copy stay exactly as they are. Changing the language never rewrites, re-translates or overwrites content you already have, which also means it will not fix a page that is in the wrong language. You edit that copy yourself.

Changing your brand's language does not rebuild your existing pages. They keep showing the old wording until each page is next rebuilt, which happens when you edit and save that page, or when you use on it. Waiting will not do it. Setting the language on a single page, or through the Bulk Page Editor, does rebuild those pages, so it is only the brand-level change that needs this.

Starter content is a separate matter. When your brand is first built, the headings and body copy your templates come with are drawn from HubPeople's library for your language, niche and market, falling back to a default where content is not yet available in that language. That happens at build time, so changing the language afterwards does not go back and redo it.

Changelog

Date	Change
11 August 2026	Rewritten for the new language controls. Brand language is now self-service on About your brand, pages can override it, and the Bulk Page Editor can set it across many pages. Added what Lang Code is and how it differs from Page Language, what "Reset to default" and "-- None --" actually do, and which parts of a page change when the language changes.
20 July 2026	Guide first published, covering the five supported languages and what arrives in your language.