# Websites In 2026: Why I Moved From WordPress To Astro And Cloudflare *By Joshua Cogar · 2026-09-29 · Web Design* > Websites in 2026 need to serve people and AI agents. See why I moved from WordPress to Astro and Cloudflare, plus how we build for UCP and AI search. - **What This Covers:** Why I stopped building on WordPress, why I now build on Astro and Cloudflare, and how we make sites readable by AI agents and ready for the Universal Commerce Protocol - **Who It's For:** Business owners, e-commerce brands, and marketing teams planning a new website or a rebuild - **Key Takeaway:** In 2026 your website has two audiences, people and AI agents, and the way the site is built decides whether agents can read it, cite it, and buy from it For more than a decade, I built nearly every client site on WordPress. It was the safe default. Then AI search and AI agents showed up, and the requirements for websites in 2026 changed faster than WordPress could keep up. Today I build everything on Astro and Cloudflare, and I haven't looked back. (Of course if a WordPress build is still better for the client in some way, I'll still use WordPress.) The best way to build a website in 2026 is to ship fast, static HTML from a global edge network, and to add a machine-readable layer on top that AI agents can use. That layer includes clean structured data, a markdown version of every page, and published endpoints that tell agents what you sell and how to act on it. A 2026 website is built for two kinds of visitors: humans who read, and agents that read, compare, and increasingly transact. ## Why Did I Stop Building On WordPress? I stopped building on WordPress because the platform's strengths no longer matched what clients need. WordPress was built to make publishing easy for humans. It wasn't built to be fast by default, secure by default, or readable by AI agents by default. Getting those three things on WordPress means stacking plugins, and every plugin adds weight and risk. The security numbers make the case on their own. [Patchstack's State of WordPress Security in 2026](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/) counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, a 42% jump over 2024, and 91% of them were in plugins. WordPress core had only six reported vulnerabilities. The core isn't the problem. The plugin stack every real site depends on is. Speed tells a similar story. In [HTTP Archive's April 2026 Core Web Vitals data](https://www.searchenginejournal.com/core-web-vitals-wordpress-and-astro/575818/), about 49% of WordPress sites passed Core Web Vitals, compared to 67% of Astro sites. That's an 18 point gap on a metric Google uses in rankings. My experience has been even better, with every site I've built on Astro scoring over 90! The market is noticing too. WordPress's share of all websites [fell from 43.2% in December 2025 to 41.9% by late May 2026](https://www.searchenginejournal.com/wordpress-market-share-in-decline/576042/), according to W3Techs data reported by Search Engine Journal. That was the fastest decline in the platform's history. To be fair, WordPress is responding. Version 6.9 shipped an Abilities API, and the WordPress team released an [MCP Adapter](https://developer.wordpress.org/news/2026/02/from-abilities-to-ai-agents-introducing-the-wordpress-mcp-adapter/) that lets AI tools interact with a WordPress site. Those are real steps. They're also add-ons bolted onto a platform that still renders pages on every request. I'd rather start from a foundation that's fast and agent-readable out of the box. I just don't believe their updates went far enough. ## What Is Astro, And Why Did Cloudflare Buy It? Astro is an open-source web framework that builds websites into static HTML ahead of time and ships almost no JavaScript to the browser. When someone visits the page, the server doesn't need to run PHP or query a database. The page is already built and waiting, so it loads fast for people and parses cleanly for crawlers. On January 16, 2026, [Cloudflare acquired the team behind Astro](https://www.cloudflare.com/press/press-releases/2026/cloudflare-acquires-astro-to-accelerate-the-future-of-high-performance-web-development/). Astro stays open source, and brands like Unilever, Visa, and NBC News already use it. For me, the acquisition settled any worry about long-term support. The framework I build on is now backed by the company whose network serves the pages. Cloudflare is the other half of the stack. Sites deploy to Cloudflare Workers, which serve pages from data centers around the world. Cloudflare's Workers Paid plan costs $5 per month, and that's what our own site runs on. There's no separate host, caching plugin, or security plugin. The edge network handles speed, SSL, bot protection, and firewall rules in one place. Here's how the two approaches compare on the things that matter for a business site in 2026.
Factor Traditional WordPress Astro + Cloudflare
How Pages Are Served Built on each request with PHP and a database Prebuilt static HTML served from the edge
Core Web Vitals Pass Rate (April 2026) About 49% About 67%
Main Security Risk Plugins (91% of 2025 vulnerabilities) Very small attack surface with no public database or admin
Hosting Cost Hosting plan plus premium plugin renewals $5 per month on Cloudflare Workers Paid
AI Agent Readability Requires plugins and custom work Built in: markdown twins, one schema graph, agent endpoints
Universal Commerce Protocol Not native Discovery manifest and catalog endpoints built to spec
Content Editing Familiar WordPress admin Markdown files, a Git-based CMS, or headless WordPress
## What Does An Agent-Ready Website Actually Look Like? An agent-ready website is one that an AI system can read, understand, and act on without guessing. Most sites still hand AI crawlers the same heavy HTML they send to browsers, full of navigation, scripts, and layout code. Agents have to dig through all of that to find the facts. We build the opposite way. When we rebuilt seomarketingadvisors.com on Astro, we built a machine-readable layer into every template from day one. Retrofitting it later means touching every page, so it has to be part of the foundation. #### One Structured Data Graph Every page carries a single, connected JSON-LD graph instead of scattered schema snippets. The organization, services, prices, people, and pages all reference each other by ID. An AI system reading any page sees how that page fits into the whole business. #### Markdown Twins Served At The Edge Each key page has a clean markdown version. Our site has 66 pages and 45 markdown twins. A Cloudflare Worker detects AI crawlers such as GPTBot, ClaudeBot, PerplexityBot, and OAI-SearchBot and serves them the markdown instead of the HTML. It also answers any request that sends an `Accept: text/markdown` header. Cloudflare's own testing of its [Markdown for Agents](https://searchengineland.com/cloudflare-markdown-for-agents-469246) feature found markdown cuts token usage by about 80% compared to HTML. Fewer tokens means an agent can read more of your content within the same budget. If you make it easy for your site to be read, that could give you an edge if an LLM is deciding to include your site, or a competitor. #### Published Agent Endpoints We publish an `agents.json` file that describes what the business does and what actions an agent can take, and an `openapi.yaml` file that documents our real API endpoints. We also add a `Link` header that points agents to these resources. This tells an agent where to look and what it's allowed to do. The result shows up in audits. After launch, our site scored 97 for Performance and 100 for Accessibility, Best Practices, and SEO on Google PageSpeed Insights mobile. It also passed all three of Lighthouse's agentic browsing checks. Before the rebuild, our WordPress homepage scored 41 for Performance on mobile, with a 7.4 second Largest Contentful Paint. The same business on Astro and Cloudflare scores 97. ![Mobile PageSpeed scores for seomarketingadvisors.com. WordPress in April 2026: Performance 41, Accessibility 88, Best Practices 69, SEO 69. Astro and Cloudflare in July 2026: Performance 97, Accessibility 100, Best Practices 100, SEO 100.](../../assets/blog/websites-in-2026/pagespeed-wordpress-vs-astro.png) ## How Do You Build A Website For The Universal Commerce Protocol? The Universal Commerce Protocol (UCP) is an open standard that gives AI agents a common way to find a business, read what it sells, and complete a purchase for a shopper. Google [announced UCP on January 11, 2026](https://www.semrush.com/blog/universal-commerce-protocol/) at the National Retail Federation conference, built with Shopify, Etsy, Wayfair, Target, and Walmart. Here's why it matters for every website. Google is already bringing [UCP-powered checkout into AI Mode in Search and the Gemini app](https://business.google.com/us/accelerate/announcements/universal-commerce-protocol-powered-features-on-google/), so shoppers can buy while they research. More and more, the first visitor to your website won't be a person. It will be an agent comparing you against your competitors for someone who asked it to find the best option. If your site can't tell that agent who you are, what you offer, and what it costs, you're left out of the answer (or the sale). The agent doesn't bounce like a human would. It just picks a business it can understand. For websites in 2026 and beyond, being readable by agents is becoming as basic as being mobile-friendly was a decade ago. ![Being readable by AI agents is becoming as basic as being mobile-friendly was a decade ago. 2015: mobile-friendly websites were rewarded by Google's mobile update. 2026: agent-readable websites, as AI agents search, compare, and buy for shoppers.](../../assets/blog/websites-in-2026/agent-readable-is-the-new-mobile-friendly.png) We build our sites to that spec and publish a UCP discovery manifest at `/.well-known/ucp` and support catalog search, so an agent can find services or products and read accurate, current details and prices. Checkout can still run through existing systems. As agentic checkout support matures, the foundation is already in place. Why build this now? AI crawlers are already visiting. [Cloudflare Radar data from July 2026](https://seomator.com/blog/ai-crawler-report) showed ClaudeBot and GPTBot together making up about a quarter of AI bot traffic on the network. Agents are reading the web today. Buying through it is the next step, and a site that can't be read by an agent won't be chosen by one. This is the future, and it's closer than many businesses realize. ## What Is Headless WordPress, And When Does It Make Sense? A [headless CMS](https://en.wikipedia.org/wiki/Headless_content_management_system) separates the back end, where content and products are managed, from the front end that visitors see. In a headless WordPress setup, WordPress keeps doing what it's good at, managing a store and its content. A faster framework like Astro handles everything the public sees. This is the right choice when a business can't simply walk away from WordPress. That's the situation we're in with our client, Prosperous Soul, the faith-based financial education brand led by Stephen K. De Silva. Their site runs a WooCommerce store, paid memberships, subscriptions, and years of content. Moving all of that to a new platform would be risky and expensive. So we kept WooCommerce as the back end and rebuilt every public page as static Astro on Cloudflare. The difference is dramatic. The old WordPress site scored 38 for Lighthouse performance. The Astro front end scores 99. We're closing in on launch now, and the migration work is what I'm proudest of. We audited 1,037 old URLs from sitemaps, the WordPress REST API, Wayback Machine history, and WordPress system paths. 1,026 of them resolve in a single hop on the new build, so years of search equity carry over. The headless build also gets the full agent layer. Prosperous Soul publishes a UCP manifest with real catalog search, lookup, and product endpoints. It also has a Google Merchant product feed, markdown twins with a rate limiter for AI agents, and the same `agents.json` and `openapi.yaml` files as our own site. Because public page views never touch WordPress, the plugin attack surface shrinks to the store and account paths only. Here's how I decide between the two approaches for a client: - **Go Fully Static On Astro:** Service businesses, agencies, professional firms, and content sites where the main job is to inform, rank, get cited, and capture leads - **Go Headless WordPress With An Astro Front End:** Businesses with an established WooCommerce store, memberships, or subscriptions, where the back end works and the front end is the bottleneck - **There Are Other Options:** The website requirements determine the "how" to accommodate the functionality and business needs. ## What Has It Been Like Since Switching? Switching has made my work simpler, and the sites perform better. Before, a big part of every WordPress project was maintenance: plugin updates, conflicts, security patches, caching tweaks, and hosting tickets. Now the sites are static files on a global network. There's no database to break into and no plugin update to test on a Friday afternoon. It also changed how I think about [website design](/services/website-design/). The design still has to win over humans, but every page is also a data source for agents. So we write content as clear, standalone sections. We keep captions and key facts as real HTML text instead of baking them into images. We put prices and specifics right on the page. These habits help people and machines at the same time. The honest tradeoff is editing. WordPress gives non-technical users a familiar dashboard. A static Astro site usually means content lives in files, managed through a Git-based CMS or by us. For clients who need to edit every day, headless WordPress keeps the dashboard they know. For most service businesses that update a few times a month, the speed, security, and AI visibility are worth it. Astro does have some CMS options, including EmDash, Sanity, etc. So if it makes sense for a client to still have a CMS, but they don't want WordPress, we can still make that happen. If you're planning a new site or wondering whether your current one can be read by AI agents, we'd love to talk. You can run our free [AI Readiness Tool](/ai-readiness-tool/) to see where your site stands. Or book a [Free Marketing Consultation](https://api.leadconnectorhq.com/widget/bookings/30-minute-marketing-consult) and we'll show you what it would take to make your website ready for both audiences. ## Websites In 2026 FAQs ### Is WordPress still a good choice for a website in 2026? WordPress still works, and it powers about 42% of the web. It's no longer the best default for speed, security, or AI readability, because those require extra plugins, and plugins caused 91% of WordPress vulnerabilities in 2025. For businesses tied to WooCommerce or memberships, headless WordPress with a static front end keeps what works and fixes what doesn't. ### What is the Universal Commerce Protocol? The Universal Commerce Protocol (UCP) is an open standard, announced by Google in January 2026, that lets AI agents discover businesses, search catalogs, and complete purchases. A business supports it by publishing a discovery manifest at `/.well-known/ucp` and exposing capabilities like catalog search and checkout. Shopify, Walmart, Target, Etsy, and Wayfair helped develop it. ### Is Astro good for SEO? Yes. Astro is one of the strongest frameworks for SEO because it ships prebuilt static HTML with almost no JavaScript. In HTTP Archive's April 2026 data, 67% of Astro sites passed Core Web Vitals, compared to about 49% of WordPress sites. Search engines and AI crawlers can read the full content without running scripts. ### What is headless WordPress? Headless WordPress uses WordPress only as a back end for managing content, products, and orders, while a separate framework like Astro builds the pages visitors see. The public site gets faster and more secure, and the team keeps the familiar WordPress dashboard. It works well for sites with an existing WooCommerce store or membership system. ### Do I need an llms.txt file? An llms.txt file is fine to add, but it isn't a growth strategy. [Ahrefs found](https://ahrefs.com/blog/llmstxt-study/) that 97% of llms.txt files got zero requests in May 2026. Put your effort into fast HTML, markdown versions of key pages, clean structured data, and content with specific facts and prices. ### How much does it cost to host an Astro site on Cloudflare? Many small Astro sites can run on Cloudflare's free tier. Cloudflare Workers Paid costs $5 per month and adds higher limits and features for sites that use Workers for things like agent routing, forms, and APIs. That covers hosting, SSL, and edge delivery with no separate caching or security plugins. #### Additional Resources - [How To Optimize For LLM Search](/blog/how-to-optimize-for-llm-search/) - [How AI Is Changing SEO: Rankings to Relevance In 2025](/blog/how-ai-is-changing-seo/) - [Website Design: Best Practices](/blog/website-design-best-practices/) - [What Is A Google Business Profile?](/blog/what-is-a-google-business-profile/) - [Website Design & Development](/services/website-design/) - [Digital Advertising](/services/digital-advertising/) --- Canonical page: https://seomarketingadvisors.com/blog/websites-in-2026/ Site index: https://seomarketingadvisors.com/llms.txt · Agent directory: https://seomarketingadvisors.com/agents.json