PHPackages                             undkonsorten/meta-tag - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Templating & Views](/categories/templating)
4. /
5. undkonsorten/meta-tag

ActiveTypo3-cms-extension[Templating & Views](/categories/templating)

undkonsorten/meta-tag
=====================

Provides Fluid view helpers to set meta tags in TYPO3 CMS

1.0.0(7y ago)0209GPL-2.0+PHPPHP ^7.2

Since Feb 27Pushed 7y ago2 watchersCompare

[ Source](https://github.com/cumuru/meta-tag)[ Packagist](https://packagist.org/packages/undkonsorten/meta-tag)[ RSS](/packages/undkonsorten-meta-tag/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (2)Dependencies (2)Versions (5)Used By (0)

meta-tag [![Build Status](https://camo.githubusercontent.com/8b8e5567daf124a4e46d4ee4618cd2aad371bc9bf629283828543097bec00fd0/68747470733a2f2f7472617669732d63692e6f72672f63756d7572752f6d6574612d7461672e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/cumuru/meta-tag)
=====================================================================================================================================================================================================================================================================================

[](#meta-tag-)

TYPO3 extension allowing to write your meta-tags in Fluid. Syntax is a close as possible to the HTML `` tag. Ships with one level of override.

Installation
------------

[](#installation)

Via composer

```
composer require undkonsorten/meta-tags

```

or from [Github](https://github.com/cumuru/meta-tag)

Configuration
-------------

[](#configuration)

No configuration is needed, there‘s no TypoScript to include.

Usage
-----

[](#usage)

To use the view helper in your Fluid templates you have to import the namespace, e.g.:

```

```

or

```
{namespace m=Undkonsorten\MetaTag\ViewHelpers}

```

Then you can use the meta view helper in any of the following forms:

```

{m:meta(property:'og:description',content:description)}

{author.fullName -> m:meta(name:'author')}

```

If the content is empty (i.e. only white-space characters) no meta tag is added. There‘s no need to wrap each of your meta tags in an if construct just to get rid of the empty ones.

### Overriding

[](#overriding)

If for a requested meta tag there‘s a collision with an existing meta tag (same `property` / `name` / `http-equiv` value) then the existing one will be kept and the new one will be discarded. To change this behavior you can set `override="1"`. Then any existing meta tag of the same type will be overridden.

That means you have a two-level hierarchy that works regardless of processing order at run time. Just define your "global" meta tag with values e.g. from `pages` record without override but set that flag for your more specific ones, e.g. coming from extension show actions.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 50% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~129 days

Total

4

Last Release

2607d ago

Major Versions

0.1.0 → 1.0.02019-03-22

PHP version history (3 changes)0.0.1PHP ^7.1

0.0.2PHP ^7.0

1.0.0PHP ^7.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/a192083f4fc05fe8020592c9b5222677998fcf0e779df21ecb51016d8fd45f98?d=identicon)[undkonsorten](/maintainers/undkonsorten)

---

Top Contributors

[![cumuru](https://avatars.githubusercontent.com/u/12487311?v=4)](https://github.com/cumuru "cumuru (12 commits)")[![eliashaeussler](https://avatars.githubusercontent.com/u/16313625?v=4)](https://github.com/eliashaeussler "eliashaeussler (12 commits)")

### Embed Badge

![Health badge](/badges/undkonsorten-meta-tag/health.svg)

```
[![Health](https://phpackages.com/badges/undkonsorten-meta-tag/health.svg)](https://phpackages.com/packages/undkonsorten-meta-tag)
```

###  Alternatives

[fluidtypo3/vhs

This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine.

1954.1M49](/packages/fluidtypo3-vhs)[bk2k/bootstrap-package

Bootstrap Package delivers a full configured frontend theme for TYPO3, based on the Bootstrap CSS Framework.

357891.4k72](/packages/bk2k-bootstrap-package)[mask/mask

Create your own content elements and page templates. Easy to use, even without programming skills because of the comfortable drag and drop user interface. Stored in structured database tables. Style your frontend with Fluid tags. Ideal, if you want to switch from Templavoila.

1391.6M10](/packages/mask-mask)[typo3/cms-fluid

TYPO3 CMS Fluid Integration - Integration of the Fluid templating engine into TYPO3.

1912.0M403](/packages/typo3-cms-fluid)[typo3/cms-fluid-styled-content

TYPO3 CMS Fluid Styled Content - Fluid templates for TYPO3 content elements.

228.8M265](/packages/typo3-cms-fluid-styled-content)[helhum/typoscript-rendering

Can render a TypoScript path by URL, especially useful for Ajax dispatching

68653.7k12](/packages/helhum-typoscript-rendering)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)