← Home

Reader-path QA log

Noog Weekly publishes slowly on purpose. This page keeps the public status badge readable while showing exactly what was checked before a reader subscribes, nominates a business, advertises, or opens an older profile.

Latest check · September 18, 2026

Core reader paths verified

Today’s product QA confirmed that the public trust path is understandable from the homepage, the detailed QA evidence has a stable URL, and the main reader actions still resolve without dead ends. This run also rechecked the sponsor, nomination, archive, correction, and subscribe-fallback paths so a slow publishing cadence still presents as maintained instead of abandoned.

  • Homepage routes to latest profile, latest issue, archive, nomination form, sponsor fit check, subscribe form, and correction email.
  • Archive, article, and homepage copy distinguish owner profiles from newsletter-format issues.
  • Subscribe fallback language remains visible if JavaScript or the signup API fails.
  • Keyboard skip-to-content path, internal local links, pretty URLs, image assets, canonical URLs, and return-home routes were rechecked across the static site on September 18.
Dated evidence

Recent QA history

These entries preserve what changed on each reliability pass, rather than replacing the public evidence with only the newest stamp.

September 18, 2026 · Public trust paths rechecked Verified homepage, archive, latest profile, latest issue, nomination, sponsor fit, subscribe fallback, correction email, QA log, and footer routes so a new reader can tell the product is maintained even between interviews.
September 17, 2026 · QA history added Rechecked core reader paths and converted this page into a dated history so board, CEO, reader, and sponsor reviews can see freshness over time.
September 16, 2026 · Pretty routes verified Confirmed homepage trust path, stable QA URL, extensionless navigation routes (/guides, /about, /advertise, /badge), article/archive clarity, subscribe fallback language, image assets, canonical URLs, and return-home routes.

Correction and freshness policy

Profiles should stay useful after publication. If something is outdated or wrong, readers can email [email protected]. New profiles are not promised until an interview clears editorial QA.