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/refresh-templates.md
View on GitHub# Content Refresh Templates
Templates for the refresh-mode steps 2-9. Referenced from [SKILL.md](../SKILL.md).
## Steps 2-3: Find And Diagnose Refresh Candidates
```markdown
## Content Refresh Analysis
| Content | Published | Last Updated | Traffic Trend | Ranking Trend | Priority | Decision |
|---------|-----------|--------------|---------------|---------------|----------|----------|
| [Title] | [date] | [date/Never] | [down/up X%] | [lost/gained X positions] | H/M/L | [refresh/merge/redirect/retire] |
| Traffic Potential | Decline Severity | Decision |
|-------------------|------------------|----------|
| High | High | Refresh immediately |
| High | Low | Schedule refresh |
| Low | High | Evaluate refresh, merge, redirect, or retire |
| Low | Low | Low priority |
## Individual Page Diagnosis: [Title]
**URL**: [URL] | **Published**: [date] | **Last Updated**: [date] | **Word Count**: [X]
| Metric | 6 Mo Ago | Current | Change | Source |
|--------|----------|---------|--------|--------|
| Organic traffic / impressions / CTR / avg position | [values] | [values] | [+/-] | [analytics/GSC/rank tracker] |
| Keyword | Old Position | Current Position | SERP / Intent Change | Refresh Angle |
|---------|--------------|------------------|----------------------|---------------|
| [kw] | [X] | [X] | [AI Overview/PAA/new intent] | [angle] |
```
## Steps 4-5: Define Updates And Plan The Rewrite
```markdown
## Refresh Requirements
| Area | Evidence | Update Needed | Priority |
|------|----------|---------------|----------|
| Year references | "[old year]" | Update only if substance changes | M |
| Statistics | "[old stat]" | Replace with current sourced stat | H |
| Tools/products | "[old tool]" | Add/remove current options | H |
| Broken links | [X broken] | Fix, replace, or remove | H |
| Missing topics | [competitor/PAA evidence] | Add source-backed section | H |
| Images | [old/missing alt/large file] | Replace, compress, add useful alt | M |
### Required SEO/GEO Updates
- [ ] Refresh title/meta only if intent changed
- [ ] Add or update H2s for missing topics
- [ ] Update internal links to newer relevant pages
- [ ] Add FAQ only when questions match real demand
- [ ] Add 40-60 word definition near the start when useful
- [ ] Include quotable statistics with source and publication date
- [ ] Use recent sources, normally from the last 2 years unless canonical
## Refresh Plan
**Current title**: [title]
**Refreshed title**: [title with updated hook if justified]
**New word count target**: [X] words (+/-[Y])
| Section / Asset | Keep / Update / Add / Remove | Current | After Refresh | Source / Reason |
|-----------------|------------------------------|---------|---------------|-----------------|
| Introduction | Update | [issue] | [target] | [reason] |
| [Section] | Keep | [still valid] | [unchanged] | [reason] |
| [New Section] | Add | 0 | [X words] | [competitor/PAA gap] |
| Statistic / Link / Image | Update | [old] | [new] | [source/date or alt/format reason] |
```
## Steps 6-7: Write And GEO-Optimize
```markdown
## Refreshed Content Sections
### Updated Introduction
[Updated hook, primary keyword in first 100 words, fresh source-backed context.]
### New Section: [Title]
[Cover competitor/PAA gap with direct answer, examples, and source-backed facts.]
### Updated Statistics
**Replace**: "[old claim]"
**With**: "[current claim] ([Source], [publication year/date])"
### FAQ
#### [Question matching PAA/common query]?
[Direct 40-60 word answer optimized for snippets and AI citations.]
## GEO Enhancement Checklist
| Element | Requirement |
|---------|-------------|
| Definition | 40-60 words, clear, quotable |
| Quotable statistic | Source + date + standalone wording |
| Q&A | Direct answer first, context second |
| Citations | Recent, authoritative, dated |
| Factual statements | Understandable out of context |
```
## Step 8: Republishing Strategy
```markdown
## Republishing Strategy
| Refresh Level | New Content Share | Date Treatment | Notes |
|---------------|-------------------|----------------|-------|
| Major overhaul | 50%+ | Update published date | Use only when structure/substance materially changed |
| Moderate update | 20-50% | Add or update "Last Updated" date | Most refreshes fit here |
| Minor update | <20% | Keep original date | Fixes or light factual updates only |
**Recommendation**: [Option] because [evidence].
### Technical Implementation
- [ ] Update `dateModified` in schema
- [ ] Update sitemap `lastmod`
- [ ] Clear cache after publishing
- [ ] Resubmit in Search Console when material changes shipped
- [ ] Monitor rankings, traffic, and CTR for 4-6 weeks
### Promotion
- [ ] Share as "updated for [current year]" only for substantial updates
- [ ] Notify email/social audiences when the update changes user value
- [ ] Add fresh internal links from related pages
```
## Step 9: Refresh Report
```markdown
# Content Refresh Report
**Content**: [Title] | **Refresh Date**: [Date] | **Refresh Level**: Major / Moderate / Minor
| Element | Before | After | Evidence |
|---------|--------|-------|----------|
| Word count / sections | [values] | [values] | [delta] |
| Statistics / sources | [outdated] | [current] | [sources + dates] |
| Internal links / FAQ / images | [values] | [values] | [source or rationale] |
| Metric | Current | 30-Day Target | 90-Day Target |
|--------|---------|---------------|---------------|
| Avg position | [X] | [Y] | [Z] |
| Organic traffic | [X]/mo | [Y]/mo | [Z]/mo |
**Next review**: [Date - 6 months from now]
```
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 |