KnownByLLM

Guide · 9 min read

llms.txt when you can't upload to the root (Wix, Notion Sites, Studio)

The spec wants a file at /llms.txt. Hosted builders do not always give you the root. What each major platform supports as of October 2026, and the fallbacks in order of how well they work.

The llms.txt specification is simple about one thing: the file lives at the root of the site. On a server you control, that is a file upload. On a hosted builder it is whatever the builder allows, which ranges from “generated for you” to “not possible”, and the answer has changed for several platforms in 2026.

This guide checks the current documentation for Wix, Notion Sites, STUDIO, Framer, Webflow, Squarespace, and Shopify, then lays out the fallbacks for a platform with no root access, from a proxy in front of the domain down to a plain page, with an honest note on what each one does and does not achieve. Checked on 17 October 2026.

The 30-second answer: check for native support first, then a proxy, then a redirect, and only then a page

Three of the platforms people ask about most have moved. Wix now generates and serves an llms.txt for eligible sites and lets you edit it in the dashboard. STUDIO added a .txt upload in February 2026. Framer and Webflow accept a static file in site settings on paid plans, and Shopify has served the file for some time. Notion Sites still has no way to put anything at the root, and Squarespace has no native upload either.

For a platform without native support, the fallbacks in order: a proxy layer such as Cloudflare in front of the domain that serves /llms.txt itself and passes everything else through; a redirect from /llms.txt to a file hosted elsewhere, if the platform allows path-level redirects; and a page at a hyphenated path with the content, which is not the spec but is better than nothing for a reader that lands on it.

What each platform supports, as of October 2026

PlatformNative llms.txtWhereNotes
WixYes, generated by WixDashboard: SEO & GEO, Tools and settings, Go to llms.txtNeeds an upgraded site with a custom domain and indexing enabled; editing stops auto-updates; a toggle hides it
ShopifyYes, generated by ShopifyServed automaticallyThe default says little about your store; see the Shopify article
STUDIOYes, upload (since 9 Feb 2026)Settings, General, txt files, AddPaid plans from Mini; 1 MB per file, up to 30 files; robots.txt replaceable
FramerYes, uploadSite Settings, Hosting, FilesPro and Enterprise; TXT and JSON; served at /llms.txt after publishing
WebflowYes, uploadProject settings (custom files)Paid hosting plan; publish to apply
SquarespaceNoNo root uploadProxy or redirect; see the install guide
Notion SitesNoNo file upload beyond imagesCustom domain must be a subdomain; Notion serves every path on it

Two details from the documentation are worth knowing before you start. Wix’s generated file describes the site and documents how agents can reach live content through Wix’s own endpoint; once you edit it, Wix stops updating it, and a reset button restores the default and the updates. STUDIO’s help article lists llms.txt, security.txt, and ads.txt as examples of what the upload is for and says uploaded files are placed automatically by type.

Wix: use the generated file, then decide whether to edit it

  1. In the site dashboard, open SEO & GEO, scroll to Tools and settings, and click Go to llms.txt, then View File.
  2. Read what Wix generated. If it names your business, your main pages, and nothing wrong, leave it alone; it will keep updating as the site changes.
  3. If you need to add a blockquote that says what you do and for whom, or fix a description, use Edit file. Know that this freezes the file: Wix says it stops updating automatically so your changes are preserved. Put a date in the file and a reminder in your calendar.
  4. Reset to Default returns the generated version and resumes updates. The toggle next to Use your llms.txt file hides the file from public view.

One consequence: you cannot upload your own file to the root on Wix, because Wix serves that path. Forum threads of people trying to do so predate the native feature or miss it. Edit the generated file instead.

STUDIO and Framer: upload the file, then publish

On STUDIO, open the project Settings, choose General, scroll to txt files, click Add, and pick the file. The feature is on paid plans from Mini up, with a 1 MB limit per file and up to 30 files. robots.txt is generated on publish and can be replaced through the same section. On Framer, open Site Settings, then Hosting, then Files, upload a TXT, and publish; Framer says the file is then reachable at /llms.txt and that the feature is on Pro and Enterprise plans. Webflow’s custom files work the same way from project settings on a paid hosting plan; the Webflow install guide has the steps.

After publishing, fetch the URL yourself and check the status code and the Content-Type header, not just that a browser shows text. Some uploaders serve .txt with a generic type or without a charset, which a validator will flag.

Notion Sites and Squarespace: the fallbacks, in order

Neither platform lets you put a file at the root. Notion’s site customization covers share preview, theme, favicon, header, navigation, Google Analytics, title and description, and a custom domain, and its domain setup requires a subdomain such as www with the bare domain redirected at your DNS provider. Squarespace controls every URL on your domain. The options:

  1. A proxy in front of the domain. Move DNS to Cloudflare, proxy the host, and add a Worker or rule that answers /llms.txt with your text and passes every other request through to the platform. This is the only fallback that yields a real file at the real root. The Squarespace install guide walks through it. On Notion, the custom-domain verification expects a direct CNAME to Notion’s host, so test on a spare subdomain before moving the live one; we have not verified a proxied setup end to end.
  2. A redirect from /llms.txt. If the platform offers path-level redirects, point /llms.txt at a file hosted elsewhere. Readers that follow redirects get the content; readers that insist on a 200 at the root do not. Notion Sites has no redirect settings, so this is a Squarespace option only.
  3. A text page at /llms-txt. A page with the content, linked from the home page. Not the spec, and most readers will never request it, but an agent that reads your home page can follow the link, and the writing is reusable when you later get a real root.
// Cloudflare Worker sketch: answer /llms.txt, pass the rest through
export default {
  async fetch(request) {
    const url = new URL(request.url);
    if (url.pathname === "/llms.txt") {
      return new Response(LLMS_TXT, {
        headers: { "content-type": "text/plain; charset=utf-8" },
      });
    }
    return fetch(request);
  },
};

What you give up with each fallback

OptionReal file at the rootWho can read itCost
Native supportYesEveryoneA paid plan on some platforms
Proxy in frontYesEveryoneDNS move, a Worker, and the platform must tolerate being proxied
RedirectNo, a 3xxReaders that follow redirectsDepends on the other host's headers
Page at /llms-txtNoReaders that find the linkNothing, and little benefit

Whichever you choose, keep the content the same as what the how-to guide describes: an H1, a blockquote, a few sections of annotated links. The hosting question changes where the file is, not what it says.

Keep the platform question in proportion

The file is read by coding agents, documentation tools, and assistants a person points at your site. Google has said Search does not use it, and OpenAI’s crawler documentation does not mention it; the Google article has the statements. So a platform that cannot serve it costs you a convenience, not your visibility. Make sure the pages themselves are readable as text, which matters to every reader, and treat the root file as the next step when the platform allows it. Check the platform’s help center again every few months: two of the seven above changed within this year.

Check what your platform actually serves

Run the checker on your URL. It fetches /llms.txt and /robots.txt the way a bot does, reports the status code and headers it gets back, and generates a draft you can upload or paste into your platform's editor.

Run the check →

FAQ

My builder has no way to upload a file to the root. What are my options, in order?

First, check whether the platform has added native support since you last looked: Wix, Shopify, STUDIO, Framer, and Webflow all serve the file today, two of them only since 2026. Second, if it has not, put a proxy layer such as Cloudflare in front of the domain and serve /llms.txt from there. Third, a redirect from /llms.txt to a file hosted elsewhere, if the platform allows path-level redirects. Last, a page at a path like /llms-txt with the content, which is not spec-compliant and helps only a reader that happens to find it.

Does Wix support llms.txt?

Yes, as of October 2026. Wix's help center says Wix automatically generates and maintains an llms.txt file, found in the site dashboard under SEO & GEO, Tools and settings. The prerequisites are an upgraded site with a connected custom domain and search engine indexing enabled. You can edit the file, which stops the automatic updates, reset it to the default, or turn it off with a toggle. Wix's developer documentation describes the file as served at the site root and exposes an API to read and update it.

Does Notion Sites support llms.txt?

Not that Notion documents. The site customization settings cover share preview, theme, favicon, header, navigation, Google Analytics, title and description, and a custom domain. There is no file upload beyond images and no mention of robots.txt, sitemaps, or llms.txt. A custom domain must be a subdomain such as www, with the bare domain redirected by your DNS provider, so Notion serves every path on that host.

What about STUDIO?

STUDIO, the Japanese no-code builder, released a .txt upload feature on 9 February 2026. The help article says you can upload .txt files such as llms.txt, security.txt, or ads.txt from Settings, General, txt files, on paid plans from Mini up, with a 1 MB limit per file and up to 30 files. robots.txt is generated automatically on publish and can be replaced the same way.

Is a redirect from /llms.txt to a file on another host good enough?

Sometimes. A reader that follows redirects gets the content; a reader that only accepts a 200 at the root does not, and the file is then served with whatever headers the other host sends. It is better than nothing and worse than the file at the root. If you use it, point at a host that returns text with a UTF-8 charset, and check the result with a validator rather than a browser.

Is it worth moving platforms just for this?

No. The file is a small, cheap improvement for the tools that read it, and Google and OpenAI do not use it for search. If your platform cannot serve it, write the same content into a text page on the site, make sure the pages themselves are readable as text, and revisit the question when you next consider a move for other reasons.

Next steps