WordPress migration to an AI-native website in Frankfurt Rhine-Main

Why companies leave WordPress

Search now runs through AI assistants as well as through Google, and both reward pages that load fast and carry their text in the HTML. Many WordPress sites fail on both counts, and each plugin adds to the security risk.

Security is the first problem. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42 percent more than in 2024. 91 percent of them were in plugins, and 46 percent were not fixed when they became public. For the flaws attackers targeted most, the first exploit came after a median of five hours (Patchstack, February 2026). A company on WordPress has to install updates within hours and depends on each plugin vendor to ship a fix in time. In a survey of 319 WordPress owners and professionals, 67.7 percent had already had a security incident (Melapress, September 2026).

Plugins also bring legal risk in Germany. In January 2022 the Munich Regional Court awarded a visitor damages because a website loaded Google Fonts from Google’s servers without consent (LG München I, 3 O 17493/20). Themes and plugins often load fonts and scripts from third-party servers in this way.

Speed is the second problem. In 2025, 45 percent of WordPress sites passed Google’s Core Web Vitals on mobile. TYPO3 sites reached 79 percent and Duda sites 85 percent (Web Almanac 2025). Google states that good Core Web Vitals match what its ranking systems reward.

AI search is the third. The crawlers of OpenAI, Anthropic and Perplexity do not run JavaScript (Vercel, December 2024). Text that a page builder or a widget inserts with JavaScript stays invisible to them, and an assistant cannot quote it.

An old installation stays a risk after the switch if it remains reachable. When this site moved, the old WordPress of the German domain went offline on the same day.

What an AI-native website is

An AI-native website is a site that AI assistants and agents can read as easily as people can. ChatGPT, Perplexity and Google’s AI Overviews answer questions with quotes from web pages, and they can only quote text they can parse. This site has the following parts, and a migration gives yours the same:

• The text is in the HTML when the page arrives. No script has to run before a reader or a crawler sees it.
• A file at /llms.txt lists the pages with one line each and is rebuilt with each release.
• Structured data in JSON-LD states who runs the site, which service a page offers and where the page sits in the site.
• An AI agent can change the content: through files under version control on a static site, or through an interface to the database on Symfony or Node.js.
• On this site a hook checks new copy against a writing guide before it is saved.

Where the inquiries come from

From 2011 to 2016 I programmed order funnels and payment connections for online shops of Lidl and REWE at Valentins and worked on their conversion rates. A company website converts on a smaller scale, with the same logic. Each page has one next step, visible in the first screen. Between the visitor and the contact stand as few fields as possible.

On a migrated site this means a page per service that answers the questions a prospect has, and a call booking or a message at the top and at the end. Details: Experienced in conversion optimization.

The WordPress migration checklist

The list I work through on a migration. You can use it for your own.

1. Collect the old addresses: pages, posts, categories, tags, author archives and attachment pages, from the sitemap and from the server logs.
2. Map each old address to a new page, or mark it as permanently removed.
3. Forward the picture files too. WordPress stores each upload in several sizes, such as -300x200, and other sites link to them.
4. Keep the file names and the alt texts of the pictures. They carry search terms.
5. Move posts and pages into the new system with their headings, captions and links.
6. Compare old and new pages by script: links, pictures and paragraphs.
7. Test each forwarding with and without the slash at the end.
8. Check each new page for its title, description, canonical link and preview picture.
9. Switch the domain, then run the forwarding list against the live site.
10. Take the old WordPress offline, and delete its database after a date you set.

Who I am

I am Michael Wutzke, an IT architect for data platforms in Frankfurt with more than twenty years in IT and media. I hold the AWS Solutions Architect Associate certification and teach at the Claude Hacker House. I build software with Claude and Codex, and I migrated this site with Claude as coding agent. I am also interested in open-source AI models that a company runs on its own servers. Details: Background.