Website

Write an accurate llms.txt and llms-full.txt for your hosted site

Reads your site's pages and real content and drafts a summary file in the llms.txt proposal format, using only facts that appear on the site. Optionally adds the clean text of the main pages as llms-full.txt, publishes after approval and verifies it live.

When to use it

Your site runs on Opus Growth hosting and you want AI assistants to find a single, accurate and current summary of your business.

What you get

An llms.txt (and llms-full.txt if you want it) built only from facts on your site, with the source of every fact shown, written to the site root after your approval and verified to return 200 as text/plain, plus a maintenance note.

Does it change anything in my account?

Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.

Works with

SEO Intelligence

Fill in before sending

[site URL][extra facts, or "none"][yes or no][business name][Page name][today's date]
Write an llms.txt file for my site [site URL] on Opus Growth hosting. Facts about my business that are not on the site but that I confirm are correct: [extra facts, or "none"]. Do I also want llms-full.txt: [yes or no]. Before you start, keep this in mind and tell me too: llms.txt is a proposal published at llmstxt.org. It is meant to help AI assistants understand a site quickly and correctly, but major providers such as Google and OpenAI have not said they use it as a ranking or citation signal. So the goal is a small, accurate file, not a promotional text. 1. Read the current state. Check [site URL]/llms.txt with site_read_url. If a file exists, show it and flag what is out of date. Read the platform's SEO rules with site_seo_guide. 2. Collect the pages. List the HTML pages with site_list_files and read [site URL]/sitemap.xml with site_read_url. Note pages that are in the sitemap but not in the file list, or the other way round. Set aside legal pages, thank-you pages and the 404 page. 3. Read the content. Read the homepage, the service or product pages, about, contact and pricing pages with site_read_url and text=true. If the reply says truncated is true, read again with max_bytes=1000000. For each page write a one-sentence description based only on what that page actually says. 4. Write the draft in the llms.txt format: 1. The first line is the heading `# [business name]`. 2. Below it, a one or two sentence summary starting with `>`: what we do, for whom, where. 3. Then a short paragraph with the core facts: service area, how to get in touch, how we work. Use only facts that are on the site or that I gave above. If prices, opening hours, ratings, customer counts, awards or certificates are not on the site, do not write them. 4. Then sections such as `## Services`, `## FAQ`, `## Company`. Each line follows `- [Page name](full URL): one-sentence description`. Use the canonical URL that returns 200; on this platform directory URLs end with a slash. 5. Put secondary links such as legal pages and the blog last, under `## Optional`. 6. If the site has several languages, give each language its own section and say which URL is in which language. 7. End the file with `Last updated: [today's date]`. 5. If I want llms-full.txt: combine the clean text of the main pages into one file, each page starting with `## Page name` and `Source: full URL`. Remove menus, footers and cookie text. If the file would exceed 500 KB, include only the service, pricing, FAQ and about pages. 6. Check it. Run seo_content_lint on the llms.txt text and fix inflated or AI-sounding phrases. Test every link with site_read_url and max_bytes=0 and remove any that does not return 200. 7. Show a preview. Give me the full file and a short source table showing where each fact came from: fact, source page. Wait for my approval. 8. Publish after approval. Write llms.txt (and llms-full.txt if I asked for it) to the site root with site_write_file. Read both with site_read_url and show that the status is 200 and the content-type is text/plain. Tell me if robots.txt blocks /llms.txt. Do not add llms.txt to the sitemap, because the sitemap is for HTML pages. Finish with a maintenance note: in three points, say which changes (a new service page, a price update, an address change) mean this file must be updated too.

Example result

An example of the output this prompt produces. Its structure comes from the tools' real output; numbers and names are fictional.

Example output (based on a fictional site, not real customer data)

Right now /llms.txt returns 404. The sitemap holds 14 URLs and the file list has 15 HTML pages; the difference is thank-you.html, which is correct because that page should stay out.

The full file:

  1. # Laurel Physio
  2. > A clinic in Brighton offering one-to-one physiotherapy for back, neck and sports injuries.
  3. Appointments are booked by WhatsApp and phone. Sessions last 45 minutes and the first visit includes an assessment.
  4. ## Services
  5. - [Herniated disc physiotherapy](https://laurelphysio.example/services/herniated-disc/): Exercise and manual therapy programme for a herniated disc.
  6. - [Sports injuries](https://laurelphysio.example/services/sports-injuries/): Return to sport after knee, ankle and shoulder injuries.
  7. ## Company
  8. - [About](https://laurelphysio.example/about/): The clinic team and how we work.
  9. - [Contact](https://laurelphysio.example/contact/): Address, phone and WhatsApp link.
  10. ## Optional
  11. - [Privacy notice](https://laurelphysio.example/privacy/)
  12. Last updated: 2026-10-11
FactSource page
Brighton, one-to-one sessions/about/
Sessions last 45 minutes/services/herniated-disc/
Booking by WhatsApp and phone/contact/

Prices and opening hours are not on the site, so they were left out. seo_content_lint scored 96 with no flagged phrases. After your approval the file was written; site_read_url returned 200 and text/plain.

Related searches

These prompts work best when your AI assistant is connected to your accounts with Opus Growth.

Connect your accounts free

More prompts

WebsiteChanges after your approvalLive demo

Build an editorial expert site with a guides section and author schema

Has your assistant build an expert's site with a magazine-cover home page, long-form guides and an author profile. Serif typography, Article and Person schema and dated, sourced articles produce a publication people read and AI answers can cite.

When to use itWhen you are a consultant, specialist or one-person knowledge business and want your site to read like a publication that shows your expertise through writing, not like a brochure.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a heritage family business site with a classic look and modern standards

Has your assistant build a site in the spirit of an old label and shop sign for a producer in its third generation, framed and with a paper texture. The look is old, the build is new: mobile first, JavaScript-free, self-hosted fonts, WebP, Product and HowTo schema.

When to use itWhen you sell a craft passed down through generations, such as Turkish delight, olive oil, cheese or copperware, and want a classic look that carries that history without giving up speed or accessibility.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a Swiss-minimal law or accounting firm site with strong trust signals

Has your assistant build a still firm site on a strict grid, with hierarchy carried by a single type family. It puts the trust signals a YMYL field needs on the page: practitioner profiles, a dated and sourced guidance note, wording that respects professional advertising rules, and Person schema.

When to use itWhen a law, accounting or similar professional practice needs a site that looks serious and plain, stays within professional advertising rules and proves its expertise.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a JavaScript-free multi-page corporate site and deliver it at 100

Has your assistant build a still, fast and accessible site for corporate work such as architecture, engineering or consulting. Menu and footer are static HTML, fonts and CSS are self-hosted, and every page is measured before hand-over.

When to use itWhen a corporate business needs a multi-page site where speed and accessibility matter more than decoration, with no animation and no JavaScript.

SEO Intelligence, Search Console