The best CMS for AI search: WordPress vs Webflow vs Squarespace vs Framer

Here's the short version. WordPress, Webflow, Squarespace and Framer all pass the one technical test that decides most of AI search: they serve real content in raw HTML, which matters because AI crawlers don't run JavaScript. The genuine differences sit elsewhere - in how much control you get over structured data, how fast the sites actually are in the field, and how much ongoing maintenance each platform quietly signs you up for. The right choice depends on your operating model, not on a feature grid. We'll declare our position up front: we build client sites in Framer, and we'll be just as clear about where Framer is the wrong call.

The technical fact that decides most of this

None of the major AI crawlers execute JavaScript. An analysis of more than 500 million GPTBot requests found no evidence of script execution, and Claude's and Perplexity's crawlers behave the same way; Google's Gemini, which inherits Googlebot's rendering, is the one exception. So a site that assembles its content in the browser can rank fine on Google and still read as an empty shell to ChatGPT, Claude and Perplexity. The content has to exist in the HTML the server sends. All four platforms here pass that test, which is exactly why the comparison has to go deeper.

One infrastructure note before the platforms. Since July 2025, Cloudflare - which sits in front of roughly a fifth of the web - blocks AI crawlers by default for new domains, with further default changes rolling through 2026. Your platform can pass every test and your CDN can still be the thing keeping the engines out. Check your settings.

The seven checks we run

Rendering method: is the content in the raw HTML. Semantic HTML quality. Real-world speed, judged on Google's field data (the Chrome UX Report, or CrUX) rather than vendor claims. Structured data control: can you add the schema types AI and search actually use, such as FAQ and review markup. Control over meta tags and canonicals. Sitemap and robots.txt handling. And AI-crawler access, including whatever your CDN is doing. Everything below is those seven checks applied.

WordPress: the highest ceiling, the heaviest bag

WordPress renders on the server, so content sits in the HTML, and its plugin ecosystem gives you more schema and technical SEO control than anything else in this comparison. That's the ceiling. The bag: in Google's field data, WordPress is the weakest performer of the four - around 49% of WordPress sites passed mobile Core Web Vitals in the May 2026 CrUX dataset - because speed depends entirely on hosting, theme and plugin discipline. It also carries a genuine maintenance and security burden. It still powers about 42% of all websites (W3Techs, May 2026), though that share has been slipping slowly for a year. Choose it when you have technical resource, in-house or on retainer, and content or product ambitions the closed platforms can't hold. It's also the most portable platform here: you own the database and can leave whenever you like.

Webflow: the content engine

Webflow publishes pre-rendered static pages through a global CDN, and it shows in the field data - roughly 69% of Webflow sites passed mobile Core Web Vitals, among the best of this group. Schema isn't automatic, but custom code handles it cleanly, and structural control runs deeper than on Squarespace or Framer. The trade-offs are cost and complexity. Webflow overhauled its pricing in May 2026: the new Premium plan is US$25 a month billed yearly with 20,000 CMS items and 40 collections, and localisation is billed per locale, which stacks quickly - check webflow.com/pricing before committing, because these figures move. The learning curve is real, and many owners end up needing agency support. Choose it when the site is a genuine content engine - a substantial blog, resource library or programmatic structure - and you want that without WordPress maintenance. CMS content exports to CSV; the design layer is less portable.

Squarespace: easy until you hit the ceiling

Squarespace is the easiest of the four for a non-technical owner, renders server-side, and posts respectable field speed, with about 70% of sites passing mobile Core Web Vitals. The ceiling is structured data and control. It auto-generates only basic schema, there's no native way to add FAQ, how-to or review markup - the types most relevant to AI answers - and there's no plugin ecosystem to fill the gap. The workaround is manual code injection, which needs the Business plan for per-page control and breaks if you change templates. You can't fully edit robots.txt, and you can't noindex a single blog post. For a services business planning to compete seriously in search and AI answers, that ceiling is real and you will hit it. As a starting point for a business whose site is a brochure, it's fine.

Framer: fast to polish, honest about the limits

Framer sites are built in React, which would normally be a red flag for AI crawlers - except Framer pre-renders on the server, so the HTML it ships contains the full page content. That's confirmed both in Framer's own engineering documentation and by independent developers who have inspected the output. Sitemaps, redirects and image optimisation are automatic, and the speed from design to polished live site is the fastest here.

Now the honest column. Framer doesn't generate JSON-LD schema automatically - you add it manually through custom code, which supports CMS variables so per-page schema on blog and service pages is workable, or through a third-party tool. robots.txt isn't fully editable, and custom canonicals sit on the Enterprise plan. Framer is also absent from the major independent CrUX datasets, so while its static edge delivery is quick by design, its speed claims aren't independently verified the way the other three platforms' are - we'd rather tell you that than quote the vendor. And there are jobs Framer is the wrong tool for: programmatic SEO at scale, ecommerce beyond a third-party bolt-on, five or more locales at high content velocity, and large relational content libraries. It also carries the highest design lock-in of the four - your content exports, your design doesn't.

Which one for a founder-led business

Match the platform to the operating model. No dev team and the site is a marketing and demand-capture asset: Framer or Squarespace - and if you intend to compete in AI answers, Framer, because Squarespace's schema ceiling is the difference. The site is a content engine with hundreds of structured pages: Webflow. Product surface area, ecommerce, or ambitions the closed platforms can't hold, plus the resource to maintain it: WordPress, or a custom build beyond this comparison. The wrong answer is choosing on familiarity and discovering the ceiling two years in.

Where we've landed

We build client sites in Framer because most of our clients are founder-led services businesses whose website is a marketing asset, not a store or a five-thousand-page library. When one of the disqualifiers above applies - and sometimes it does - we say so and recommend a different platform. The checklist only works if you're willing to fail your own preference against it.

For what to publish once the platform is sorted, see what kind of content AI actually cites (/journal/what-content-ai-actually-cites).

FAQ

Which CMS is best for SEO? All four handle the fundamentals. The differences that matter are schema control, real-world speed and maintenance burden - and the best platform is the one your team will actually run well for years.

Do AI crawlers read JavaScript? No. Analysis of hundreds of millions of crawler requests found no script execution, with Google's Gemini the exception. Content must be in the served HTML.

Is Framer good for AI search? Yes on the fundamentals - it serves pre-rendered HTML and handles sitemaps and redirects automatically. Add schema manually, and check the disqualifiers before committing.

Should we leave WordPress? Not for AI reasons alone. A well-maintained, fast WordPress site with proper schema is as citable as anything here. The question is whether yours is one.

Sources

• Vercel and MERJ - The rise of the AI crawler: vercel.com/blog/the-rise-of-the-ai-crawler

• Google CrUX field data via HTTP Archive - platform Core Web Vitals pass rates (May 2026), as compiled by PageSpeed Matters and WebVitals.tools

• W3Techs - CMS usage statistics (May 2026): w3techs.com

• Webflow - pricing and plan documentation (May 2026): webflow.com/pricing

• PandaCodeGen - Squarespace SEO testing across 40+ sites: pandacodegen.com/blog/is-squarespace-bad-for-seo

• Schema Pilot - Squarespace schema markup guide: schemapilot.app/blog/squarespace-schema-markup

• Framer - engineering blog on traffic-aware pre-rendering: framer.com/blog/dynamic-optimization

• Independent analysis of Framer's rendering (dev.to, reverse-engineering Framer's React runtime)

• INSIDEA - Framer SEO and AEO assessment: insidea.com/blog/seo/is-framer-good-for-seo-and-aeo

• Cloudflare - AI crawler default policy announcements (July 2025 and 2026)