Measured numbers
Counted by the collection, not written by hand. A figure we cannot support is left out rather than shown as zero.
- Pages
- 42
- 16th of 18 measured in Tech/AI, by sitemap URLs
- Page count over time
- 15 → 42 pages measured, 30 Sep to 25 Oct
- Languages
- English
- Last deploy
- 31 Aug 2026
- From the public status feed
- llms.txt
- Published
- llms.txt 10.5 KB · llms-full.txt 80.2 KB
- Sitemap
- Listed in robots.txt
- Content last updated
- 12 Oct 2026
- As reported by the site itself
Tech and AI search
Read from the live site on 2026-10-23: its homepage, robots.txt and llms.txt. A line we could not read is left out.
- Built with
- Next.js
- Read from the homepage markup
- Structured data
- Organization, WebApplication, WebSite
- schema.org types on the homepage
- AI crawler access
- Allows all 11 major AI crawlers
- From the site’s robots.txt
- llms.txt link depth
- 42 page links
- Markdown links in the site’s llms.txt
How it is built, by role
The same roles apply across the whole collection. Nothing in this block is specific to this site; what the site says about itself is quoted word for word below it.
- 1
Edge network
Visitors reach a site through an edge layer: a content delivery network with a web application firewall in front of it.
- 2
Application host
The edge talks to an application host that serves the site and renders its pages.
- 3
Data
What the pages show comes from a relational database or, for a site pre-rendered at build time, from data files built into its release.
- 4
Scheduled measurement
The collection measures its sites on a schedule: content dates and site health nightly, page counts read from each site’s sitemap weekly. Every reading is kept with its date. A site too large to re-walk is not re-measured, and shows no trend.
- 5
Public status feed
A monitoring panel sends a signed report on uptime, deploys and backups once a day, and the Operations page publishes it. A figure on this page that comes from that report says so.
In the site's own words
Each passage is copied unaltered from a page the site publishes, with the address it was taken from and the date we took it. We add nothing between them.
“Cite Files checks whether AI assistants can reach, read and cite a website, then generates the files it is missing from that site's own published text.”
“Cite Files requests each site as a browser and again as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot, then compares the answers.”
“The full rubric is published at https://citefiles.com/methodology — no score is ever set by a language model.”
“Every line of a generated file traces to text your site already publishes.”
“Where we have no source — your social profiles, your licence, your correction policy — you get a visible TODO, not a confident guess.”
“It runs on our own hardware, including the language models — nothing you scan is sent to a third-party model provider.”
“We do not solve challenges, we do not rotate addresses, and we do not touch anything behind a login.”
“We will tell you what your current settings actually do, which is often not what their owner believes, and leave the decision where it belongs.”
“The address you test, the text you paste and the result are not stored.”
Screenshots
Timeline
15 → 42 pages measured, 30 Sep to 25 Oct
| Date | Pages |
|---|---|
| 2026-09-30 | 15 |
| 2026-10-10 | 21 |
| 2026-10-18 | 42 |
| 2026-10-25 | 42 |
- 30 Sep 202615 pages
- 10 Oct 202621 pages
- 18 Oct 202642 pages
- 25 Oct 202642 pages