Corrections
When we publish something wrong, we fix it and record it here. Each entry states what was wrong, how many pages it affected, and what changed. This is the record itself; the process for reporting an error is on the editorial and corrections policy page.
This record starts on 2026-08-11. Corrections made before that date were not recorded publicly, and we are not reconstructing them from memory, because an invented history would defeat the purpose of keeping one.
-
Severity labels showed a hazard class the issuing agency never assigned
Scope: 7,015 NHTSA vehicle-recall pages, about 8,200 CPSC pages, and 830 USDA FSIS pages
What was wrong: Recall pages presented a severity for every record. Only the FDA and USDA FSIS actually publish a hazard class (Class I/II/III). NHTSA publishes none, so our pipeline inferred one from wording in the consequence text, and CPSC records carried a stored default. On vehicle recalls this produced a "Class I Recall, High Risk" panel stating that the FDA had determined the product posed a probability of serious injury or death, a determination no agency made, from an agency with no role in vehicle recalls. Separately, USDA FSIS Class I recalls, which are genuinely classified, were attributed to the FDA rather than to FSIS.
What it is now: A severity is shown only where the issuing agency published one. NHTSA and CPSC records now read "No agency class" and carry no hazard colour or Class I panel, on both listing pages and individual recall pages. Where a class does exist it is attributed to the agency that assigned it.
If this affected you: If you read a vehicle or consumer-product recall here before 2026-08-11 and took the severity label as an agency judgement, it was not one. The recall itself was real; the severity ranking beside it was ours. Always confirm against the official notice linked on the page.
-
USDA FSIS meat and poultry recalls were listed as covered but held no records
Scope: The USDA FSIS agency page and every meat/poultry listing, from 2026-03-25 to 2026-08-11
What was wrong: The site presented USDA FSIS as one of its covered agencies while its record count was zero. The fetch step had been failing since March, and the loader that would have imported the records was never finished, so a reader looking for a meat or poultry recall found an empty agency rather than an answer or a stated gap.
What it is now: 1,231 FSIS notices are published, covering 2014-01-10 to 2026-08-08, including public health alerts (which FSIS issues when it cannot recall a product) labelled as alerts rather than as recalls.
If this affected you: If you searched this site for a meat or poultry recall between March and August 2026 and found nothing, that absence was our defect, not evidence that no recall existed. Please re-check.
-
Recall data was months out of date across every agency
Scope: The whole archive: 101,704 records before, 104,158 after
What was wrong: The FDA food, drug and device feeds had not been refreshed for 56 days against a 30-day cadence; CPSC for 36 days; and the NHTSA vehicle corpus had been frozen since 2026-03-19 because its refresh job could not reach the API. Recalls issued in that window were missing from the site.
What it is now: All feeds are current: FDA and CPSC to late July and early August 2026, NHTSA to 2026-08-06, USDA FSIS to 2026-08-08, and the freshness check now fails loudly when a source falls behind its published cadence instead of passing silently.
If this affected you: A recall issued between roughly March and August 2026 may not have appeared here when you looked. It should now.
-
Breadcrumb structured data pointed at an invalid address
Scope: Five pages: contact, editorial policy, privacy, disclaimer, research
What was wrong: The machine-readable breadcrumb data on these pages contained a placeholder address rather than a real one. The visible navigation was correct throughout; the defect affected only what search engines read.
What it is now: The breadcrumb data carries real addresses, and a final breadcrumb with no destination is simply omitted rather than given an invented one.
Found something that looks wrong? The reporting process, and what we do with a report, is on the editorial & corrections policy page. Because our pages are generated from the agencies' own datasets, a genuine error usually traces back either to our pipeline, in which case it appears here once fixed, or to the source record itself, in which case we will say so and point at the official notice.