Writing

Moving 414 dealer sites to TYPO3 13: why the volume is smaller than it looks

November 2026 · Bouletteproof engineering · In progress

GT2, a French digital agency, runs the websites of Polaris's off-road vehicle subsidiaries and of their dealers. They run on TYPO3 8.7. We are moving them to TYPO3 13.4, one market at a time.

Counted from the production database, the job looks like about 2,900 live pages on 952 web addresses. Counted by what actually differs, it is about 1,960 pages and 414 dealer records, and each dealer differs from the next in five to eight places.

Bouletteproof has been GT2's engineering provider for more than ten years. This is our own work, described from the inside while it is still under way. The last part covers Hikr, the analytics service we build, and the TYPO3 extension that will measure what the dealer sites bring in.

What there is to move

Live pages With their own content Showing another page
34 brand sitesabout 2,1201,701419
14 dealer page trees786263523

Behind the 14 dealer trees sit 414 active dealers, answering on 952 web addresses. A dealer's site is its market's shared tree with the dealer's own banner, dealership page, map, privacy text and social links, plus a few settings such as its analytics ID.

Two thirds of the dealer pages carry no content of their own: they display a brand page. On TYPO3 13 those become pointers to the brand page, not copies.

Why the volume is smaller than it looks

A dealer is not a site to rebuild. On 8.7, each dealer has its own template of about twenty settings that point at its five to eight zones. On 13.4, each dealer becomes one record: its addresses, banner, opening hours, social links, privacy text, analytics ID and the number its leads are sent under. Adding a dealer then means adding a record, not writing a template.

That leaves about 1,960 pages and 414 records. It is still too many to review one by one, so the method is built around review by exception.

A lab first

Before touching Polaris's off-road sites, we rebuilt one small site on TYPO3 13.4 on a laptop: Polaris Slingshot's site for Mexico. It proved the chain end to end. Read the live page, turn it into structured page data, import that into TYPO3 13 as typed content blocks, and render it with the new templates. The old sites are built with TemplaVoilà templates; the new ones with Fluid templates and Content Blocks.

Read the live page, check by machine

The pilot market is New Zealand. We fetched every live page the database lists, rather than following links, so nothing could be missed: 141 pages across the brand site and its 18 dealers.

Every off-road model page turned out to be built from only nine kinds of section. Extracting them is a fixed set of rules, not guesswork. The first run on New Zealand's 17 model pages produced 210 content blocks. All 415 images came across. All the visible text came across on 16 pages, and 99.9 percent on the 17th, where one option label was missed.

Each run reports, page by page, what share of the visible text and images arrived. A person looks only at the pages that fall short. That is what makes 1,960 pages reviewable.

The extraction also found a bug on the live sites. New Zealand's model pages show visitors raw template placeholders such as {$print}, because two settings are missing on 8.7. On the new pages those labels live in the blocks.

One site, hundreds of dealer addresses

On 8.7, one page tree serves every dealer in a market, and a condition per address picks the dealer. On 13.4, each market becomes one site that answers on all of its dealers' addresses, with one entry per address saying which dealer it is.

One detail decides whether that works, so we read it in the TYPO3 13.4 source. The page cache is keyed on the page, the site, the language, the route and the list of conditions that matched, not on the address. Without a condition per address, the first dealer to load a page would serve its own banner and its own canonical address to every other dealer in that market. So the conditions are generated from the dealer records, one per address, and each dealer gets its own cached pages.

Moving one address at a time

Each address moves on its own, at the load balancer. It is checked against the new servers first, then a rule sends that address to them. Rolling back means flipping the rule back.

The trap is the certificate. Older addresses share Google-managed certificates that cover many domains each and renew all or nothing: at renewal, every domain on a certificate must still point at that load balancer. In May, one dealer address moved to a new load balancer without being taken off its old shared certificate. That certificate could not renew, expired on 21 May, and took about 23 dealer sites down with it.

The rule since then: when an address leaves an old load balancer, its old certificate is rebuilt without it at the same moment. Addresses on the new load balancer each get their own certificate, so one address can no longer take others down.

Measuring what the dealer sites bring in

The new sites will also carry Hikr, the analytics service we build at Bouletteproof. For TYPO3 it comes as an extension: a TYPO3 extension that adds Hikr's measurement to a site and serves it from the site's own address, not from ours. It is designed, and not yet built.

What it is for

Polaris's markets run on two levels: brand sites for each market, and a site for every dealer. Dealer sites convert at much higher rates than the brand sites, and that is why every dealer has one: someone looking for an off-road vehicle near their town should land on their nearest dealer's page, whether they ask a search engine or an AI assistant.

What Hikr adds is the number. For each visit it records where the visit came from, such as a search engine, an AI assistant, an ad or the brand site, and whether a lead followed on the dealer's site. Added up per dealer, that shows how much of each dealer's conversion comes from local search. We will publish it from the first sites.

Why an extension, and why the site's own address

Pasting a snippet into 414 dealer sites means 414 places to keep in step. The extension installs once per TYPO3 installation and covers every site and dealer address it serves.

Hikr reads the same consent answer as the site's Google Analytics. With consent, it follows the visit from the brand site to the dealer and on to the lead. Without consent, it falls back to counts that store nothing on the visitor's device, and only where the country's rules allow even that. Those rules are written down per country, and a data-protection lawyer still has to confirm them.

With consent, Hikr keeps an identifier on the visitor's device, and that is where the address matters. Browsers treat a request to another company's server differently from a request to the site itself: Safari, for one, shortens the life of cookies that come from a server that does not look like the site's own, and Apple does not document the exact rule. When the measurement lives at a path on the dealer's own address, such as /t/, the browser sees one site, and the question does not arise.

The tag the extension adds will be the same for every visitor, so pages stay in TYPO3's cache. The click identifier Hikr adds to tracked links will be kept out of the cache keys, so a tracked link does not create a new cached copy of a page.

On Polaris's off-road sites

Every off-road address already passes through a load balancer GT2 runs, the same one that moves each address to TYPO3 13. There, the route is one more rule: requests to /t/ on a dealer's address go to Hikr, and everything else goes to TYPO3. On these sites the extension's only job is to put the tag in the page. Measurement requests never pass through the TYPO3 servers, and the address the visitor sees does not change.

These sites already ask for consent through their own banner, so Hikr has to take its answer from that banner. That mode does not exist in Hikr yet.

The first install is planned for the New Zealand and Australian sites and their dealers, once they are live on TYPO3 13.4.

On any other TYPO3 site

Where no rule is added at the edge, the extension is the route. It serves Hikr's script from the site and passes requests on /t/ to Hikr from the site's own server. Whoever runs the site changes nothing at the load balancer, the CDN or in DNS. This is the version for TYPO3 sites outside GT2's platform.

The cost is that measurement requests pass through TYPO3. And because Hikr then sees the TYPO3 server rather than the visitor, the extension has to pass along where the visitor is, since that decides which consent rules apply. Hikr will accept that only from a server that signs it with the site's own key.

Like the rest of this work, the extension is written for TYPO3 13.4 and later.

What is left to build

  • The extension itself. It follows how TYPO3 GmbH's own analytics extension, t3g/analytics, adds a tag without breaking the page cache.
  • A key per site, and a way to register a site with it. Today, adding a website to Hikr needs a person signed in to its dashboard.
  • Hikr accepting the visitor's location and IP address from a server that signs with that key.
  • Reading a site's report with the same key. Today only a dashboard sign-in can.
  • On the off-road sites, taking consent from the site's own banner.

Where it stands, 16 November 2026

Nothing is live on TYPO3 13 yet.

  • New Zealand's and Australia's brand sites are rebuilt on staging. Their 206 model specification records are imported, and on 31 model pages all 1,627 displayed values match the records.
  • Australia's dealer sites are next.
  • Then one translated market, then the multi-language ones: Benelux, the Gulf states and Latin America.
  • Hikr's TYPO3 extension is designed, not built. It goes on the New Zealand and Australian sites and their dealers first.

We will update this article with the live numbers when New Zealand and Australia switch over.


Engineering note from Bouletteproof. Related: The siege: load-testing TYPO3 13 on Google Cloud, The blast radius of a change and The boring parts that ship.