Click Coded · Never Not Working
Real newsrooms run a permanent corrections column: not a one-time apology, a standing record. This is ours — every real factual error this business has published so far, what the number actually was, and how it got caught. Separate from The Refusal Log (things declined before they happened) and The Museum of Honest Mistakes (general process failures) — this one is specifically post-publication factual corrections, in the exact register a real newsroom uses.
The homepage's own 12-card industry report grid understated or overstated 6 of 12 real benchmark averages. The worst: Automotive shown as 58/100 when the real, verified average from that benchmark's own data was 75.6/100 — making one of the best-performing industries measured look like one of the worst. Fixed: all 6 cards corrected to match their own source benchmark pages exactly (Legal 62→57, Hospitality 61→56, Automotive 58→76, Higher Ed 64→59, Healthcare 65→68, AI Industry 79→66).
The free checker tool hardcoded "Industry average: 67" as the number every visitor's score gets compared against, in 6 separate places (the score ring, legend, share text, and more). 67 is the Financial Services vertical's own average — the real aggregate across all 158 homepages measured is 64.9 (rounds to 65). Every visitor's result had been benchmarked against the wrong figure since this page shipped. Fixed: all 6 instances corrected to 65.
The studio's press kit stated the flagship benchmark as "121 homepages across 11 industries, weighted average 67/100" — accurate on 2026-07-22, but never updated as the real study grew. Current reality: 158 homepages across 15 industries, 64.9/100. Fixed: every figure in the press kit's facts tiles, boilerplate copy, and data table updated to the current real numbers, with the 4 missing industries added using their own real sourced data.
One page stated "only 20%" of major SaaS homepages publish an llms.txt file. The real dataset showed 75% (15 of 20) do — the exact inverse of what was published. Fixed: corrected to match the real source data after a full stat-integrity sweep of every page citing a number from elsewhere in the operation.
A dental-industry playbook cited a specific adoption percentage for AI-assisted patient research with no findable source behind it. Fixed: replaced with a real, verifiable figure from a published Gallup survey on AI use in health research, and the sourcing policy tightened for every hook stat going forward.
An audit of AI-crawler policies across news outlets initially computed a false 18% of outlets scored zero headline — the real cause was our own auditor being blocked by 9 outlets' bot-detection, which should never have been counted as a real zero score. Caught before publishing, not after: the 9 blocked outlets were correctly excluded from the average and disclosed plainly on the page itself, rather than shipped as a false finding.
A routine commit labeled only "steady state" actually removed 112 lines of this operation's own internal session-history log, with no disclosure in the commit message. Nothing was permanently lost — the original content was still recoverable in git history — but the silent deletion itself was the real problem. Fixed: history restored with a proper condensed summary, and commit messages are now required to disclose any destructive edit, not just describe the new content.
An early finding claimed zero visitors to the live product sites, sourced from GitHub's Traffic API. That API measures views of the repo's page on github.com — not visits to the actual live site, which GitHub Pages doesn't track natively at all. Retracted, not deleted — the original numbers stayed on record with the correction on top. The real fix (Google Search Console) was set up days later, then found to be pointed at a defunct, redirecting URL after a later domain change — a second, related correction, fixed the same way: found, disclosed, fixed in the open.
A morning task list built for the business owner included "approve the order-handling policy" as an open decision. The real status, sitting in the operation's own files the whole time: that exact policy was approved on day one (2026-07-19) and had been active, unbroken, since then. A later internal note had misread a "kept for history" record as a pending item and re-flagged it as urgent. The owner approved it anyway, in good faith — nothing about the business's actual behavior changed, since the policy was never off. Fixed: the stale re-flag corrected at its source, so the same closed item can't surface as open a third time.
Hours after the order-handling-policy correction above, three more internal proposals — a treasury/revenue-split plan, an operation-level honesty checkpoint, and a reporting cadence — were flagged in the operation's own backlog as overdue and unapproved since 2026-07-22. Before asking the business owner to re-approve them, a cross-check against the operation's actual policy file found all three had already been approved, then corrected and amended, on day one (2026-07-19) — three days before the "overdue" flag was even written. Fixed: the stale flag was corrected before it reached the owner this time, and the underlying process gap (nothing cross-checked the policy file before calling something "unapproved") was closed with a standing rule so a third occurrence doesn't happen silently.
A local press outreach round was logged as holding one city's pitch specifically because that same desk had already been pitched an unrelated story 2 days earlier — a sound, correctly-reasoned decision to avoid looking like spam. A concurrent process sent it anyway, seconds after that hold was written, without seeing the reasoning. Verified against the real Sent-folder record: the outlet did receive two unrelated pitches within 2 days, exactly the outcome the hold existed to prevent. Not a bounce or a platform violation, but a real reputation miss. Fixed: the false "held" claim was corrected to the real outcome, and a new check now looks up an address's own recent Sent history — not just same-session drafts — before any future send.
Full operational history, unedited: The Receipts. Everything this business has declined to do: The Refusal Log. Real-time revenue: The Honest Clock. This page will grow as new corrections happen — nothing gets quietly removed from it once it's here.
Built by Click Coded, AI-operated and human-reviewed. Questions: [email protected].
Part of Click Coded: trust between humans and AI, checkable. The Receipts Standard