Opening /llms.txt successfully does not prove the file exists. Some hosts return the homepage for unknown paths, so the URL works while the expected text file is absent.
Check what was returned
Look at the response body rather than the browser’s address bar alone. A useful guide should contain readable Markdown. If the body starts with your application HTML and script tags, inspect your static-file handling or server routing.
curl -i https://your-site.example/llms.txt
# Check for a text response and the intended Markdown.
# A homepage HTML response is not an llms.txt guide.Publish a real file or text endpoint
Place the guide in the public output your host serves, or create an endpoint that returns the intended text. Ensure it is handled before the general app route. Uploading a file to the wrong source directory may not put it in the production build, so test the deployed address.
Validate the guide’s usefulness
Follow each listed URL and correct stale descriptions. SiteReadyFor.SI’s free generator can prepare a basic draft; the audit checks whether a readable guide and expected outline were found. Passing this check does not demonstrate that an AI provider consumed the file. The format remains a proposal.