What TYPO3 brings to your visibility and where development begins
TYPO3 is a solid foundation for search engine optimization once someone actually uses the available options. Since version 9, the system has included slugs, meta fields, XML sitemaps, canonical tags, and hreflang without requiring a single extension to be installed. The difference between a TYPO3 website that gets found and one that does not is therefore rarely a lack of features. It comes down to whether those features are maintained and whether someone knows where the backend ends and the template begins. This article takes you through the process step by step: what TYPO3 can do itself, when an extension makes sense, which mistakes we encounter most often in projects, and which topics can only be solved by intervening in the integration.
What TYPO3 includes out of the box
The most important SEO functions are provided by the system extension EXT:seo, which has been part of the core since TYPO3 9.5. It is already active in most installations, but it does not appear as a separate module in the backend. Instead, its functions are distributed across the page properties.
Slugs and readable URLs
The slug is a page's URL, and TYPO3 automatically creates it from the page title and its position in the page tree. The result is usually useful, but long page titles create long URLs, and deeply nested structures create paths with several levels. Shortening them is worthwhile as long as the URL remains understandable. Stability is more important than maximum brevity. An established structure should not be rebuilt solely because of its length.
Meta information for each page
The page properties contain the SEO title, meta description, and information for Open Graph and X/Twitter. The SEO title can differ from the page title in the page tree. The description does not influence rankings, but it does help determine whether someone clicks your result. With large numbers of pages, maintaining this information quickly becomes a project. The AI Suite can be used to prepare page titles and meta descriptions directly in the TYPO3 backend for many pages at once.
The XML sitemap
TYPO3 generates the XML sitemap itself. It is usually located at /sitemap.xml and points to sub-sitemaps for pages and records. Depending on the extension, records from extensions may require their own sitemap provider. A sitemap speeds up the discovery of new pages, but it does not guarantee indexing. The difference between submitted URLs and URLs actually indexed in Google Search Console is crucial.
Canonical tags
Normally, TYPO3 sets the page's own URL as the canonical. Intervention becomes necessary when the same content can be accessed through multiple URLs, for example due to parameters or alternative detail views. The “Canonical link” field can then be used to define the authoritative address.
Controlling indexing: robots directives and robots.txt
Individual pages can be assigned noindex and nofollow. The robots.txt file, on the other hand, controls which areas may be crawled. Excluding something in robots.txt does not reliably prevent a URL from being added to the index. If a page must definitely not appear, it needs to remain crawlable and deliver noindex. robots.txt can also be used to decide whether AI crawlers such as GPTBot or ClaudeBot may retrieve content.
hreflang and multilingual pages
TYPO3 generates hreflang information from the site's language configuration. This only works properly if the specified language versions actually exist. Otherwise, fallback content can pretend that a translation exists when there is none editorially. In that case, a deliberate decision is necessary: translate it or do not deliver the second version.
Does TYPO3 still need an SEO extension?
No SEO extension is strictly necessary, because the basic functions have been part of the core since version 9. The more interesting question is how much work maintaining many pages creates in everyday use. This is exactly where extensions come in: with a preview of the search result, overviews of missing information, and evaluations based on a focus keyword.
clickstorm SEO provides a backend module in which the SEO fields of several pages are displayed side by side. Yoast SEO for TYPO3 analyzes texts as they are written. Embedding schema.org vocabulary provides the basis for structured data. b13/de-slash standardizes URLs without a trailing slash, including links, canonicals, and hreflang.
A green traffic light is not a ranking guarantee, but an editorial guideline. The larger the page tree, the more worthwhile a tool can become. What no extension takes over is the decision about which pages should be worked on first. When choosing one, what matters above all is how closely the developers keep up with TYPO3 and support version upgrades.
An extension that we develop ourselves is described in more detail in the next section: our AI Suite.
How the AI Suite supports you with SEO
The AI Suite is a TYPO3 extension that handles recurring SEO work in the backend. It covers three areas that would otherwise be handled in different places and with different tools: metadata, analysis of a page, and questions that arise during work.
Metadata for many pages at once
Page titles, meta descriptions, OpenGraph and Twitter information, and keywords are created directly in the backend, either for a single page or for many pages in one go. The same applies to image metadata, including alternative texts, both for images in content elements and in the file list. Titles, descriptions, and keywords can also be generated for news from EXT:news. Filling in empty fields thus becomes a matter of reviewing and approving them, and this is exactly where most initiatives fail with large page trees.
The AI Audit checks six areas
The audit module examines a publicly accessible page URL and offers six types of analysis: SEO and performance, accessibility, W-question and FAQ coverage, content gaps based on existing rankings, topic clusters, and competitors. The findings are condensed into an audit score from 0 to 100 and then categorized according to how they can be resolved.
The “SEO and performance” analysis also uses Lighthouse and evaluates how readable a page is for AI systems. When a focus keyword is set, search volume, detected search intent, and your own position in the search results are added. The AI Suite uses keyword candidates to suggest suitable terms, each with monthly search queries, competition, and difficulty. This covers exactly the preliminary work required for the content in the section below about prioritization.
Metadata findings and missing alternative texts can be fixed directly from the results. That is the difference compared with an audit tool that simply outputs a list and leaves you to deal with it alone: analysis and implementation take place in the same location.
ChEddi answers questions directly in the backend
ChEddi is an AI assistant located in the TYPO3 backend that can be expanded on every backend page. Requests are entered in plain language, for example, “which pages still have no meta description?” For daily SEO work, this is the fastest way to find gaps in the page tree without first searching for a module or starting a crawl.
Two things are important here. ChEddi works with the permissions of the logged-in user, so it can only see and change what the editor is allowed to see and change anyway. And by default, all changes are placed in a draft workspace, meaning they remain invisible to visitors until someone publishes them.
Five mistakes we repeatedly see in TYPO3 projects
A page is renamed, its slug changes with it, and the old URL leads nowhere. External links, bookmarks, and the previous ranking lose their connection. The system extension redirects can automatically record slug changes as redirects, provided it is installed and configured accordingly. After entire branches of pages have been moved, the redirects must still be checked. They should point directly to the final destination; chains and loops should be cleared out regularly.
Thank-you pages, search results, print views, old campaign pages, or forgotten test areas do not belong in the sitemap. Pages with noindex are normally excluded. What matters is that the sitemap and the desired indexing communicate the same message. A long list is not a quality indicator if some of the URLs should not be found at all.
If a second language is configured but not fully translated, fallback pages can generate incorrect hreflang signals. Search engines check these details against one another. If the English version does not properly link back to the German version, or if the content is clearly the same, hreflang is ignored. The editorial decision is therefore: translate it or do not deliver this language version.
If the description remains empty, Google selects an excerpt from the text itself. Sometimes it fits, but often it contains a sentence from the navigation or cookie notice. An identical description for every page is even less favorable. It does not affect rankings, but it does affect the click-through rate. Two suitable sentences for each important page are usually more valuable than a generic template.
A clean structure means exactly one H1, followed by H2 headings for sections and H3 headings for subtopics. Headings should not be chosen solely because of their size. There are other settings for visual design. This is important for screen readers and machine-based analysis. More about the connection with accessibility can be found in the article about implementing the BFSG in TYPO3.
Where TYPO3 SEO can no longer be solved from the backend
Up to this point, we have discussed fields and settings that an editorial team can maintain itself. The following four topics have at least as much influence on visibility, but they lie in the template and configuration. Anyone looking for them in the backend will search in vain.
Loading time and Core Web Vitals
Unoptimized images, blocking scripts, and unsuitable caching slow down a page. TYPO3 can deliver image variants and modern formats, but the Fluid template must also use them. Ideally, measurements should be taken on several page types, not just the homepage.
Structured data
TYPO3 does not automatically output structured data in full. Articles, organizations, breadcrumbs, or FAQs must be added and linked together depending on the project. The schema extension can serve as a shared foundation.
Internal linking through the page tree
Menu links show the hierarchy, but links from running text establish a stronger topical connection. TYPO3 makes internal links robust because they move with a page when it is moved or renamed. The editorial decision about which page is the appropriate target in which location is nevertheless still necessary.
Semantic markup
Navigation, main content, lists, and controls must be marked up semantically in the template. This is primarily a matter of accessibility, but it also helps machines distinguish the actual content from the page framework. More background can be found in the article about implementing the BFSG in TYPO3.
Why clean content elements contribute to visibility
When an appropriate content element exists for every use case, clean structures emerge almost by themselves. When such building blocks are missing, layouts are built from tables, headings are chosen for visual reasons, and formatting is copied from Word. The result is source code that is difficult to analyze. With Content Blocks and the Content Blocks GUI, custom content elements can be defined in a structured way. The SEO benefit is indirect but real: the better the building blocks fit the editorial routine, the less often a page's structure becomes a product of chance.
Relaunch and version upgrade: the two moments when rankings are lost
A relaunch is the riskiest moment in a website's life. The structure, URLs, templates, and content all change at the same time. Before rebuilding, existing URLs should be recorded using data from Google Search Console and assigned to new target addresses. Pages without a direct equivalent should point to the next-best thematically relevant page, not automatically to the homepage. After launch, error pages and index coverage must be monitored for several weeks.
A pure version upgrade from TYPO3 v12 to v13 normally does not change URLs. It becomes risky when templates, the page structure, or addresses are changed at the same time. In that case, it is effectively a relaunch. In addition, all extensions must be checked for compatibility and maintenance status. TYPO3 security updates should be included in the planning. The versions currently supported are listed at get.typo3.org.
The situation is different when upgrading from TYPO3 8 or older. Until then, readable URLs were not part of the core, but were created using extensions such as RealURL. Since version 9, routing with slugs has taken over this task. Addresses are therefore generated using a different technology and do not necessarily match the previous ones. Before such an upgrade, the same procedure as for a relaunch is therefore required: record all old URLs, assign new addresses to them, and create the redirects before switching over.
For the AI Suite, our managing directors at AutoDudes are personally involved in the TYPO3 Content Types Team. This allows them to see changes in the core at an early stage and prepare the extension for major versions. More information is available on the about us page.
The order that delivers the most in practice
Start with the basics in the backend: important SEO titles and meta descriptions, noindex for irrelevant pages, and a sitemap that actually contains the desired URLs. Then crawl for 404 errors, redirect chains, duplicate titles and descriptions, and incorrect hreflang information. Google Search Console adds insight into the pages Google knows about or rejects. Next comes the technology in the template: measure loading times across several page types, optimize image delivery, and add structured data. This requires development, and analysis and implementation should work closely together. Ongoing SEO support differs from a one-time audit precisely because it also turns findings into implementation. Finally, focus on the content: clarify search intent, structure headings, sharpen introductions, and add suitable internal links. Good content has no effect when the technology is holding it back, and good technology leads nowhere if nobody knows what people are searching for.
Frequently asked questions about TYPO3 and SEO
Is TYPO3 good for SEO?
Yes, and this is true even for a standard installation. TYPO3 provides clean URLs, per-page meta fields, an automatically generated XML sitemap, canonical tags, hreflang for multilingual websites, and controllable indexing. What TYPO3 does not provide is an automated process that fills these fields with good content. Whether a TYPO3 website gets found therefore depends not only on the system, but also on the maintenance and quality of the integration.
Which SEO extension does TYPO3 need?
None is strictly necessary, because the SEO functions themselves have been part of the core since version 9. For editorial work, clickstorm SEO and Yoast SEO for TYPO3 are widely used. The AI Suite covers three areas. It generates page titles, meta descriptions, OpenGraph information, and image alternative texts for many pages in one go. Its audit module examines a page in six areas, from SEO and performance to accessibility, competitors, and topic clusters, and metadata findings can be fixed directly from the results. In addition, there is ChEddi, an assistant in the TYPO3 backend that answers questions in plain language, such as which pages still have no meta description. With all extensions, it remains important how closely their developers work with the TYPO3 core and support version upgrades.
How do I create an XML sitemap in TYPO3?
You do not need to create one manually: TYPO3 generates the XML sitemap itself as soon as the system extension EXT:seo and its associated configuration are active. It is usually located at /sitemap.xml and points to sub-sitemaps for pages and records. Extensions such as News may require their own provider. The sitemap should then be submitted to Google Search Console.
Will I lose my rankings when upgrading to a new TYPO3 version?
Normally not with a pure version upgrade. An update does not change your URLs as long as the structure and content remain the same. It becomes risky when new templates, a new page structure, or new addresses are created at the same time. In that case, it is effectively a relaunch, and a redirect strategy must be prepared before the rebuild.
A Shopware store has different requirements in many of these areas because it automatically generates its pages from product data. The guide to Shopware SEO explains what needs to be considered there. If you are looking for support with your Shopware store, you can find our TYPO3 services here.