Command: deploy-optimizations
Inputs
- cluster – keyword/theme reference from
prioritize-keywords. - owner – responsible team (content, web, technical, revops).
- due – target completion date.
- scope – optional notes (net-new page, refresh, technical fix, structured data).
- dependencies – optional list (design, product, partners).
Workflow
- Brief Retrieval – load cluster data, content brief, and technical requirements.
- Task Breakdown – create checklist covering copy, design, CMS, technical fixes, internal links, schema, QA.
- Execution Coordination – assign owners, manage approvals, and track status in shared board.
- QA & Publishing – validate metadata, performance (CWV), accessibility, and analytics tagging before go-live.
- Post-launch Monitoring – collect early KPI signals, ensure logs/reporting are updated.
Outputs
- Optimization checklist with owners, status, and evidence links.
- Publishing confirmation (URL, timestamp, environment, approvals).
- Follow-up tasks for link building, experimentation, or refresh cadence.
Agent/Skill Invocations
on-page-lead– manages content + CMS workflow.technical-analyst– validates technical requirements and QA.publishing-processskill – enforces approval gates and evidence capture.