A Node script that reads the latest approved report (or the latest pending one if none is approved, clearly labelled as not approved), prints the authority line, the bucket counts, the traffic delta, the signals, the full per-keyword benchmark and every proposal with its forClaude instruction, then tells you the exact command to mark it implemented when the work ships.
Also called: implement the approved SEO report · seo-report script · CLI report
- 1node scripts/seo-report.mjs prints the newest approved report, preferring approved over pending.
- 2node scripts/seo-report.mjs <id> prints a specific report.
- 3node scripts/seo-report.mjs --done <id> flips its status to implemented.
- 4A pending report is printed with the explicit warning that it is not yet approved.
- 5It connects with DATABASE_URL — the IPv4 pooler URL, same as the other query scripts.
The script header describes the designed path: "Keith approves an SEO audit report in the panel, then tells Claude in the terminal 'implement the approved SEO report' — Claude runs this to pull the full report + per-proposal instructions and gets to work." This was the original implementation route, and the autopilot's implementer later automated the safe subset of it — but the manual lever stays, because the proposals that need judgement still land here.
- Handing a report to whoever does the work meant retyping it.
- Proposal detail was lost in translation between panel and terminal.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →