TYPO3 SEO

TYPO3 plays to its strengths in exactly the kind of website that is most complex SEO-wise — multi-site and multi-language presences. We make sure this complexity translates into visibility instead of cannibalising itself.

Get expert advice

Official Silver Member of the TYPO3 Association

TYPO3 SEO is more than installing an extension

Keyword analysis, content structure and technical SEO work at their core the same with TYPO3 as with any other system — how we approach it methodically, we describe on our general SEO services page. This page is about what specifically comes on top with TYPO3, above all where several languages or several site presences converge in the same backend.

Hreflang & international SEO — TYPO3's crowning discipline

As soon as a website exists in several languages or for several countries, correct hreflang annotation decides whether Google shows every user the right language version — or whether language versions displace each other in the rankings.

How we implement hreflang cleanly in TYPO3

Automatic hreflang generation: for multi-language setups within one page tree, we configure hreflang directly via the TYPO3 site configuration instead of maintaining it manually
Cross-site hreflang: if your language or country versions sit on separate TYPO3 installations, we connect them cleanly via a dedicated hreflang multisite module
Self-referencing tags: every language version references itself and all alternatives correctly, including x-default for the language-neutral standard version
A consistent canonical strategy: hreflang and canonical tags quickly contradict each other in TYPO3 multisite setups when they don't come from one configuration source. We make sure both fit together

Precisely with grown corporate structures spanning several country domains, a technical check pays off here — hreflang errors often go unnoticed for months because they don't stand out obviously in the search results.

The technical foundation — EXT:seo and structured data

The TYPO3 extension EXT:seo is the standard for meta tags, XML sitemaps and basic structured data. We configure it cleanly per site and language, instead of relying on the defaults.

Typical technical traps in TYPO3 multisite

One shared XML sitemap for several sites instead of separate, cleanly referenced sitemaps per domain
Missing or wrongly set canonical tags after sitepackage or domain changes
Structured data (Schema.org) that editors can't maintain without developer intervention
Duplicate content between linguistically very similar country variants without a clean hreflang foundation

Core Web Vitals with TYPO3

With TYPO3 too, the Core Web Vitals help decide rankings and user experience. Reverse-proxy and ESI caching, a lean sitepackage and a well-considered extension selection are the levers we pull here.

The three Core Web Vitals metrics

Largest Contentful Paint (LCP): how quickly the largest visible content loads, usually a hero image or a large heading
Interaction to Next Paint (INP): how quickly your page reacts to clicks and input
Cumulative Layout Shift (CLS): how stable the layout stays while loading, instead of shifting content during the load

Concretely we rely on TYPO3's own image processing with modern formats, reverse-proxy caching for recurring requests and a deliberately lean extension stack, instead of covering functions multiple times across different extensions.

Ready for your TYPO3 project?

Tell us about your project. We'll get back to you promptly with an honest assessment.

By the way: aceArt is an official Silver Member of the TYPO3 Association.