aaron-he-zhu/aaron-marketing-skills / seo-geo/implement/content-writer
content-writer
VerifiedUse when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with keywords, headers, snippets, and evidence boundaries; refresh scores decay, prioritizes update work, and produces a republish plan with GEO guidance. Not for AI-citation/GEO readiness scoring — use geo-content-optimizer; not for publish-gate scoring — use content-quality-auditor. SEO文章写作/内容更新/排名恢复
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.4 KB |
| references/content-decay-signals.md | markdown | 4.1 KB |
| references/content-structure-templates.md | markdown | 3.4 KB |
| references/instructions-detail.md | markdown | 4.5 KB |
| references/refresh-example.md | markdown | 3.3 KB |
| references/refresh-templates.md | markdown | 5.4 KB |
| references/seo-writing-checklist.md | markdown | 3.6 KB |
| references/title-formulas.md | markdown | 4.0 KB |
references/seo-writing-checklist.md
View on GitHub# SEO Writing Checklist and Content Template
Compact checklist for drafting SEO content that is useful, scannable, and ready for a CORE-EEAT review.
## On-Page Checklist
| Area | Required checks |
|------|-----------------|
| Keyword placement | Primary keyword in title, H1, first 100 words, at least one H2, conclusion, and meta description; secondary terms in H2/H3s; related entities throughout body. |
| Search intent | Content type, angle, depth, and CTA match the dominant SERP intent; mixed-intent pages answer the primary intent first. |
| Quality | Comprehensive coverage, original insight or data, actionable takeaways, examples, and expert/source support where claims need evidence. |
| Readability | 3-5 sentence paragraphs, varied sentence length, bullets/tables for dense points, bold only for key phrases, and TOC for long-form content. |
| Technical | 2-5 relevant internal links, 2-3 authoritative external links, descriptive image alt text, concise keyword-led URL slug. |
| Snippet targeting | Definition answers in 40-60 words, ordered steps for how-to queries, tables for comparisons, concise FAQ answers. |
## Copy-Start Template
```markdown
# [H1 with Primary Keyword]
**Meta Description**: [150-160 char value proposition with keyword and CTA]
[Hook] [Problem statement] [Promise: what the reader will learn] [Primary keyword naturally]
## [H2 with Secondary Keyword]
[1-2 sentence setup]
[Useful explanation with evidence, examples, or data]
### [H3 if needed]
- [Actionable point]
- [Actionable point]
- [Actionable point]
## [H2 for next major section]
> **Pro Tip**: [Specific, non-obvious implementation note]
| Comparison point | Option A | Option B |
|------------------|----------|----------|
| [Factor] | [Evidence] | [Evidence] |
## Frequently Asked Questions
### [Question from PAA or common query]?
[Direct 40-60 word answer that can stand alone as a snippet.]
## Conclusion
[Summarize key points, restate the primary keyword naturally, and give one clear CTA.]
**Sources**: [Source name + URL + access date], [Source name + URL + access date]
```
## Snippet Patterns
| Snippet type | Pattern |
|--------------|---------|
| Definition | `[Term] is [clear definition]. It matters because [outcome].` Keep to 40-60 words. |
| List | Introduce the list under an H2, then use numbered or bulleted items with parallel phrasing. |
| Table | Use simple headers and one idea per cell; avoid over-wide tables on mobile. |
| How-to | Label each action `Step 1`, `Step 2`, and include prerequisites before the steps. |
| FAQ | Answer directly first, then add nuance or caveats in the next sentence. |
## Example Calibration Card
Use this instead of copying a full sample article:
| Field | Example shape |
|-------|---------------|
| User request | `Write an SEO article about [topic] for [audience] targeting [keyword].` |
| H1 | `[Primary keyword]: [benefit/audience hook]` |
| Meta | `[Primary keyword] + concrete benefit + CTA, 150-160 chars.` |
| Intro | Hook, pain point, promise, then 3-5 bullets on what the reader will learn. |
| Evidence | Cite current sources for stats; never ship stale benchmark claims without dates. |
| FAQ answer | 40-60 words, direct first sentence, one caveat if needed. |
| CTA | One action matched to intent: subscribe, download, book, compare, or buy. |
## Final Self-Check
- [ ] The draft answers the dominant search intent before selling.
- [ ] Every claim that depends on data has a named source and date.
- [ ] Internal links support the topic journey, not just link volume.
- [ ] Headings form a useful outline when read alone.
- [ ] FAQ answers are direct enough for featured snippets.
- [ ] The conclusion gives one clear next action.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |