Marketer, Agency · 1 min

TYPO3 redirects in bulk: audit, fix and import in one batch

Before a relaunch, old links pile up: redirect chains, temporary 302 redirects that should be permanent, targets that no longer exist, and a list of new links from the agency. In Redirect Management that means opening one redirect after another. With TYPO3 MCP you ask your AI assistant once and get an audit and one batch of fixes.

The prompt

  • We're cleaning up the redirects on our Mustermann Outdoor site. Please check every redirect: which ones end in a 404, run through another redirect first, are switched off, or are temporary although the move is permanent? Then fix the chain and the temporary one, and add these old links from our agency's list: /tents-2025 to the Tents page, /storm-jacket to the Storm Shell Jacket page, /warranty-info to the Warranty page. Do it as one batch with a dry run first.
    An audit, a dry run, then one batch: two redirects corrected, three new 301 redirects

What does the assistant do?

  1. Ask once: name the site, the problems to look for, the fixes you want and the new links. Ask for a dry run first.
  2. The assistant reads every redirect and the page tree, and checks whether file targets exist.
  3. It tests the whole batch as a dry run, then writes it and gives you the batch ID. On our demo that fixed one chain, turned one 302 into a 301 and added three new 301 redirects.
  4. It leaves what needs a decision to you: a link to a missing catalogue PDF and a switched-off redirect. It also named a redirect that applies to every site on the install.
  5. Check the result in Redirect Management and follow two old links on the website.

Shown in Claude; other MCP assistants work too.

How do I check it and put it back?

Keep the batch ID. records_undo with that ID, after a dry run of the undo, puts both changed redirects back and removes the three new ones in one step. Redirects act live: a draft workspace does not hold them back.

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?

  • Redirects act live: a draft workspace does not hold them back, so the dry run and the batch ID are what let you check and take a change back.
  • The assistant checks targets it can see in TYPO3, pages and files. It does not call external target URLs.
  • A redirect with no site attached applies to every site on the install. On our demo the assistant found one, named it and left it alone.
  • The assistant reaches only the tables you enable: extension tables such as news need Table Discovery.
  • What your assistant reads through MCP goes to the vendor of that assistant, as with any chat.

Questions about this episode

What does this video show?

One request in Claude on our demo install: audit every redirect of the Mustermann Outdoor site, fix the chain and the temporary redirect, and add three old links from an agency list, as one batch with a dry run first. Then Redirect Management in the TYPO3 backend, and two old links followed on the website.

Why did it not fix every problem?

Two had no clear right answer: the catalogue PDF is not in fileadmin, and the switched-off winter sale redirect would point at the Jackets page. The assistant asked instead of guessing.

How do I take the change back?

Keep the batch ID. records_undo with that ID, after a dry run of the undo, puts both changed redirects back and removes the three new ones in one step. That is how we reset our demo after the recording.

In this video
Transcript of the video
  1. 0:00MCP in Practice for TYPO3 · Episode 18: TYPO3 redirects in bulk: audit, fix and import in one batch
  2. 0:03One request: audit every Mustermann redirect, fix the chain and the temporary one, and add three old links from a list.
  3. 0:05Claude reads the redirects and the page tree, then runs the whole batch as a dry run before it writes.
  4. 0:07The chain is fixed: /summer-sale now goes straight to the Spring Sale page.
  5. 0:09The temporary /e-bikes redirect is now a permanent 301.
  6. 0:10Three new 301 redirects from the agency list: Tents, Storm Shell Jacket and Warranty.
  7. 0:12The 404 target and the switched-off redirect are left for you to decide.
  8. 0:14Now check it in TYPO3.
  9. 0:16Redirect Management: /summer-sale points at the Spring Sale page, /e-bikes answers with 301.
  10. 0:28The three new redirects are at the end of the list; the catalogue and winter sale redirects are unchanged.
  11. 0:40On the website, the old link /tents-2025 lands on the Tents page.
  12. 0:45And /summer-sale reaches the Spring Sale page in one hop.
  13. 0:50A redirect audit and fix from one request, instead of opening every redirect in the backend.
  14. 0:52All episodes: t3planet.de/en/blog/typo3-mcp-in-practice/

All episodes