Publish in a second language

HarperFlow can write part of your autopilot articles in a second language, researched against that language's own search market. You control all of it from one card on Your site.

Turning it on

On Your site, find the Second publishing language card and tick Enable. Three choices appear:

• Language — any supported publishing language other than your site's primary one.
• Search market — the country whose search demand topic discovery should use for this language. Leave it on the language default if you're not sure; pick a specific market when your audience is concentrated there (for example French with the France market, or Spanish with Mexico rather than Spain).
• Share of articles — a slider from 10% to 50%. This is the portion of your autopilot articles written in the secondary language.

Save, and the next autopilot run takes it into account. No restart or reconnection is needed.

How the share works

The share is honored over time, not per week. Before each run, HarperFlow looks at what it actually published for your site in the trailing thirty days and writes the next article in whichever language is furthest behind its target. At 25%, roughly one article in four ends up in your secondary language; a given week can naturally be all-primary or all-secondary.

Two things never switch language:

• Topics you type yourself are written in your primary language by default — but once a second language is enabled, the "Have a topic in mind?" form on Home grows a language picker, so you can write any manual article in either language.
• Existing scheduled articles keep the language they were written in.

What each language gets

A secondary-language article is not a translation. It gets the full pipeline in that language: topic discovery against the market you chose, sources evaluated for that language, writing, formatting, and publishing. Where few native-language sources exist for a topic, HarperFlow may lean on carefully verified translated evidence rather than refusing to write — the sourcing bar stays the same.

Webflow sites: locale check at save time

On Webflow, articles in a secondary language publish into the matching Webflow Localization locale, under its own URL prefix (for example /fr/...). Because of that, HarperFlow checks your site's locale setup when you save: if the language you picked isn't enabled in your Webflow Localization settings, the save is rejected with the list of locales your site actually has. Enable the locale in Webflow first (Site settings → Localization), then save again.

WordPress and Shopify sites don't need any locale setup — articles publish normally and carry the right language metadata.

Turning it off

Untick Enable and save. Discovery and writing return to your primary language only. Already-written secondary-language articles are unaffected: scheduled ones still publish, live ones stay live.

More in Autopilot & Publishing

• How autopilot works
• The veto digest
• Scheduling and spread
• Topic runs
• On-demand runs
• Article states
• Unpublish and take-down
• Images and internal linking
• Run your blog on autopilot

Browse all Autopilot & Publishing guides