Glossary

Explore Meshline

Products Pricing Blog Support Log In

Start with your goals.

Book a call
Autonomous Operations

Target a HubSpot Chatflow by URL or Browser Language? Decide Before You Publish

Running a multi-language site with HubSpot chat? See when URL targeting fits and what changing a chatflow's language does not update automatically.

A smaller webpage icon overlapping a larger speech bubble icon.

You localized your landing pages and blog posts for organic search, then noticed the chat widget greeting French visitors in English.

The pages did their job; the chat undermined them.

Now you have to decide how to scope the chatflow: by website URL or by the visitor's browser language or country.

This article walks through that decision using HubSpot's documented behavior.

It also covers a manual consequence most teams miss: switching an existing chatflow's language does not rewrite its default text.

By the end you will have a mapping checklist you can run before publishing.

What HubSpot recommends for multi-language pages

HubSpot's chatflow language documentation is direct on this point.

For multi-language landing pages and website pages, it is recommended to target based on website URLs instead of targeting based on the visitor's browser language or country.

The documentation's reasoning is practical: targeting rules control which pages a chatflow appears on.

So the correct language chatflow appears only on pages hosted on that language domain.

In other words, the page itself tells you the language.

A visitor on your French-language pages should see the French chatflow, and URL targeting ties the chatflow to those pages directly.

How URL targeting works in practice

The documented procedure runs through the Target tab of a chatflow.

You select Website URL in the first dropdown, choose contains in the second, and enter your language domain or slug.

If your French content lives at www.company.com/fr/, you enter that path, and the chatflow appears on any page whose URL contains it.

Alternatively, you can enter the language slug, such as /fr/.

If you have multiple page variations, HubSpot recommends creating a different chatflow for each language and targeting only the desired language URL in each chatflow's settings.

Two prerequisites apply before any of this becomes visible.

Chatflow permissions are required to create and edit chatflows.

Adding live chat to a site not hosted on HubSpot?

The tracking code must be installed on your external pages before you create the live chat.

Without it, the live chat will not appear.

When browser-language targeting might still come up

The same documentation notes you can create separate welcome messages.

You can also target visitors from specific countries or regions when your website has different language versions.

So country and region targeting exists as an option.

The documented recommendation for multi-language pages, however, remains URL-based targeting.

A useful way to frame the decision: URL targeting anchors the chatflow to the localized content you built.

Browser-language or country targeting anchors it to assumptions about the visitor.

If your localized page sets are well organized under language domains or slugs, the URL approach matches the structure you already control.

If your language pages are not cleanly separated by URL, that is a structural question to resolve first, because the documented recommendation depends on that separation.

One caution belongs here.

The supplied documentation describes the URL-targeting procedure and the general recommendation; it does not enumerate every failure mode of browser-language targeting.

Weighing the two approaches for an edge case, like visitors browsing in one language but navigating to another language's pages?

Treat that as an open question to verify against your own visitor behavior, not a settled rule.

The consequence teams miss: changing language does not update default text

This is the part that catches teams after the decision is made.

HubSpot's documentation states plainly: changing the language on the Options tab for an existing chatflow will not automatically update its default text values.

This includes the Welcome message and Knowledge Base search.

If you want to update the default text values for an existing chatflow, you must update them manually on the Build tab, or create a new bot or live chat for a specific language.

So if you built an English live chat and later decide it should serve your German pages, flipping the language setting leaves the English default text in place.

You either edit the text manually on the Build tab or build a new chatflow for that language.

Planning for that manual step up front changes the calculus.

For several languages, the documentation points toward separate chatflows per language, each with its own URL targeting and written text.

The welcome message and email capture message are entirely configurable and can be changed to any language when editing each live chat.

That flexibility is what makes the per-language chatflow approach workable, but it also means the text does not translate itself.

Someone has to write and verify each language version.

Contextual widget data is configured separately

Even after your welcome message is in the right language, parts of the widget speak a different language unless you configure them separately.

The contextual widget data language is set in your live chat settings.

It covers the date and time stamps.

It also covers the Send button.

It covers the write-a-message prompt.

It covers the email address prompt, including its help text and confirmation message.

It covers the typically-replies-in message.

It also covers the will-return-at message.

One documented display note: if the chatflow language is set to German or Japanese, the user's full name will display in the live chat widget.

If that display behavior matters for your audience or privacy expectations, check it before publishing rather than after.

There is also a follow-up touchpoint outside the chatflow itself.

The follow-up email containing the chat transcript is sent in the language set in your account settings.

If your account default does not match the languages you serve, that mismatch is worth resolving at the account level, not per chatflow.

Bot language limits to know before you automate

If your chatflow uses a rule-based chatbot, you can select one of HubSpot's supported languages in the bot's settings.

The language you select determines the language your bot messages and actions display in.

But visitor-side parsing has documented limits.

For visitor messages in languages other than English, the bots tool cannot extract all date and time expressions.

It also cannot fully extract names, number ranges, or iterations of yes or no.

The documentation's example: a visitor writing in English can say 'tomorrow at three PM' and the bots tool can parse that into a structured date and time.

A visitor using a date or time expression in another language will not have that expression extracted and translated by the bots tool.

If your bot logic depends on parsing visitor messages, this limit shapes how much you can automate in non-English languages.

Test with real phrases in each language before relying on it.

A mapping checklist before you publish

Before publishing, run this checklist against your actual site and account.

It turns the decision above into verifiable steps.

  • Map each localized page set to a chatflow. List your language domains or slugs and assign one chatflow per language. If a language's pages are scattered across URLs with no shared path, resolve that structure first, because URL targeting depends on it.
  • Confirm the targeting string matches. For each chatflow, check the Target tab: Website URL selected, contains chosen, and the full language domain or slug entered exactly as it appears in your live URLs. A typo in the string means the chatflow appears nowhere or everywhere.
  • Verify the written text in the target language. Open the Build tab and read the welcome message and email capture text in each language. Remember that changing the Options-tab language does not update these, so verify the words themselves, not just the setting.
  • Check the contextual widget data language. In live chat settings, confirm the language covering the Send button, prompts, and availability messages matches the chatflow's audience.
  • Confirm prerequisites. Verify the editing user has chatflow permissions, and for external sites, that the HubSpot tracking code is installed on the pages where the chat should appear.

This checklist can surface concrete mismatches, such as a targeting string that does not match any live URL or welcome text still in the wrong language.

It does not catch every possible configuration error, so a preview of the widget on an actual localized page before full publication remains worthwhile.

Where this fits in your broader setup

Chatflow targeting is one of many places where a scoping decision made at publish time shapes results later.

If you are also deciding how workflow criteria combine, the choice between AND and OR logic in workflows raises a similar question about what a condition set actually selects.

And if your chatflows feed records that workflows then update, it is worth asking whether a workflow should update associated company records before that automation goes live.

Verification habits transfer here too.

Just as a spelling and grammar check belongs in your pre-publish QA workflow, a language check on chatflow text belongs in the same pass for localized pages.

The pattern is the same: catch the mismatch while it is still cheap to fix.

The decision in one view

ApproachWhat it anchors toDocumented guidance
Website URL targetingThe language domain or slug of the pages themselvesRecommended for multi-language pages; use contains targeting with the full language domain or the language slug
Browser language or country targetingAssumptions about the visitorAvailable, including country and region targeting, but not the documented recommendation for multi-language pages

Whichever approach you evaluate, the manual text step stays the same: default text values follow the Build tab, not the language setting.

Plan the per-language writing work into the launch, verify the targeting strings against live URLs, and preview the widget on a real localized page before publishing.

Source references: knowledge.hubspot.com; knowledge.hubspot.com.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.

Revenue Intel

Ask us about this workflow.

Tell us what you want to fix or automate. We'll reply with the most useful next step.

See how we can help

Implementation decisions

Put this into practice

Before choosing a solution, define the problem, the available data and who will review the outcome.