Guides and reviews for people who run small UK firmsNewsletterHow we reviewAbout us
Advertisement

Home › AI for small firms › Putting it to work

Putting it to work

Free llms.txt generators and alternatives: what should you use?

Compare a manual file, native Shopify output and free generators by maintenance and validation, without promising that a valid file will increase AI citations.

Choose an llms.txt generator by how it selects links, what you can edit and how you will keep the file current. A small site may need only a short manual file or its platform's native output.

The options below are ordered by the amount of new machinery a business needs to add. This is a documented-function comparison checked on 30 October 2026, not a benchmark of citation gains.

Which alternative needs the least maintenance?

Starting order Option Useful when What you still own
1 Existing native platform output The platform already generates an accurate file Checking the public output after important site changes
2 A short manually maintained file A small site has a few stable authoritative pages Link selection and review dates
3 AEO Lookup generator and validator You want an editable draft from the homepage and sitemap Reviewing the draft before publishing
4 llmstxt.info generator or manual builder You want a documented crawler-based or form-based alternative Reviewing selected content and the served file

A different order may suit a documentation site with hundreds of changing pages. The relevant question is who updates the result when the source content changes.

Can I use my platform's native file?

Inspect the domain before installing anything. Current Shopify provides native agent-facing files and supports theme overrides. Our Shopify guide explains the default and the dedicated llms.txt template.

If native output is accurate, another app can create duplicate responsibility without improving the result. If it is incomplete, identify the actual missing information and the supported customisation route.

Do not create a file containing stale price lists merely because a generator can collect them. Stable links to authoritative pages are often easier to review than a copied catalogue that changes daily.

When is a manual file sensible?

The llms.txt proposal describes a concise Markdown guide with background and links. It is a proposal, not a requirement imposed on every website by every assistant.

For a small site, start with the public name, a factual description and a short set of useful destinations. Link to the pages that explain services, important conditions and contact routes. Keep confidential material out of a public file.

For an illustrative UK consultancy with five stable service pages, that can be a short editing task. A hand-written map still needs a named owner and a review when page addresses or services change.

What does the AEO Lookup generator produce?

The AEO Lookup generator reads the homepage and sitemap to draft an editable file. The same page offers validation of an existing live file.

Treat the generated text as a starting draft. Read its description, remove irrelevant links and verify each remaining destination. A sitemap can contain pages that exist without being the most useful pages for a reader.

The documented API and MCP route can support repeatable checks. Automation helps with consistency; a person still needs to decide whether the public guidance is accurate and worth maintaining.

How does llmstxt.info differ?

llmstxt.info's tools page describes a free generator that crawls a site, a manual builder, a full-text variant and a validator. Its documentation says the generator can inspect up to 100 pages.

That provides a useful alternative when the task calls for more source-page extraction or a form-based manual draft. Review the current page cap and output before selecting it. A larger crawl is not automatically a better map.

This comparison does not endorse claims that a format score proves all major assistants will read the result. The capability being compared is drafting or checking a public file.

What should I verify before publishing?

  1. Read the generated description for factual errors.
  2. Remove private, obsolete or irrelevant destinations.
  3. Open every retained link and check its final URL.
  4. Publish through the platform's supported route.
  5. Confirm that the live path returns the expected text rather than an HTML fallback page.
  6. Record who reviews the file after future changes.

The crawler-access guide covers a separate question: whether a service can reach the public content at all. A descriptive file does not override an access restriction.

How will I know whether it changed visibility?

Keep the file's technical result separate from actual citations. A valid file with working links is an observable maintenance outcome. A citation is an answer linking to the site, and a referral is a recorded visit.

Use the measurement guide to track those outcomes without claiming that every later change was caused by llms.txt. If the site has unclear services, missing public facts or broken access, resolve those issues alongside any file work.

Which questions come up most often?

Do I need to pay for an llms.txt generator?

No purchase is inherently required. A manual file, supported native output and free generators are available options.

Does a larger generated file guarantee better results?

No. Useful selection, accurate descriptions and current working links matter more than adding every available page.

Does validation prove ChatGPT will cite the site?

Validation checks the file and its format. Actual citations and visits require separate measurement.

Where this comes from: llmstxt.org current proposal; Shopify native template reference; llmstxt.info official tools documentation; AEO Lookup generator source; checked 30 October 2026. Worked examples are illustrative unless a source is named.

Put a number on it: AI readiness score: is your business ready for AI? · How many hours can AI save me each week? Free, in your browser, no sign-up.

AL

AEO Lookup editorial team

We write practical guides for people who run small UK firms, and we check every fact against its source on the date shown. Read how we review, or tell us if something has changed.

More on AI for small firms