---
title: "Administration"
manual: "AI Content Quality Assistant"
version: "0.2"
permalink: "https://docs.typo3.org/permalink/woit/t3-content-quality:administration@0.2"
source: "Administration/Index.rst"
rendered: "2026-11-05T14:11:53+00:00"
---

# Administration {#administration}

-   [Backend user permissions](https://docs.typo3.org/permalink/woit/t3-content-quality:backend-user-permissions@0.2)
-   [Database tables](https://docs.typo3.org/permalink/woit/t3-content-quality:database-tables@0.2)
-   [Maintenance](https://docs.typo3.org/permalink/woit/t3-content-quality:maintenance@0.2)
-   [API keys](https://docs.typo3.org/permalink/woit/t3-content-quality:api-keys@0.2)
-   [Outgoing HTTP requests](https://docs.typo3.org/permalink/woit/t3-content-quality:outgoing-http-requests@0.2)
-   [Ollama](https://docs.typo3.org/permalink/woit/t3-content-quality:ollama@0.2)
-   [Logging](https://docs.typo3.org/permalink/woit/t3-content-quality:logging@0.2)

## Backend user permissions {#admin-permissions}

### Content Quality module {#admin-permissions-module}

Grant access in **Administration > Backend Users** in the backend
user group, tab **Access Rights**, module
**Content > Content Quality**.

The quality panel in **Content > Layout** is shown to every user who
can open the page module. It does not need the module permission.

### File list metadata button {#admin-permissions-filelist}

The button is only shown for files that are indexed and for which the user
has the `editMeta` permission. Grant it in the backend user group, tab
**Mounts and Workspaces**, **File Operation Permissions**.

### Bulk image metadata (CLI and scheduler) {#admin-filemetadata-command}

The command `t3contentquality:filemetadata:generate` does the same as the
file list metadata button for many images at once. It selects images whose
default-language metadata has an empty **Alternative text** and fills
every empty field: first from embedded EXIF/IPTC data, then
`download_name` from the file name, then alternative text, title,
description and caption via AI vision. Existing values are never
overwritten.

```bash
# list the images that would be processed (no AI requests, no DB writes)
vendor/bin/typo3 t3contentquality:filemetadata:generate --dry-run

# process up to 20 images (default)
vendor/bin/typo3 t3contentquality:filemetadata:generate

# only storage 1, folder /user_upload/, 50 images
vendor/bin/typo3 t3contentquality:filemetadata:generate --storage=1 --folder=/user_upload/ --limit=50
```

| Option | Description |
| --- | --- |
| `--limit`, `-l` | Maximum number of images per run (default 20). Each image costs one AI vision request. |
| `--storage`, `-s` | Only images of this storage uid (default 0 = all storages). |
| `--folder`, `-f` | Only images below this folder identifier. Requires `--storage`. |
| `--dry-run` | Only list the images, without AI requests or database writes. |
| `-v` | Also list skipped files (missing on disk or storage offline). |

Only JPEG, PNG, GIF and WebP files up to 5 MB are selected. Files that are
missing on disk or in an offline storage are skipped and do not count
against `--limit`. The command exits with an error if the AI provider is
not usable or if a file throws an exception.

To run it regularly, add a task **Execute console commands** in
**Administration > Scheduler** and choose
`t3contentquality:filemetadata:generate`. The command runs as the
`_cli_` user, so the `editMeta` file permission does not apply.

Recommendations for scheduler tasks:

-   Run `--dry-run` once on the command line to see how many images
    are selected.
-   Keep `--limit` small (for example 20 to 50) and run the task more
    often instead. Every image costs one AI request; with Ollama, each
    image takes several seconds.
-   Images for which the AI returns nothing keep their empty alternative
    text and are selected again in the next run.

### Page permissions {#admin-permissions-fixes}

All actions respect the backend user's web mounts, page permissions,
table permissions and language access:

| Action | Required permission |
| --- | --- |
| See the panel, the module page view and analysis results; analyse a page; check links; AI schema detection | Show page |
| Generate, apply or discard title and meta description fixes; approve or remove the schema | Edit page, and modify permission for the `pages` table |
| Generate, apply or discard ALT text fixes | Edit content on the page, and modify permission for the `sys_file_reference` table |
| All pages overview, batch fixes, CSV export | Only pages the user may show (or edit, for fixes) are included |
| File list metadata button | `editMeta` on the file |

Applied fixes are written with the TYPO3 DataHandler. Changes appear in the
record history, respect workspaces and clear the page cache like a normal
edit. For a translated page, the change is written to the translation.

## Database tables {#admin-database}

### tx_t3contentquality_result {#admin-database-result}

The latest analysis result per page and language. A new analysis replaces
the previous row.

-   **page_uid, language_uid**

    Page and language of the result.

-   **overall_score, accessibility_score, seo_score, readability_score, schema_score**

    Scores from 0 to 100.

-   **issues_json**

    JSON list of issues with `category`, `severity`, `message` and
    `suggestion`.

-   **suggestions_json**

    JSON list of AI suggestions.

-   **metadata_json**

    Page facts collected during the analysis, for example title, meta
    description, headings, Flesch score, link check results and schema
    detection details.

-   **analyzed_at**

    Unix timestamp of the analysis.

-   **model_used, provider_used**

    AI model and provider used.

### tx_t3contentquality_history {#admin-database-history}

One row with the scores of every analysis run. Used for the score trend.
Rows are never deleted automatically.

### tx_t3contentquality_pending_fix {#admin-database-pending}

AI proposals waiting for review. `fix_type` is `title`,
`description` or `alt_text`. For `alt_text`, `target_ref` is the
UID of the `sys_file_reference` record. Rows are deleted when they are
applied or discarded. If the DataHandler rejects a change (for example
missing permissions), the row stays pending.

### tx_t3contentquality_schema {#admin-database-schema}

Approved JSON-LD per page and language (`schema_type`, `jsonld_json`,
`approved`, `approved_at`). Every row with `approved = 1` is added to
the frontend output of its page.

## Maintenance {#admin-maintenance}

Remove the history of old analysis runs, for example everything older than
one year:

```sql
DELETE FROM tx_t3contentquality_history
WHERE analyzed_at < UNIX_TIMESTAMP() - 365 * 86400;
```

Remove all analysis results (pages then show **Not analysed yet.**):

```sql
TRUNCATE tx_t3contentquality_result;
```

> [!WARNING]
> Emptying `tx_t3contentquality_schema` removes the JSON-LD from the
> frontend of all pages immediately.

Pages are only analysed when an editor starts the analysis. There is no
scheduler task or console command for batch analysis in this version.

## API keys {#admin-api-keys}

API keys entered in the extension configuration are stored in plain text in
[`config/system/settings.php`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Configuration/Typo3ConfVars/Index.html#file-project-config-system-settings-php). Set them from environment variables
instead, see [Keep API keys out of version control](https://docs.typo3.org/permalink/woit/t3-content-quality:configuration-api-keys-env@0.2).

Further recommendations:

-   Allow outgoing HTTPS connections only to the provider you use:
    `api.anthropic.com` or `api.openai.com`.
-   Set a spending limit in the provider's dashboard.

## Outgoing HTTP requests {#admin-network}

Besides the AI provider, the extension makes these HTTP requests from the
web server:

-   During every analysis, a `GET` request to the frontend URL of the page
    (timeout 10 seconds) to read the rendered headings. The page must be
    reachable from the server; otherwise the headings are taken from the
    database.
-   When **Check Links** is clicked, `HEAD` requests to up to 30
    links of the page.

The requests use the TYPO3 HTTP client settings in
`$GLOBALS['TYPO3_CONF_VARS']['HTTP']` (proxy, SSL verification).

## Ollama {#admin-ollama}

The extension connects to the Ollama server set in
[ollamaUrl](https://docs.typo3.org/permalink/woit/t3-content-quality:confval-t3cq-ollamaurl@0.2) (default `http://ollama:11434`, the host name
of an `ollama` container in a Docker Compose or DDEV setup).

Before each analysis request, the extension checks whether Ollama is
reachable. If it is not, the AI part is skipped and a warning is logged.

Pull the configured model on the Ollama server:

```bash
ollama pull llama3.2
```

For image descriptions in the file list, pull a model that supports
images:

```bash
ollama pull llava
```

## Logging {#admin-logging}

The extension logs through the TYPO3 logging API. Logger names start with
`Woit.T3ContentQuality`.

| Level | Messages |
| --- | --- |
| error | AI analysis failed, AI image metadata generation failed, AI text generation failed, Batch fix generation failed for page, Internal link suggestion failed |
| warning | AI analysis skipped: Ollama not reachable, AI fix skipped: no API key configured, AI schema detection failed, AI schema detection skipped: Ollama not reachable, Pending fix rejected by DataHandler, Pending fix skipped: no page record for language |
| info | File metadata updated, Image too large for AI vision (both from the file list button and the bulk command) |

By default TYPO3 writes messages of level `warning` and higher to
`var/log/typo3_*.log`. To also log `info` messages of this
extension:

**config/system/additional.php**

```php
$GLOBALS['TYPO3_CONF_VARS']['LOG']['Woit']['T3ContentQuality']['writerConfiguration'] = [
    \Psr\Log\LogLevel::INFO => [
        \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [
            'logFileInfix' => 't3_content_quality',
        ],
    ],
];
```