A weekly coordinator that reviews traffic and errors across all your sites, ranks the problems, and starts one focused fix session per problem — then tracks them to done.

When to use it

You have more sites than you can look at every week. You want one place that says “these three things matter this week” and gets them moving.

Coordinator brief

Task: weekly review of all sites in <PORTFOLIO_LIST>.
1. For each site collect: visits and trend, top landing pages, 404s, Core Web Vitals,
   search impressions/clicks, form submissions. Note which data you could not access.
2. Rank the top problems by expected impact, not by ease.
3. For each of the top N problems, write a self-contained brief (site, evidence, goal,
   done-when, what not to touch) and start one session for it.
4. Keep a shared notes file: one line per session (site, goal, status, PR link).
5. When sessions report, check their PRs/diffs before marking anything done.
Do not fix things yourself; dispatch.

Approval rules

Each fix session inherits the default rules: pushes, merges and deploys wait for you. The coordinator itself should never need approval; if it asks, it is doing work it should have dispatched.

Budget

Give the coordinator a small daily budget and each fix its own. When a fix hits its budget, it stops and the coordinator reports it as blocked rather than starting it again.

Done when

The week’s notes file lists every problem with a status and evidence
Every “done” item has a merged PR or a verified live change

Lessons from real runs

A note from a sub-session is a report, not proof. Have the coordinator check the diff or the live page.
Overnight runs hit usage limits; schedule the expensive fixes first and keep briefs self-contained so a session can resume cleanly.

Multi-site traffic review & dispatch