Most mainstream builders are fine for AI search, and the platform is rarely what's holding a small business back. WordPress, Webflow, Framer, Wix and Shopify all deliver real HTML and give you robots.txt control. Squarespace serves HTML but only lets you flip checkboxes, and its single AI-crawler toggle blocks some AI search agents along with the training ones. The one setup that does cause trouble is a single-page app rendered in the browser, the default for many hand-built and AI-generated React sites until recently, because most AI crawlers see an empty page.
We rated each platform on four things that decide whether an AI crawler can read you and whether you can steer it. For each claim we link the platform's own documentation where it exists, and we flag the cases where we're relying on someone else's write-up. We couldn't run our own view-source tests from our research environment this quarter, so none of the ratings below come from our own measurement. Anyone can test a live site in a few seconds with the access checker, and we'd suggest you do that for yours before taking our word for any of it.
The ratings
| Platform | Server-rendered HTML | robots.txt control | llms.txt | Schema control | Source notes |
|---|---|---|---|---|---|
| WordPress | Yes, pages render on the server (PHP) | Full: file or SEO plugin | Yes, via Yoast SEO and other plugins | Full, via plugins or theme | Yoast llms.txt |
| Webflow | Yes, published as static HTML | Editable in site settings | Upload under Site settings, SEO (max 100 KB) | Custom code per page | Webflow llms.txt |
| Framer | Yes: "every page is pre-rendered to HTML" | Auto-generated; restrict agents in settings | Yes, plus Markdown versions of pages for agents | Custom code | Framer AI agents |
| Wix | Yes, per Wix: "built on server-side rendering" | Editable (dashboard and API) | Yes (llms.txt API) | Custom structured data | Wix SEO, Wix txt files API |
| Shopify | Yes, Liquid themes render on the server | Editable via robots.txt.liquid |
Via Yoast SEO for Shopify | Theme code and apps | Shopify robots.txt, Yoast for Shopify |
| Squarespace | Yes (widely reported; not stated in Squarespace docs we found) | Checkboxes only; file not editable | Native setting on 7.1 (reported July 2026) | Not documented in the sources we checked | Robots guide, llms.txt guide |
| Browser-rendered SPA (React + Vite) | No: the HTML is an empty shell until JavaScript runs | Full, if you host it yourself | Full | Full, but only visible after JavaScript on many setups | Vercel AI crawler study |
| Lovable | New apps (from May 13, 2026): yes. Older apps: pre-rendered copies served to verified crawlers | Yes | Yes | Yes | Lovable FAQ |
| Custom server-rendered build (Next.js, Astro, TanStack Start) | Yes | Full | Full | Full | Your own code |
Checked October 2026. "Widely reported" means we found the claim in practitioner write-ups but not in the platform's own documentation.
On speed, the fourth thing small businesses ask about: we didn't measure it this quarter, and published builder benchmarks vary too much with the template to be useful. Check your own homepage in Google's PageSpeed Insights, which reports field data from real Chrome users when your site has enough traffic.
Why server-rendered HTML is the one that matters
Google's crawler runs JavaScript, and Google says it can process content in JavaScript "as long as it isn't blocked". Most AI crawlers don't. Vercel and MERJ measured AI crawler traffic across Vercel's network and found that "none of the major AI crawlers currently render JavaScript", naming OpenAI's crawlers, ClaudeBot, Meta-ExternalAgent, Bytespider and PerplexityBot. They fetch the HTML, and if your words only appear after a script runs, they read nothing.
That matters more than it used to. In our Observatory data, 35% of AI fetches on small-business sites were user-triggered: ChatGPT, Claude or Perplexity loading a page live because someone had just asked about the business. If that fetch lands on an empty shell, the assistant answers without you.
All the hosted builders in the table avoid the problem for you. It mostly bites custom React apps and sites generated by AI app builders, which often default to rendering in the browser. Lovable switched new apps to server rendering on May 13, 2026, and serves pre-rendered copies of older apps to verified search engines and AI crawlers, according to its docs. Other app builders vary, so check yours.
Platform notes
WordPress gives you the most control, and the most ways to break it. A "discourage search engines" checkbox left on after launch adds noindex to every page, and some security plugins block unfamiliar bots. Yoast SEO can generate llms.txt for you.
Webflow and Framer both publish pre-rendered HTML and are friendly to AI crawlers out of the box. Framer goes further than most, serving a Markdown copy of each page to agents that request it with an Accept: text/markdown header.
Wix says its sites are server-rendered, and it lets you edit robots.txt and add custom structured data. Its own marketing blog is the main source for the rendering claim, so it's worth a quick check on your live site.
Shopify themes render on the server, and the robots.txt.liquid template lets you add or remove rules for specific crawlers. Shopify's docs warn to compare the rendered output with the default before publishing, which is good advice.
Squarespace is the most limited on control. You can't edit robots.txt directly, only toggle settings, and its "Artificial Intelligence Crawlers" toggle disallows 26 agents, according to a Squarespace designer's guide. That list includes DuckAssistBot and YouBot, which feed AI answers rather than training. If you want to block training but stay in AI search, Squarespace can't do that precisely today.
Custom builds give you full control, and with it the responsibility to render on the server. This site is a server-rendered TanStack Start app hosted on cite-met, which is our own platform, so take that as a disclosure, not a recommendation. Hosts like cite-met, Vercel, Netlify and Cloudflare all run server-rendered frameworks well.
What to do on your platform
- Run your homepage through the access checker. If it reports hundreds of words without JavaScript, rendering isn't your problem.
- Check that AI search crawlers are allowed, and if your platform has a single "block AI" switch, find out exactly which agents it blocks.
- Put your services, area, prices and contact details in plain text on the page, which every platform here supports.
- Add LocalBusiness structured data if your platform allows it. Google says it isn't required for AI features, but it states your facts without ambiguity.
- Only consider moving if you're on a browser-rendered app with no server rendering option. For most small businesses on a mainstream builder, the time is better spent on content.
Questions people ask
Which website builder is best for AI search?
Any platform that delivers your text as server-rendered HTML and lets you edit robots.txt does the job. WordPress, Webflow, Framer, Wix and Shopify all do both. Squarespace serves HTML but doesn't let you edit robots.txt directly.
Can ChatGPT read a React or Lovable website?
Not if the page is rendered in the browser. Vercel's study found none of the major AI crawlers it measured run JavaScript. Lovable says apps created from May 13, 2026 render on the server, and it serves pre-rendered copies of older apps to verified crawlers, including AI crawlers.
Do I need to switch platforms for AI search?
Usually not. Run your homepage through an AI access checker first. If it shows hundreds of words of real text without JavaScript and AI search crawlers are allowed, your platform isn't the problem.