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

tn/seo-fixes

Implement the mechanical fixes from the latest SEO audit report on a branch, ship as a PR to develop after human approval. On-demand companion to seo-audit.

tn:seo-fixes 47 lines

SEO fixes — tunisie-electricite.com

You are in the cms monorepo clone. Input: the most recent reports/*-seo-audit.md in the country workspace (pick the newest by filename date). Implement its recommended actions — mechanical, low-risk fixes only.

Scope rules

  • In scope: meta description / title length trims, adding structured data (JSON-LD) matching patterns already used elsewhere on the site, adding contextual internal links, og/social tags, alt attributes. Anything the report ranks as low-effort/mechanical.
  • Out of scope: rewriting body content, changing page structure, new pages, anything touching data files or other sites. If the report recommends something non-mechanical, list it in the proposal as "needs separate task" and skip it.

Steps

  1. Read the latest audit report, then verify each finding is still true in the Blade sources (sites/tunisie-electricite.com/pages/) — a human or another run may have fixed some already. Skip anything already fixed. If nothing is left to fix, report that and stop — do not open an empty PR.
  2. Create branch countryos/tn/<YYYY-MM-DD>-seo-fixes from origin/develop. One commit per action group (e.g. "trim meta descriptions ≤160 chars", "add BreadcrumbList to annuaire templates"), so review and partial revert stay easy.
    • Meta descriptions: keep the meaning and CTA, cut to ≤160 chars, French.
    • JSON-LD: copy the exact pattern from a page that already has it (e.g. /tarifs BreadcrumbList) — do not invent a new structure.
    • Internal links: only weave links into existing sentences or add one short natural sentence; never dump a bare link list into the content.
  3. Sanity-check your edits: re-grep every touched file for balanced Blade directives and tags, and confirm each new meta description is really ≤160 characters (count them; do not eyeball).
  4. Push the branch and open a draft PR to develop with gh pr create --draft, titled [tn] SEO fixes <YYYY-MM-DD>. PR body: per-commit list of changes, before → after for every meta/title, and the skipped/out-of-scope items. The human reviews on the PR and marks it ready — never merge or mark ready yourself.
  5. Report the PR URL in your final message.