Open Orbit

Answer-engine files

Understand how an app's llms.txt file directs answer engines to its pages, and why readable content does not guarantee a citation.

Orbit provides /llms.txt to help answer engines find your app's pages in plain text.

A text entry point for your app

An answer engine uses information from other pages to answer a person's question. A readable list of pages helps the engine find relevant content.

Orbit's product overview identifies /llms.txt as the app's plain-text page resource for answer engines. It has a different job from the page itself. The page serves the visitor, while the file helps software find the content.

You can see a working example in Orbit Docs' llms.txt. The file starts with the documentation name and a short description. Its Pages section lists page titles, links, and descriptions. It also has sections for languages and developer resources.

Those sections describe the Docs example. They are not a required format for every Orbit app.

Give each page a clear answer

Consider a repair business with a public page about the repairs it offers. The business is an example, not a built-in Orbit template.

A title such as “Bicycle repair services” tells a reader more than “Welcome.” A description that names brake repairs and tyre replacement gives the reader a reason to open the page.

The page itself must supply those details. A useful title and description cannot replace the service information a customer needs.

Server-rendered pages explains how crawlers read the page content. Server rendering and a text list of pages support different parts of discovery.

Check the file and its destination pages

For an app at https://example.com, the file address is https://example.com/llms.txt. Replace the example domain with your app's address.

Open that address to inspect what the app supplies. Follow a page link and compare the page with its title and description. For the repair business, the linked page should state which repairs the business offers.

If the file does not load, do not treat its presence as confirmed. If a link opens the wrong page, record the file address and the incorrect destination before you request a fix.

Discovery is not a promise of a citation

A readable file does not guarantee that an answer engine reads it, uses a linked page, or cites your app. Check the file and the page content as separate results from any citation you hope to receive.

Use Review an app before launch to check the app's main task and access rules. A public text file does not replace tests for private pages or customer records.