Two agency website builders shipped llms.txt support in 2026. One ships it for every site, on every publish, on every plan. The other gates it to premium eCommerce subscribers only. The structural difference between those two postures decides which platform an agency picks for SMB clients in 2026 — and it does so before the first design decision.
What is the Duda vs Wix llms.txt gap?
Duda auto-generates a complete llms.txt file on every publish, for every site, across every plan tier — Basic at $19 per month through White Label at $149 per month. Wix Studio offers llms.txt management only to premium eCommerce subscribers. For agencies serving SMBs, the structural difference is decisive: Duda ships AI-citation infrastructure by default; Wix ships it as an upsell.
The honest framing matters here. Llms.txt as a retrieval signal is not yet load-bearing — adoption sits at roughly 10.13% across 300,000 sampled domains in early 2026 per SE Ranking, and John Mueller’s public stance remains that no AI system uses llms.txt as a citation input. But the file is the canary. A platform that ships llms.txt by default is a platform that has thought about the rest of the entity-graph stack: schema completeness, freshness signals, server-rendered HTML, sitemap honesty. A platform that gates llms.txt is a platform that gates the surrounding infrastructure too.
What llms.txt actually does in 2026 (the honest answer)
Llms.txt was proposed by Jeremy Howard at Answer.AI on September 3, 2024. The spec lives at llmstxt.org and the AnswerDotAI/llms-txt GitHub repo. There has been no revision in 2026. The format is a markdown file at the site root that summarizes the site’s content for LLM ingestion — the AI equivalent of a sitemap, but human-readable and intent-tagged.
The empirical record on whether it drives citation lift is unflattering. SE Ranking’s early-2026 crawl of 300,000 domains found ~10.13% adoption, skewed toward medium- and low-traffic sites; authoritative publishers are largely not adopting. A Search Engine Land audit cited by Webflow’s own blog found that 8 of 9 sites saw zero traffic change after implementing llms.txt. Google’s John Mueller stated on the record: “No AI system currently uses llms.txt.” Anthropic and OpenAI publish their own llms.txt files at docs.claude.com and platform.openai.com/docs/llms.txt — but that is documentation publishing, not an endorsement of llms.txt as a retrieval signal for the open web.
So why care about which platform ships it? Two reasons. First, future-proofing: if any major engine flips and starts using llms.txt as a hint, the platforms that auto-generate it have a frictionless on-ramp and the platforms that gate or skip it have a migration project. Second — and this is the load-bearing reason — llms.txt support is a leading indicator of the platform’s overall AI-citation posture. If a platform ships llms.txt for everyone, it usually also ships server-rendered schema, an editable robots.txt, and a fast default theme. If a platform paywalls llms.txt, the rest of the infrastructure tends to be paywalled too. The file is the tell.
Why Duda ships llms.txt for everyone and Wix doesn’t
Duda’s product update — Duda is Prepping Your Sites for the Future of AI Search — confirms that llms.txt is auto-generated on every publish for every Duda site, across every plan tier (Basic at $19/mo, Team at $29/mo, Agency at $52/mo, White Label at $149/mo). The file regenerates whenever a publish event occurs, so it stays in sync with the live site without manual maintenance. The auto-generated file includes structured data, live URLs, and meta descriptions for every indexed page; drafts and noindex pages are skipped automatically.
Wix’s posture is the opposite. Per the Wix Help Center article Understanding Your Site’s LLMs.txt File, llms.txt management is available only to “premium eCommerce users” — gated to a paid SKU and to a specific product vertical. The Wix AI Visibility Overview (launched July 2025, in market 2026) tracks ChatGPT, Gemini, Perplexity, and Claude citations and is a genuinely best-in-class native AI tracking tool — but it sits inside the same paywall logic that gates llms.txt itself. AI infrastructure on Wix is a premium SKU.
The two postures reflect two business models. Duda’s customer is the agency reselling to SMBs at the $19 to $52 per month band, and Duda’s product priority is reducing per-site setup work for those agencies. Auto-generating llms.txt is a per-site setup task removed. Wix’s customer is the SMB direct, and Wix’s product priority is feature-gating to drive plan upgrades. Llms.txt is a feature gate.
What’s inside Duda’s auto-generated llms.txt
The structure of Duda’s auto-generated file matches the llmstxt.org spec but goes further than most platform implementations:
- Markdown-formatted summary of the site, including the business name, primary value proposition, and area served (Duda added the Area Served field to the Content Library Business Info panel in 2026 specifically to feed this).
- Live page URLs with meta descriptions for every published page — not just the homepage. This is what Webflow’s manual-upload model does not give you: when you upload a static llms.txt to Webflow, it goes stale the moment you publish a new page. Duda’s regenerates.
- Structured data summary: Duda’s native schema covers LocalBusiness, FAQPage, Product, and Breadcrumb out of the box; the llms.txt file references the schema graph rather than restating it, but the link surface is there for AI engines that follow it.
- Skip rules: drafts, noindex pages, and pages explicitly excluded from the sitemap are not included. This is structurally important because llms.txt that lists a draft URL can leak unpublished content to AI crawlers — a real concern that the manual-upload model on Webflow does not address.
The implementation contrasts with Framer’s well-known files panel, which also supports llms.txt natively but treats the file as user-authored rather than auto-generated. Framer is structurally strong on this — pre-rendered HTML, markdown variants of every page served to AI agents, native well-known files panel — but the llms.txt itself is something the user writes once and updates manually. Duda’s posture is closer to a CMS plugin: the file is a derived artifact of the published site, not a hand-maintained document.
Wix Studio’s llms.txt premium-eCommerce paywall — the math
For an agency calculating which platform to standardize on for SMB clients in 2026, the Wix llms.txt gate has a specific cost. Wix Studio Basic at $19/mo does not include llms.txt management. Studio Core at ~$29/mo does not. Studio Business at ~$36/mo does not. The premium-eCommerce paywall sits well above any of those tiers, and most SMB clients on Wix Studio are not on the eCommerce stack — they are on portfolio, services, or local-business templates.
That means an agency running 30 SMB sites on Wix Studio either pays the premium-eCommerce delta on every site that needs llms.txt, or accepts that 30 of its sites ship without llms.txt while the agency doing the same work on Duda gets it on every site at no incremental cost. At scale, this compounds. Duda’s $52/mo Agency plan and $149/mo White Label plan both include llms.txt for every client site. The same agency footprint on Wix’s premium-eCommerce gate is a meaningfully bigger monthly bill — for a feature that Duda treats as table stakes.
The compounding effect is worse when you add the rest of the schema cap on Wix Studio. Wix caps page-level structured data at 8,000 characters total and 7,000 per entry, and Velo-injected JSON-LD renders client-side only — invisible to ClaudeBot and PerplexityBot, which do not consistently execute JavaScript. So even if you pay for the Wix llms.txt SKU, the schema graph it points to is itself capped and partially invisible. Duda’s server-rendered HTML and native LocalBusiness/FAQPage/Product/Breadcrumb schema do not have the same ceiling.
This is the agency arithmetic for 2026: Duda ships AI-citation infrastructure as a default; Wix Studio ships it as a paywalled SKU sitting on top of a capped schema layer. The decision is structural, not preferential.
If llms.txt utility is unproven, why care?
This is the question every honest GEO advisor should answer directly. The 10.13% adoption number, John Mueller’s public denial, and the 8-of-9 zero-traffic-change audit result are real. Llms.txt is not the citation lever. The schema graph is. The freshness mechanic is. The 458-day median age of cited pages is. The platform’s CWV pass rate is. Llms.txt is downstream of those.
But the question of whether to ship llms.txt and the question of whether llms.txt drives citations are different questions. Shipping it is essentially free on a platform that auto-generates it; not shipping it on a paywalled platform is a sunk cost. The decision is asymmetric. If llms.txt utility increases — and the symbolic future-proofing case is plausible because every major LLM lab now publishes one for their own docs — the platforms that auto-generate are positioned. The platforms that gate are not.
More importantly, llms.txt support is a proxy for the rest of the platform’s AI-citation thinking. Duda’s 2026 product roadmap — Full-Stack AI for Web Professionals, the DudaCon 2025 launch, the Area Served field — points in one direction. Wix’s product roadmap — AI Visibility Overview, AI Search Lab content hub — points in the same direction at the strategy layer but contradicts itself at the pricing layer. The pricing layer is what your client experiences.
For the closed-by-default anti-pattern at the other end of the spectrum, GoDaddy ships no editable robots.txt and no custom JSON-LD. For the manual-upload comparison, Webflow has supported llms.txt upload since April 2025 but auto-generation is still on the wishlist. The full 12-platform leaderboard ranks all of these against Duda’s auto-generation default in the platform vs AI citation guide for 2026.
For technical depth on what shipping llms.txt correctly looks like — and why Framer and Duda are the two reference implementations in 2026 — see the honest 10% adoption check on llms.txt utility.
The decision for an agency standardizing in 2026 is not “is llms.txt worth shipping” — the platforms that ship it well make that question moot. The decision is “which platform’s defaults match my AI-citation posture for SMB clients.” Duda’s defaults match. Wix Studio’s, behind the eCommerce paywall, do not.
If your agency runs SMB sites on Wix Studio today and the math above is the math you’re looking at, run the platform check on a sample client site — we’ll show you the schema cap, the LCP penalty, and the migration cost before you make the platform decision.
