Initial commit
This commit is contained in:
30
skills/diagnostics/SKILL.md
Normal file
30
skills/diagnostics/SKILL.md
Normal file
@@ -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.
|
||||
|
||||
---
|
||||
30
skills/keyword-strategy/SKILL.md
Normal file
30
skills/keyword-strategy/SKILL.md
Normal file
@@ -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.
|
||||
|
||||
---
|
||||
31
skills/publishing-process/SKILL.md
Normal file
31
skills/publishing-process/SKILL.md
Normal file
@@ -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.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user