# Setting up LLMS.TXT {% hint style="success" %} We recommend creating this as a standard Webflow page, under `/data/llms` . * The folder and page must be published and can not be password-protected. * The page should be excluded from the Sitemap, as it is not needed by search engines. {% endhint %} The LLMS page is a standard Webflow page that you manage in the designer- however its goal is to specify the content that you want in your `/llms.txt` and nothing else.

Hyperflow LLMS converts the page to Markdown, following your content structure; | e.g. HTML | e.g. Markdown | | | -------------------- | ------------- | - | | `

Heading 1

` | `# Heading 1` | | | `

List item

` | `* List item` | | | | | | ## The LLMS.TXT Formal Specification {% hint style="info" %} Hyperflow LLMS gives you full flexibility on the structure and content of your page, however it's important to follow the Formal Specifical for LLMS.TXT page construction. {% endhint %} The `/llms.txt` file is Markdown but follows a specific format; [https://llmstxt.org/#:\~:text=An%20H1%20with,about%20the%20file.](https://llmstxt.org) * An H1 with the name of the project or site. This is the only required section * A blockquote with a short summary of the project, containing key information necessary for understanding the rest of the file * Zero or more markdown sections (e.g. paragraphs, lists, etc) of any type except headings, containing more detailed information about the project and how to interpret the provided files * Zero or more markdown sections delimited by H2 headers, containing “file lists” of URLs where further detail is available * Each “file list” is a markdown list, containing a required markdown hyperlink `[name](url)`, then optionally a `:` and notes about the file. Examples; ## Key Points * Links should be suffixed with `.md` extension. ## Best Practices *No visual styling or artwork are needed, and should be avoided.* For designer convenience, add this ` ``` ### Headings Use Webflow's Heading elements, and arrange them in the correct hierarchical order; e.g. ``` H1 Fuzzy wuzzy was a bear H2 Chapter 1 H3 In the beginning H2 Chapter 2 ``` ### Lists {% hint style="success" %} You can use regular Webflow List and List Item elements, however custom elements are more suitable for use in CMS-driven lists. {% endhint %} We recommend an arrangement like this;

Key points; 1. Custom `

` element 4. Webflow Link element 1. The link can be bound to a CMS link field 2. The text should be bound to the text you want directly represented by the link 5. Custom `` , containing 6. Custom `` with literal `:` ( colon-space ) text sequence 7. Custom `` element 1. Text is a brief description of the link content Or if you want more control over the formatting, you can use Embeds.

### Tables Use an Embed element, with **HTML Table** content in it. Use cases; * Hours of operation * A list of branch locations and addresses * Products, SKUs, Inventory and Pricing {% hint style="success" %} You can also create your tables using a mix of custom elements and collection lists. {% endhint %} ```html

Header 1	Header 2	Header 3
Row 1, Col 1	Row 1, Col 2	Row 1, Col 3
Row 2, Col 1	Row 2, Col 2	Row 2, Col 3

``` Generates the following markdown; ```markdown |Header 1|Header 2|Header 3| |---|---|---| |Row 1, Col 1|Row 1, Col 2|Row 1, Col 3| |Row 2, Col 1|Row 2, Col 2|Row 2, Col 3| ``` {% hint style="warning" %} `` is not supported by the markdown converter. {% endhint %} ## Technical Notes In `llms.txt`, Relative links will be converted to absolute links, using the same path. All links within the site will be suffixed with `.md` This is automatically handled by Hyperflow LLMS. ## Designer CSS {% hint style="success" %} **OPTIONAL.** Copy and paste this into an EMBED in your Webflow LLMS page. \ This will make your LLMS.TXT page consistent and readable with minimal site styling interference. {% endhint %} ```html ``` ## Future Exclude conditionally hidden content