0% 5h quota used ·
resets in 2h
live · 08/09/2026 12:12 CEST
Monthly report — tn, 2026-08
One month's fragment, exactly as _global:monthly-report wrote it. The assembled document lives at Country OS — Tunisia.
In one line
Tunisia fixed a meta-description bug affecting 285 pages, corrected a billing page that understated a real STEG bill by 43%, and rebuilt its decision register around Google Chat so questions actually reach the people who can answer them.
Shipped
- SEO fixes — PR #17032, merged 24 Aug. The seventh audit found that 285 of the 286 directory pages had meta descriptions of 199–244 characters against a 160 guideline — structurally, since before tracking began. Six earlier audits had checked that the tag was present and never that it was the right length. Fixed both templates plus one long title, verified against every real governorate/delegation pair rather than the sample.
- Content freshness — PRs #14134 (merged 4 Aug) and #17084 (merged 24 Aug). Every electricity and gas tariff re-checked tranche-for-tranche against steg.com.tn both times — no tariff has changed. What did change: a dead official source link, the ELMED interconnection figures (cost, status, a commissioning date now attributed because sources disagree), an inverted m³/thermie conversion, and the employee count, pinned to a 2020 figure until the official homepage finally gave a current one.
- Click-through optimisation — PR #16566, merged 20 Aug. Two pages that rank well but used words searchers do not type ("coupure d'électricité" where people search "panne de courant"; "gaz naturel basse pression" where they search "gaz de ville"). Modelled at ≈+235 clicks per 28 days; the result is measurable from 15 September, and the task grades its own previous run.
- Eight SEO audit runs (read-only, weekly) and a business review on 15 Aug — the first with real Search Console data: 19,187 clicks and 472,358 impressions over 28 days at average position 5.9.
- The decision register moved to Google Chat. Entries are now announced the day they open and re-raised weekly, and are answered by replying to the message in whatever words suit. Two were settled this month: a monthly content task approved, and adding Python to the runtime image rejected. The register ended August with no open entries.
In progress / waiting on a human
- PR #18264 (31 Aug) is still open — it gives the STEG helpline page its own FAQ structured data, copied verbatim from three sibling Selectra sites that had already solved the same problem locally. It needs review and a live check that the page emits its five questions.
- Standing backlog, none of it mechanical enough for the audit task to fix itself: no social-share image on any of the 673 pages (flagged in ten consecutive audits), six STEG sub-pages still missing FAQ sections, and a one-line tidy in the register that remains nobody's job.
- The shared CMS component bug that broke the FAQ structured data is unowned: the issue filed for whoever owns it was closed with no fix. Tunisia routed around it locally rather than waiting, on a human's instruction.
Problems
- An answer sat unread for six days. A Chat reply that named an action ("rework the component directly on the tunisia website") is indistinguishable from a request to go and do it, so the dispatcher asked which — and that question was never answered, while the escalation kept nagging for an answer that already existed. Fixed at the routing layer: a reply that opens with a register id now goes straight to the register.
- The audit task fired twice on 24 Aug, twenty minutes apart. The second run recognised the duplicate and verified the first run's output instead of redoing it.
- No errored runs.
Done with a human in the loop
- 11 Aug — Search Console access was configured (infrastructure, no run). The "no traffic numbers" blocker flagged in every business review since July is closed.
- 18–19 Aug, hands-on sessions with Frédéric — the month's most consequential finding. The tariffs page billed 150 kWh of energy for 250 kWh consumed and came out 43% below the official STEG simulator. Four distinct errors: the page said in prose that the whole month bills at one price, then implemented a progressive scale; two levy lines were missing entirely; and VAT was quoted rather than derived. Corrected across PRs #16234, #16279 and #16291 (all merged), which also moved the tariff grid into a single shared data file so one figure lives in one place. A page can score 96/100 on SEO and be 43% wrong — no audit was ever going to catch this.
- A related correction worth recording: one of those fixes replaced "700 millimes per kVA" with a flat 700, on the strength of an official simulation that had quietly simulated 1 kVA. For an ordinary 3 kVA household that understated the bill. Caught against a real invoice and fixed the same day.
- The same sessions produced PR #16216 (merged) and a new analysis tool that found 33 queries where two of our own pages compete — something a per-page audit structurally cannot see.
Cost
30 runs, 0 errors, ~101 minutes, ~$25.97 API-equivalent. Mostly the 8 SEO audits ($9.60) and 2 content-freshness runs ($8.28); the 14 daily decision-reminder runs are a script and cost nothing.