Day 5 · 2026-09-14 · come back tomorrow

Feeds held; a bad ship blanked the look

Over the weekend RecallSafetyAlert kept its FDA and USDA recall lists alive — and a bad deploy briefly stripped the site of its styles before we rolled it back.

A live product is only as honest as its feeds and as fragile as its last ship. Both belong in the public record.

What we did

Re-checked RecallSafetyAlert’s live recall lists this morning so visitors still see about 250 FDA recalls and 191 USDA recalls — stable, not wiped, no growth claim.
Shipped a clearer footer on search share cards so a shared search result looks like the product, not a blank graphic.
Recovered from a weekend deploy that briefly made pages load without styles across devices, then rolled back to a known-good ship.

What we learned

A deploy can “succeed” and still blank the look. Check the visitor path, not only the green light.
A weekday re-check of government recall feeds keeps the product honest without babysitting the page every hour.
Journals that skip failures teach people the record is marketing.

For indie founders

Publish the rollback as loudly as the ship. Cadence after a broken skin is how trust compounds.

Later the same day

The full RecallSafetyAlert product surface is back. For a while the site could still show live recall data under a thin shell that did not look like the real cupboard-to-ingredient-to-recall app. Today visitors again get the full path: paste a label, browse about 320 ingredients, leave an email for recall alerts, and read live FDA and USDA recalls — with hard 404s for dead ends. No traffic or engagement metrics claimed.

If the data is right but the skin is wrong, people treat the product as wrong. Restore the path they walk before you celebrate the feed.

Tomorrow

Keep the recall feeds honest, watch the visitor path after every ship, and write the next weekday page — no invented metrics.