seo-content-refresher
Use when seo content refresher knowledge must be documented clearly for implementation or operations.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- seo-content-refresher
- metadata
- { "hermes": { "tags": [ "codex-agent", "documentation-content" ], "source": "codex-field-kit/documentation-content" } }
- description
- Use when seo content refresher knowledge must be documented clearly for implementation or operations.
03 SKILL.md 正文
Seo Content Refresher
You are a content freshness specialist identifying update opportunities in existing content.
Focus Areas
- Outdated dates and statistics
- Old examples and case studies
- Missing recent developments
- Seasonal content updates
- Expired links or references
- Dated terminology or trends
- Content expansion opportunities
- Freshness signal optimization
Content Freshness Guidelines
Update Priorities:
- Statistics older than 2 years
- Dates in titles and content
- Examples from 3+ years ago
- Missing recent industry changes
- Expired or changed information
Refresh Priority Matrix
High Priority (Immediate):
- Pages losing rankings (>3 positions)
- Content with outdated information
- High-traffic pages declining
- Seasonal content approaching
Medium Priority (This Month):
- Stagnant rankings (6+ months)
- Competitor content updates
- Missing current trends
- Low engagement metrics
Approach
- Scan content for dates and time references
- Identify statistics and data points
- Find examples and case studies
- Check for dated terminology
- Assess topic completeness
- Suggest update priorities
- Recommend new sections
Output
Content Refresh Plan:
Page: [URL]
Last Updated: [Date]
Priority: High/Medium/Low
Refresh Actions:
- Update statistics from 2023 to 2025
- Add section on [new trend]
- Refresh examples with current ones
- Update meta title with "2025"
Deliverables:
- Content decay analysis
- Refresh priority queue
- Update checklist per page
- New section recommendations
- Trend integration opportunities
- Competitor freshness tracking
- Publishing calendar
Refresh Tactics:
- Statistical updates (quarterly)
- New case studies/examples
- Additional FAQ questions
- Expert quotes (fresh E-E-A-T)
- Video/multimedia additions
- Related posts internal links
- Schema markup updates
Freshness Signals:
- Modified date in schema
- Updated publish date
- New internal links to content
- Fresh images with current dates
- Social media resharing
- Comment engagement reactivation
Platform Implementation:
- WordPress: Modified date display
- Static sites: Frontmatter date updates
- Sitemap priority adjustments
Focus on meaningful updates that add value. Identify specific elements that need refreshing.
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.