dpn_glossary for TYPO3

A glossary delivers SEO value when internal linking runs automatically

Manually linking technical terms across a website is Sisyphean work. A company with 200 pages and 80 technical terms would theoretically need to review every page and connect relevant terms to the glossary page. In practice, this never happens completely, and it is forgotten for new content. dpn_glossary automates this process: the extension detects defined technical terms in the content and automatically links them to the respective glossary page or displays a tooltip definition.

The SEO effect is measurable. Each glossary term creates its own indexable URL. The automatic linking from content creates a dense internal link network that helps Google assess the website’s topical authority. Websites with 50+ glossary terms typically generate 5 to 15% additional organic traffic through long-tail keywords.

Typical use cases

Industry portals and sector websites. Insurance companies, financial services, law firms, technical companies - wherever specialized language is part of daily business, visitors benefit from clear definitions. An insurer with terms like “coverage limit”, “deductible”, “right of recourse” can display these as tooltips in running text without disrupting the reading flow. Simultaneously, an alphabetical glossary page serves as a reference work.

Technical documentation and knowledge bases. Software companies that maintain their documentation in TYPO3 use dpn_glossary to consistently explain technical terms (API, SDK, Webhook, OAuth). New employees and customers find definitions directly in context without needing to look up a separate document.

Multilingual websites with language-specific terms. dpn_glossary supports TYPO3 translation mechanisms. Terms can be defined per language, including different definitions and abbreviations. A German glossary term “Betriebsrat” is recognized and linked as “Works Council” in the English content.

Technical architecture

dpn_glossary stores glossary terms in a dedicated table (tx_dpnglossary_domain_model_term). Each term has a name, a definition (RichText), optionally a short form, synonyms, media (images, files) and a detail URL. Synonyms are important: the term “AI” can be defined as a synonym for “Artificial Intelligence” so both spellings are automatically recognized in the content.

The automatic linking works as a content post-processor: after TYPO3 has rendered the page content, dpn_glossary searches the HTML output for known terms and replaces them with links or tooltip markup. HTML tags, attributes and existing links are excluded to prevent broken nesting. The replacement is configurable: first mention per page only, all mentions, or no replacement (tooltip only).

The glossary page is set up as a TYPO3 plugin page. The default view shows an alphabetical navigation (A-Z) with all terms. Each term has a detail page with definition, related terms and optionally embedded media. URLs follow the pattern /glossary/term-name/, which is optimal for SEO.

Performance: the automatic linking searches every rendered page content. With 100+ terms and long pages, this can become noticeable. dpn_glossary caches the term list and uses regular expressions for the search, which is not a problem with TYPO3 page cache enabled (cached_pages) because the replacement only runs on the first request.

Common problems and solutions

Terms linked in headings, menus or forms. The automatic linking sometimes captures HTML areas that should not be linked. Solution: the extension offers configuration for excluded tags (e.g. h1, h2, h3, nav, form, a). By default, headings and links are excluded, but the list must be adjusted per project.

Tooltip display conflicts with the layout. Tooltips (hover popups with the definition) can overflow the page edge or cover other elements. Solution: adjust the tooltip CSS (max-width, z-index, position). dpn_glossary includes a default CSS that can be overridden via TypoScript. For mobile devices, tap-instead-of-hover behavior is recommended.

Performance issues with many terms. Websites with 500+ glossary terms experience the linking on uncached pages. Solution: restrict the term list to active terms (deactivate outdated ones), limit the linking to specific page areas (main content only, not footer or sidebar) and consistently use the TYPO3 page cache.

Migration and version compatibility

dpn_glossary supports TYPO3 v11 and v12 in the current stable version. TYPO3 v13 compatibility is in development (as of April 2026). The extension is actively maintained with regular releases and a clear upgrade path.

For projects migrating from another glossary solution (e.g. a custom-built glossary plugin or a WordPress migration), data migration is straightforward: export terms as CSV and load them into the dpn_glossary table via import script. Gosign has a CLI tool that supports CSV, JSON and XML sources.

Long-term, Gosign recommends additionally outputting glossary data as Schema.org DefinedTerm markup. dpn_glossary does not offer native support for this, but a Fluid template override can add the markup per glossary term. This improves visibility in Knowledge Panels and AI-generated answers.

Another use case that is often overlooked: glossaries as onboarding tools for new employees. Companies with many internal technical terms (insurance, banking, government agencies) can use dpn_glossary in their intranet TYPO3 so new colleagues can look up unfamiliar terms directly in context. The extension works in the intranet exactly as on public websites.

Gosign estimates the initial setup of a dpn_glossary project (installation, configuration, template customization, import of 50 terms) at 1 to 2 development days. Ongoing maintenance of terms is handled by the editorial team through the TYPO3 backend. Per term, the name, definition, synonyms and an optional image need to be maintained - achievable in 5 to 10 minutes.