CMS & ecommerce
Sites with a real content layer. WordPress is the one of these we publish into.
- WordPressThe platform we publish into. An SEO plugin serves most of what AI crawlers read; the page itself is the gap.Publishing · live
- ShopifyShopify writes robots.txt, an llms.txt and product schema for you. The missing piece is the page that compares.
- BigCommerceEvery AI crawler may read the store, slowly: a hidden robots.txt group asks 42 of them to wait ten seconds.
Website builders
Hosted builders. You own the content, the platform owns the file system — which decides what is possible at the root of the domain. Webflow is the one of these we publish into.
- WixWix writes robots.txt, structured data and an llms.txt, and lets every AI crawler in. Content is the gap.
- SquarespaceAI crawlers allowed, structured data automatic, and one box in Settings → Crawlers that can turn 26 of them away.
- WebflowClean HTML and every file and field you need. Its 'AI bots' toggle also blocks the crawlers that answer.Publishing · live
- GoDaddy Website BuilderWrites an llms.txt and LocalBusiness markup for you, and gives you no robots.txt or head code at all.
- FramerPre-rendered pages and an open robots.txt, but no structured data, and files only by upload on Pro.
- DudaWrites robots.txt, the sitemap and an llms.txt for every site: built for agencies running many sites.
App, funnel & dev platforms
Code you or an AI builder own, and funnel builders. Nothing is locked, so the question is what the first response holds: some of these send an empty page until JavaScript runs.
- LovableNew apps render on the server; older ones are pre-rendered only for the crawlers Lovable verifies.
- ReplitAgent builds single-page apps, and a single-page app sends a crawler an empty page.
- GitHub PagesStatic files and nothing in the way. The catch is where robots.txt has to live.
- GoHighLevelServer-rendered funnels and a per-domain llms.txt. Schema put in tracking code never reaches a crawler.
FAQ
Questions
- Does the platform change the diagnosis?
- No. The report reads public pages the way any visitor does, so the prompts and the answers are identical whatever the site runs on. The platform decides what happens next — which pages we publish for you, and which are copied in by whoever runs the site.
- Which platforms can you publish to?
- WordPress and Webflow — a self-hosted WordPress or WordPress.com on a paid plan with its hosting features on, and one of a Webflow site's CMS collections: an approved new page goes straight onto the site, and one click takes it back down. A section for a page that already exists, and every page on any other platform, is copied — rich text, HTML or Markdown — and pasted in, and everything else in the report comes as tasks with steps.
- Is a builder like Wix or Squarespace a disadvantage here?
- Less than people expect. Wix and Squarespace both add structured data on their own and let every AI crawler in by default; Wix also writes an llms.txt and has a robots.txt editor, and Squarespace has a box that blocks AI crawlers if you check it. The usual gap on a builder site is not markup — it is that no page answers a comparative buyer question, and that is a writing problem, not a platform one.
- What about sites built by an AI app builder?
- Those are the ones worth checking first. A single-page build serves an almost empty document and paints the content in the browser, and most AI crawlers never run that script. Lovable now renders new apps on the server; most Replit Agent apps still send the empty page. It is invisible unless you look at the raw response.
- Can I still use this if my client is on something not listed?
- Yes. The report does not care. The 13 pages here exist because those are the platforms people ask about, not because anything else is unsupported.
- How current is each platform page?
- Each page carries the date it was checked against the platform's own help pages and against live sites built with it. Platforms change what they expose, and we would rather show a stale date than quietly leave a wrong row in place.
See who the engines recommend instead
The prompts your client loses, who wins them, and the tasks that would change it.