LLMs.txt Checker
Live website test
LLMs.txt Checker
Check whether a website has an accessible llms.txt file. Review its HTTP status, redirects, content type, size, Markdown structure, and common file issues.
- Real server response
- Structure report
- No account required
Enter a website or file URL
Check a live LLMs.txt file
Live check results
Enter a website above to inspect its file response, redirects, format, and resource links.
Checking the live file
Requesting the website and reviewing its response…
Overall result
Check complete
- HTTP status
- —
- Content type
- —
- File size
- —
- Response time
- —
Network and discovery
0 checksFile structure
0 checksRedirect path
0 redirectsLinked resource availability
0 linksRetrieved file
Three simple steps
How to use the LLMs.txt checker
Inspect a public file without manually opening developer tools or reading response headers.
- 1
Enter the website
Paste a domain or an exact URL. A plain domain is automatically checked at its root
/llms.txtpath. - 2
Run the live check
The server follows safe redirects, retrieves the file, records response details, and returns its text.
- 3
Review the report
Inspect discovery, HTTP, content-type, structure, duplicate-link, and optional resource-availability results.
Technical checks
What the live checker reviews
The report combines the website response with a practical structural review of the retrieved Markdown file.
File discovery
Builds the expected root URL when a domain is entered and confirms the final location reached.
HTTP response
Reports the final status code, redirect chain, response time, and whether the file is publicly retrievable.
Content type
Checks whether the server returns plain text or Markdown rather than an HTML error or rendered webpage.
Core structure
Looks for the required H1 plus the recommended summary and H2 resource sections.
Resource syntax
Counts Markdown resource links and flags malformed, duplicate, relative, or unsafe URLs.
Linked pages
Optionally tests a small sample of linked resources while limiting request volume and execution time.
Understand the result
What makes a live file accessible?
A usable file should normally return a successful response, expose readable text, and avoid redirecting visitors to a login page, challenge screen, or HTML error document.
- A stable public URL, commonly
/llms.txt - An HTTP 200 response after any intentional redirect
- A text-oriented content type
- Readable Markdown with one H1
- Absolute resource URLs that visitors can open
Responsible requests
How the checker processes a URL
Your browser sends the entered public URL to this website’s WordPress REST endpoint. The server retrieves a capped amount of text, follows a limited number of safe redirects, and returns the report to your browser.
Private, local, reserved, and unsafe network destinations are rejected. Requests are rate-limited and briefly cached to reduce repeated load on other websites.
Continue your workflow
Related LLMs.txt tools and guides
Common questions
LLMs.txt checker FAQs
Practical answers about live file discovery, server responses, privacy, and limitations.
What does an LLMs.txt checker do?
It requests a public website’s file, records the HTTP response and redirects, reviews the returned content type, and checks the file’s basic Markdown structure and resource links.
What URL does the checker test?
When you enter a plain domain, the tool checks the root /llms.txt path. When you enter an exact URL ending in llms.txt, it checks that location instead.
Why does my file return an HTML content type?
The URL may be returning an error page, security challenge, login screen, WordPress template, or hosting fallback instead of the raw text file. Open the final URL and review the server configuration.
Are redirects allowed for LLMs.txt?
A redirect can still lead to a readable file, but a stable direct URL is simpler. The checker records each redirect and warns about long chains or a final URL that no longer ends in llms.txt.
Does the checker test every linked page?
No. Link checking is optional and intentionally limited to the first five unique HTTP or HTTPS resources to control request time and server load.
Does this tool save the checked file?
The report is briefly cached to reduce repeated requests, but the tool does not publish or modify the remote file. Site operators should describe operational logging in their privacy policy.
Why are private or local URLs blocked?
Blocking localhost, private IP ranges, and reserved network destinations prevents the public checker from being used to request internal services or devices.
Does a passing result improve Google rankings?
No ranking benefit is promised. A passing result only means the file was reachable and passed this tool’s technical checks at the time of the request.
Check before sharing
Confirm that your LLMs.txt file is live
Review the real response, catch configuration problems, and copy a technical report for your next update.