Translate Website to French: Voice, Typographic Detail & Locales

If your brief says “translate website to French,” stop treating French as one vocabulary file. French on the web is a voice and market problem: vous vs tu on every CTA, France French vs Canadian French on legal and everyday terms, and typography that French readers treat as a quality signal.

This article is a launch guide for a French (fr) website version: locale choice across France, Canada, Belgium, and Switzerland; spacing and expansion; crawlable URLs; checkout QA; MTPE vs human review; SEO pitfalls; and a checklist you can actually run.

What does it take to translate a website to French beyond swapping strings?

Beyond CMS fields, you need a pipeline that preserves accents and narrow/non-breaking spaces through templates, email, and PDFs; a locked vous/tu policy; a market decision (fr-FR vs fr-CA at minimum); layouts that absorb 15–20% expansion; a real French URL whose body is actually French; and gender agreement in status messages before anyone opens a file.

Questions this guide answers

• What does it take to translate a website to French beyond swapping strings?
• Which French locale or regional variants should you choose?
• What script, typography, and layout issues are unique to French?
• How should URLs, hreflang, and indexing work for a French site version?
• What onboarding and checkout nuances matter in French?
• Should you use AI translation, MTPE, or human review for French?
• What SEO mistakes specifically hurt French pages?
• How do you launch and measure a French website version?

Quick answer: translate your website to French the right way

A durable French launch looks like this:

1. Lock vous vs tu once, then apply it to errors, empty states, emails, and ads. Mixing both is worse than either choice.
2. Ship crawlable French URLs—typically fr-FR first, with a separate fr-CA when Canada is material revenue—not a cookie-only switch.
3. Prototype nav, cards, checkout, and emails with real French copy so expansion, clipped accents, and stripped punctuation show up before launch.
4. Research queries per market. Quebec search language can diverge from France for the same category.
5. Add reciprocal hreflang, same-language canonicals, and sitemaps before you scale.
6. Put product nouns, vous/tu, and regional legal terms in a glossary so MTPE cannot silently flatten voice.

CSA Research’s survey of 8,709 consumers in 29 countries found 76% prefer buying with information in their own language and 40% will never buy from websites in other languages. That still holds when some French speakers also read English: checkout, invoices, and support are where an English-only journey loses the sale. Google’s helpful-content guidance favors people-first pages; a French nav around English body copy is a weak locale. For market-versus-language strategy, read how international SEO differs from multilingual SEO.

Choose the right French locale

Most consumer and B2B teams start with fr-FR when France is the first commercial market. That is a reasonable first release. It is not a license to paste Paris copy onto a Quebec pricing page and call it “the French locale.”

Canadian French differs in vocabulary and sometimes legal terminology from France French. Everyday UI words, public-sector phrasing, and consumer protection language can diverge enough that a Montreal reviewer will redline a France-first file (and the reverse). If Canada is material revenue, ship fr-CA as its own message set and URL—not a handful of “eh” substitutions in comments.

Belgium and Switzerland often ride with France French plus light local review—unless you run country-specific campaigns, pricing, or legal entities. Swiss French may need lighter local passes for offers and support hours; Belgian French usually tracks France more closely than Quebec does. Put the audience and register in the brief: B2B vous vs consumer tu, and which market owns legal pages.

Vous vs tu sets brand personality in every CTA and error message. Usual defaults:

• B2B, finance, health, and government-adjacent products: vous
• Youthful consumer mobile brands: tu, if marketing, product, and support agree
• Mixed: the worst option—pick one system and document it

Overseas Francophone readers exist, but currency, address formats, and legal pages still follow the market you sell in. Also decide how you will handle names, addresses, and phone numbers. Forms that reject accented characters or assume US ZIP patterns will fail after the strings look “translated.”

French script, typography, and layout nuances

French uses the Latin alphabet plus diacritics. Characters like é è ê ë à â ù û ç œ must survive CMS fields, emails, PDFs, and autogenerated titles. A font stack that only tested English will clip accents at small sizes or fall back to a face that makes œ look like a broken oe.

Spacing before punctuation (! ? : ;) is a typographic norm in France that looks “wrong” if stripped. Teams often lose thin spaces and non-breaking spaces in a CMS “cleanup,” Markdown pipeline, or email sanitizer. That is a quality failure, not a translator personality quirk. Prototype the actual banner, tooltip, and invoice—not a spreadsheet cell.

Layout rules that prevent launch-week screenshots:

• Prototype key screens with real French copy—including long formal vous lines and expanded CTAs.
• Plan for about 15–20% text expansion versus English. Flexible buttons beat ellipsis soup.
• Increase line-height versus a cramped English-first theme so accents have vertical room.
• Allow buttons to wrap; do not shrink type to keep a one-line English CTA.
• Ship production fonts with French coverage in UI, email, and PDFs.
• Watch card titles, badges, and table headers—these are where clipping shows first.

Gender agreement in adjectives and past participles appears in status messages. English “Invitation sent” can become a gendered French line depending on what was sent and who is addressed. Design templates that can hold the longer agreed form.

Dates and numbers are part of the layout contract. France typically expects day-month-year, local number grouping, and EUR (or CAD on fr-CA) when you sell there.

Slogans and wordplay rarely survive MT. Budget human review for campaign lines even when product UI is MTPE.

Crawlable URLs, hreflang, and indexing

Google recommends different crawlable URLs for each language or region version rather than cookies or browser language alone. Google determines page language primarily from visible content—so a translated nav around English body copy is a weak French version. Give French its own folder or host pattern (/fr/, /fr-fr/, /fr-ca/) and keep that pattern consistent across templates, analytics, and internal links.

When both France and Canada exist, treat them as separate region versions, not as one “French” URL with a toggle. Reciprocal hreflang should distinguish fr-FR and fr-CA (and other fr-* you actually ship). Each locale URL should carry a clear canonical that prefers the same-language preferred URL when duplicates exist. Do not canonical a French page to its English equivalent, and do not canonical Quebec pages to France to “consolidate.”

Bing Webmaster Guidelines emphasize crawlable, useful content and clear site structure. Google advises against automatically redirecting users based on assumed language or location; offer a visible selector that links to the French URL instead. IP-guessing “France → /fr” traps travelers, VPNs, Canadian users on holiday, and crawlers.

URL policy and on-page policy can differ: you may ASCII-fold a slug for operational reasons, but titles, H1s, and body copy should keep accents. Stripping diacritics for “cleaner URLs” and stripping them on the page hurts readability. If you fold slugs, redirect consistently; do not publish two competing French URLs without a canonical.

Research French-language queries per market. A category term that works in France may not be how Quebec users search. Do not copy France title tags onto fr-CA pages.

Onboarding, trust, and checkout in the target language

French trust pages do more work than a translated feature list. French-speaking markets are sensitive to clumsy legal tone. Privacy, terms, and (where relevant) payment and after-sales copy must read as real pages, not leftover English templates. That is not a ranking tactic; it is what users look for when they decide whether a checkout is legitimate. Treat those pages as first-class localization, and keep France vs Canada legal language on the matching URL.

Practical French conversion checks:

• Homepage, ads, and product UI use the same vous/tu policy.
• Forms accept accented characters for names and addresses, or they explain why a Latin-ASCII field is required.
• Cookie and consent strings are reviewed in the actual banner—these run long, pick up extra spaces before ?, and wrap badly.
• Pricing, invoices, and currency language match the market you claim to serve (EUR vs CAD, tax footnotes).
• Support macros and transactional email keep accents and typographic spaces; a “safe ASCII” email template is a leak.
• Error messages name the fix rather than a polite empty apology—and they stay in the same address form as the rest of the product.
• Quebec vs France vocabulary belongs on checkout, not only on the homepage.

You do not need every blog post on day one. You do need homepage, product explanation, authentication, pricing, checkout, privacy basics, support entry points, and the legal pages the market expects. Some French speakers will browse docs in English; enough will not complete checkout or support in English that English-only still costs sales.

AI, MTPE, and human review for this language

Should you use AI translation, MTPE, or human review for French? Use risk to choose the workflow—not tool branding:

• Raw machine translation: fine for internal drafts only. Models mix vous and tu, flatten rhythm, drop thin spaces, and produce France wording on Canadian screens (or the reverse).
• MTPE (machine translation + post-editing): a solid default for many product and support pages when the glossary locks product nouns, vous/tu, and a typography check exists.
• Human translation / brand editing: homepage, pricing, campaigns, cookie/consent, slogans, and any legal-adjacent page.

A practical review loop for French: MTPE against the glossary (vous/tu and regional legal terms locked); a brand editor pass on homepage, pricing, and wordplay; a linguist pass on errors, billing, and gender agreement; then staging QA at mobile widths including email and PDFs (accents and punctuation spaces). Add a publishing check for vous/tu collisions and ASCII-only French body on fr URLs.

People-first helpful content expectations apply in every language. “Good enough MT” often lands the meaning and still fails the brand: inconsistent vous, flattened homepage rhythm, and legal pages that sound overnight-translated.

French-specific SEO pitfalls

French searchers look for language they can read in their market. Do French keyword research per market, then write titles and H1s that sound like local results pages—with accents. Localize titles, meta descriptions, and headings per French URL—do not reuse one English metadata set.

Mistakes that specifically hurt French pages:

1. Vous/tu drift across templates, emails, and ads.
2. France copy on Canadian URLs (or the reverse), including legal terminology.
3. Stripped punctuation spaces that make copy look machine-made.
4. Missing accents in titles, buttons, or body copy.
5. Boilerplate-only translation — chrome French, body still English.
6. Cookie-only language switches that hide the French URL from crawlers.
7. Broken hreflang (missing return links), including fr-FR / fr-CA not pointing at each other when both exist.
8. Automatic geo redirects that trap users and bots.
9. English canonicals on French URLs.
10. Truncated CTAs from English-width buttons after 15–20% expansion.
11. Thin MT-only locales that fail helpful-content expectations.

Fix voice, typography, and architecture before you scale content volume. Tooling should enforce the process—not invent ranking promises.

Launch checklist

Use this checklist when you are ready to ship French:

• Locale matrix approved (fr-FR, fr-CA if needed; BE/CH review notes) with vous/tu policy documented
• Crawlable French URL pattern chosen and shared with engineering
• Primary screens prototyped with real French copy (nav, cookies, tables, checkout)
• Layouts tested for ~15–20% expansion vs English
• Priority templates translated with reviewed main content—not chrome only
• Titles, descriptions, and Open Graph localized per French URL, with accents
• Typographic spaces before ! ? : ; surviving CMS, email, and PDF
• Font glyph coverage verified in UI, email, and PDFs
• Gender agreement reviewed on status messages
• Dates, numbers, currency, and form field rules checked per market
• Privacy / terms pages reviewed as first-class content (France vs Canada as needed)
• Language selector links to crawlable alternates (no forced redirect)
• Canonical policy verified per locale (same-language preferred URL)
• Reciprocal hreflang generated (fr-FR / fr-CA when both exist)
• XML sitemaps list French URLs
• Glossary and review workflow live for ongoing English source updates
• Vous/tu collision detector enabled on French URLs
• Search Console / Bing coverage checks scheduled for the French URLs

Where GlotEO fits

French is a strong fit for translation memory: product nouns recur, vous/tu must not drift, and regional legal terms must stay on the right URL. Glossary and memory in the website localization platform keep voice, register, and feature names stable while layout-tested copy ships. Pair that with multilingual SEO tooling so French URLs, hreflang, and metadata stay reviewable as you expand. Compare GlotEO pricing and plans when you scope the first fr release, or start from a broader website translation workflow if you are still choosing languages.

Explore GlotEO website localization when JSON dictionaries and unmarked MT drafts are no longer a safe way to ship fr.