Skip directly to page content
b13 GmbH

Hauptstätter Str. 59
70178 Stuttgart
Germany
+49 (0) 711 460 589 70 [email protected]
Graphic featuring a stylized link icon surrounded by overlapping shapes, set against a blue background with a gradient.

Hreflang Multisite—One Set, Every Market

Your European site and your North American site describe the same product. Google has no idea they are related.

TYPO3 builds hreflang tags for translations inside one page tree. Run separate trees for separate markets—and most international setups do—and each tree tells search engines it is the only version that exists. Visitors land in the wrong region, and your markets compete against each other in the results.

Hreflang Multisite links pages across those trees into one page set. Every page in the set carries the tags of all the others, including each tree’s own translations.

Maintained by editors, in the backend they already use. Not by a developer, in a configuration file.

Read the documentation

The Problem

You run one TYPO3 installation with separate page trees per market. Europe with English, German, Spanish, French, and Swiss German. North America with English, Spanish, and French.

That separation is deliberate, and usually not only organisational. The markets sell different things: a product line that does not exist in North America has no page there, and a regional service section exists in Europe and nowhere else. The navigation differs because the offering differs. A single tree with translations was never an option—the structures are not translations of each other.

TYPO3 handles the languages inside each tree correctly. What it cannot do is connect the two trees, because hreflang in the core is bound to the site of the current request—one site, its languages, done.

The result is two islands. Your Spanish page in Europe and your Spanish page in North America both exist, both rank, and neither tells Google the other is for a different audience.

Where your markets sell the same thing, those pages are often near-identical—frequently word for word, because both came from the same source text. That is duplicate content, and a search engine resolves it the way it always does: it keeps one version, largely ignores the other, and you do not get to choose which one it keeps. hreflang is the mechanism that declares them regional alternates instead of copies.

You end up competing with yourself for your own customers.

Doing it by hand is not a solution either. Hreflang has to be reciprocal: every language version must name every other one and itself, with the same list on all of them, and one wrong entry invalidates the group for everyone in it.

Writing that list is not the hard part. Keeping it right is. The mapping changes whenever a page is added, renamed, or moved—and it is your editors who change content, while the tags sit in a template they cannot reach. Nothing validates the result, and nobody can tell you which groups are currently incomplete. With a page set an editor links one page per tree and every language follows from your site configuration—two links in a setup where fifteen languages would otherwise mean a fifteen-entry list repeated on fifteen pages. And the damage stays hidden either way: nothing breaks, no error is logged, and the cost turns up months later as a line in a traffic report that nobody traces back.

hreflang is not a tag you set. It is a group you maintain.

How It Works

An editor opens a page, picks the pages in other trees that belong with it, and marks one as the x-default. That is the whole interaction.

From then on, every page in the group renders the full set of tags—one per language and region, plus the x-default fallback, in the language codes your site configuration already defines. No template changes, no TypoScript per page, no second place to keep language codes.

Three things happen automatically:

  • Every translation is included. A group of three pages across three trees with four languages each yields twelve tags on every one of them.
  • Pages that should not be listed are left out—hidden pages, no_index, and pages outside their start and end date.
  • The tags replace what the core generated, so there is no chance of two hreflang blocks contradicting each other.
The Page Set Editor in the TYPO3 backend: a list of the linked pages from multiple page trees, together with the selection of which one is treated as the x-default.

What You Get

Maintain the Group From Any Page in It

This is the part that decides whether hreflang survives contact with a real editorial team.

Every page in a set shows the same group and lets you edit it. An editor working on the North American page sees the whole group there and can change it from there. There is no master page, no “go to the English original first”, no rule anyone has to remember.

The alternatives store links on each page individually: you see what your page points at, not what the group looks like. That difference is invisible on a demo with three pages and decisive on a site with five markets and two hundred pages each.

The Hreflang Multisite overview in the TYPO3 Status module: a flat list of the page tree, each row showing the linked pages of the other markets with their language code and URL, one page still unlinked and one linked to a single market.

See Every Group at a Glance—and the Broken Ones

A backend overview walks your page tree and shows which page belongs to which set. Filter by pages with hreflang, without hreflang, or incomplete—the last one flags groups that are missing a market, marked per row.

That last filter is the difference between “we have hreflang” and “we know our hreflang is right”.

Four empty browser windows arranged in a grid, with one window featuring a star and a basket design at the bottom.

Decide Which Page Catches Everyone Else—Per Group

x-default is the page a search engine falls back to when a visitor matches none of your markets. TYPO3 sets it automatically, and the rule is the same on every page: it points at the site’s first configured language.

Here it is chosen per group, by an editor, and validated against that group.

That matters because the right fallback is not the same everywhere. A product page group spanning every market should probably fall back to your international English page. A group that only exists in Europe should fall back to a European page—not to a US page that is not even in the set. A global setting cannot express that; it picks one answer and applies it to content it knows nothing about.

The extension checks that your choice is actually a member of the group, so a fallback pointing outside the set is rejected rather than silently shipped.

Decide Which Page Trees May Be Linked at All

Not every tree belongs in a hreflang group, and some belong in none. Configuration defines which trees may be linked together—everything else is simply not offered to editors.

Campaign pages are the case that comes up most often. Where campaigns live in their own tree, that tree is short-lived, frequently near-duplicate content, and often on its own domain. Nobody wants a landing page for last spring’s promotion sitting in the permanent hreflang structure of a market—and nobody notices when it happens, because a wrong group looks exactly like a right one. Leave that tree out of every group and the mistake becomes impossible rather than unlikely.

The same boundary does the organisational job on a corporate installation: an editor in one national company cannot accidentally wire their pages into another one’s structure.

Two green rectangles connected by a yellow line, with a pink exclamation mark below, indicating a warning or alert.

Catch Configuration Errors Before Google Does

Two pages in one group claiming the same language and region make the whole group invalid—and search engines discard the group rather than the offending entry. That mistake is invisible in the backend and expensive in the results.

A configuration check in the page module reports duplicate hreflang codes across your linked trees, so the problem surfaces while someone can still fix it.

Extend It Where Your Setup Is Unusual

Hreflang Multisite handles pages: things that live in your page tree and have their own URL. A market running on a different platform, a legacy domain, a partner site—content that belongs in the group but is not a page in your tree—goes in through a PSR-14 event. It fires while the tags for a group are being assembled, so your own code can add, change, or remove entries with whatever logic your project needs.

The case that comes up most often is records—news, products, events. A record often has no counterpart in another market at all, the counterpart is rarely unambiguous, and record URLs come out of a route enhancer rather than the page tree, so there is nothing to store a relation against. The mapping is specific to your project, which is why it ships as an event rather than a setting.

We have built these. If you would rather not, tell us about your setup and we’ll tell you what it takes.

Compared to What You Have Today

 TYPO3 coreOther free extensionsHreflang Multisite
Tags for translations in one treeyesyesyes
Links pages across separate treesnoyesyes
Edit the group from any page in it—no—each page holds its own linksyes
Backend overview of all groupsnonoyes
Flags incomplete groupsnonoyes
Restrict which trees may be linked at all—noyes
x-default chosen editoriallyno—first language automaticallyone does; the other derives it from PHP configurationyes, validated against the group
A different x-default per groupno—one rule for the whole siteone does; for the other, one tree is the global defaultyes
Language codes read from site configurationyesone duplicates them in a PHP arrayyes

TYPO3 keeps page trees apart on purpose—different editorial teams, different permissions, different structures. Hreflang Multisite bridges that separation without dissolving it.

Who This Is For

Companies whose markets are genuinely different, not just translated. Manufacturers with national sales companies, universities with faculty sites, groups with separate brands.

Usually the trees are separate for two reasons at once. Different teams maintain them—and the markets sell different things. A product line that does not exist in North America has no page there. A regional service section exists in one tree and nowhere else. The navigation differs because the offering differs, which is exactly why a single tree with translations was never an option.

Only part of the content matches, and only that part needs to be in a group. Pages that exist in one market and nowhere else simply belong to no set, and nothing about them changes.

Editorial teams that maintain their own market. The group is editable from every page in it, so nobody has to know where the “real” version lives.

Anyone who has already tried it by hand. If you have a spreadsheet mapping page IDs across markets, this replaces it.

This is for separate page trees. Languages inside a single tree already get correct hreflang tags from TYPO3 itself—there is nothing here to add.

Where it earns its price is growth, and growth arrives on two axes at once. Add a language and the list every page carries gets longer; add a tree and the number of pages you link by hand goes up. A setup with two trees and fifteen languages means a fifteen-entry list that has to be identical on fifteen versions—with a page set it is two links, and every language follows from your site configuration. The list is the easy part. Keeping it right while editors move pages around is the part that fails.

Building it yourself is the option that looks cheapest and is not. The tags are the easy part. What takes the time is the editing surface: one group resolved from any member page, validated on save, and visible in an overview. Lullabot—one of the best-known Drupal agencies—put the manual-selection part of exactly this problem on their roadmap, wrote down why the interface is the hard bit, and never built it. Their module has been unmaintained since 2022.

System Requirements

TYPO3 v13.4 LTS and v14, PHP 8.2 or higher. The system extensions info and seo come along automatically.

More than one root page, and unique language and region codes within each group—two pages claiming en-us in one set is not valid hreflang, regardless of which product creates it.

Installation

After purchase you get access to the b13 Marketplace with your own Composer repository.

1
2
composer config repositories.b13 composer https://b13.com/_api/composer/p/<your-project>/
composer require b13/hreflang-multisite

Your credentials go into auth.json. A ZIP download is available in your account for installations without Composer access.

Add the shipped site set to your site configuration, define which root pages may be linked, and editors can start. 

Pricing

One price, and it does not go up when you add a language.

Hreflang Multisite is licensed per year and per production instance—one TYPO3 installation, one codebase, one database. How many sites, page trees, languages, or groups run inside it does not change the price. Staging, test, and local installations are free.

Hreflang Multisite

One production instance

Running this for client projects? Instances are counted per production installation, and a project can be handed over to your client later without repurchasing—the license moves with it. Tell us how many you need and we’ll price it.

Why a yearly license. This sits directly in your frontend output and depends on how TYPO3 resolves sites, languages, and URLs—the area that changes most between major versions. Until now this product was sold per TYPO3 version, which meant you paid again at every major upgrade. Over an LTS cycle the yearly license comes out about even, and sooner than that it is cheaper.

If you bought it before: your license covers the TYPO3 version you bought it for, and nothing changes while you stay on it. The natural moment to switch is your next major upgrade—talk to whoever you work with at b13 and we will sort it out with your project, not with a form.

Florian “Flix” Keitgen

Product Development

Questions?

Do you need more instances or do you have any other questions?
Talk to us!

Support

Every license includes email support, bug fixes, updates for new TYPO3 versions, and security fixes. One inbox, one queue. Requests that stop your operation get pulled forward. You get a ticket reference and can ask for the status at any time.

Priority—€300 per year per license. A guaranteed reply within one business day and prioritized bug fixes.

Enterprise—from €990 per year. Response times agreed by severity, a defined availability window, an escalation path, and an annual review. Individually contracted.

What support does not cover: installing and configuring it in your project, adapting it to your specific case, debugging your own code or environment, data cleanup, and training. We diagnose for up to an hour per request; if the cause turns out to be outside Hreflang Multisite, we tell you what we found and where to look.

Hreflang Multisite runs in your instance, so there is no uptime to commit to—what we commit to is when we answer.

Security reports go to [email protected]. We read every report and reply with an assessment, and we agree a disclosure date with you before anything is published. If your own disclosure process needs a fixed date, say so in the report and we will agree one.

FAQ

Does this work if my markets are on different domains?

Yes. The extension reads the URLs from your site configuration, whether your markets differ by domain, by subdomain, or by path.

What happens to the hreflang tags TYPO3 already generates?

For pages in a set they are replaced by the set’s own tags, so the two cannot contradict each other. Pages that belong to no set keep the core behaviour unchanged.

Do editors need to maintain the group on every page?

No—that is the point. The group is one record. Editing it from any member page changes it for all of them.

Can a page belong to two groups?

No, and that is a property of hreflang rather than of this extension: a page that claims membership in two competing groups gives search engines contradictory information.

My markets don’t have identical content. Does that break it?

No. Hreflang connects pages that serve the same purpose, not pages that contain the same words—markets write their own copy, drop sections, and add local ones. The German “Produkte” belongs with the English “Products”, not with “Services”. What has to match is the job the page does for a visitor in that market.

Does it handle news articles and products, or only pages?

Pages. Records—news, products, events—get their tags through the PSR-14 event with a mapping written for your project, and there is a reason it works that way: a record often has no counterpart in another market at all, the counterpart is rarely unambiguous, and record URLs come out of a plugin rather than the page tree. We have built this for customers; talk to us about your case.

Do I have to link every page by hand?

Every group, yes—only you know which pages are equivalent. What the extension removes is the per-language part: you link one page per tree, and every language follows from your site configuration. The overview module shows you which pages are still unlinked, so the work is a list to work through rather than a hunt.

What if a market runs outside TYPO3?

Add it through the PSR-14 event. It joins the set like any other entry.

What happens to my hreflang tags if I stop using the extension?

The pages fall back to what TYPO3 generates on its own—correct tags within each tree, no links across them. Your page sets remain in the database; nothing is deleted on uninstall.

What happens when the license expires?

Your running installation is unaffected—the code on your server keeps working, and nothing switches itself off. What ends is access to the releases: our Composer repository stops serving you new downloads.

One thing to know about your pipeline. If your deployment runs composer install against our repository on every build, that build will fail once the license has lapsed. Your production site keeps running, but your next deploy doesn’t. The code is GPL-2.0-or-later, so the copies you already hold remain yours to keep.

And this is why there’s a grace period: if a payment fails, you keep pulling for another 13 days while it gets sorted out. We also remind you twice before the license runs out.

Is it open source?

The code is GPL-2.0-or-later, like every TYPO3 extension. What you pay for is access to the releases, updates for new TYPO3 versions, security fixes, and support. You can read every line.

Do we need a license for staging and test systems?

Your production license covers them. Staging, test, integration, and every local installation of the same project are included—only production instances are counted.

What counts as one instance?

One TYPO3 installation—one codebase, one database. Everything inside it is covered: any number of site trees and language versions. Ten customer sites in one multi-site installation are one instance. Ten separate installations are ten—talk to us.

One Set, Every Market

Your regional sites already describe the same products. Hreflang Multisite is what tells search engines they belong together—maintained by the editors who own the content, not by a developer in a configuration file.

Talk to Us First