Initial commit
This commit is contained in:
33
commands/audit-technical.md
Normal file
33
commands/audit-technical.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: audit-technical
|
||||
description: Runs technical SEO diagnostics, prioritizes issues, and packages remediation guidance.
|
||||
usage: /seo-workflow-orchestration:audit-technical --scope "core-web-vitals" --window 30d --detail full
|
||||
---
|
||||
|
||||
# Command: audit-technical
|
||||
|
||||
## Inputs
|
||||
- **scope** – focus area (crawl, index, CWV, schema, hreflang, redirects).
|
||||
- **window** – data range (7d, 30d, 90d) for Search Console/log metrics.
|
||||
- **detail** – summary | full output detail.
|
||||
- **environment** – optional prod | staging to analyze releases.
|
||||
- **pages** – optional URL or directory filter for targeted audits.
|
||||
|
||||
## Workflow
|
||||
1. **Signal Collection** – pull Search Console, log files, crawler data, Lighthouse/CWV metrics for specified scope.
|
||||
2. **Diagnostics** – run automated checks (status codes, render depth, CLS/LCP, schema validation, hreflang pairs).
|
||||
3. **Impact Assessment** – quantify affected pages, traffic at risk, and business impact.
|
||||
4. **Remediation Plan** – outline recommended fixes, owners, SLAs, and dependencies.
|
||||
5. **Governance Logging** – document incidents, change requests, and QA requirements before deployment.
|
||||
|
||||
## Outputs
|
||||
- Technical audit report (issue, severity, pages impacted, evidence links, proposed fix).
|
||||
- Ticket backlog or PRD with prioritized actions.
|
||||
- Monitoring plan (dashboards/alerts) for post-fix validation.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `technical-analyst` – leads diagnostics and remediation planning.
|
||||
- `diagnostics` skill – provides checklists, tooling references, and QA steps.
|
||||
- `seo-director` – reviews impact and signs off on priorities.
|
||||
|
||||
---
|
||||
33
commands/deploy-optimizations.md
Normal file
33
commands/deploy-optimizations.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: deploy-optimizations
|
||||
description: Coordinates content, technical, and linking updates for priority SEO initiatives.
|
||||
usage: /seo-workflow-orchestration:deploy-optimizations --cluster "AI sales enablement" --owner content --due 2025-12-01
|
||||
---
|
||||
|
||||
# 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
|
||||
1. **Brief Retrieval** – load cluster data, content brief, and technical requirements.
|
||||
2. **Task Breakdown** – create checklist covering copy, design, CMS, technical fixes, internal links, schema, QA.
|
||||
3. **Execution Coordination** – assign owners, manage approvals, and track status in shared board.
|
||||
4. **QA & Publishing** – validate metadata, performance (CWV), accessibility, and analytics tagging before go-live.
|
||||
5. **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-process` skill – enforces approval gates and evidence capture.
|
||||
|
||||
---
|
||||
33
commands/prioritize-keywords.md
Normal file
33
commands/prioritize-keywords.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: prioritize-keywords
|
||||
description: Generates prioritized keyword clusters, intent mapping, and ownership plans.
|
||||
usage: /seo-workflow-orchestration:prioritize-keywords --goal "pipeline" --regions "us,uk" --max-clusters 8
|
||||
---
|
||||
|
||||
# Command: prioritize-keywords
|
||||
|
||||
## Inputs
|
||||
- **goal** – business objective (pipeline, product launch, category, retention).
|
||||
- **regions** – optional comma-separated locales for SERP nuance.
|
||||
- **max-clusters** – numeric cap on keyword clusters returned.
|
||||
- **competitors** – optional list to bias SERP/Gap analysis.
|
||||
- **constraints** – optional notes (brand terms, restricted topics, resources).
|
||||
|
||||
## Workflow
|
||||
1. **Intent Alignment** – map objectives to funnel stages + persona questions.
|
||||
2. **Data Pull** – aggregate search volume, difficulty, CTR opportunity, and SERP features.
|
||||
3. **Clustering** – group keywords into themes with intent, content format, and recommended owner.
|
||||
4. **Prioritization** – score clusters by impact, effort, competitive gap, and timeline.
|
||||
5. **Activation Plan** – outline required assets, supporting content, and measurement KPIs.
|
||||
|
||||
## Outputs
|
||||
- Keyword cluster table (cluster, intent, volume, difficulty, priority, owner).
|
||||
- Content/technical recommendations per cluster.
|
||||
- Experiment backlog or refresh list tied to priority items.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `seo-director` – validates alignment with roadmap.
|
||||
- `keyword-strategy` skill – enforces clustering + scoring methodology.
|
||||
- `on-page-lead` – receives top clusters for brief development.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user