llms-full.txt file
The long form of llms.txt — the site content or documentation as one Markdown file, for tools that will read the whole thing in one go.
/llms-full.txt is the companion of llms.txt. Where llms.txt is a short map with links, the full version contains the content itself — typically the whole documentation or the key pages of the site — merged into a single Markdown file. A tool that wants to answer questions about your product can read it in one request instead of crawling dozens of pages and stripping out navigation, scripts and layout.
The file is most useful for documentation sites, developer tools and products with a lot of reference material. For a small brochure site it adds little, and like llms.txt it is an informal convention: nothing requires it and the report treats a missing file as a plain fact, not as a warning.
How SiteScan checks
The scan requests /llms-full.txt without following redirects. It counts as published when the answer is a 200 with a non-empty body that is not HTML or XML. A soft 404 page or a redirect to the homepage does not count.
How to produce one
Generate it at build time rather than writing it by hand, so it never drifts from the real content: many documentation generators and static-site plugins can emit it. Strip navigation and boilerplate, keep headings and code samples, and serve it as text/plain or text/markdown. More on the topic: AI visibility.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Well-known files”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data