We write the content sections of your llms.txt file — structured summaries of specific parts of your site (a product line, a documentation section) — derived from what’s actually on those pages, formatted for AI crawlers to reference. This is more detailed content authoring than basic llms.txt setup, still grounded entirely in your existing site content.
llms.txt content section authoring
Detailed llms.txt content sections written from what's genuinely on your site.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of which sections of your site need a detailed llms.txt content section written
- Access to the relevant pages so the summary is drawn from what’s actually there
- Confirmation of the existing baseline llms.txt file, since this adds sections to it rather than starting from nothing
This or something else?
| You already have a baseline llms.txt file and want detailed content sections written for specific parts of your site | This fix covers it |
| You don’t have a baseline llms.txt file set up yet at all | Crawler configuration – robots.txt, AI bots, llms.txt, in the Schema & Machine Readability category, the prerequisite step |
| You want the full llms.txt file authored from scratch as one complete piece of work | llms.txt authoring & deployment, in the Schema & Machine Readability category, the broader version of this |
| You want to know what AI content strategy will get your brand mentioned by assistants | Outside what this fix does — that’s a strategic marketing question, not a file content question |
What we do
- Review the specific site sections needing a detailed content summary
- Write structured, accurate content sections derived from what’s genuinely on those pages
- Integrate the new sections into your existing llms.txt file structure
- Verify the file remains correctly formatted after the addition
- Review the written content with you before finalising
- Publish the updated file
What is included
- Detailed llms.txt content sections written for your specified site areas, grounded in existing content
- Correct integration into your existing file structure
- A review with you before finalising
- The updated file published and verified
Not included
- Setting up the baseline llms.txt file, if it doesn’t already exist — a separate, prerequisite fix
- Inventing claims or positioning not reflected in your actual site content
- Guaranteeing any specific AI assistant uses or references the file
- Ongoing updates as the relevant site sections change substantially
Questions about this fix
Is this different from the basic llms.txt setup?
Yes — the basic setup establishes the file and its overall structure; this fix writes more detailed content sections for specific parts of your site, going deeper than a baseline summary, though both stay grounded in your actual content.
Will this help get my products mentioned by AI assistants?
It gives AI crawlers a clearer, more detailed, accurate picture of that section if they access your site; it doesn't influence or guarantee whether any specific assistant chooses to reference or recommend what's described.
Can you make my product line sound more impressive than the page itself does?
No — the content sections need to accurately reflect what's genuinely on the referenced pages, since inflated claims risk being surfaced by an AI system in a way that damages credibility rather than helping it.
How many sections can be added at once?
This scales to cover as many distinct site sections as you specify, though each one needs its own genuine, existing content to draw from.
Do I need to update these sections if the underlying pages change significantly?
Yes, a substantial change to the referenced content would mean the llms.txt section is now stale — updating it to match is a separate, follow-up piece of work.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.