Marketer, Agency · 1 min

TYPO3 SEO audit by conversation: descriptions, titles, noindex, canonicals

An SEO check of every page usually means a crawler, an export and a spreadsheet. With TYPO3 MCP you ask once: which descriptions are missing or too long, which titles are duplicate, which pages are noindex, which canonicals point elsewhere. This episode runs that check read-only on 48 pages of our demo install.

The prompt

  • Check the SEO of all pages on our two sites: missing or overlong meta descriptions, missing, duplicate or overlong SEO titles, noindex, and canonicals. List what to fix, page by page. Do not change anything.
    Read-only. The whole audit in one prompt

What does the assistant do?

  1. Ask for the check in one prompt, and add: do not change anything.
  2. The assistant reads five SEO fields of every page: 48 pages on our demo.
  3. It lists the findings page by page: missing and overlong descriptions, duplicate and overlong titles, noindex, canonicals.
  4. It says what to fix first and how.
  5. Fix the pages one by one, or ask for drafts of the missing descriptions to review before anything is saved.

Shown in Claude; other MCP assistants work too.

How do I check it and put it back?

The audit only reads: nothing is written and nothing needs to be put back. When you let the assistant write descriptions, ask for a dry run, keep the batch ID and read each text before it stays.

What do I need?

AI Foundation with its MCP server switched on, and an MCP-capable assistant; AI Foundation is free.

What can the assistant not do for you?

  • The assistant reads the SEO fields; the rendered canonical tag and the H1 are best checked on the page itself.
  • Writing descriptions and titles with AI Assistant needs its licence.
  • Since AI Foundation 2.0, a batch written with records_apply can run as a dry run first and be taken back in full with records_undo. Other writes act at once: read the current value first, check the change on the page, and have the assistant write the old value back if needed.
  • What your assistant reads through MCP goes to the vendor of that assistant, as with any chat.

Questions about this episode

Does the audit change any page?

No. The prompt says not to change anything, and the tools used only read the page records and their content.

Which SEO fields does it check?

Meta description, SEO title, noindex, canonical and the page title, for every page of both sites on our demo.

Do I need a licence for this?

Not for the audit: it uses AI Foundation, which is free and open source. Writing descriptions with the AI Assistant tool needs an AI Assistant licence; records_apply in AI Foundation can write them too.

In this video
Transcript of the video
  1. 0:02One prompt in your own words: check the SEO of every page, and change nothing.
  2. 0:04The connector is AI Universe Demo. Read only. The wait is sped up.
  3. 0:07It read the SEO fields page by page and changed nothing.
  4. 0:09First fix: Find a dealer is set to noindex, probably unintended.
  5. 0:14Now check it in TYPO3.
  6. 0:15The Find a dealer page in the backend: the SEO tab, Index this page is off.
  7. 0:22Claude's finding next to the page it came from: set to noindex.
  8. 0:40English site: visitors can still open the page.
  9. 0:45German site: the same page in German. Nothing was changed.
  10. 0:50131.7 seconds from prompt to audit, instead of checking every page by hand.
  11. 0:52All episodes: t3planet.de/en/blog/typo3-mcp-in-practice/

Sovereign TYPO3 AI

AI Foundation for TYPO3T3AF

The base every extension runs on. Manage providers, prompts, permissions and costs in one place.

Install free