How do you manage FR/EN hreflang on a web agency website?

Hreflang connects language or regional versions of the same content. Map equivalent page pairs before generating annotations and check their return links. Do not advertise a nonexistent version. The language switcher and canonical URLs should agree with the mapping.

Use a language architecture before touching hreflang

For a French web agency with French and English content, the most maintainable pattern is usually a single domain with language folders such as / for French and /en/ for English, or equivalent parallel paths. Google documents subdirectories, subdomains, and country domains as valid options, while noting that URL parameters are not recommended for locale targeting. For most agencies, subdirectories keep governance, analytics, templates, and authority consolidation simpler. developers.google.com

Recommended FR/EN mapping

• French default market: primary pages in French on their stable canonical URLs.
• English market: equivalent pages under /en/.
• One intent, one pair: each French service page should map to one English equivalent, not to a broader category page.
• No automatic redirection by IP: users and crawlers must be able to access both versions directly.

Google explicitly warns against relying on IP-based adaptation for language or locale discovery because crawlers may not see all variations correctly. For an agency site, language switching should be explicit in links, menus, breadcrumbs where relevant, and footer navigation. developers.google.com

Implement hreflang at page level, not site level

Hreflang works best when each page declares its exact alternates. A French homepage should reference the English homepage. A French service page should reference the English version of that same service. A French case study should reference only its English equivalent if one exists. If there is no equivalent, do not force a hreflang pair.

What each equivalent page should contain

• Self-referencing canonical to its own URL.
• Self hreflang for its own language version.
• Reciprocal hreflang to the alternate version.
• Optional x-default only for a real language selector or neutral gateway page.

Google’s documentation for localized versions stresses that alternate language annotations should list each version, including the page itself, and that the return links must be consistent. This is why hreflang errors often come from CMS migrations, missing return tags, and page pairs that are no longer aligned after a redesign. developers.google.com

Typical FR/EN examples

• fr-FR for a page primarily intended for France.
• en when English is generic and not country-specific.
• en-US only if the English page is truly tailored to the United States.

Do not over-specify regional codes if the content is not region-specific. Google distinguishes multilingual from multi-regional targeting, and those are not the same thing. If your English version is for all English-speaking prospects, a language code may be more appropriate than a country-language pair. developers.google.com

Decide whether your English pages are translated, adapted, or localized

Many agency websites create an English version that is linguistically correct but commercially weak. Hreflang can send the right user to the right URL, but it cannot fix a page that speaks to the wrong market. For SEO, SXO, GEO, AEO, and LLM visibility, the English page should match the intent of an English-speaking buyer: service wording, proof points, contact expectations, currency when relevant, trust signals, and examples.

Three useful content levels

1. Translated: same offer, same structure, minimal adaptation.
2. Adapted: wording, CTAs, examples, and FAQs adjusted for English-speaking users.
3. Localized: market-specific offers, references, legal cues, testimonials, and conversion paths.

For an agency, most core pages should be at least adapted. That is particularly true for service pages such as website creation or SEO and SXO, where user expectations and terminology differ by language. Better intent alignment improves both classic rankings and downstream AI retrieval quality.

Main hreflang risks on agency websites

1. Wrong page pairing

The most common issue is pairing unlike pages: a French service detail page linked to an English category page, or a French article linked to a generic English homepage. Search engines then receive conflicting equivalence signals.

2. Canonical conflicts

If the English page canonical points to the French page, hreflang becomes unreliable. Canonical and hreflang must support the same page logic: each language page should usually canonicalize to itself.

3. Incomplete reciprocity

If FR points to EN but EN does not return the link, the pair is weakened or ignored. This often happens after content deletions, slug changes, or CMS template exceptions.

4. Mixed language pages

Google notes that some pages translate only template text while keeping most main content in one language. That weakens language targeting. If a page is meant to be English, the main content, not only the navigation, must be English. developers.google.com

5. Auto-redirects and forced popups

Users and crawlers should be able to reach any language URL directly. Forced interstitials, script-based redirects, or browser-language overrides often create crawl and UX problems.

6. Redesign regression

During a website redesign, hreflang errors often appear because templates change faster than page mappings, sitemaps, or canonicals. Hreflang should therefore be included in the redirect plan, QA plan, and post-launch crawl.

Checks to run before launch and after every major update

Editorial checks

• Does every strategic French page have a true English equivalent?
• Are page titles, H2 logic, CTAs, FAQs, and forms aligned by intent, not merely translated?
• Are local references, phone numbers, addresses, and trust markers coherent for the audience?

Technical checks

• HTTP status 200 on all hreflang targets.
• No blocked targets in robots rules.
• Self-canonical on each live version.
• Reciprocal hreflang on each page pair.
• XML sitemap entries updated if hreflang is managed there.
• No accidental noindex on one language branch.

Search and crawl checks

• Inspect whether branded FR queries surface FR URLs and branded EN queries surface EN URLs.
• Review indexation parity between priority FR and EN pages.
• Check server logs or crawl data to confirm both language sections are regularly crawled.
• Monitor whether international users land on the intended language path.

Google supports hreflang implementation via HTML, HTTP headers, or sitemaps. For most agency websites, HTML head tags or sitemap-level management are easiest to govern, but the right choice depends on the CMS and publishing workflow. developers.google.com