0% 5h quota used · resets in 2h live · 08/09/2026 12:12 CEST

tn:seo-audit

Weekly SEO and health audit of tunisie-electricite.com — scores every page, checks the live site, reports top actions. Read-only on the site; chains tn:seo-fixes when it finds 2+ mechanical fixes.

Runs 13

last 1d ago

Failed 1

no current streak

Median run $1.17

3m · tn ceiling $8.00 per run

Spent in total $15.92

395 turns of agent work

Manifest

tn/tasks.yaml

Address: tn:seo-audit — also tn:seo-audit
Runner: claude-code
Policy: autonomous writes only inside its own workspace, no outward action
Workspace: the cms clone
Schedule: 0 6 * * 1 · next 14/09/2026 06:00
Model: sonnet
Budget: 80 turns · 45 minutes
Triggerable: yes — free text can reach it
Notifies: every run — 🟢 on success, 🔴 on failure
Description (manifest): Weekly SEO and health audit of tunisie-electricite.com — scores every page, checks the live site, reports top actions. Read-only on the site; chains tn:seo-fixes when it finds 2+ mechanical fixes.

Cost per run

Runs

When	What it reported	Turns	Took	Cost
07/09/2026 06:03	SEO audit complete for 2026-09-07. The TN-002 arc is fully closed — `/steg/numero-vert` now emits its 5-question FAQPage live (PR #18264 verified), and the underlying sha…	21	3m	$0.84	ok
31/08/2026 06:05	Tenth SEO audit (2026-08-31) ran clean: no TN content changes since 08-27, all 8 core URLs 200 OK, and title/meta lengths hold at guideline across static, annuaire and ou…	20	5m	$0.83	ok
27/08/2026 16:16	SEO audit complete for tunisie-electricite.com (run 2026-08-27): all 8 core URLs and 3 dynamic spot-checks returned 200 OK, the two #17032 template fixes are holding live…	19	2m	$0.63	ok
25/08/2026 12:05	SEO audit complete for 2026-08-25. Both yesterday's `countryos/tn` PRs (annuaire meta fixes #17032, content freshness #17084) are merged and verified live with cache-bust…	45	2m	$1.09	ok
24/08/2026 12:06	Done. Both the report addendum and the journal entry are written. Outcome (2-3 sentences for the notification channel): The scheduled seo-audit fired a second time…	27	3m	$0.89	ok
24/08/2026 09:45	Ran the weekly `/seo-audit` on tunisie-electricite.com: all 16 checked URLs are healthy (200 OK), the 6 pages touched by last week's 5 merged commits still meet SEO guide…	35	3m	$1.69	ok
17/08/2026 06:05	The audit is complete. Report written to `reports/2026-08-17-seo-audit.md`, journal updated. Summary: All 16 URLs healthy (200 OK), and every previously-fixed item h…	38	5m	$1.92	ok
10/08/2026 10:14	The audit is complete and the report/journal are written; nothing was modified on the site (this run stayed read-only as required). Outcome: Ran the full `/seo-audit…	30	3m	$1.17	ok
04/08/2026 12:12	Audit complete, no site files touched, git tree clean. Report saved to `reports/2026-08-04-seo-audit.md`, journal updated. Outcome: all 13 static pages and 286 annua…	38	14m	$1.38	ok
27/07/2026 10:09	Audit complete. All 16 live URLs return 200 OK; the 13 static pages and 286 annuaire directory pages score unchanged from the 07-03 baseline. Biggest finding: the 374 pow…	47	5m	$2.11	ok
03/07/2026 19:42	The audit is complete and read-only as required — no site files were touched. Outcome: Re-ran the SEO audit and confirmed all 5 fixes from the merged PR #8895 are li…	32	3m	$1.38	ok
02/07/2026 17:03	Audit complete. All 13 static pages plus the 3 directory templates (covering ~286 generated governorate/delegation pages) were scored, live URLs and a directory spot-chec…	43	5m	$1.99	ok
02/07/2026 16:54	no log	—	—	$0	error

The skill it runs

Read the skill

Weekly SEO audit — tunisie-electricite.com

You are in the cms monorepo clone. This task is read-only on the site: you may write only to the country workspace (reports, memory). Do not modify any Blade file.

Steps

Live site health. curl -sI the production URLs: homepage, /tarifs, /tarifs-gaz, /steg, /coupures, /annuaire, /sitemap.xml, /robots.txt on https://tunisie-electricite.com. Record status codes and response times. Any non-200 is a top-priority finding.
Page audits. For each static page in sites/tunisie-electricite.com/pages/ (~18 Blade files), apply the checks of the monorepo's SEO audit skill (.claude/skills/seo-audit/): title, meta description, heading structure, internal links, images/alt, structured data, OG tags. Score each page /10. Reuse last week's report (country workspace reports/) to focus on what changed; re-verify only pages that scored below 8 or were modified since (git log).
Directory spot-check. Render 3 random dynamic pages (governorate/delegation) locally if possible, or fetch them on production. Check they resolve with real agency data, valid title/meta.
Report. Write reports/<YYYY-MM-DD>-seo-audit.md in the country workspace: scored table, week-over-week deltas, and the top 5 actions ranked by impact/effort. Mark each action as mechanical (in scope for the seo-fixes task: title/meta trims, JSON-LD, internal links, og tags, alt text) or non-mechanical (content strategy, structure, data — needs a human or a different task).
Hand off to seo-fixes when it's worth it. If 2 or more top actions are mechanical, chain the fixes task:
```
countryos-trigger tn:seo-fixes implement the mechanical items from today's audit report
```
But first check gh pr list --state open --search "countryos/tn" --json title,headRefName — if an open seo-fixes PR already exists, do NOT trigger (its review is still pending; stacking a second PR just splits attention). Note in the report and journal whether you triggered and why. If fewer than 2 mechanical items, or they're all trivial (< ~10 min of human review value), skip — the weekly cadence will batch them up.

Budget discipline

Deterministic checks (curl loops, grep for missing meta) must be shell one-liners, not page-by-page reasoning. Spend model turns only on judgment (scoring, ranking actions).

Findings you cannot fix

When you find something real that is outside TN scope — a shared fleet component, another team's regression — a line in the report is not enough. The FaqAnswer regression of 2026-08-17 was correctly diagnosed, complete with a repro, and then sat in a markdown file nobody else can read (reports/ is gitignored).

Open a signalement entry in countries/tn/decisions.md instead: what breaks, the repro, the commit or PR responsible, and who should own it. That file is git-tracked and tn:decisions-escalate will chase it. Then carry on — filing it is the action; fixing it is not yours.