SEO & Search

Hreflang for B2B Sites: Map Language and Regional Pages Before Adding Tags

A German product page exists. The implementation guide still exists only in English. The British page describes a different support package.

Putting the same language menu above all three pages does not answer which URLs belong together.

Start with that decision. A useful hreflang implementation begins with a map of equivalent pages. The tags come after the content relationships are clear.

This guide uses a fictional software site to build that map. The process separates commercial decisions from annotations, then turns one approved page family into HTML. Use the worksheet with your content owner before asking a developer to generate tags across the site.

Separate Four Decisions Before Mapping URLs

Language describes the words on the page. Country describes the market the page targets. Currency describes a commercial presentation choice. Availability describes what the business can deliver.

Keep four columns. A German-language page does not establish German support coverage. A euro price does not establish service across Europe. An English page may serve several markets with different procurement requirements.

For a B2B site, ask the commercial owner to confirm supported products, contract boundaries, and the next step offered in each market. Ask the language reviewer to confirm the page's wording independently.

Google distinguishes multilingual sites from multi-regional sites. It recommends separate language URLs and visible language-switching links. Its multi-regional site guidance also cautions against automatic language redirects.

The worksheet below is an editorial planning method. Its commercial approval fields are proposed controls, not Google requirements.

Before creating a locale, write a sentence describing the buyer it serves. For example: English-speaking buyers comparing the standard product, wherever that product is supported. That sentence gives the reviewer something concrete to compare against the content.

If nobody can explain why a regional version exists, hold the new URL decision. A country name in a directory is a weak substitute for a defined audience.

Build an Equivalent-Page Map

Imagine a fictional business at https://example.com. It sells a document workflow product. The following inventory is illustrative. The paths are examples, not live destinations.

Page family Generic English Generic German British English Decision
Product overview /en/product/ /de/produkt/ /en-gb/product/ Three equivalent overviews
Implementation guide /en/implementation/ Missing /en-gb/implementation/ Two equivalents; no German member
Regional onboarding service Missing Missing /en-gb/onboarding-service/ Standalone regional service

The overview family contains a regional variant. In this example, the British overview describes local support arrangements while preserving the same product and comparison task.

The implementation family contains a missing translation. Its blank cell is deliberate. Leave it blank until a reviewed German guide exists.

The onboarding service has no equivalent. Its purpose differs from the implementation guide: one page describes a separate service, while the other explains product setup. Do not connect them because they share an onboarding word.

Match the buyer task before matching the directory. Two pages can use different headings and still answer the same question. Two pages can share a slug and describe different offers.

Add an owner and review date beside each family. Record the reason for disputed mappings. That small note prevents a later developer from filling an intentional blank during a sitewide cleanup.

The broader technical SEO checklist covers surrounding site checks. Keep this map focused on content relationships rather than expanding it into another full audit.

Turn One Page Family Into HTML

Google supports HTML, HTTP headers, and sitemap annotations. The methods are equivalent; choose one maintainable method. For HTML, put the annotation set in each member's head. Include self references, full URLs, and reciprocal references. Google ignores nonreciprocal pairs. See its localized-version documentation.

For the fictional overview family, place this identical alternate block on all three overview pages:

<link rel="alternate" hreflang="en"
      href="https://example.com/en/product/">
<link rel="alternate" hreflang="de"
      href="https://example.com/de/produkt/">
<link rel="alternate" hreflang="en-GB"
      href="https://example.com/en-gb/product/">

On the German overview, the de entry is the self reference. The English and British pages carry that same block. Their respective entries supply their self references.

Review the family as a unit. Start at the German URL, open each named alternate, and compare the returned annotation sets. Then read the pages. A mechanically complete block attached to the wrong product family still fails the content review.

Use de for German without a regional restriction, and en-GB for English targeting the United Kingdom. A country alone is invalid. Google documents language codes and optional region codes. The fallback value x-default covers unmatched settings; it is useful for selectors. Those rules come from the same annotation reference.

In this example, generic English is an intentional audience choice. It is not shorthand for a United States offer. Confirm that choice against the page before reusing the block elsewhere.

Decide What the Fallback Page Does

A fallback needs a destination that helps the reader choose. For this fictional product family, suppose the site has a product-specific language selector:

<link rel="alternate" hreflang="x-default"
      href="https://example.com/product-language/">

This is a hypothetical URL. Add it only after that selector exists and has been reviewed. If adopted, include it in every family member's alternate set. Give the selector the same set, including its own fallback entry.

The selector should keep the product context visible. A reader who arrives looking for document workflow software should understand that the choices lead to versions of that product overview.

Write down what happens when the reader chooses a language without a version. A useful interface can say the guide is available in English and let the reader choose it. It should not imply that a missing guide has been translated.

Avoid adding a fallback entry solely to make a validation report look complete. The destination is a reader-facing decision. Review its wording, choices, and links as part of the page family.

Review Canonicals Separately

A canonical expresses a preferred URL among duplicate or very similar pages. Hreflang describes localized alternatives. Keep the two decisions separate in the worksheet.

Google's canonical documentation recommends a canonical in the same language when using hreflang, or the best available substitute if none exists. Canonical preferences are signals; Google can select another URL.

For this fictional family, the team chooses self canonicals for its distinct, reviewed overview versions. The German page therefore carries:

<link rel="canonical"
      href="https://example.com/de/produkt/">

The English and British pages each name their own URL in their canonical element. That is this example's decision, not a universal instruction for every regional duplicate.

If two regional pages contain effectively identical English content, record the duplication question before copying this pattern. Google's multi-regional guidance discusses using canonical and hreflang annotations together for same-language regional duplicates.

Keep the evidence for each decision beside the URLs. A canonical copied from the English template deserves inspection when the visible article is German. Ask whether it reflects a deliberate duplicate-content decision or an unchanged template field.

Leave Missing Translations Out of the Family

Return to the implementation guide. Only the English and British versions exist in the fictional inventory. Their alternate set contains those two URLs. It contains no German placeholder.

Do not point the missing German guide to the German homepage. Do not point it to a German product page that answers another question. Both choices conceal the gap in the inventory.

Write a translation backlog entry instead: source URL, intended audience, content owner, terminology reviewer, and acceptance criteria. That entry belongs in the publishing workflow until the guide exists.

Review the source guide before commissioning the translation. If the British guide contains an extra setup step, decide whether that step is regional or simply missing from the generic guide. The translation brief needs a settled source.

For the standalone onboarding service, record that no equivalent exists. You can still provide ordinary navigation to relevant resources. An ordinary link does not assert that two pages are localized versions of one another.

This distinction also keeps product expansions honest. A plan to offer a service in another country is not a published equivalent page. Keep future commercial scope out of the current annotation map.

Review the Release With a Small Checklist

Use the approved family map as the comparison target. Review the smallest family first, then apply the same process to the remaining families.

  • Confirm each page answers the same buyer task as its mapped alternatives.
  • Confirm the visible language and regional offer match the assigned label.
  • Open every destination and inspect its response and final URL.
  • Compare the alternate sets across family members, including self references.
  • Review canonical choices beside the content rather than in isolation.
  • Confirm missing translations remain absent from the annotation sets.
  • Test the visible language choices without relying on automatic redirection.
  • Record the reviewed URLs, release version, reviewer, and unresolved questions.

This is a proposed release checklist. A passing checklist is evidence about the implementation you inspected. Hreflang annotations do not guarantee indexing or rankings.

For an existing site, review URL changes with the site migration checklist. A changed address means the map needs review again. Retain the previous map so someone can explain the transition.

If the team is choosing URL structures, use the SaaS URL architecture article as a discussion starting point. Verify the international requirements against current primary documentation before selecting an architecture.

Keep the Map With the Content

Assign maintenance to a named publishing role. A translated page can change after its original release. A product can become unavailable in one market. A guide can acquire a regional step that changes its relationship to another version.

When one member changes, review the family. Ask whether the buyer task still matches, whether the commercial scope remains accurate, and whether every referenced version still exists.

Keep intentional gaps visible. A blank cell with a reason gives the next editor a useful instruction. A guessed URL gives them a defect to discover.

Approve the page relationships before generating the tags.

Sources

Topic map: Technical SEO, crawling, and migrations

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Technical SEO, crawling, and migrations

Neighbor: SEO by industry and location

Neighbor: Search measurement and reporting

Neighbor: Topical authority and keyword strategy