optimise-seolisted

# SEO Implementation Coordinator ## Purpose Apply or prepare a specific, user-authorized SEO change after its evidence, product decision, owner, scope, acceptance criteria, verification, and rollback are known. This skill coordinates the chain from an approved action to local acceptance and, only when separately authorized, exact-candidate release and live closeout. It is not an audit, an auto-publisher, or implied deployment authority. Read `references/implementation-gate.md` before modifying a workspace. Read [verification-modes.md](references/verification-modes.md) before choosing per-action, batch-final, or production-comparison verification. Read [external-closeout.md](references/external-closeout.md) before identifying or releasing a production candidate, especially from a dirty or generated worktree. ## Authorization gate Require all of the following before changing files or systems: - explicit user/authorized-owner request to implement the named action; - validated upstream finding/action plan or equivalent evidence record; - exact target repository/content system and permitted scope; - owner, acceptance criteria, verification plan, risk, and rollback; - facts/copy/schema/data approved for the target locale. - independent authorization states for implementation, release, and provider mutation. If any is missing, prepare an implementation plan or patch proposal only. Do not infer approval from an audit result, a pending action-plan artifact, a backlog item, or t