Social Share Buttons for TYPO3

In most TYPO3 projects, a social share button extension is unnecessary

The idea is simple: visitors should be able to share content on LinkedIn, X or Facebook with one click. insign_share_buttons delivers exactly that as a TYPO3 extension, with buttons for various networks that you configure in the backend. In practice, though, a feature that essentially consists of five HTML links doesn’t need a full extension with its own configuration, TypoScript setup and update obligations. In most cases, that’s overhead. Gosign recommends native share links instead: they take 15 minutes to implement and create no dependency.

This matters even more under the GDPR. Many social share extensions load JavaScript from the networks in the background, which violates data protection law unless visitors have consented first. Plain URL-based share links avoid the problem entirely, because they only connect to the network when someone clicks. Data protection officers routinely check share buttons during website audits, and an extension that loads external scripts without asking will show up as a finding.

Typical use cases are limited to editorially managed content

The standard scenario is a corporate website with a blog or magazine. Editors want buttons for LinkedIn, X, Facebook and email below every article. insign_share_buttons provides this through a content element that is built into the page template. The extension reads the title and URL of the current page and generates the share URLs from them.

A second scenario involves intranet portals where employees are meant to share internal news via Teams or Slack. Here, the extension actually adds more value than on public websites, because the GDPR assessment is different inside a company and the share targets can be maintained in the backend.

The third scenario is websites focused on employer branding, where job postings are meant to spread through social media. The share buttons are placed specifically on career pages so that employees can share open positions with their networks. Experience shows that 0.5 to 2% of page visitors use these buttons. On LinkedIn, click-through rates on shared job postings are twice as high as on general company news, which makes this the most effective use case for social share buttons.

Technical architecture: a simple content element with TypoScript configuration

insign_share_buttons registers a content element in TYPO3 that is inserted via the page template or as a plugin. The configuration defines which networks are shown, whether icons or text labels are used and whether share counters are displayed. Rendering runs through Fluid templates that can be overridden in the sitepackage.

The share URLs are generated on the server side and follow each network’s standard scheme: https://www.linkedin.com/sharing/share-offsite/?url= plus the encoded page URL for LinkedIn, https://twitter.com/intent/tweet?url= for X. Metadata such as title and description is read from the page properties or the OpenGraph tags.

Apart from the TYPO3 core, the extension has no significant dependencies. No JavaScript is loaded from external domains as long as the counter feature stays disabled. Once the counter feature is enabled, it triggers API calls to the networks, which in turn requires consent.

One technical detail that is often overlooked: the share URL has to be URL-encoded so that special characters in page titles (umlauts, ampersands, quotation marks) reach the networks correctly. The extension handles this encoding automatically, and it’s a common mistake with hand-built share links.

Common problems: GDPR violations, missing OpenGraph tags and styling conflicts

Problem one is data protection. Many installations have the counter feature switched on, which transfers personal data to US servers without cookie consent. The fix: disable the counters and use only URL-based share links that connect when clicked. Better still, replace the extension entirely with native share links kept as a Fluid partial in the sitepackage.

Problem two is missing or incorrect OpenGraph tags. If the TYPO3 page doesn’t provide og:title and og:description meta tags, LinkedIn and Facebook show an empty preview when the page is shared, or they pull in random text fragments. The fix isn’t in the share extension but in the page’s SEO configuration: the OpenGraph tags have to be set correctly in the page template.

Problem three is styling conflicts between the extension’s bundled CSS and the corporate design. The extension ships its own stylesheets, which can clash with existing button styles. The clean solution: disable the extension’s CSS and style the buttons through your own sitepackage stylesheet.

Another problem that often surfaces late is missing WhatsApp sharing. On mobile devices, WhatsApp is the most widely used sharing channel, but not every extension supports the WhatsApp share link natively. Adding it manually is trivial (https://api.whatsapp.com/send?text={url}), but someone has to build it in explicitly.

The extension works under TYPO3 v12, but rebuilding is more cost-effective

insign_share_buttons is compatible with TYPO3 v12. For TYPO3 v13, availability depends on the maintainer. When migrating to v12 or v13, Gosign recommends replacing the extension with a simple Fluid partial: five lines of HTML per network, no extension dependency, no update obligations, full GDPR compliance. The switch takes one to two hours, including styling and testing all network links. At Gosign, we use this approach as standard in every new TYPO3 project and maintain a set of partial templates for LinkedIn, X, Facebook, WhatsApp and email that can be integrated into any sitepackage.