A TYPO3 content-health report you can rerun any time

• Make a content-health report for our Mustermann Outdoor site that we can rerun any time: empty pages, pages without a meta description or with an overlong or duplicate SEO title, pages set to noindex, hidden or scheduled pages, images without alt text, pages without a German version, and product names in the text that don't match our product pages. One table, most important first. Read only, answer here in the chat.
  One question; save it and ask again to compare

1. Ask once: name the site, the checks you want and how the answer should look. Say that it is read only.
2. The assistant reads the page tree, the languages, every page with its SEO fields and every content element, and asks AI Accessibility for images without alt text.
3. On our demo it finds eleven points. First: the Deals page still sells a TX-6 e-bike, a model with no product page.
4. Then pages without a German version, a dealer page set to noindex by mistake, an empty Events page, images without alt text, missing meta descriptions and a duplicate and an overlong SEO title.
5. It ends with the thresholds it used, such as 60 characters for an SEO title. Keep the question: asked again later, it compares the same way.

Shown in Claude; other MCP assistants work too.

A question changes nothing: the assistant only reads, so there is nothing to put back. To check a finding, open the page in the backend: the Page module shows its content, the SEO tab of the page properties shows the description and Index this page.

AI Foundation with its MCP server switched on, an MCP-capable assistant, and AI Accessibility for the alt text check; AI Foundation is free, AI Accessibility is licensed.

• A report is as good as the question: name the checks and the limits you use (for example 60 characters for an SEO title), and ask for the thresholds in the answer, so the next run compares the same way.
• Rerunning means asking again. Nothing is scheduled and no report is stored in TYPO3; keep the answer if you want to compare later.
• Whether a product name is wrong is a judgement: on our demo the assistant flagged an old model on a sale page and let the same name pass on two pages that refer to it on purpose. Check each finding before you change it.
• The checks read the database fields. What the visitor sees, such as a headline rendered by the template, is not part of this answer; check it on the page.
• The alt text check uses AI Accessibility. The assistant reaches only the tables you enable: extension tables need Table Discovery.
• What your assistant reads through MCP goes to the vendor of that assistant, as with any chat.