Migrating a WordPress Corporate Site to Astro + Cloudflare

What changed

• Delivery platform
  WordPress (dynamic CMS)→ Cloudflare Pages (static CDN)
• Maintenance burden
  Plugin updates & vulnerability response→ near zero after going static
• Attack surface
  Dynamic CMS→ minimized with a serverless origin
• Content operations
  Admin console→ AI edits Markdown directly on Git (AI-native)

Challenge

A corporate site running on WordPress tends to carry an ongoing burden of keeping up with plugin vulnerabilities, patch operations, and server maintenance, with response required every time a critical vulnerability appears. Being a dynamic CMS, its attack surface is also wider. At the same time, the site wanted to strengthen page speed and its readiness for AI search optimization (AIO / GEO) so it would be cited by generative AI. Meanwhile, there was a constraint that none of the existing URL, design, or SEO assets could be lost.

Approach

1. 01 Took inventory of every page, piece of content, and URL on the current site
2. 02 Migrated content to Markdown / structured data (articles, news, cases, recruiting, and more)
3. 03 Reused the current design's CSS and faithfully reproduced each page (URLs fully preserved)
4. 04 Deployed to Cloudflare Pages and connected the custom domain (email left as-is)
5. 05 Implemented the contact form with a Cloudflare Pages Function + Resend
6. 06 Set up structured data, sitemap, robots, and llms.txt to ensure SEO and AIO / GEO

Key success factors

Fully preserving URLs and design

We swapped out only the platform, without losing the existing SEO standing, backlinks, or look and feel.

AI-native content operations

By keeping content as Markdown on Git, generative AI can read and write it directly, making operations easier to automate.

Optimizing speed and AI search (AIO / GEO)

We sped things up with static delivery and, with clean HTML, structured data, and llms.txt, shaped it to be readily cited by generative AI.

Solution

We rebuilt the entire site with Astro (a static site generator) + Content Collections and migrated it to a Cloudflare Pages delivery setup. We reused the current design's CSS as-is to reproduce the look, and preserved the URLs of every page. Content is managed on Git as Markdown / structured data, realizing "AI-native content operations" in which generative AI can read and write it directly. The contact form was made serverless with a Cloudflare Pages Function + Resend. We set up structured data, sitemap, canonical, and llms.txt, and strengthened both page speed through static delivery and AIO / GEO readiness. Email (Google Workspace) was left unchanged.