How The Recall Desk is built
Measured numbers
Counted by the collection, not written by hand. A figure we cannot support is left out rather than shown as zero.
- Pages
- 15,116
- 9th of 24 measured in Legal/Civic, by sitemap URLs
- Page count over time
- 15,101 → 15,116 pages measured, 30 Sep to 25 Oct
- Languages
- English
- Uptime
- 99.99% over 30 days
- From the public status feed
- Deploys
- 15 in the last 30 days
- Last deploy 18 Oct 2026. From the public status feed
- llms.txt
- Published
- llms.txt 4.9 KB · llms-full.txt 141 KB
- Feed
- Published
- Sitemap
- Listed in robots.txt
- Content last updated
- 22 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, 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
- 35 page links
- Markdown links in the site’s llms.txt
- Search
- Search box on the homepage
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.
“The Recall Desk aggregates US product recalls from the FDA, USDA FSIS, CPSC, NHTSA, and EPA and rewrites the official notices into plain English.”
“Every recall is scored 1 to 5 against objective criteria — agency classification, documented injuries or deaths, distribution scope, and hazard type.”
“The full agency notice is one click away on every recall page, and the raw source data — UPC codes, lot numbers, distribution states, establishment numbers — is preserved verbatim so you can verify a recall against the product in front of you.”
“Our LLM rewrites are grounded in the source recall text. We never invent lot numbers, dates, distribution scope, or affected-unit counts. If a fact isn’t in the source, that field is left blank on our page.”
“In October 2026 a review found that 2,889 Class I recalls had been scored below 4. They were corrected, and the Class I floor is now enforced in code after the model returns.”
“Every page shows the agency, the recall number, and the source URL prominently. If our summary ever conflicts with the source notice, the source notice wins.”
“No ads. No affiliate links. No paid placement. No sponsored content. No tracking pixels in alert emails. We don’t rank manufacturers and we don’t link to retailer pages.”
Screenshots
Timeline
15,101 → 15,116 pages measured, 30 Sep to 25 Oct
| Date | Pages |
|---|---|
| 2026-09-30 | 15,101 |
| 2026-10-10 | 15,107 |
| 2026-10-18 | 15,104 |
| 2026-10-25 | 15,116 |
- 30 Sep 202615,101 pages
- 10 Oct 202615,107 pages
- 18 Oct 202615,104 pages
- 25 Oct 202615,116 pages