---
title: VG Wort Pro for TYPO3—Report Texts Without the Handwork
url: "https://b13.com/products/vg-wort-pro-for-typo3"
description: Counting pixels, authors, shares and the report itself—managed where the texts already live.
image: "https://b13.com/fileadmin/_processed_/7/4/csm_sharing-ext-VGWortPro-M_2f07b52138.png"
date: 2026-09-17
modified: 2026-09-29
lastUpdated: 2026-09-29
---
# VG Wort Pro for TYPO3—Report Texts Without the Handwork
VG Wort Pro—Report Your Texts From the Backend
================================================
**VG Wort pays authors for texts that are read online—and the publisher too, where the publisher’s share is declared. Getting there takes a counting pixel on the page and a report that says which text those counts belong to, and who wrote it: checked before it goes out, because a sent report cannot be corrected.**
VG Wort Pro keeps the pixels in TYPO3 instead of in a spreadsheet, takes the text from the page as your visitors see it, and sends the report over the METIS interface. What VG Wort already has on file can be read back, so you work from one list.
Get VG Wort Pro [ Read the documentation ](https://b13.com/products/vg-wort-pro-for-typo3/documentation)
The Problem
-------------
A pixel is quick. Everything after it is not.
You order counting pixels in blocks and keep them in a spreadsheet next to the backend. You paste one into a page and note down which page got it. A year later you look up which texts passed the access threshold, copy each one out of the site, paste it into the reporting portal, add the author, check the length, and send.
That works for a handful of texts. At a few hundred pages and more than one author it turns into a week of December—and into mistakes you only notice a year later:
- A page gets **duplicated** to create a similar one, and two texts now carry the same pixel. Both reports are void, not one.
- A page is **translated, moved, or relaunched**, and the address you reported points nowhere.
- The **author** in the system is whoever saved the record last: an editorial assistant, an import, a developer. Not the person the money belongs to.
- The **length** comes from a database field, while your visitors see what the template delivered—teasers, captions, quotes, a sign-up box.
A report that is wrong has to be withdrawn. That is the part worth automating.
How It Works
--------------
**Pixels live in the system, not beside it.** Import the blocks you already own as CSV, or order new ones over the API. VG Wort Pro keeps the pool, assigns from it, and locks an assignment once it is out.
**The text comes from the page, not from the database.** Extraction runs against the frontend as it is actually delivered, with the parts that belong to the template—teasers, captions, related links, calls to action—excluded per site. You see what went into the number before anything is sent.
**The checks run before the report does.** Minimum length, an author that resolves, a pixel that is really in the HTML, a text that is not already registered.
**Then it reports.** Over the METIS interface, from the backend module, with the result coming back into the page record. Reports you made in earlier years can be read back and matched to your pages.
What You Get
--------------
### A Pixel Pool That Hands Out Each Pixel Once
Import by CSV or order over the API. One pixel belongs to one text, permanently, and it stays that way through the everyday operations of a CMS: copying a page, translating it, moving it. A pixel that is out is locked against editing.
### The Length Your Visitors See
Extraction happens on the delivered page, with template parts excluded per site. Read the extracted text and the character count in the backend before the report goes out. Two extractions of the same page give the same number.
###
### Authors as Records, With Card Numbers
Authors are stored with their card numbers and validated against VG Wort before they are used. A text whose author does not resolve is marked as not reportable instead of going out under a plausible, wrong name. Publisher participation is set per page.
### One Text Across Several Pages
A manual or a guide usually is its page tree. The entry page adopts its subpages into one bundle in a single step, in tree order, and the whole thing is reported as one text. Pages that cannot belong to it are left out and counted.
### Reconciliation With What VG Wort Already Has
Read back what is registered, matched to your pages. You end up with one list instead of two, and you see where the two disagree.
### The Deadline, Where You Work
The backend module shows the reporting deadline and what is still open before it. With the dashboard installed you also get a status widget.
### Several Sites, Several Accounts
Multiple site roots with separate VG Wort accounts in one installation, each with its own pool and its own credentials.
Start With the Free Extension
-------------------------------
`b13/vgwort` **is free, open source, and runs on TYPO3 v13 and v14.** It adds the pixel field to pages and delivers the pixel—no cookies, nothing stored about your readers.
**VG Wort Pro takes over where the pixel stops:** the pool, the extraction, the authors, the report, the reconciliation. It builds on the free extension, so nothing you configured has to be redone.
[ Get the free extension on GitHub ](https://github.com/b13/vgwort)
Who This Is For
-----------------
**It earns its price where the work is real:**
A magazine, portal, or knowledge base with **a few hundred texts** and new ones every month
**More than one author**, especially with publisher participation to declare
Someone who answers for the report: **editorial management, a publishing house, a university department**
An **agency** that does this for a client and bills the hours
Pricing
---------
**Licensed per year and per production instance**—one TYPO3 installation, one codebase, one database. Staging, test, and local installations are free.
| | **VG Wort Pro** | **VG Wort Pro for Publishers** |
|---|---|---|
| For | Sites reporting **their own** texts | Reporting for **several authors**, with publisher participation |
| Pixel pool, assignment, extraction, reporting, reconciliation, bundles, deadlines | ✓ | ✓ |
| Author records with card numbers and validation | ✓ | **✓** |
| Several sites with separate VG Wort accounts | ✓ | **✓** |
| | **€490** per year | **€990** per year |
**Which one you need follows from how you report.** One author reporting their own texts is the first licence. As soon as several authors are involved, or the publisher’s share is part of the report, it is the second.
**Why a yearly license.** Thresholds, deadlines, and the reporting format come from VG Wort and change—the 2026 reform is the current example. A yearly license is what keeps the product current with them.
### VG Wort Pro
Sites reporting **their own** texts
Buy Standard — €490.00 / year
### VG Wort Pro for Publishers
Reporting for **several authors**, with publisher participation
Buy Publisher licence — €990.00 / year
Support
---------
**Every license includes** email support, bug fixes, updates for new TYPO3 versions, and security fixes. One inbox, one queue. Requests that stop your operation get pulled forward. You get a ticket reference and can ask for the status at any time.
**Priority—€300 per year per license**. A guaranteed reply within one business day and prioritized bug fixes.
**Enterprise—from €990 per year.** Response times agreed by severity, a defined availability window, an escalation path, and an annual review. Individually contracted.
**What support does not cover:** installing and configuring it in your project, adapting it to your specific case, debugging your own code or environment, data cleanup, and training. We diagnose for up to an hour per request; if the cause turns out to be outside Mail Queue, we tell you what we found and where to look.
**VG Wort Pro runs in your instance**, so there is no uptime to commit to—what we commit to is when we answer.
Security reports go to [**security@b13.com**](mailto:security@b13.com). We read every report and reply with an assessment, and we agree a disclosure date with you before anything is published. If your own disclosure process needs a fixed date, say so in the report and we will agree one.
System Requirements
---------------------
- VG Wort Pro: TYPO3 v14 LTS, PHP 8.2 and above
- VG Wort (free): TYPO3 v13 LTS and v14 LTS, PHP 8.2 and above
- Optional: `typo3/cms-dashboard` for the status widget.
- On your side: A VG Wort account with METIS access
Installation
--------------
**Composer, through the b13 Marketplace—the recommended way.** After purchase your account holds a Composer repository of your own. Two commands, credentials in `auth.json`, and updates arrive like any other package.
```
1
2
```
```
composer config repositories.b13 composer https://b13.com/_api/composer/p//
composer require b13/vgwort-pro
```
FAQ
-----
### We already use the free extension. What changes?
The pixel keeps working exactly as it does. Pro adds the pool, the extraction, the authors, the report, and the reconciliation. Nothing you configured has to be redone.
### Can it read back texts we registered by hand in earlier years?
Yes, for the last three years: VG Wort’s research endpoint returns reports from the **last 36 months**, and those are matched to your pages so you work from one list. Anything older stays unmarked—that is a limit of the interface, not of the sync.
### What happens when we copy a page?
The copy does not take the pixel with it. That is the most common way to void two reports at once, and it is handled.
### Does the counting pixel need consent?
The pixel is an image loaded from VG Wort’s server, and how you treat it is a question for your data protection officer. Our free extension delivers it without cookies.
### How many of our texts will actually earn?
Fewer than your traffic suggests, and the reason is worth knowing before you estimate. VG Wort sets a minimum length and a minimum number of accesses per year—but only **accesses from Germany** count toward that second threshold. A site with solid overall numbers can still land well under it once the rest of the world is taken out. Longer texts clear a lower bar, so a few substantial pieces often earn where many short ones do not.
### We publish in several languages. What gets reported?
One text, one pixel, every URL. The counting pixel is not translated—each language version of a page delivers the same one—so all of them count toward the same text. The report carries the URL of every language version, and the text itself is taken from the German version, because that is what VG Wort pays for and what the character count has to be based on.
The one case where a language is left out is a text bundled across several pages: if one of those pages has no translation, that language is dropped rather than reported as a partial range. Telling VG Wort the whole text is readable under URLs where a chapter is missing would be wrong.
### We work in workspaces. Does that matter?
The backend module always works on live data—what is actually published is what gets reported—and it tells you when you are in a workspace instead of showing you numbers that would not match the report. Bundling several pages into one text is the one operation that expects live pages.
### What happens when the license expires?
Your running installation is unaffected—the code on your server keeps working, and nothing switches itself off. What ends is access to the releases: our Composer repository stops serving you new downloads.
**With this product that matters more than with most.** The rules come from VG Wort, not from us, and they change on a schedule: thresholds, deadlines, the reporting format, and from 2026 the second report type with its ISSN condition. An installation that stops getting updates keeps reporting—against rules that are no longer current.
**One thing to know about your pipeline.** If your deployment runs `composer install` against our repository on every build, that build will fail once the license has lapsed. Your production site keeps running, but your next deploy doesn’t. The code is [GPL-2](https://b13.atlassian.net/browse/GPL-2?atlOrigin=eyJpIjoiYjM0MTA4MzUyYTYxNDVkY2IwMzVjOGQ3ZWQ3NzMwM2QiLCJwIjoianN3LWdpdGxhYlNNLWludCJ9 "Issue in Jira issues").0-or-later, so the copies you already hold remain yours to keep.
And this is why there’s a grace period: if a payment fails, you keep pulling for another 13 days while it gets sorted out. We also remind you twice before the license runs out.
### Is it open source?
The free extension is, and stays that way: `b13/vgwort` is [GPL-2](https://b13.atlassian.net/browse/GPL-2?atlOrigin=eyJpIjoiYjM0MTA4MzUyYTYxNDVkY2IwMzVjOGQ3ZWQ3NzMwM2QiLCJwIjoianN3LWdpdGxhYlNNLWludCJ9 "Issue in Jira issues").0-or-later on GitHub, and it is what delivers the counting pixel. VG Wort Pro is the paid part—also GPL, like every TYPO3 extension, so you can read every line. What you pay for is access to the releases, updates for new TYPO3 versions, security fixes, and support.
### Do we need a license for staging and test systems?
Your production license covers them. Staging, test, integration, and every local installation of the same project are included—only production instances are counted. Set `testMode` on those, and reports go nowhere.
### What counts as one instance?
One TYPO3 installation—one codebase, one database. Everything inside it is covered: any number of sites, languages, and authors. Ten customer sites in one multi-site installation are one instance. Ten separate installations are ten.
[ See pricing ](#c12802) [ Get the free extension ](https://github.com/b13/vgwort)