From 86d1436c9f1712db5d9904ad14b643be6ba7f893 Mon Sep 17 00:00:00 2001 From: Zhongwei Li Date: Sat, 29 Nov 2025 18:31:54 +0800 Subject: [PATCH] Initial commit --- .claude-plugin/plugin.json | 24 ++++++++++ README.md | 3 ++ agents/on-page-lead.md | 27 +++++++++++ agents/seo-director.md | 27 +++++++++++ agents/technical-analyst.md | 27 +++++++++++ commands/audit-technical.md | 33 +++++++++++++ commands/deploy-optimizations.md | 33 +++++++++++++ commands/prioritize-keywords.md | 33 +++++++++++++ plugin.lock.json | 77 ++++++++++++++++++++++++++++++ skills/diagnostics/SKILL.md | 30 ++++++++++++ skills/keyword-strategy/SKILL.md | 30 ++++++++++++ skills/publishing-process/SKILL.md | 31 ++++++++++++ 12 files changed, 375 insertions(+) create mode 100644 .claude-plugin/plugin.json create mode 100644 README.md create mode 100644 agents/on-page-lead.md create mode 100644 agents/seo-director.md create mode 100644 agents/technical-analyst.md create mode 100644 commands/audit-technical.md create mode 100644 commands/deploy-optimizations.md create mode 100644 commands/prioritize-keywords.md create mode 100644 plugin.lock.json create mode 100644 skills/diagnostics/SKILL.md create mode 100644 skills/keyword-strategy/SKILL.md create mode 100644 skills/publishing-process/SKILL.md diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..c34d177 --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "seo-workflow-orchestration", + "description": "SEO workflow orchestration from keyword strategy through technical diagnostics", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/keyword-strategy/SKILL.md", + "./skills/publishing-process/SKILL.md", + "./skills/diagnostics/SKILL.md" + ], + "agents": [ + "./agents/seo-director.md", + "./agents/on-page-lead.md", + "./agents/technical-analyst.md" + ], + "commands": [ + "./commands/prioritize-keywords.md", + "./commands/deploy-optimizations.md", + "./commands/audit-technical.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..7ad117a --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# seo-workflow-orchestration + +SEO workflow orchestration from keyword strategy through technical diagnostics diff --git a/agents/on-page-lead.md b/agents/on-page-lead.md new file mode 100644 index 0000000..e62ee71 --- /dev/null +++ b/agents/on-page-lead.md @@ -0,0 +1,27 @@ +--- +name: on-page-lead +description: Drives content optimization, publishing readiness, and cross-functional execution for SEO initiatives. +model: haiku +--- + +# On-page Lead Agent + +## Responsibilities +- Turn keyword priorities into briefs, outlines, and optimization checklists for writers/designers. +- Coordinate publishing workflow (copy, design, CMS, localization) with clear SLAs. +- Ensure on-page elements (metadata, schema, internal links, CTAs) match playbooks. +- Track performance per asset and backlog new experiments or refreshes. + +## Workflow +1. **Brief Intake** – capture target keyword cluster, intent, persona, and success metrics. +2. **Outline & Requirements** – produce outline, SERP analysis, internal linking plan, and conversion goals. +3. **Execution Support** – partner with writers/editors, manage reviews, and QA CMS implementation. +4. **Optimization Pass** – finalize metadata, structured data, media compression, accessibility, and CTA modules. +5. **Launch & Monitor** – confirm publishing, track early performance, flag deviations for iteration. + +## Outputs +- SEO content brief + outline with optimization checklist. +- Publishing tracker with owner status, approvals, and go-live timestamps. +- Post-launch report with KPIs, learnings, and next steps. + +--- diff --git a/agents/seo-director.md b/agents/seo-director.md new file mode 100644 index 0000000..5f605e1 --- /dev/null +++ b/agents/seo-director.md @@ -0,0 +1,27 @@ +--- +name: seo-director +description: Owns SEO roadmap, cross-team alignment, and performance governance. +model: sonnet +--- + +# SEO Director Agent + +## Responsibilities +- Translate GTM priorities into SEO initiatives spanning content, technical, and authority workstreams. +- Align product marketing, content, web, and RevOps teams on keyword focus, publishing cadence, and goals. +- Maintain backlog of experiments, technical fixes, and cross-functional dependencies. +- Report on organic performance, tying KPIs back to leads, pipeline, and revenue. + +## Workflow +1. **Brief Intake** – capture business objectives, ICP, target personas, and launch timelines. +2. **Opportunity Analysis** – review keyword gaps, SERP trends, competitive intel, and site audits. +3. **Roadmap Planning** – prioritize initiatives across content, technical, authority, and experimentation. +4. **Stakeholder Sync** – ensure owners have briefs, resources, and KPIs. +5. **Performance Review** – run retros, adjust roadmap, and document lessons learned. + +## Outputs +- SEO roadmap with quarterly initiatives, owners, and success metrics. +- Executive summary tying organic KPIs to business impact. +- Resourcing + dependency tracker for upcoming sprints. + +--- diff --git a/agents/technical-analyst.md b/agents/technical-analyst.md new file mode 100644 index 0000000..4d3f8e9 --- /dev/null +++ b/agents/technical-analyst.md @@ -0,0 +1,27 @@ +--- +name: technical-analyst +description: Handles technical SEO diagnostics, backlog, and incident response for site health. +model: haiku +--- + +# Technical SEO Analyst Agent + +## Responsibilities +- Monitor crawl/index/CLS/LCP metrics and prioritize technical fixes with web engineering. +- Run site audits (logs, crawlers, lighthouse) to surface issues impacting organic performance. +- Manage change requests for redirects, structured data, hreflang, and performance tuning. +- Validate fixes post-deployment and maintain documentation for governance. + +## Workflow +1. **Signal Intake** – review monitoring alerts, search console data, and release notes. +2. **Diagnostics** – replicate issues, analyze server logs, and run headless crawls or CWV audits. +3. **Prioritization** – score impact vs effort, attach owners, and log tickets. +4. **Implementation Support** – provide detailed acceptance criteria and QA scripts to engineering. +5. **Validation & Reporting** – verify fix, update dashboards, and document learnings. + +## Outputs +- Technical audit report with severity ratings and recommended actions. +- Ticket backlog with requirements, dependencies, and SLAs. +- Validation checklist showing before/after metrics. + +--- diff --git a/commands/audit-technical.md b/commands/audit-technical.md new file mode 100644 index 0000000..6c504a1 --- /dev/null +++ b/commands/audit-technical.md @@ -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. + +--- diff --git a/commands/deploy-optimizations.md b/commands/deploy-optimizations.md new file mode 100644 index 0000000..9d2d183 --- /dev/null +++ b/commands/deploy-optimizations.md @@ -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. + +--- diff --git a/commands/prioritize-keywords.md b/commands/prioritize-keywords.md new file mode 100644 index 0000000..f1b0abf --- /dev/null +++ b/commands/prioritize-keywords.md @@ -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. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..616b7a3 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/seo-workflow-orchestration", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "1f4f8e3e8b88a34d58872c28d7b84b229054d9ed", + "treeHash": "93bddc8163f52a6077e6216066978edcd636484a8531ca81fa6d2cfeaae485bc", + "generatedAt": "2025-11-28T10:17:19.232605Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "seo-workflow-orchestration", + "description": "SEO workflow orchestration from keyword strategy through technical diagnostics", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "fe93bf81d50a15f5e6e30cc43b8d90b955289b98431794def646ec3cc0bf780c" + }, + { + "path": "agents/on-page-lead.md", + "sha256": "ca49b220417ebf710c21d9b1907879413d442a18e37af52679bfd3b063d89134" + }, + { + "path": "agents/seo-director.md", + "sha256": "559579c23a9596f5fcd5164f3807326c65560210896933724b19823e3a18e8b7" + }, + { + "path": "agents/technical-analyst.md", + "sha256": "5dedcdd8171ad0917b605ca28df0c868f6672321bc4a16c40f95ff9b80c08177" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "84b43c4738736c669863da17e833e2b21344bec52c7f02922db935d1e4fc2923" + }, + { + "path": "commands/prioritize-keywords.md", + "sha256": "6fb86d2f7975358b184250ad3d7749d51ca2d00acf3717ce81536be044645a5f" + }, + { + "path": "commands/deploy-optimizations.md", + "sha256": "69af2d70013adf7a1cbe525521c815a00596248a32a6e6ef1d75d9b1068721a7" + }, + { + "path": "commands/audit-technical.md", + "sha256": "5b7b7fdeab13dfc70237d64086dc2edc26531ddb206a4bb1e9600cf9a604d928" + }, + { + "path": "skills/publishing-process/SKILL.md", + "sha256": "85717e47aedb330ac69581d9d8d9d6d4975d99b853c527e824a2867406b791e3" + }, + { + "path": "skills/diagnostics/SKILL.md", + "sha256": "73ff6c1d242e062c32013a36d57722249b67114d8e66744ffed4a71fba89eb41" + }, + { + "path": "skills/keyword-strategy/SKILL.md", + "sha256": "21e20fcacd3350a38bf289c36568975428f742a16ae77ed936eba7ac6198559d" + } + ], + "dirSha256": "93bddc8163f52a6077e6216066978edcd636484a8531ca81fa6d2cfeaae485bc" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/diagnostics/SKILL.md b/skills/diagnostics/SKILL.md new file mode 100644 index 0000000..1d55f7b --- /dev/null +++ b/skills/diagnostics/SKILL.md @@ -0,0 +1,30 @@ +--- +name: diagnostics +description: Use for structured technical SEO audits, incident response, and validation. +--- + +# Technical Diagnostics Toolkit Skill + +## When to Use +- Investigating crawl/index anomalies, traffic drops, or Core Web Vitals regressions. +- Running scheduled audits ahead of major launches or migrations. +- Validating fixes before/after engineering deployments. + +## Framework +1. **Signal Triangulation** – combine Search Console, log files, crawler output, and analytics deltas. +2. **Replication Scripts** – document steps to reproduce issues (user agents, locales, device types). +3. **Root Cause Hypotheses** – map symptoms to likely causes (render blocking, redirects, robots, schema errors). +4. **Fix Design** – outline remediation options, risk level, dependencies, and testing approach. +5. **Validation & Monitoring** – specify metrics and alerts to confirm resolution. + +## Templates +- Diagnostics worksheet (symptom, evidence, hypothesis, owner, next action). +- Crawl + render checklist per environment. +- Validation log capturing metrics pre/post change. + +## Tips +- Keep historical baselines to quickly detect regressions. +- Pair with engineering release notes to correlate incidents. +- Automate recurring crawls and lighthouse runs to catch issues early. + +--- diff --git a/skills/keyword-strategy/SKILL.md b/skills/keyword-strategy/SKILL.md new file mode 100644 index 0000000..c3d70ed --- /dev/null +++ b/skills/keyword-strategy/SKILL.md @@ -0,0 +1,30 @@ +--- +name: keyword-strategy +description: Use when researching, clustering, and prioritizing keywords for SEO roadmaps. +--- + +# Keyword Strategy Playbook Skill + +## When to Use +- Planning quarterly SEO initiatives or briefing writers. +- Auditing existing keyword portfolios for gaps or cannibalization. +- Aligning organic strategy with launches or revenue themes. + +## Framework +1. **Search Intent Mapping** – align keywords to persona questions and funnel stages. +2. **Data Sources** – combine Search Console, keyword tools, intent data, and first-party conversion signals. +3. **Clustering & Scoring** – group by topic, assign difficulty/opportunity/demand scores. +4. **Competitive Context** – track SERP features, content freshness, and authority benchmarks. +5. **Action Plan** – tie clusters to asset types, owners, and KPIs. + +## Templates +- Cluster sheet (keyword, intent, volume, KD, SERP notes, priority, owner). +- Opportunity heatmap for exec reviews. +- Experiment backlog linking cluster tests to hypotheses. + +## Tips +- Refresh clusters monthly for high-volatility topics. +- Pair with product/CS insights to uncover long-tail opportunities. +- Track cannibalization by monitoring internal links and ranking URLs. + +--- diff --git a/skills/publishing-process/SKILL.md b/skills/publishing-process/SKILL.md new file mode 100644 index 0000000..e17986f --- /dev/null +++ b/skills/publishing-process/SKILL.md @@ -0,0 +1,31 @@ +--- +name: publishing-process +description: Use to orchestrate approvals, QA, and go-live steps for SEO content + + technical launches. +--- + +# SEO Publishing Process Skill + +## When to Use +- Coordinating multi-team releases (writers, designers, web, legal). +- Ensuring SEO assets meet quality, accessibility, and analytics requirements before launch. +- Running retros after missed deadlines or publishing defects. + +## Framework +1. **Pre-flight Checklist** – briefs approved, assets uploaded, localization complete, legal sign-off captured. +2. **CMS/Code QA** – metadata, schema markup, internal links, CWV budgets, responsive design. +3. **Analytics & Tracking** – UTMs, event triggers, conversion modules, A/B test configs. +4. **Launch Controls** – staging reviews, smoke tests, rollback plan, comms schedule. +5. **Post-launch Validation** – indexation check, monitoring alerts, performance baseline snapshot. + +## Templates +- Publishing runbook (steps, owner, evidence link, status). +- QA checklist (content, technical, analytics, accessibility). +- Launch log capturing timestamps, environments, and approvals. + +## Tips +- Timebox approvals with clear SLAs to keep calendars on track. +- Automate checklist reminders via project tools or Git hooks. +- Pair with `deploy-optimizations` to keep evidence attached to each task. + +---