← Back to the dashboard

How to publish the llms.txt and the FAQ (5.2)

Two things go on the website. Both are plain text, so they work on any platform; Squarespace's steps are below because the site is on Squarespace today ("We will be transferring out of square space", 2026-10-23). After the move, do both again on the new platform.

Where the text is. Each run of cd db && npm run aeo-basics writes a folder out/aeo-basics-<site>-<time>/. The newest one holds:

• llms.txt: the whole file, ready to paste.
• faq-about-us.txt: the 12 questions and answers for the About page.

Always paste from the newest folder: the text is rebuilt from the facts files each run.

1. The llms.txt (about 2 minutes)

An llms.txt is a short summary of the site for AI assistants, at /llms.txt. No engine has said it reads one (evidence.md, grade D); card 5.2 asks for it.

On Squarespace (version 7.1), from Squarespace's help page, checked 2026-10-23:

1. Open the SEO/AI Visibility panel.
2. Click SEO Settings, then the LLMS.txt tab.
3. Paste the whole of llms.txt into the text field.
4. Click Save.

On another platform: publish the file so that https://<your site>/llms.txt shows it as plain text in the browser (not a download, not a web page).

2. The FAQ (about 15 minutes)

1. Open the About us page in the editor.
2. Near the bottom, add a heading "Frequently asked questions".
3. For each question in faq-about-us.txt: add the question as a small heading (Heading 3 or 4), then the answer as a normal paragraph below it. Copy the words exactly; the check looks for them word for word.
4. Save and publish.

The FAQ structured data (the hidden code that labels these as questions and answers) is 3.2's: see how-to-add-structured-data.md. It is built from the same file, so it always matches the text.

3. Check it's live

Run cd db && npm run aeo-basics again. You should see:

• llms.txt: {"pass":1}
• faq on page: {"pass":12}

Anything else prints the reason, for example not on /about-us yet: answer if an answer was changed while pasting.

4. Changing the text

Change the facts files, not the website: db/config/faq-<site>.json for questions, db/config/llms-<site>.json for the summary and page list, db/config/business-<site>.json for contact details. Each answer lists the words on the site that back it up (sources); a number that isn't in those words is refused. Then run the check, and paste the new text.