{"id":"69ff57ba-cde0-4cdc-bd6f-1b78d3d18fbc","entityType":"agent","slug":"clawhub-aaron-he-zhu-content-refresher","name":"Content Refresher","canonicalUrl":"https://www.xpersona.co/agent/clawhub-aaron-he-zhu-content-refresher","canonicalPath":"/agent/clawhub-aaron-he-zhu-content-refresher","generatedAt":"2026-10-09T19:10:43.006Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"description":"Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt... Skill: Content Refresher Owner: aaron-he-zhu Summary: Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt... Tags: latest:2.0.0 Version history: v2.0.0 | 2026-02-14T04:20:42.826Z | auto **Major update with improved usability, triggers, and documentation.** - Added explicit natural language triggers and use case k","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 903 downloads reported by the source. Last updated 4/15/2026.","installCommand":"clawhub skill install kn73qjxwmbna25qq8q051epqt980sys5:content-refresher","sourceUrl":"https://clawhub.ai/aaron-he-zhu/content-refresher","homepage":"https://clawhub.ai/aaron-he-zhu/content-refresher","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/aaron-he-zhu/content-refresher","kind":"source"}],"safetyScore":84,"overallRank":62,"popularityScore":59,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"stars":null,"forks":null,"downloads":903,"packageName":null,"latestVersion":"2.0.0","tractionLabel":"903 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-03-01T01:41:01.062Z","emptyReason":null},"lastUpdatedAt":"2026-04-15T00:45:39.800Z","lastCrawledAt":"2026-03-01T01:41:01.062Z","lastIndexedAt":null,"nextCrawlAt":"2026-03-02T01:41:01.062Z","lastVerifiedAt":null,"highlights":[{"version":"2.0.0","createdAt":"2026-02-14T04:20:42.826Z","changelog":"**Major update with improved usability, triggers, and documentation.** - Added explicit natural language triggers and use case keywords to improve discoverability when users request content refresh or updates. - Expanded and clarified the skill description and metadata to specify when to use this skill versus others. - Included a full skills library directory with navigation and cross-links to related SEO and GEO skills. - Updated author and licensing metadata for clarity and attribution. - No changes to underlying refresh methodology or process instructions.","fileCount":3,"zipByteSize":14869},{"version":"0.1.2","createdAt":"2026-02-11T15:37:49.256Z","changelog":"content-refresher 0.1.2 - Added references/content-decay-signals.md to document signals of content decay. - Revised SKILL.md: updated metadata, removed explicit version field, and added \"geo-relevance\". - No changes to the skill’s logic or commands; documentation updates only.","fileCount":3,"zipByteSize":14230},{"version":"0.1.1","createdAt":"2026-02-10T16:05:52.743Z","changelog":"- Added a skill version header with `version: \"1.0\"` to SKILL.md. - Updated refresh instructions to use dynamic placeholders for the current year and other variables, increasing clarity and flexibility. - Improved table presentation for update requirements by making element/year fields generic (e.g. \"[old year]\" and \"[current year]\"). - No logic changes—documentation and formatting improvements only.","fileCount":null,"zipByteSize":null},{"version":"0.1.0","createdAt":"2026-02-08T14:06:30.562Z","changelog":"Initial release of content-refresher: Helps identify, prioritize, and update outdated content to boost search rankings and traffic. - Analyzes content freshness and performance decline to find refresh candidates. - Assesses CORE-EEAT strengths/weaknesses with a quick scoring matrix to guide improvements. - Identifies gaps vs. competitors and outlines specific, actionable updates for SEO & GEO optimization. - Provides detailed refresh plans, including recommended structural changes and optimization steps. - Supports both automated data connections and manual review, adapting based on available info.","fileCount":null,"zipByteSize":null}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install kn73qjxwmbna25qq8q051epqt980sys5:content-refresher","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T19:10:43.003Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-content-refresher/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"readme":"Skill: Content Refresher\n\nOwner: aaron-he-zhu\n\nSummary: Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt...\n\nTags: latest:2.0.0\n\nVersion history:\n\nv2.0.0 | 2026-02-14T04:20:42.826Z | auto\n\n**Major update with improved usability, triggers, and documentation.**\n\n- Added explicit natural language triggers and use case keywords to improve discoverability when users request content refresh or updates.\n- Expanded and clarified the skill description and metadata to specify when to use this skill versus others.\n- Included a full skills library directory with navigation and cross-links to related SEO and GEO skills.\n- Updated author and licensing metadata for clarity and attribution.\n- No changes to underlying refresh methodology or process instructions.\n\nv0.1.2 | 2026-02-11T15:37:49.256Z | auto\n\ncontent-refresher 0.1.2\n\n- Added references/content-decay-signals.md to document signals of content decay.\n- Revised SKILL.md: updated metadata, removed explicit version field, and added \"geo-relevance\".\n- No changes to the skill’s logic or commands; documentation updates only.\n\nv0.1.1 | 2026-02-10T16:05:52.743Z | auto\n\n- Added a skill version header with `version: \"1.0\"` to SKILL.md.\n- Updated refresh instructions to use dynamic placeholders for the current year and other variables, increasing clarity and flexibility.\n- Improved table presentation for update requirements by making element/year fields generic (e.g. \"[old year]\" and \"[current year]\").\n- No logic changes—documentation and formatting improvements only.\n\nv0.1.0 | 2026-02-08T14:06:30.562Z | auto\n\nInitial release of content-refresher:  \nHelps identify, prioritize, and update outdated content to boost search rankings and traffic.\n\n- Analyzes content freshness and performance decline to find refresh candidates.\n- Assesses CORE-EEAT strengths/weaknesses with a quick scoring matrix to guide improvements.\n- Identifies gaps vs. competitors and outlines specific, actionable updates for SEO & GEO optimization.\n- Provides detailed refresh plans, including recommended structural changes and optimization steps.\n- Supports both automated data connections and manual review, adapting based on available info.\n\nArchive index:\n\nArchive v2.0.0: 3 files, 14869 bytes\n\nFiles: references/content-decay-signals.md (13819b), SKILL.md (27104b), _meta.json (136b)\n\nFile v2.0.0:SKILL.md\n\n---\nname: content-refresher\ndescription: 'Use when the user asks to \"update old content\", \"refresh content\", \"content is outdated\", \"improve declining rankings\", \"revive old blog posts\", \"this post is outdated\", \"traffic is declining on this page\", or \"rankings dropped for this article\". Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and optimizes for current SEO and GEO best practices. For writing new content from scratch, see seo-content-writer. For auditing without rewriting, see on-page-seo-auditor.'\nlicense: Apache-2.0\nmetadata:\n  author: aaron-he-zhu\n  version: \"2.0.0\"\n  geo-relevance: \"medium\"\n  tags:\n    - seo\n    - geo\n    - content refresh\n    - content update\n    - outdated content\n    - content decay\n    - ranking recovery\n    - content optimization\n  triggers:\n    - \"update old content\"\n    - \"refresh content\"\n    - \"content is outdated\"\n    - \"improve declining rankings\"\n    - \"revive old blog posts\"\n    - \"content decay\"\n    - \"ranking dropped\"\n    - \"this post is outdated\"\n    - \"traffic is declining on this page\"\n    - \"rankings dropped for this article\"\n---\n\n# Content Refresher\n\n\n> **[SEO & GEO Skills Library](https://skills.sh/aaron-he-zhu/seo-geo-claude-skills)** · 20 skills for SEO + GEO · Install all: `npx skills add aaron-he-zhu/seo-geo-claude-skills`\n\n<details>\n<summary>Browse all 20 skills</summary>\n\n**Research** · [keyword-research](../../research/keyword-research/) · [competitor-analysis](../../research/competitor-analysis/) · [serp-analysis](../../research/serp-analysis/) · [content-gap-analysis](../../research/content-gap-analysis/)\n\n**Build** · [seo-content-writer](../../build/seo-content-writer/) · [geo-content-optimizer](../../build/geo-content-optimizer/) · [meta-tags-optimizer](../../build/meta-tags-optimizer/) · [schema-markup-generator](../../build/schema-markup-generator/)\n\n**Optimize** · [on-page-seo-auditor](../on-page-seo-auditor/) · [technical-seo-checker](../technical-seo-checker/) · [internal-linking-optimizer](../internal-linking-optimizer/) · **content-refresher**\n\n**Monitor** · [rank-tracker](../../monitor/rank-tracker/) · [backlink-analyzer](../../monitor/backlink-analyzer/) · [performance-reporter](../../monitor/performance-reporter/) · [alert-manager](../../monitor/alert-manager/)\n\n**Cross-cutting** · [content-quality-auditor](../../cross-cutting/content-quality-auditor/) · [domain-authority-auditor](../../cross-cutting/domain-authority-auditor/) · [entity-optimizer](../../cross-cutting/entity-optimizer/) · [memory-management](../../cross-cutting/memory-management/)\n\n</details>\n\nThis skill helps identify and revitalize outdated content to reclaim lost rankings and traffic. It analyzes content freshness, identifies update opportunities, and guides the refresh process for maximum SEO and GEO impact.\n\n## When to Use This Skill\n\n- Content has lost rankings or traffic over time\n- Statistics and information are outdated\n- Competitors have published better content\n- Content needs updating for a new year\n- Industry changes require content updates\n- Adding new sections to existing content\n- Converting old content for GEO optimization\n\n## What This Skill Does\n\n1. **Freshness Analysis**: Identifies outdated content needing updates\n2. **Performance Tracking**: Finds content with declining traffic\n3. **Gap Identification**: Spots missing information competitors have\n4. **Update Prioritization**: Ranks content by refresh potential\n5. **Refresh Recommendations**: Provides specific update guidance\n6. **GEO Enhancement**: Updates content for AI citation potential\n7. **Republishing Strategy**: Advises on date and promotion tactics\n\n## How to Use\n\n### Identify Content to Refresh\n\n```\nFind content on [domain] that needs refreshing\n```\n\n```\nWhich of my blog posts have lost the most traffic?\n```\n\n### Refresh Specific Content\n\n```\nRefresh this article for [current year]: [URL/content]\n```\n\n```\nUpdate this content to outrank [competitor URL]: [your URL]\n```\n\n### Content Refresh Strategy\n\n```\nCreate a content refresh strategy for [domain/topic]\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool category placeholders.\n\n**With ~~analytics + ~~search console + ~~SEO tool connected:**\nClaude can automatically pull historical traffic trends from ~~analytics, fetch impression and ranking data from ~~search console, retrieve keyword position history from ~~SEO tool, and identify content with declining performance. This enables data-driven refresh prioritization.\n\n**With manual data only:**\nAsk the user to provide:\n1. Traffic data or screenshots showing performance trends\n2. Ranking screenshots or history for key pages\n3. Content publish dates and last update dates\n4. List of pages the user suspects need refreshing\n\nProceed with the analysis using provided data. Note in the output which findings are from automated data vs. manual review.\n\n## Instructions\n\nWhen a user requests content refresh help:\n\n1. **CORE-EEAT Quick Score — Identify Weak Dimensions**\n\n   Before refreshing, run a quick CORE-EEAT assessment to focus effort on the weakest areas. Reference: [CORE-EEAT Benchmark](../../references/core-eeat-benchmark.md)\n\n   ```markdown\n   ### CORE-EEAT Quick Assessment\n\n   **Content**: [title or URL]\n   **Content Type**: [type]\n\n   Rapidly score each dimension (estimate 0-100):\n\n   | Dimension | Quick Score | Key Weakness | Refresh Priority |\n   |-----------|-----------|--------------|-----------------|\n   | C — Contextual Clarity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | O — Organization | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | R — Referenceability | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | E — Exclusivity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Exp — Experience | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Ept — Expertise | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | A — Authority | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | T — Trust | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n\n   **Weakest Dimensions** (focus refresh here):\n   1. [Dimension] — [what needs fixing]\n   2. [Dimension] — [what needs fixing]\n\n   **Refresh Strategy**: Focus on 🔴 dimensions first, then 🟡.\n\n   _For full 80-item audit, use [content-quality-auditor](../../cross-cutting/content-quality-auditor/)_\n   ```\n\n2. **Identify Content Refresh Candidates**\n\n   ```markdown\n   ## Content Refresh Analysis\n   \n   ### Refresh Candidate Identification\n   \n   **Criteria for Content Refresh**:\n   - Published more than 6 months ago\n   - Contains dated information (years, statistics)\n   - Declining traffic trend\n   - Lost keyword rankings\n   - Outdated references or broken links\n   - Missing topics competitors now cover\n   - No GEO optimization\n   \n   ### Content Audit Results\n   \n   | Content | Published | Last Updated | Traffic Trend | Priority |\n   |---------|-----------|--------------|---------------|----------|\n   | [Title 1] | [date] | [date] | ↓ -45% | 🔴 High |\n   | [Title 2] | [date] | Never | ↓ -30% | 🔴 High |\n   | [Title 3] | [date] | [date] | ↓ -20% | 🟡 Medium |\n   | [Title 4] | [date] | [date] | → 0% | 🟡 Medium |\n   \n   ### Refresh Prioritization Matrix\n   \n   ```\n   High Traffic + High Decline = 🔴 Refresh Immediately\n   High Traffic + Low Decline = 🟡 Schedule Refresh\n   Low Traffic + High Decline = 🟡 Evaluate & Decide\n   Low Traffic + Low Decline = 🟢 Low Priority\n   ```\n   ```\n\n3. **Analyze Individual Content for Refresh**\n\n   ```markdown\n   ## Content Refresh Analysis: [Title]\n   \n   **URL**: [URL]\n   **Published**: [date]\n   **Last Updated**: [date]\n   **Word Count**: [X]\n   \n   ### Performance Metrics\n   \n   | Metric | 6 Mo Ago | Current | Change |\n   |--------|----------|---------|--------|\n   | Organic Traffic | [X]/mo | [X]/mo | [+/-X]% |\n   | Avg Position | [X] | [X] | [+/-X] |\n   | Impressions | [X] | [X] | [+/-X]% |\n   | CTR | [X]% | [X]% | [+/-X]% |\n   \n   ### Keywords Analysis\n   \n   | Keyword | Old Position | Current Position | Change |\n   |---------|--------------|------------------|--------|\n   | [kw 1] | [X] | [X] | ↓ [X] |\n   | [kw 2] | [X] | [X] | ↓ [X] |\n   | [kw 3] | [X] | [X] | ↓ [X] |\n   \n   ### Why This Content Needs Refresh\n   \n   1. **Outdated information**: [specific examples]\n   2. **Competitive gap**: [what competitors added]\n   3. **Missing topics**: [new subtopics to cover]\n   4. **SEO issues**: [current optimization problems]\n   5. **GEO potential**: [AI citation opportunities]\n   ```\n\n4. **Identify Specific Updates Needed**\n\n   ```markdown\n   ## Refresh Requirements\n   \n   ### Outdated Elements\n   \n   | Element | Current | Update Needed |\n   |---------|---------|---------------|\n   | Year references | \"[old year]\" | Update to [current year] |\n   | Statistics | \"[old stat]\" | Find current data |\n   | Tool mentions | \"[old tool]\" | Add newer tools |\n   | Links | [X] broken | Fix or replace |\n   | Screenshots | Outdated UI | Recapture |\n   \n   ### Missing Information\n   \n   **Topics competitors now cover that you don't**:\n   \n   | Topic | Competitor Coverage | Words Needed | Priority |\n   |-------|---------------------|--------------|----------|\n   | [Topic 1] | 3/5 competitors | ~300 words | High |\n   | [Topic 2] | 2/5 competitors | ~200 words | Medium |\n   | [Topic 3] | 4/5 competitors | ~400 words | High |\n   \n   ### SEO Updates Needed\n   \n   - [ ] Update title tag with current year\n   - [ ] Refresh meta description\n   - [ ] Add new H2 sections for [topics]\n   - [ ] Update internal links to newer content\n   - [ ] Add FAQ section for featured snippets\n   - [ ] Refresh images and add new alt text\n   \n   ### GEO Updates Needed\n   \n   - [ ] Add clear definition at start\n   - [ ] Include quotable statistics with sources\n   - [ ] Add Q&A formatted sections\n   - [ ] Update sources with current citations\n   - [ ] Create standalone factual statements\n   ```\n\n5. **Create Refresh Plan**\n\n   ```markdown\n   ## Content Refresh Plan\n   \n   ### Title/URL\n   **Current**: [current title]\n   **Refreshed**: [updated title with year/hook]\n   \n   ### Structural Changes\n   \n   **Keep As-Is**:\n   - [Section 1] - Still relevant and accurate\n   - [Section 2] - Still relevant and accurate\n   \n   **Update/Expand**:\n   - [Section 3] - Update statistics, add [X] words\n   - [Section 4] - Add new examples from [current year]\n   \n   **Add New Sections**:\n   - [New Section 1] - [description, ~X words]\n   - [New Section 2] - [description, ~X words]\n   - FAQ Section - [X questions for featured snippets]\n   \n   **Remove/Consolidate**:\n   - [Section 5] - Outdated, remove or redirect topic\n   \n   ### Content Additions\n   \n   **New Word Count Target**: [X] words (+[Y] from current)\n   \n   | Section | Current | After Refresh | Notes |\n   |---------|---------|---------------|-------|\n   | Introduction | [X] | [X] | Add hook, update context |\n   | [Section 1] | [X] | [X] | Keep |\n   | [Section 2] | [X] | [X] | Update stats |\n   | [New Section] | 0 | [X] | Add entirely |\n   | FAQ | 0 | [X] | Add for GEO |\n   | Conclusion | [X] | [X] | Update CTA |\n   \n   ### Specific Updates\n   \n   **Statistics to Update**:\n   \n   | Old Statistic | New Statistic | Source |\n   |---------------|---------------|--------|\n   | \"[old stat]\" | \"[find current]\" | [source] |\n   | \"[old stat]\" | \"[find current]\" | [source] |\n   \n   **Links to Update**:\n   \n   | Anchor Text | Old URL | New URL | Reason |\n   |-------------|---------|---------|--------|\n   | \"[anchor]\" | [old] | [new] | Broken |\n   | \"[anchor]\" | [old] | [new] | Better resource |\n   \n   **Images to Update**:\n   \n   | Image | Action | New Alt Text |\n   |-------|--------|--------------|\n   | [img 1] | Replace | \"[keyword-rich alt]\" |\n   | [img 2] | Keep | Update alt text |\n   ```\n\n6. **Write Refresh Content**\n\n   ```markdown\n   ## Refreshed Content Sections\n   \n   ### Updated Introduction\n   \n   [Write new introduction with:]\n   - Updated hook for current year\n   - Fresh statistics\n   - Clear value proposition\n   - Primary keyword in first 100 words\n   \n   ### New Section: [Title]\n   \n   [Write new section covering:]\n   - [Topic competitors now cover]\n   - Current information and examples\n   - GEO-optimized with quotable statements\n   \n   ### Updated Statistics Section\n   \n   **Replace**:\n   > \"[Old statement with outdated stat]\"\n   \n   **With**:\n   > \"[New statement with current stat] (Source, [current year])\"\n   \n   ### New FAQ Section\n   \n   ## Frequently Asked Questions\n   \n   ### [Question matching PAA/common query]?\n   \n   [Direct answer in 40-60 words, optimized for featured snippets]\n   \n   ### [Question 2]?\n   \n   [Direct answer]\n   \n   ### [Question 3]?\n   \n   [Direct answer]\n   ```\n\n7. **Optimize for GEO During Refresh**\n\n   ```markdown\n   ## GEO Enhancement Opportunities\n   \n   ### Add Clear Definitions\n   \n   **Add at start of article**:\n   > **[Topic]** is [clear, quotable definition in 40-60 words that \n   > AI systems can cite directly].\n   \n   ### Add Quotable Statements\n   \n   **Transform**:\n   > \"Email marketing is effective for businesses.\"\n   \n   **Into**:\n   > \"Email marketing delivers an average ROI of $42 for every $1 \n   > invested, making it the highest-ROI digital marketing channel \n   > according to the Data & Marketing Association ([current year]).\"\n   \n   ### Add Q&A Sections\n   \n   Structure content with questions AI might answer:\n   - What is [topic]?\n   - How does [topic] work?\n   - Why is [topic] important?\n   - What are the benefits of [topic]?\n   \n   ### Update Citations\n   \n   - Add sources for all statistics\n   - Link to authoritative references\n   - Include publication dates\n   - Use recent sources (last 2 years)\n   ```\n\n8. **Generate Republishing Strategy**\n\n   ```markdown\n   ## Republishing Strategy\n   \n   ### Date Strategy\n   \n   **Options**:\n   \n   1. **Update Published Date** \n      - Use when: Major overhaul (50%+ new content)\n      - Pros: Signals freshness to Google\n      - Cons: Loses \"original\" authority\n   \n   2. **Add \"Last Updated\" Date**\n      - Use when: Moderate updates (20-50% new)\n      - Pros: Shows both original and fresh\n      - Cons: Original date visible\n   \n   3. **Keep Original Date**\n      - Use when: Minor updates (<20% new)\n      - Pros: Maintains authority\n      - Cons: Doesn't signal update\n   \n   **Recommendation**: [Option X] because [reason]\n   \n   ### Technical Implementation\n   \n   - [ ] Update `dateModified` in schema\n   - [ ] Update sitemap lastmod\n   - [ ] Clear cache after publishing\n   - [ ] Resubmit to ~~search console\n   \n   ### Promotion Strategy\n   \n   **Immediately after refresh**:\n   - [ ] Share on social media as \"updated for [current year]\"\n   - [ ] Send to email list if significant update\n   - [ ] Update internal links with fresh anchors\n   - [ ] Reach out for new backlinks\n   \n   **Track Results**:\n   - [ ] Monitor rankings for 4-6 weeks\n   - [ ] Track traffic changes\n   - [ ] Watch for featured snippet capture\n   - [ ] Check AI citation improvements\n   ```\n\n9. **Create Refresh Report**\n\n   ```markdown\n   # Content Refresh Report\n   \n   ## Summary\n   \n   **Content**: [Title]\n   **Refresh Date**: [Date]\n   **Refresh Level**: [Major/Moderate/Minor]\n   \n   ## Changes Made\n   \n   | Element | Before | After |\n   |---------|--------|-------|\n   | Word count | [X] | [Y] (+[Z]%) |\n   | Sections | [X] | [Y] |\n   | Statistics | [X] outdated | [Y] current |\n   | Internal links | [X] | [Y] |\n   | Images | [X] | [Y] |\n   | FAQ questions | 0 | [X] |\n   \n   ## Updates Completed\n   \n   - [x] Updated title with current year\n   - [x] Refreshed meta description\n   - [x] Added [X] new sections\n   - [x] Updated [X] statistics with sources\n   - [x] Fixed [X] broken links\n   - [x] Added FAQ section for GEO\n   - [x] Implemented FAQ schema\n   - [x] Updated images and alt text\n   \n   ## Expected Outcomes\n   \n   | Metric | Current | 30-Day Target | 90-Day Target |\n   |--------|---------|---------------|---------------|\n   | Avg Position | [X] | [Y] | [Z] |\n   | Organic Traffic | [X]/mo | [Y]/mo | [Z]/mo |\n   | Featured Snippets | 0 | 1+ | 2+ |\n   \n   ## Next Review\n\n   Schedule next refresh review: [Date - 6 months from now]\n   ```\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Target content URL or title clearly identified\n- [ ] Historical performance data available (traffic trends, rankings)\n- [ ] Content publish/update dates known\n- [ ] If comparing to competitors, competitor URLs provided\n\n### Output Validation\n- [ ] Every recommendation cites specific data points (not generic advice)\n- [ ] Outdated elements identified with specific examples and replacement data\n- [ ] All suggested additions include word counts and section locations\n- [ ] Source of each data point clearly stated (~~analytics data, ~~search console, ~~SEO tool, user-provided, or estimated)\n\n## Example\n\n**User**: \"Refresh my blog post about 'best cloud hosting providers'\"\n\n**Output**:\n\n```markdown\n### CORE-EEAT Quick Assessment\n\n**Content**: \"Best Cloud Hosting Providers 2023\"\n**Content Type**: Commercial comparison / listicle\n\n| Dimension | Quick Score | Key Weakness | Refresh Priority |\n|-----------|-----------|--------------|-----------------|\n| C — Contextual Clarity | 60/100 | Title says 2023 — stale intent signal | 🔴 |\n| O — Organization | 75/100 | Good comparison tables but no summary box | 🟡 |\n| R — Referenceability | 35/100 | Pricing from Q1 2023, 3 broken links | 🔴 |\n| E — Exclusivity | 50/100 | No original benchmarks or test data | 🟡 |\n| Exp — Experience | 30/100 | No first-person testing narrative | 🔴 |\n| Ept — Expertise | 65/100 | Author bio present but lacks credentials | 🟡 |\n| A — Authority | 55/100 | 12 backlinks, was ranking page 1 | 🟢 |\n| T — Trust | 60/100 | Affiliate links present but not disclosed | 🔴 |\n\n**Weakest Dimensions** (focus refresh here):\n1. **Experience** — Add hands-on testing results (\"We migrated a test site to each provider\")\n2. **Referenceability** — Replace all 2023 pricing/uptime data with current figures\n\n## Content Refresh Analysis: Best Cloud Hosting Providers 2023\n\n**URL**: cloudhosting.com/best-cloud-hosting\n**Published**: 2023-02-14\n**Last Updated**: Never\n**Word Count**: 2,100\n\n### Performance Metrics\n\n| Metric | 6 Mo Ago | Current | Change |\n|--------|----------|---------|--------|\n| Organic Traffic | 3,200/mo | 1,400/mo | -56% |\n| Avg Position | 4.2 | 14.8 | ↓ 10.6 |\n| Impressions | 18,000 | 9,500 | -47% |\n| CTR | 6.1% | 2.3% | -3.8% |\n\n### Content Decay Signals Identified\n\n1. **Outdated year in title and H1** — \"2023\" signals stale content to users and search engines\n2. **Pricing data 18+ months old** — AWS Lightsail listed at $3.50/mo (now $5/mo), DigitalOcean at $4/mo (now $6/mo)\n3. **Missing new entrants** — No mention of Hetzner Cloud or Vultr, which 4/5 top competitors now cover\n4. **3 broken outbound links** — Provider comparison pages that have moved or been retired\n\n### Refresh vs. Rewrite Decision\n\n| Factor | Assessment |\n|--------|-----------|\n| Content quality | Good structure, solid comparison tables — foundation is sound |\n| URL equity | 12 referring domains, 18 months old |\n| Scope of changes | ~40% of content needs updating |\n| Search intent | Unchanged — still commercial comparison |\n\n**Decision**: **REFRESH** — The URL has earned backlinks, the structure is solid, and less than 50% needs rewriting. Keep the URL, update in place.\n\n## Content Refresh Plan\n\n**Current Title**: \"Best Cloud Hosting Providers 2023\"\n**Refreshed Title**: \"Best Cloud Hosting Providers 2024: 7 Platforms Tested & Compared\"\n\n### Specific Refresh Actions\n\n1. **Update all pricing and specs** (~30 min)\n   - Replace 2023 pricing for all 5 listed providers with current data\n   - Add uptime stats from the last 12 months (source: UptimeRobot public status pages)\n   - Update feature comparison table with current plan tiers\n\n2. **Add 2 missing providers + testing narrative** (~600 words)\n   - Add Hetzner Cloud and Vultr sections with same comparison format\n   - Write intro paragraph: \"We deployed a WordPress benchmark site to each provider and measured TTFB, uptime, and support response times over 30 days\"\n\n3. **Add affiliate disclosure and FAQ section** (~200 words)\n   - Add disclosure statement below introduction: \"This post contains affiliate links. See our editorial policy.\"\n   - Add FAQ with 4 questions targeting People Also Ask (e.g., \"What is the cheapest cloud hosting?\", \"Is cloud hosting faster than shared hosting?\")\n   - Implement FAQ schema markup for rich result eligibility\n\n4. **Fix broken links and update internal links** (~15 min)\n   - Replace 3 broken outbound links with current provider URLs\n   - Add internal links to cloudhosting.com/vps-vs-cloud and cloudhosting.com/hosting-speed-test\n\n### Republishing Strategy\n\n**Recommendation**: Update Published Date — this is a major overhaul (40%+ new content, new providers, fresh test data). Update `dateModified` in Article schema, resubmit URL in Search Console, and share on social as \"Updated for 2024.\"\n\n### Expected Outcomes\n\n| Metric | Current | 30-Day Target | 90-Day Target |\n|--------|---------|---------------|---------------|\n| Avg Position | 14.8 | 8-10 | 3-6 |\n| Organic Traffic | 1,400/mo | 2,200/mo | 3,500/mo |\n| Featured Snippets | 0 | 1 (FAQ) | 2+ |\n```\n\n## Content Refresh Checklist\n\n```markdown\n### Pre-Refresh\n- [ ] Analyze current performance metrics\n- [ ] Identify outdated information\n- [ ] Research competitor updates\n- [ ] Note missing topics\n\n### Content Updates\n- [ ] Update year references\n- [ ] Refresh statistics with sources\n- [ ] Add new examples and case studies\n- [ ] Expand thin sections\n- [ ] Add new relevant sections\n- [ ] Create FAQ section\n\n### SEO Updates\n- [ ] Update title tag\n- [ ] Refresh meta description\n- [ ] Optimize headers\n- [ ] Update internal links\n- [ ] Add new images with alt text\n\n### GEO Updates\n- [ ] Add clear definition\n- [ ] Include quotable statements\n- [ ] Add Q&A formatted content\n- [ ] Update source citations\n\n### Technical\n- [ ] Update schema dateModified\n- [ ] Clear page cache\n- [ ] Update sitemap\n- [ ] Test page speed\n```\n\n## Tips for Success\n\n1. **Prioritize by ROI** - Refresh high-potential content first\n2. **Don't just add dates** - Make substantial improvements\n3. **Beat competitors** - Add what they have and more\n4. **Track results** - Monitor ranking changes post-refresh\n5. **Schedule regular audits** - Check content health quarterly\n6. **Optimize for GEO** - Every refresh is a GEO opportunity\n\n## Content Decay Signal Taxonomy\n\n### Decay Indicators\n\n| Signal | Source | Severity | Detection Method |\n|--------|--------|----------|-----------------|\n| Traffic decline >20% MoM | Analytics | High | Monthly traffic comparison |\n| Position drop >5 positions | Rank tracker | High | Weekly rank monitoring |\n| Outdated statistics/dates | Manual review | Medium | Annual content audit |\n| Broken external links | Crawler | Medium | Monthly crawl reports |\n| Decreased CTR | Search Console | Medium | Quarterly CTR analysis |\n| Competitor new content | SERP monitoring | Medium | Monthly SERP checks |\n| User engagement drop | Analytics | Low | Quarterly engagement review |\n| Index coverage issues | Search Console | High | Weekly coverage monitoring |\n\n### Content Decay Stages\n\n| Stage | Symptoms | Urgency | Recommended Action |\n|-------|---------|---------|-------------------|\n| **Early decay** | Slight traffic/position dip | Low | Monitor for 2-4 weeks |\n| **Active decay** | Consistent decline across 2+ months | Medium | Schedule refresh within 2 weeks |\n| **Significant decay** | 50%+ traffic loss, page 2+ | High | Immediate refresh or rewrite |\n| **Terminal decay** | No organic traffic, deindexed | Critical | Rewrite, redirect, or retire |\n\n## Refresh vs. Rewrite Decision Framework\n\n| Factor | Refresh (Update) | Rewrite (New version) |\n|--------|-----------------|---------------------|\n| Content quality | Good foundation, needs updating | Fundamentally flawed or outdated approach |\n| Position | Was ranking well, now dropping | Never ranked well despite optimization |\n| URL age | 1+ years, has earned backlinks | Young URL with no backlink equity |\n| Backlinks | Has external links pointing to it | No backlinks worth preserving |\n| Scope of changes needed | <50% of content changing | >50% needs rewriting |\n| Search intent | Intent hasn't changed | Search intent has evolved |\n\n**Decision rule:** If the URL has backlinks and was ranking, REFRESH. If not, consider REWRITE at a new URL (with 301 redirect if old URL has any equity).\n\n## Content Lifecycle Model\n\n```\nCREATE → PROMOTE → MAINTAIN → REFRESH → [REFRESH again] or RETIRE\n  │         │          │          │                          │\n  │      Month 1    Month 2-6   Month 6-12              When terminal\n  │    Social,      Monitor     Update facts,            301 redirect\n  │    outreach,    rankings,   add new sections,         to related\n  │    email        fix issues  improve depth              content\n```\n\n### Lifecycle Actions by Phase\n\n| Phase | Duration | Key Actions | Metrics to Track |\n|-------|----------|------------|-----------------|\n| Create | Week 1 | Publish, submit to Search Console | Indexation |\n| Promote | Month 1 | Social shares, email, outreach | Referral traffic, backlinks |\n| Maintain | Months 2-6 | Monitor, fix broken links, respond to comments | Rankings, traffic trend |\n| Refresh | Months 6-12+ | Update data, add sections, improve structure | Traffic recovery, new keywords |\n| Retire | When terminal | 301 redirect to best alternative | Redirect traffic recovery |\n\n## Update Strategy by Content Type\n\n| Content Type | Refresh Frequency | Key Updates | Shelf Life |\n|-------------|-------------------|------------|-----------|\n| Statistics roundups | Every 6 months | Replace old stats, add new sources | 6-12 months |\n| Tool comparisons | Every 3-6 months | Update pricing, features, screenshots | 3-6 months |\n| How-to guides | Annually | Update steps, screenshots, links | 12-18 months |\n| Evergreen guides | Every 12-18 months | Add new sections, update examples | 18-24 months |\n| News/trend content | Don't refresh | Archive or redirect | 1-3 months |\n| Case studies | Rarely | Update results if available | 2-3 years |\n| Glossary/definitions | As needed | Update when definitions evolve | 2-5 years |\n\n## Reference Materials\n\n- [Content Decay Signals](./references/content-decay-signals.md) — Decay indicators, lifecycle stages, and refresh triggers by content type\n\n## Related Skills\n\n- [content-gap-analysis](../../research/content-gap-analysis/) — Find what to add\n- [seo-content-writer](../../build/seo-content-writer/) — Write new sections\n- [geo-content-optimizer](../../build/geo-content-optimizer/) — Enhance for AI\n- [on-page-seo-auditor](../on-page-seo-auditor/) — Audit refreshed content\n- [content-quality-auditor](../../cross-cutting/content-quality-auditor/) — Full 80-item CORE-EEAT audit\n\nFile v2.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn73qjxwmbna25qq8q051epqt980sys5\",\n  \"slug\": \"content-refresher\",\n  \"version\": \"2.0.0\",\n  \"publishedAt\": 1771042842826\n}\n\nFile v2.0.0:references/content-decay-signals.md\n\n# Content Decay Signals\n\nComprehensive decay detection system with automated monitoring setup, severity scoring, refresh playbooks by content type, and ROI estimation for content refresh investments.\n\n## Decay Signal Detection System\n\n### Primary Signals (High Reliability)\n\nThese signals directly indicate content performance decline and should trigger immediate investigation.\n\n#### 1. Organic Traffic Decline\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 10-20% decline | Month-over-month | Add to monitoring list |\n| Warning | 20-40% decline | Month-over-month | Schedule refresh within 2 weeks |\n| Critical | 40-60% decline | Month-over-month | Refresh this week |\n| Emergency | >60% decline | Month-over-month | Investigate immediately (may be technical issue) |\n\n**Detection method**: Compare current month's organic sessions to same month previous year (to account for seasonality) and to previous month (for trend detection).\n\n**False positive check**: Before attributing traffic decline to content decay, rule out:\n- Seasonal variations (compare year-over-year, not just month-over-month)\n- Algorithm updates (check if decline coincides with known Google updates)\n- Technical issues (crawl errors, indexation problems, site speed regression)\n- Tracking code changes (analytics misconfiguration)\n\n#### 2. Ranking Position Drops\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 1-3 positions lost | 2-week average | Monitor |\n| Warning | 3-5 positions lost | 2-week average | Investigate cause |\n| Critical | 5-10 positions lost | 2-week average | Schedule immediate refresh |\n| Emergency | Dropped off page 1 to page 3+ | Any timeframe | Priority refresh or rewrite |\n\n**Detection method**: Track primary keyword positions weekly. Use 2-week rolling averages to smooth daily fluctuations.\n\n#### 3. Click-Through Rate Decline\n\n| Severity | Threshold | Context | Action |\n|----------|-----------|---------|--------|\n| Watch | CTR below expected for position | Position stable, CTR dropping | Review title and meta description |\n| Warning | CTR dropped 20%+ vs. baseline | With stable impressions | Rewrite title tag and meta description |\n| Critical | CTR dropped 40%+ vs. baseline | May indicate stale SERP appearance | Full refresh of title, description, and structured data |\n\n**Expected CTR by position** (organic, desktop, approximate):\n\n| Position | Expected CTR Range | Below This = Investigate |\n|----------|--------------------|-------------------------|\n| 1 | 25-35% | <20% |\n| 2 | 12-18% | <10% |\n| 3 | 8-12% | <6% |\n| 4-5 | 5-8% | <4% |\n| 6-10 | 2-5% | <2% |\n\n---\n\n### Secondary Signals (Moderate Reliability)\n\nThese signals suggest potential decay but may have other causes. Use them to corroborate primary signals.\n\n#### 4. Engagement Metric Decline\n\n| Metric | Decay Indicator | Possible Cause |\n|--------|----------------|---------------|\n| Bounce rate increase >15% | Content no longer satisfies intent | Outdated information, better competitor content |\n| Time on page decrease >20% | Users leaving faster | Content not comprehensive enough |\n| Scroll depth decrease | Users not reading full content | Front-loading outdated info, losing interest |\n| Pages per session decrease | Users not exploring further | Poor internal linking, irrelevant content |\n\n#### 5. Content Freshness Indicators\n\n| Indicator | Decay Risk | Detection |\n|-----------|-----------|-----------|\n| Published >12 months ago, never updated | High | CMS date audit |\n| Contains year references 2+ years old | High | Text search for year patterns |\n| Statistics from 3+ years ago | Medium | Manual review or text search for \"20XX\" |\n| Broken external links (>10% of total) | Medium | Monthly crawl report |\n| Screenshots of outdated UI | Medium | Manual visual review |\n| References to discontinued products/tools | High | Manual review |\n\n#### 6. Competitive Displacement Signals\n\n| Signal | Detection Method | Severity |\n|--------|-----------------|----------|\n| New competitor content ranking above you | SERP monitoring | High |\n| Competitor content is longer and more comprehensive | Manual comparison | Medium |\n| Competitor has more recent publication date displayed in SERP | SERP monitoring | Medium |\n| Featured snippet lost to competitor | SERP monitoring | High |\n| AI overview now answers query without click | SERP monitoring | High |\n\n---\n\n### Tertiary Signals (Low Reliability, Supporting Evidence)\n\nThese signals alone do not indicate decay but strengthen the case when combined with primary or secondary signals.\n\n| Signal | What It Suggests |\n|--------|-----------------|\n| Fewer social shares over time | Content less share-worthy (may be stale) |\n| Decrease in backlink acquisition | Content no longer being cited as a resource |\n| Fewer comments or engagement | Community interest waning |\n| Content not appearing in AI responses | Not structured for GEO or information is outdated |\n\n---\n\n## Automated Monitoring Setup\n\n### Monitoring Dashboard Configuration\n\nSet up these automated checks to catch decay early.\n\n#### Weekly Checks\n\n| Check | Data Source | Alert Threshold |\n|-------|-----------|----------------|\n| Keyword position changes | Rank tracker | Any target keyword drops >3 positions |\n| Crawl errors on key pages | Search Console | Any new crawl error on monitored pages |\n| Index coverage changes | Search Console | Any page drops from index |\n\n#### Monthly Checks\n\n| Check | Data Source | Alert Threshold |\n|-------|-----------|----------------|\n| Traffic comparison (MoM) | Analytics | >15% decline on any monitored page |\n| CTR comparison | Search Console | >20% CTR decline for any target keyword |\n| Broken link scan | Crawler | Any new broken links on monitored pages |\n| Competitor SERP changes | SERP tracker | New competitor enters top 5 |\n\n#### Quarterly Checks\n\n| Check | Data Source | Process |\n|-------|-----------|---------|\n| Content freshness audit | CMS + manual | Review all content older than 6 months |\n| Statistics accuracy check | Manual | Verify top 20 pages have current data |\n| Engagement trend review | Analytics | Compare engagement metrics across quarters |\n| Full competitive content gap | SEO tool | Identify new competitor content opportunities |\n\n### Alert Priority Matrix\n\nWhen multiple signals fire simultaneously, use this matrix to determine response urgency.\n\n| Primary Signal + Secondary Signal | Priority | Response |\n|----------------------------------|----------|----------|\n| Traffic decline + Position drop | P1 (Critical) | Refresh within 48 hours |\n| Traffic decline + CTR decline | P1 (Critical) | Rewrite title/description immediately, schedule content refresh |\n| Position drop + Competitor displacement | P2 (High) | Refresh within 1 week |\n| Traffic decline + Engagement decline | P2 (High) | Refresh within 1 week |\n| CTR decline only | P3 (Medium) | Rewrite title and meta description this week |\n| Freshness indicators only | P3 (Medium) | Schedule refresh within 2 weeks |\n| Engagement decline only | P4 (Low) | Investigate and schedule if confirmed |\n\n---\n\n## Decay Severity Scoring\n\n### Composite Decay Score\n\nCalculate a 0-100 decay severity score by summing weighted signal scores.\n\n| Signal Category | Weight | Score Range |\n|----------------|--------|-------------|\n| Traffic decline | 30% | 0 = no decline, 100 = >60% decline |\n| Position drops | 25% | 0 = stable, 100 = dropped off page 1 |\n| CTR decline | 15% | 0 = stable, 100 = >40% decline |\n| Content freshness | 15% | 0 = updated this quarter, 100 = >2 years stale |\n| Competitive displacement | 15% | 0 = no new competitors, 100 = displaced from top 3 |\n\n### Score Interpretation\n\n| Composite Score | Decay Stage | Action |\n|----------------|-------------|--------|\n| 0-20 | Healthy | Continue monitoring |\n| 21-40 | Early decay | Add to refresh queue (next month) |\n| 41-60 | Active decay | Schedule refresh (this week) |\n| 61-80 | Significant decay | Immediate refresh or rewrite decision |\n| 81-100 | Terminal decay | Rewrite, redirect, or retire |\n\n---\n\n## Refresh Playbooks by Content Type\n\n### Blog Post / Article Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Update title with current year or hook | 10 min |\n| 2 | Rewrite introduction with fresh angle | 20 min |\n| 3 | Update all statistics with current sources | 30-60 min |\n| 4 | Add 1-2 new sections covering gaps | 60-90 min |\n| 5 | Update screenshots and images | 30 min |\n| 6 | Add or update FAQ section | 20 min |\n| 7 | Refresh internal links | 15 min |\n| 8 | Update meta description | 5 min |\n| 9 | Add/update schema markup | 10 min |\n| 10 | Update dateModified and republish | 5 min |\n| **Total** | | **3-4 hours** |\n\n### Product/Service Page Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Update pricing, features, specifications | 30 min |\n| 2 | Add new customer testimonials/reviews | 20 min |\n| 3 | Update product images | 30 min |\n| 4 | Refresh comparison tables | 20 min |\n| 5 | Update internal links to related products | 15 min |\n| 6 | Verify and update schema markup | 10 min |\n| **Total** | | **2-2.5 hours** |\n\n### Statistics/Data Roundup Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Verify every statistic is still current | 60-90 min |\n| 2 | Replace outdated stats with current data | 60 min |\n| 3 | Add new statistics from recent studies | 30 min |\n| 4 | Update source links and citations | 30 min |\n| 5 | Update year references throughout | 15 min |\n| 6 | Add new visualization if data changed significantly | 30 min |\n| 7 | Update title, meta description with year | 10 min |\n| **Total** | | **4-5 hours** |\n\n### How-To Guide Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Verify all steps are still accurate | 30 min |\n| 2 | Update screenshots for UI changes | 60 min |\n| 3 | Add new methods or alternative approaches | 30 min |\n| 4 | Update tool recommendations | 15 min |\n| 5 | Add troubleshooting section if missing | 20 min |\n| 6 | Update FAQ with new common questions | 15 min |\n| 7 | Test all links and embedded resources | 15 min |\n| **Total** | | **3-3.5 hours** |\n\n---\n\n## ROI Estimation for Content Refresh\n\n### Cost-Benefit Framework\n\n| Factor | Measurement |\n|--------|------------|\n| **Cost of refresh** | Writer hours x hourly rate + tool costs |\n| **Current monthly traffic value** | Organic sessions x conversion rate x avg order value |\n| **Projected traffic recovery** | Based on decay stage and content potential |\n| **Time to recover** | Typically 4-8 weeks for rankings to respond |\n\n### Traffic Recovery Benchmarks\n\nBased on industry data for content refreshes (not rewrites):\n\n| Decay Stage at Refresh | Typical Traffic Recovery | Recovery Timeline |\n|------------------------|------------------------|-------------------|\n| Early decay | 90-110% of peak (often exceeds) | 2-4 weeks |\n| Active decay | 70-90% of peak | 4-8 weeks |\n| Significant decay | 40-70% of peak | 6-12 weeks |\n| Terminal decay | 10-40% of peak (rewrite may be better) | 8-16 weeks |\n\n### ROI Calculation Template\n\n```\nRefresh Cost:\n  Writer time: [X hours] x [$Y/hour] = $[Z]\n  Tool costs: $[A] (one-time crawl, research tools)\n  Total cost: $[Z + A]\n\nMonthly Traffic Value (before decay):\n  Peak monthly organic sessions: [N]\n  Conversion rate: [X]%\n  Average conversion value: $[Y]\n  Peak monthly value: [N] x [X]% x $[Y] = $[V]\n\nExpected Recovery:\n  Projected recovery: [%] of peak = $[V x %] per month\n  Current monthly value: $[current]\n  Monthly value increase: $[V x % - current]\n\nROI:\n  Payback period: $[total cost] / $[monthly value increase] = [months]\n  12-month ROI: ($[monthly value increase] x 12 - $[total cost]) / $[total cost] x 100 = [X]%\n```\n\n### Refresh Priority Scoring\n\nWhen choosing which content to refresh first, score each candidate:\n\n| Factor | Weight | Score (1-10) |\n|--------|--------|-------------|\n| Current traffic value | 25% | Higher traffic = higher score |\n| Decay severity | 20% | More decay = more urgency |\n| Competitive opportunity | 20% | Weaker competition = higher score |\n| Refresh difficulty | 15% | Easier refresh = higher score |\n| Strategic importance | 10% | Aligns with business goals = higher score |\n| Backlink equity | 10% | More backlinks = more worth preserving |\n\n**Priority formula**: Weighted score total. Refresh highest-scoring content first.\n\n---\n\n## Content Retirement Decision\n\nNot all decaying content should be refreshed. Use this checklist to decide when to retire content instead.\n\n### Retire When\n\n- [ ] Content targets a keyword with zero search volume\n- [ ] Topic is no longer relevant to your business\n- [ ] No backlinks worth preserving\n- [ ] Content never ranked well even when fresh\n- [ ] Cost to refresh exceeds projected 12-month value recovery\n- [ ] Content cannibalizes a better-performing page on the same topic\n\n### Retirement Options\n\n| Option | When to Use | Implementation |\n|--------|------------|---------------|\n| 301 redirect | Content has backlinks or residual traffic | Redirect to best related page |\n| Consolidate | Multiple weak pages on same topic | Merge into one strong page, redirect others |\n| Noindex | Page has internal utility but should not rank | Add noindex, keep page accessible |\n| Delete (410) | Content has no value, no links, no traffic | Return 410 Gone status |\n\n### Post-Retirement Monitoring\n\nAfter retiring content, monitor for 4 weeks:\n- Verify redirects are working (no 404 errors)\n- Check that target pages are receiving redirected traffic\n- Monitor rankings of consolidated/target pages\n- Ensure no orphan pages were created by removing internal links\n\nArchive v0.1.2: 3 files, 14230 bytes\n\nFiles: references/content-decay-signals.md (13819b), SKILL.md (24701b), _meta.json (136b)\n\nFile v0.1.2:SKILL.md\n\n---\nname: content-refresher\ndescription: Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and optimizes for current SEO and GEO best practices.\ngeo-relevance: \"medium\"\n---\n\n# Content Refresher\n\nThis skill helps identify and revitalize outdated content to reclaim lost rankings and traffic. It analyzes content freshness, identifies update opportunities, and guides the refresh process for maximum SEO and GEO impact.\n\n## When to Use This Skill\n\n- Content has lost rankings or traffic over time\n- Statistics and information are outdated\n- Competitors have published better content\n- Content needs updating for a new year\n- Industry changes require content updates\n- Adding new sections to existing content\n- Converting old content for GEO optimization\n\n## What This Skill Does\n\n1. **Freshness Analysis**: Identifies outdated content needing updates\n2. **Performance Tracking**: Finds content with declining traffic\n3. **Gap Identification**: Spots missing information competitors have\n4. **Update Prioritization**: Ranks content by refresh potential\n5. **Refresh Recommendations**: Provides specific update guidance\n6. **GEO Enhancement**: Updates content for AI citation potential\n7. **Republishing Strategy**: Advises on date and promotion tactics\n\n## How to Use\n\n### Identify Content to Refresh\n\n```\nFind content on [domain] that needs refreshing\n```\n\n```\nWhich of my blog posts have lost the most traffic?\n```\n\n### Refresh Specific Content\n\n```\nRefresh this article for [current year]: [URL/content]\n```\n\n```\nUpdate this content to outrank [competitor URL]: [your URL]\n```\n\n### Content Refresh Strategy\n\n```\nCreate a content refresh strategy for [domain/topic]\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool category placeholders.\n\n**With ~~analytics + ~~search console + ~~SEO tool connected:**\nClaude can automatically pull historical traffic trends from ~~analytics, fetch impression and ranking data from ~~search console, retrieve keyword position history from ~~SEO tool, and identify content with declining performance. This enables data-driven refresh prioritization.\n\n**With manual data only:**\nAsk the user to provide:\n1. Traffic data or screenshots showing performance trends\n2. Ranking screenshots or history for key pages\n3. Content publish dates and last update dates\n4. List of pages the user suspects need refreshing\n\nProceed with the analysis using provided data. Note in the output which findings are from automated data vs. manual review.\n\n## Instructions\n\nWhen a user requests content refresh help:\n\n1. **CORE-EEAT Quick Score — Identify Weak Dimensions**\n\n   Before refreshing, run a quick CORE-EEAT assessment to focus effort on the weakest areas. Reference: [CORE-EEAT Benchmark](../../references/core-eeat-benchmark.md)\n\n   ```markdown\n   ### CORE-EEAT Quick Assessment\n\n   **Content**: [title or URL]\n   **Content Type**: [type]\n\n   Rapidly score each dimension (estimate 0-100):\n\n   | Dimension | Quick Score | Key Weakness | Refresh Priority |\n   |-----------|-----------|--------------|-----------------|\n   | C — Contextual Clarity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | O — Organization | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | R — Referenceability | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | E — Exclusivity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Exp — Experience | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Ept — Expertise | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | A — Authority | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | T — Trust | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n\n   **Weakest Dimensions** (focus refresh here):\n   1. [Dimension] — [what needs fixing]\n   2. [Dimension] — [what needs fixing]\n\n   **Refresh Strategy**: Focus on 🔴 dimensions first, then 🟡.\n\n   _For full 80-item audit, use [content-quality-auditor](../../cross-cutting/content-quality-auditor/)_\n   ```\n\n2. **Identify Content Refresh Candidates**\n\n   ```markdown\n   ## Content Refresh Analysis\n   \n   ### Refresh Candidate Identification\n   \n   **Criteria for Content Refresh**:\n   - Published more than 6 months ago\n   - Contains dated information (years, statistics)\n   - Declining traffic trend\n   - Lost keyword rankings\n   - Outdated references or broken links\n   - Missing topics competitors now cover\n   - No GEO optimization\n   \n   ### Content Audit Results\n   \n   | Content | Published | Last Updated | Traffic Trend | Priority |\n   |---------|-----------|--------------|---------------|----------|\n   | [Title 1] | [date] | [date] | ↓ -45% | 🔴 High |\n   | [Title 2] | [date] | Never | ↓ -30% | 🔴 High |\n   | [Title 3] | [date] | [date] | ↓ -20% | 🟡 Medium |\n   | [Title 4] | [date] | [date] | → 0% | 🟡 Medium |\n   \n   ### Refresh Prioritization Matrix\n   \n   ```\n   High Traffic + High Decline = 🔴 Refresh Immediately\n   High Traffic + Low Decline = 🟡 Schedule Refresh\n   Low Traffic + High Decline = 🟡 Evaluate & Decide\n   Low Traffic + Low Decline = 🟢 Low Priority\n   ```\n   ```\n\n3. **Analyze Individual Content for Refresh**\n\n   ```markdown\n   ## Content Refresh Analysis: [Title]\n   \n   **URL**: [URL]\n   **Published**: [date]\n   **Last Updated**: [date]\n   **Word Count**: [X]\n   \n   ### Performance Metrics\n   \n   | Metric | 6 Mo Ago | Current | Change |\n   |--------|----------|---------|--------|\n   | Organic Traffic | [X]/mo | [X]/mo | [+/-X]% |\n   | Avg Position | [X] | [X] | [+/-X] |\n   | Impressions | [X] | [X] | [+/-X]% |\n   | CTR | [X]% | [X]% | [+/-X]% |\n   \n   ### Keywords Analysis\n   \n   | Keyword | Old Position | Current Position | Change |\n   |---------|--------------|------------------|--------|\n   | [kw 1] | [X] | [X] | ↓ [X] |\n   | [kw 2] | [X] | [X] | ↓ [X] |\n   | [kw 3] | [X] | [X] | ↓ [X] |\n   \n   ### Why This Content Needs Refresh\n   \n   1. **Outdated information**: [specific examples]\n   2. **Competitive gap**: [what competitors added]\n   3. **Missing topics**: [new subtopics to cover]\n   4. **SEO issues**: [current optimization problems]\n   5. **GEO potential**: [AI citation opportunities]\n   ```\n\n4. **Identify Specific Updates Needed**\n\n   ```markdown\n   ## Refresh Requirements\n   \n   ### Outdated Elements\n   \n   | Element | Current | Update Needed |\n   |---------|---------|---------------|\n   | Year references | \"[old year]\" | Update to [current year] |\n   | Statistics | \"[old stat]\" | Find current data |\n   | Tool mentions | \"[old tool]\" | Add newer tools |\n   | Links | [X] broken | Fix or replace |\n   | Screenshots | Outdated UI | Recapture |\n   \n   ### Missing Information\n   \n   **Topics competitors now cover that you don't**:\n   \n   | Topic | Competitor Coverage | Words Needed | Priority |\n   |-------|---------------------|--------------|----------|\n   | [Topic 1] | 3/5 competitors | ~300 words | High |\n   | [Topic 2] | 2/5 competitors | ~200 words | Medium |\n   | [Topic 3] | 4/5 competitors | ~400 words | High |\n   \n   ### SEO Updates Needed\n   \n   - [ ] Update title tag with current year\n   - [ ] Refresh meta description\n   - [ ] Add new H2 sections for [topics]\n   - [ ] Update internal links to newer content\n   - [ ] Add FAQ section for featured snippets\n   - [ ] Refresh images and add new alt text\n   \n   ### GEO Updates Needed\n   \n   - [ ] Add clear definition at start\n   - [ ] Include quotable statistics with sources\n   - [ ] Add Q&A formatted sections\n   - [ ] Update sources with current citations\n   - [ ] Create standalone factual statements\n   ```\n\n5. **Create Refresh Plan**\n\n   ```markdown\n   ## Content Refresh Plan\n   \n   ### Title/URL\n   **Current**: [current title]\n   **Refreshed**: [updated title with year/hook]\n   \n   ### Structural Changes\n   \n   **Keep As-Is**:\n   - [Section 1] - Still relevant and accurate\n   - [Section 2] - Still relevant and accurate\n   \n   **Update/Expand**:\n   - [Section 3] - Update statistics, add [X] words\n   - [Section 4] - Add new examples from [current year]\n   \n   **Add New Sections**:\n   - [New Section 1] - [description, ~X words]\n   - [New Section 2] - [description, ~X words]\n   - FAQ Section - [X questions for featured snippets]\n   \n   **Remove/Consolidate**:\n   - [Section 5] - Outdated, remove or redirect topic\n   \n   ### Content Additions\n   \n   **New Word Count Target**: [X] words (+[Y] from current)\n   \n   | Section | Current | After Refresh | Notes |\n   |---------|---------|---------------|-------|\n   | Introduction | [X] | [X] | Add hook, update context |\n   | [Section 1] | [X] | [X] | Keep |\n   | [Section 2] | [X] | [X] | Update stats |\n   | [New Section] | 0 | [X] | Add entirely |\n   | FAQ | 0 | [X] | Add for GEO |\n   | Conclusion | [X] | [X] | Update CTA |\n   \n   ### Specific Updates\n   \n   **Statistics to Update**:\n   \n   | Old Statistic | New Statistic | Source |\n   |---------------|---------------|--------|\n   | \"[old stat]\" | \"[find current]\" | [source] |\n   | \"[old stat]\" | \"[find current]\" | [source] |\n   \n   **Links to Update**:\n   \n   | Anchor Text | Old URL | New URL | Reason |\n   |-------------|---------|---------|--------|\n   | \"[anchor]\" | [old] | [new] | Broken |\n   | \"[anchor]\" | [old] | [new] | Better resource |\n   \n   **Images to Update**:\n   \n   | Image | Action | New Alt Text |\n   |-------|--------|--------------|\n   | [img 1] | Replace | \"[keyword-rich alt]\" |\n   | [img 2] | Keep | Update alt text |\n   ```\n\n6. **Write Refresh Content**\n\n   ```markdown\n   ## Refreshed Content Sections\n   \n   ### Updated Introduction\n   \n   [Write new introduction with:]\n   - Updated hook for current year\n   - Fresh statistics\n   - Clear value proposition\n   - Primary keyword in first 100 words\n   \n   ### New Section: [Title]\n   \n   [Write new section covering:]\n   - [Topic competitors now cover]\n   - Current information and examples\n   - GEO-optimized with quotable statements\n   \n   ### Updated Statistics Section\n   \n   **Replace**:\n   > \"[Old statement with outdated stat]\"\n   \n   **With**:\n   > \"[New statement with current stat] (Source, [current year])\"\n   \n   ### New FAQ Section\n   \n   ## Frequently Asked Questions\n   \n   ### [Question matching PAA/common query]?\n   \n   [Direct answer in 40-60 words, optimized for featured snippets]\n   \n   ### [Question 2]?\n   \n   [Direct answer]\n   \n   ### [Question 3]?\n   \n   [Direct answer]\n   ```\n\n7. **Optimize for GEO During Refresh**\n\n   ```markdown\n   ## GEO Enhancement Opportunities\n   \n   ### Add Clear Definitions\n   \n   **Add at start of article**:\n   > **[Topic]** is [clear, quotable definition in 40-60 words that \n   > AI systems can cite directly].\n   \n   ### Add Quotable Statements\n   \n   **Transform**:\n   > \"Email marketing is effective for businesses.\"\n   \n   **Into**:\n   > \"Email marketing delivers an average ROI of $42 for every $1 \n   > invested, making it the highest-ROI digital marketing channel \n   > according to the Data & Marketing Association ([current year]).\"\n   \n   ### Add Q&A Sections\n   \n   Structure content with questions AI might answer:\n   - What is [topic]?\n   - How does [topic] work?\n   - Why is [topic] important?\n   - What are the benefits of [topic]?\n   \n   ### Update Citations\n   \n   - Add sources for all statistics\n   - Link to authoritative references\n   - Include publication dates\n   - Use recent sources (last 2 years)\n   ```\n\n8. **Generate Republishing Strategy**\n\n   ```markdown\n   ## Republishing Strategy\n   \n   ### Date Strategy\n   \n   **Options**:\n   \n   1. **Update Published Date** \n      - Use when: Major overhaul (50%+ new content)\n      - Pros: Signals freshness to Google\n      - Cons: Loses \"original\" authority\n   \n   2. **Add \"Last Updated\" Date**\n      - Use when: Moderate updates (20-50% new)\n      - Pros: Shows both original and fresh\n      - Cons: Original date visible\n   \n   3. **Keep Original Date**\n      - Use when: Minor updates (<20% new)\n      - Pros: Maintains authority\n      - Cons: Doesn't signal update\n   \n   **Recommendation**: [Option X] because [reason]\n   \n   ### Technical Implementation\n   \n   - [ ] Update `dateModified` in schema\n   - [ ] Update sitemap lastmod\n   - [ ] Clear cache after publishing\n   - [ ] Resubmit to ~~search console\n   \n   ### Promotion Strategy\n   \n   **Immediately after refresh**:\n   - [ ] Share on social media as \"updated for [current year]\"\n   - [ ] Send to email list if significant update\n   - [ ] Update internal links with fresh anchors\n   - [ ] Reach out for new backlinks\n   \n   **Track Results**:\n   - [ ] Monitor rankings for 4-6 weeks\n   - [ ] Track traffic changes\n   - [ ] Watch for featured snippet capture\n   - [ ] Check AI citation improvements\n   ```\n\n9. **Create Refresh Report**\n\n   ```markdown\n   # Content Refresh Report\n   \n   ## Summary\n   \n   **Content**: [Title]\n   **Refresh Date**: [Date]\n   **Refresh Level**: [Major/Moderate/Minor]\n   \n   ## Changes Made\n   \n   | Element | Before | After |\n   |---------|--------|-------|\n   | Word count | [X] | [Y] (+[Z]%) |\n   | Sections | [X] | [Y] |\n   | Statistics | [X] outdated | [Y] current |\n   | Internal links | [X] | [Y] |\n   | Images | [X] | [Y] |\n   | FAQ questions | 0 | [X] |\n   \n   ## Updates Completed\n   \n   - [x] Updated title with current year\n   - [x] Refreshed meta description\n   - [x] Added [X] new sections\n   - [x] Updated [X] statistics with sources\n   - [x] Fixed [X] broken links\n   - [x] Added FAQ section for GEO\n   - [x] Implemented FAQ schema\n   - [x] Updated images and alt text\n   \n   ## Expected Outcomes\n   \n   | Metric | Current | 30-Day Target | 90-Day Target |\n   |--------|---------|---------------|---------------|\n   | Avg Position | [X] | [Y] | [Z] |\n   | Organic Traffic | [X]/mo | [Y]/mo | [Z]/mo |\n   | Featured Snippets | 0 | 1+ | 2+ |\n   \n   ## Next Review\n\n   Schedule next refresh review: [Date - 6 months from now]\n   ```\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Target content URL or title clearly identified\n- [ ] Historical performance data available (traffic trends, rankings)\n- [ ] Content publish/update dates known\n- [ ] If comparing to competitors, competitor URLs provided\n\n### Output Validation\n- [ ] Every recommendation cites specific data points (not generic advice)\n- [ ] Outdated elements identified with specific examples and replacement data\n- [ ] All suggested additions include word counts and section locations\n- [ ] Source of each data point clearly stated (~~analytics data, ~~search console, ~~SEO tool, user-provided, or estimated)\n\n## Example\n\n**User**: \"Refresh my blog post about 'best cloud hosting providers'\"\n\n**Output**:\n\n```markdown\n### CORE-EEAT Quick Assessment\n\n**Content**: \"Best Cloud Hosting Providers 2023\"\n**Content Type**: Commercial comparison / listicle\n\n| Dimension | Quick Score | Key Weakness | Refresh Priority |\n|-----------|-----------|--------------|-----------------|\n| C — Contextual Clarity | 60/100 | Title says 2023 — stale intent signal | 🔴 |\n| O — Organization | 75/100 | Good comparison tables but no summary box | 🟡 |\n| R — Referenceability | 35/100 | Pricing from Q1 2023, 3 broken links | 🔴 |\n| E — Exclusivity | 50/100 | No original benchmarks or test data | 🟡 |\n| Exp — Experience | 30/100 | No first-person testing narrative | 🔴 |\n| Ept — Expertise | 65/100 | Author bio present but lacks credentials | 🟡 |\n| A — Authority | 55/100 | 12 backlinks, was ranking page 1 | 🟢 |\n| T — Trust | 60/100 | Affiliate links present but not disclosed | 🔴 |\n\n**Weakest Dimensions** (focus refresh here):\n1. **Experience** — Add hands-on testing results (\"We migrated a test site to each provider\")\n2. **Referenceability** — Replace all 2023 pricing/uptime data with current figures\n\n## Content Refresh Analysis: Best Cloud Hosting Providers 2023\n\n**URL**: cloudhosting.com/best-cloud-hosting\n**Published**: 2023-02-14\n**Last Updated**: Never\n**Word Count**: 2,100\n\n### Performance Metrics\n\n| Metric | 6 Mo Ago | Current | Change |\n|--------|----------|---------|--------|\n| Organic Traffic | 3,200/mo | 1,400/mo | -56% |\n| Avg Position | 4.2 | 14.8 | ↓ 10.6 |\n| Impressions | 18,000 | 9,500 | -47% |\n| CTR | 6.1% | 2.3% | -3.8% |\n\n### Content Decay Signals Identified\n\n1. **Outdated year in title and H1** — \"2023\" signals stale content to users and search engines\n2. **Pricing data 18+ months old** — AWS Lightsail listed at $3.50/mo (now $5/mo), DigitalOcean at $4/mo (now $6/mo)\n3. **Missing new entrants** — No mention of Hetzner Cloud or Vultr, which 4/5 top competitors now cover\n4. **3 broken outbound links** — Provider comparison pages that have moved or been retired\n\n### Refresh vs. Rewrite Decision\n\n| Factor | Assessment |\n|--------|-----------|\n| Content quality | Good structure, solid comparison tables — foundation is sound |\n| URL equity | 12 referring domains, 18 months old |\n| Scope of changes | ~40% of content needs updating |\n| Search intent | Unchanged — still commercial comparison |\n\n**Decision**: **REFRESH** — The URL has earned backlinks, the structure is solid, and less than 50% needs rewriting. Keep the URL, update in place.\n\n## Content Refresh Plan\n\n**Current Title**: \"Best Cloud Hosting Providers 2023\"\n**Refreshed Title**: \"Best Cloud Hosting Providers 2024: 7 Platforms Tested & Compared\"\n\n### Specific Refresh Actions\n\n1. **Update all pricing and specs** (~30 min)\n   - Replace 2023 pricing for all 5 listed providers with current data\n   - Add uptime stats from the last 12 months (source: UptimeRobot public status pages)\n   - Update feature comparison table with current plan tiers\n\n2. **Add 2 missing providers + testing narrative** (~600 words)\n   - Add Hetzner Cloud and Vultr sections with same comparison format\n   - Write intro paragraph: \"We deployed a WordPress benchmark site to each provider and measured TTFB, uptime, and support response times over 30 days\"\n\n3. **Add affiliate disclosure and FAQ section** (~200 words)\n   - Add disclosure statement below introduction: \"This post contains affiliate links. See our editorial policy.\"\n   - Add FAQ with 4 questions targeting People Also Ask (e.g., \"What is the cheapest cloud hosting?\", \"Is cloud hosting faster than shared hosting?\")\n   - Implement FAQ schema markup for rich result eligibility\n\n4. **Fix broken links and update internal links** (~15 min)\n   - Replace 3 broken outbound links with current provider URLs\n   - Add internal links to cloudhosting.com/vps-vs-cloud and cloudhosting.com/hosting-speed-test\n\n### Republishing Strategy\n\n**Recommendation**: Update Published Date — this is a major overhaul (40%+ new content, new providers, fresh test data). Update `dateModified` in Article schema, resubmit URL in Search Console, and share on social as \"Updated for 2024.\"\n\n### Expected Outcomes\n\n| Metric | Current | 30-Day Target | 90-Day Target |\n|--------|---------|---------------|---------------|\n| Avg Position | 14.8 | 8-10 | 3-6 |\n| Organic Traffic | 1,400/mo | 2,200/mo | 3,500/mo |\n| Featured Snippets | 0 | 1 (FAQ) | 2+ |\n```\n\n## Content Refresh Checklist\n\n```markdown\n### Pre-Refresh\n- [ ] Analyze current performance metrics\n- [ ] Identify outdated information\n- [ ] Research competitor updates\n- [ ] Note missing topics\n\n### Content Updates\n- [ ] Update year references\n- [ ] Refresh statistics with sources\n- [ ] Add new examples and case studies\n- [ ] Expand thin sections\n- [ ] Add new relevant sections\n- [ ] Create FAQ section\n\n### SEO Updates\n- [ ] Update title tag\n- [ ] Refresh meta description\n- [ ] Optimize headers\n- [ ] Update internal links\n- [ ] Add new images with alt text\n\n### GEO Updates\n- [ ] Add clear definition\n- [ ] Include quotable statements\n- [ ] Add Q&A formatted content\n- [ ] Update source citations\n\n### Technical\n- [ ] Update schema dateModified\n- [ ] Clear page cache\n- [ ] Update sitemap\n- [ ] Test page speed\n```\n\n## Tips for Success\n\n1. **Prioritize by ROI** - Refresh high-potential content first\n2. **Don't just add dates** - Make substantial improvements\n3. **Beat competitors** - Add what they have and more\n4. **Track results** - Monitor ranking changes post-refresh\n5. **Schedule regular audits** - Check content health quarterly\n6. **Optimize for GEO** - Every refresh is a GEO opportunity\n\n## Content Decay Signal Taxonomy\n\n### Decay Indicators\n\n| Signal | Source | Severity | Detection Method |\n|--------|--------|----------|-----------------|\n| Traffic decline >20% MoM | Analytics | High | Monthly traffic comparison |\n| Position drop >5 positions | Rank tracker | High | Weekly rank monitoring |\n| Outdated statistics/dates | Manual review | Medium | Annual content audit |\n| Broken external links | Crawler | Medium | Monthly crawl reports |\n| Decreased CTR | Search Console | Medium | Quarterly CTR analysis |\n| Competitor new content | SERP monitoring | Medium | Monthly SERP checks |\n| User engagement drop | Analytics | Low | Quarterly engagement review |\n| Index coverage issues | Search Console | High | Weekly coverage monitoring |\n\n### Content Decay Stages\n\n| Stage | Symptoms | Urgency | Recommended Action |\n|-------|---------|---------|-------------------|\n| **Early decay** | Slight traffic/position dip | Low | Monitor for 2-4 weeks |\n| **Active decay** | Consistent decline across 2+ months | Medium | Schedule refresh within 2 weeks |\n| **Significant decay** | 50%+ traffic loss, page 2+ | High | Immediate refresh or rewrite |\n| **Terminal decay** | No organic traffic, deindexed | Critical | Rewrite, redirect, or retire |\n\n## Refresh vs. Rewrite Decision Framework\n\n| Factor | Refresh (Update) | Rewrite (New version) |\n|--------|-----------------|---------------------|\n| Content quality | Good foundation, needs updating | Fundamentally flawed or outdated approach |\n| Position | Was ranking well, now dropping | Never ranked well despite optimization |\n| URL age | 1+ years, has earned backlinks | Young URL with no backlink equity |\n| Backlinks | Has external links pointing to it | No backlinks worth preserving |\n| Scope of changes needed | <50% of content changing | >50% needs rewriting |\n| Search intent | Intent hasn't changed | Search intent has evolved |\n\n**Decision rule:** If the URL has backlinks and was ranking, REFRESH. If not, consider REWRITE at a new URL (with 301 redirect if old URL has any equity).\n\n## Content Lifecycle Model\n\n```\nCREATE → PROMOTE → MAINTAIN → REFRESH → [REFRESH again] or RETIRE\n  │         │          │          │                          │\n  │      Month 1    Month 2-6   Month 6-12              When terminal\n  │    Social,      Monitor     Update facts,            301 redirect\n  │    outreach,    rankings,   add new sections,         to related\n  │    email        fix issues  improve depth              content\n```\n\n### Lifecycle Actions by Phase\n\n| Phase | Duration | Key Actions | Metrics to Track |\n|-------|----------|------------|-----------------|\n| Create | Week 1 | Publish, submit to Search Console | Indexation |\n| Promote | Month 1 | Social shares, email, outreach | Referral traffic, backlinks |\n| Maintain | Months 2-6 | Monitor, fix broken links, respond to comments | Rankings, traffic trend |\n| Refresh | Months 6-12+ | Update data, add sections, improve structure | Traffic recovery, new keywords |\n| Retire | When terminal | 301 redirect to best alternative | Redirect traffic recovery |\n\n## Update Strategy by Content Type\n\n| Content Type | Refresh Frequency | Key Updates | Shelf Life |\n|-------------|-------------------|------------|-----------|\n| Statistics roundups | Every 6 months | Replace old stats, add new sources | 6-12 months |\n| Tool comparisons | Every 3-6 months | Update pricing, features, screenshots | 3-6 months |\n| How-to guides | Annually | Update steps, screenshots, links | 12-18 months |\n| Evergreen guides | Every 12-18 months | Add new sections, update examples | 18-24 months |\n| News/trend content | Don't refresh | Archive or redirect | 1-3 months |\n| Case studies | Rarely | Update results if available | 2-3 years |\n| Glossary/definitions | As needed | Update when definitions evolve | 2-5 years |\n\n## Reference Materials\n\n- [Content Decay Signals](./references/content-decay-signals.md) — Decay indicators, lifecycle stages, and refresh triggers by content type\n\n## Related Skills\n\n- [content-gap-analysis](../../research/content-gap-analysis/) — Find what to add\n- [seo-content-writer](../../build/seo-content-writer/) — Write new sections\n- [geo-content-optimizer](../../build/geo-content-optimizer/) — Enhance for AI\n- [on-page-seo-auditor](../on-page-seo-auditor/) — Audit refreshed content\n- [content-quality-auditor](../../cross-cutting/content-quality-auditor/) — Full 80-item CORE-EEAT audit\n\nFile v0.1.2:_meta.json\n\n{\n  \"ownerId\": \"kn73qjxwmbna25qq8q051epqt980sys5\",\n  \"slug\": \"content-refresher\",\n  \"version\": \"0.1.2\",\n  \"publishedAt\": 1770824269256\n}\n\nFile v0.1.2:references/content-decay-signals.md\n\n# Content Decay Signals\n\nComprehensive decay detection system with automated monitoring setup, severity scoring, refresh playbooks by content type, and ROI estimation for content refresh investments.\n\n## Decay Signal Detection System\n\n### Primary Signals (High Reliability)\n\nThese signals directly indicate content performance decline and should trigger immediate investigation.\n\n#### 1. Organic Traffic Decline\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 10-20% decline | Month-over-month | Add to monitoring list |\n| Warning | 20-40% decline | Month-over-month | Schedule refresh within 2 weeks |\n| Critical | 40-60% decline | Month-over-month | Refresh this week |\n| Emergency | >60% decline | Month-over-month | Investigate immediately (may be technical issue) |\n\n**Detection method**: Compare current month's organic sessions to same month previous year (to account for seasonality) and to previous month (for trend detection).\n\n**False positive check**: Before attributing traffic decline to content decay, rule out:\n- Seasonal variations (compare year-over-year, not just month-over-month)\n- Algorithm updates (check if decline coincides with known Google updates)\n- Technical issues (crawl errors, indexation problems, site speed regression)\n- Tracking code changes (analytics misconfiguration)\n\n#### 2. Ranking Position Drops\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 1-3 positions lost | 2-week average | Monitor |\n| Warning | 3-5 positions lost | 2-week average | Investigate cause |\n| Critical | 5-10 positions lost | 2-week average | Schedule immediate refresh |\n| Emergency | Dropped off page 1 to page 3+ | Any timeframe | Priority refresh or rewrite |\n\n**Detection method**: Track primary keyword positions weekly. Use 2-week rolling averages to smooth daily fluctuations.\n\n#### 3. Click-Through Rate Decline\n\n| Severity | Threshold | Context | Action |\n|----------|-----------|---------|--------|\n| Watch | CTR below expected for position | Position stable, CTR dropping | Review title and meta description |\n| Warning | CTR dropped 20%+ vs. baseline | With stable impressions | Rewrite title tag and meta description |\n| Critical | CTR dropped 40%+ vs. baseline | May indicate stale SERP appearance | Full refresh of title, description, and structured data |\n\n**Expected CTR by position** (organic, desktop, approximate):\n\n| Position | Expected CTR Range | Below This = Investigate |\n|----------|--------------------|-------------------------|\n| 1 | 25-35% | <20% |\n| 2 | 12-18% | <10% |\n| 3 | 8-12% | <6% |\n| 4-5 | 5-8% | <4% |\n| 6-10 | 2-5% | <2% |\n\n---\n\n### Secondary Signals (Moderate Reliability)\n\nThese signals suggest potential decay but may have other causes. Use them to corroborate primary signals.\n\n#### 4. Engagement Metric Decline\n\n| Metric | Decay Indicator | Possible Cause |\n|--------|----------------|---------------|\n| Bounce rate increase >15% | Content no longer satisfies intent | Outdated information, better competitor content |\n| Time on page decrease >20% | Users leaving faster | Content not comprehensive enough |\n| Scroll depth decrease | Users not reading full content | Front-loading outdated info, losing interest |\n| Pages per session decrease | Users not exploring further | Poor internal linking, irrelevant content |\n\n#### 5. Content Freshness Indicators\n\n| Indicator | Decay Risk | Detection |\n|-----------|-----------|-----------|\n| Published >12 months ago, never updated | High | CMS date audit |\n| Contains year references 2+ years old | High | Text search for year patterns |\n| Statistics from 3+ years ago | Medium | Manual review or text search for \"20XX\" |\n| Broken external links (>10% of total) | Medium | Monthly crawl report |\n| Screenshots of outdated UI | Medium | Manual visual review |\n| References to discontinued products/tools | High | Manual review |\n\n#### 6. Competitive Displacement Signals\n\n| Signal | Detection Method | Severity |\n|--------|-----------------|----------|\n| New competitor content ranking above you | SERP monitoring | High |\n| Competitor content is longer and more comprehensive | Manual comparison | Medium |\n| Competitor has more recent publication date displayed in SERP | SERP monitoring | Medium |\n| Featured snippet lost to competitor | SERP monitoring | High |\n| AI overview now answers query without click | SERP monitoring | High |\n\n---\n\n### Tertiary Signals (Low Reliability, Supporting Evidence)\n\nThese signals alone do not indicate decay but strengthen the case when combined with primary or secondary signals.\n\n| Signal | What It Suggests |\n|--------|-----------------|\n| Fewer social shares over time | Content less share-worthy (may be stale) |\n| Decrease in backlink acquisition | Content no longer being cited as a resource |\n| Fewer comments or engagement | Community interest waning |\n| Content not appearing in AI responses | Not structured for GEO or information is outdated |\n\n---\n\n## Automated Monitoring Setup\n\n### Monitoring Dashboard Configuration\n\nSet up these automated checks to catch decay early.\n\n#### Weekly Checks\n\n| Check | Data Source | Alert Threshold |\n|-------|-----------|----------------|\n| Keyword position changes | Rank tracker | Any target keyword drops >3 positions |\n| Crawl errors on key pages | Search Console | Any new crawl error on monitored pages |\n| Index coverage changes | Search Console | Any page drops from index |\n\n#### Monthly Checks\n\n| Check | Data Source | Alert Threshold |\n|-------|-----------|----------------|\n| Traffic comparison (MoM) | Analytics | >15% decline on any monitored page |\n| CTR comparison | Search Console | >20% CTR decline for any target keyword |\n| Broken link scan | Crawler | Any new broken links on monitored pages |\n| Competitor SERP changes | SERP tracker | New competitor enters top 5 |\n\n#### Quarterly Checks\n\n| Check | Data Source | Process |\n|-------|-----------|---------|\n| Content freshness audit | CMS + manual | Review all content older than 6 months |\n| Statistics accuracy check | Manual | Verify top 20 pages have current data |\n| Engagement trend review | Analytics | Compare engagement metrics across quarters |\n| Full competitive content gap | SEO tool | Identify new competitor content opportunities |\n\n### Alert Priority Matrix\n\nWhen multiple signals fire simultaneously, use this matrix to determine response urgency.\n\n| Primary Signal + Secondary Signal | Priority | Response |\n|----------------------------------|----------|----------|\n| Traffic decline + Position drop | P1 (Critical) | Refresh within 48 hours |\n| Traffic decline + CTR decline | P1 (Critical) | Rewrite title/description immediately, schedule content refresh |\n| Position drop + Competitor displacement | P2 (High) | Refresh within 1 week |\n| Traffic decline + Engagement decline | P2 (High) | Refresh within 1 week |\n| CTR decline only | P3 (Medium) | Rewrite title and meta description this week |\n| Freshness indicators only | P3 (Medium) | Schedule refresh within 2 weeks |\n| Engagement decline only | P4 (Low) | Investigate and schedule if confirmed |\n\n---\n\n## Decay Severity Scoring\n\n### Composite Decay Score\n\nCalculate a 0-100 decay severity score by summing weighted signal scores.\n\n| Signal Category | Weight | Score Range |\n|----------------|--------|-------------|\n| Traffic decline | 30% | 0 = no decline, 100 = >60% decline |\n| Position drops | 25% | 0 = stable, 100 = dropped off page 1 |\n| CTR decline | 15% | 0 = stable, 100 = >40% decline |\n| Content freshness | 15% | 0 = updated this quarter, 100 = >2 years stale |\n| Competitive displacement | 15% | 0 = no new competitors, 100 = displaced from top 3 |\n\n### Score Interpretation\n\n| Composite Score | Decay Stage | Action |\n|----------------|-------------|--------|\n| 0-20 | Healthy | Continue monitoring |\n| 21-40 | Early decay | Add to refresh queue (next month) |\n| 41-60 | Active decay | Schedule refresh (this week) |\n| 61-80 | Significant decay | Immediate refresh or rewrite decision |\n| 81-100 | Terminal decay | Rewrite, redirect, or retire |\n\n---\n\n## Refresh Playbooks by Content Type\n\n### Blog Post / Article Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Update title with current year or hook | 10 min |\n| 2 | Rewrite introduction with fresh angle | 20 min |\n| 3 | Update all statistics with current sources | 30-60 min |\n| 4 | Add 1-2 new sections covering gaps | 60-90 min |\n| 5 | Update screenshots and images | 30 min |\n| 6 | Add or update FAQ section | 20 min |\n| 7 | Refresh internal links | 15 min |\n| 8 | Update meta description | 5 min |\n| 9 | Add/update schema markup | 10 min |\n| 10 | Update dateModified and republish | 5 min |\n| **Total** | | **3-4 hours** |\n\n### Product/Service Page Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Update pricing, features, specifications | 30 min |\n| 2 | Add new customer testimonials/reviews | 20 min |\n| 3 | Update product images | 30 min |\n| 4 | Refresh comparison tables | 20 min |\n| 5 | Update internal links to related products | 15 min |\n| 6 | Verify and update schema markup | 10 min |\n| **Total** | | **2-2.5 hours** |\n\n### Statistics/Data Roundup Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Verify every statistic is still current | 60-90 min |\n| 2 | Replace outdated stats with current data | 60 min |\n| 3 | Add new statistics from recent studies | 30 min |\n| 4 | Update source links and citations | 30 min |\n| 5 | Update year references throughout | 15 min |\n| 6 | Add new visualization if data changed significantly | 30 min |\n| 7 | Update title, meta description with year | 10 min |\n| **Total** | | **4-5 hours** |\n\n### How-To Guide Refresh Playbook\n\n| Step | Action | Time Estimate |\n|------|--------|--------------|\n| 1 | Verify all steps are still accurate | 30 min |\n| 2 | Update screenshots for UI changes | 60 min |\n| 3 | Add new methods or alternative approaches | 30 min |\n| 4 | Update tool recommendations | 15 min |\n| 5 | Add troubleshooting section if missing | 20 min |\n| 6 | Update FAQ with new common questions | 15 min |\n| 7 | Test all links and embedded resources | 15 min |\n| **Total** | | **3-3.5 hours** |\n\n---\n\n## ROI Estimation for Content Refresh\n\n### Cost-Benefit Framework\n\n| Factor | Measurement |\n|--------|------------|\n| **Cost of refresh** | Writer hours x hourly rate + tool costs |\n| **Current monthly traffic value** | Organic sessions x conversion rate x avg order value |\n| **Projected traffic recovery** | Based on decay stage and content potential |\n| **Time to recover** | Typically 4-8 weeks for rankings to respond |\n\n### Traffic Recovery Benchmarks\n\nBased on industry data for content refreshes (not rewrites):\n\n| Decay Stage at Refresh | Typical Traffic Recovery | Recovery Timeline |\n|------------------------|------------------------|-------------------|\n| Early decay | 90-110% of peak (often exceeds) | 2-4 weeks |\n| Active decay | 70-90% of peak | 4-8 weeks |\n| Significant decay | 40-70% of peak | 6-12 weeks |\n| Terminal decay | 10-40% of peak (rewrite may be better) | 8-16 weeks |\n\n### ROI Calculation Template\n\n```\nRefresh Cost:\n  Writer time: [X hours] x [$Y/hour] = $[Z]\n  Tool costs: $[A] (one-time crawl, research tools)\n  Total cost: $[Z + A]\n\nMonthly Traffic Value (before decay):\n  Peak monthly organic sessions: [N]\n  Conversion rate: [X]%\n  Average conversion value: $[Y]\n  Peak monthly value: [N] x [X]% x $[Y] = $[V]\n\nExpected Recovery:\n  Projected recovery: [%] of peak = $[V x %] per month\n  Current monthly value: $[current]\n  Monthly value increase: $[V x % - current]\n\nROI:\n  Payback period: $[total cost] / $[monthly value increase] = [months]\n  12-month ROI: ($[monthly value increase] x 12 - $[total cost]) / $[total cost] x 100 = [X]%\n```\n\n### Refresh Priority Scoring\n\nWhen choosing which content to refresh first, score each candidate:\n\n| Factor | Weight | Score (1-10) |\n|--------|--------|-------------|\n| Current traffic value | 25% | Higher traffic = higher score |\n| Decay severity | 20% | More decay = more urgency |\n| Competitive opportunity | 20% | Weaker competition = higher score |\n| Refresh difficulty | 15% | Easier refresh = higher score |\n| Strategic importance | 10% | Aligns with business goals = higher score |\n| Backlink equity | 10% | More backlinks = more worth preserving |\n\n**Priority formula**: Weighted score total. Refresh highest-scoring content first.\n\n---\n\n## Content Retirement Decision\n\nNot all decaying content should be refreshed. Use this checklist to decide when to retire content instead.\n\n### Retire When\n\n- [ ] Content targets a keyword with zero search volume\n- [ ] Topic is no longer relevant to your business\n- [ ] No backlinks worth preserving\n- [ ] Content never ranked well even when fresh\n- [ ] Cost to refresh exceeds projected 12-month value recovery\n- [ ] Content cannibalizes a better-performing page on the same topic\n\n### Retirement Options\n\n| Option | When to Use | Implementation |\n|--------|------------|---------------|\n| 301 redirect | Content has backlinks or residual traffic | Redirect to best related page |\n| Consolidate | Multiple weak pages on same topic | Merge into one strong page, redirect others |\n| Noindex | Page has internal utility but should not rank | Add noindex, keep page accessible |\n| Delete (410) | Content has no value, no links, no traffic | Return 410 Gone status |\n\n### Post-Retirement Monitoring\n\nAfter retiring content, monitor for 4 weeks:\n- Verify redirects are working (no 404 errors)\n- Check that target pages are receiving redirected traffic\n- Monitor rankings of consolidated/target pages\n- Ensure no orphan pages were created by removing internal links","readmeExcerpt":"Skill: Content Refresher Owner: aaron-he-zhu Summary: Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt... Tags: latest:2.0.0 Version history: v2.0.0 | 2026-02-14T04:20:42.826Z | auto **Major update with improved usability, triggers, and documentation.** - Added explicit natural language triggers and use case k","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Find content on [domain] that needs refreshing"},{"language":"text","snippet":"Which of my blog posts have lost the most traffic?"},{"language":"text","snippet":"Refresh this article for [current year]: [URL/content]"},{"language":"text","snippet":"Update this content to outrank [competitor URL]: [your URL]"},{"language":"text","snippet":"Create a content refresh strategy for [domain/topic]"},{"language":"markdown","snippet":"### CORE-EEAT Quick Assessment\n\n   **Content**: [title or URL]\n   **Content Type**: [type]\n\n   Rapidly score each dimension (estimate 0-100):\n\n   | Dimension | Quick Score | Key Weakness | Refresh Priority |\n   |-----------|-----------|--------------|-----------------|\n   | C — Contextual Clarity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | O — Organization | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | R — Referenceability | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | E — Exclusivity | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Exp — Experience | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | Ept — Expertise | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | A — Authority | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n   | T — Trust | [X]/100 | [main issue] | 🔴/🟡/🟢 |\n\n   **Weakest Dimensions** (focus refresh here):\n   1. [Dimension] — [what needs fixing]\n   2. [Dimension] — [what needs fixing]\n\n   **Refresh Strategy**: Focus on 🔴 dimensions first, then 🟡.\n\n   _For full 80-item audit, use [content-quality-auditor](../../cross-cutting/content-quality-auditor/)_"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: content-refresher\ndescription: 'Use when the user asks to \"update old content\", \"refresh content\", \"content is outdated\", \"improve declining rankings\", \"revive old blog posts\", \"this post is outdated\", \"traffic is declining on this page\", or \"rankings dropped for this article\". Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and optimizes for current SEO and GEO best practices. For writing new content from scratch, see seo-content-writer. For auditing without rewriting, see on-page-seo-auditor.'\nlicense: Apache-2.0\nmetadata:\n  author: aaron-he-zhu\n  version: \"2.0.0\"\n  geo-relevance: \"medium\"\n  tags:\n    - seo\n    - geo\n    - content refresh\n    - content update\n    - outdated content\n    - content decay\n    - ranking recovery\n    - content optimization\n  triggers:\n    - \"update old content\"\n    - \"refresh content\"\n    - \"content is outdated\"\n    - \"improve declining rankings\"\n    - \"revive old blog posts\"\n    - \"content decay\"\n    - \"ranking dropped\"\n    - \"this post is outdated\"\n    - \"traffic is declining on this page\"\n    - \"rankings dropped for this article\"\n---\n\n# Content Refresher\n\n\n> **[SEO & GEO Skills Library](https://skills.sh/aaron-he-zhu/seo-geo-claude-skills)** · 20 skills for SEO + GEO · Install all: `npx skills add aaron-he-zhu/seo-geo-claude-skills`\n\n<details>\n<summary>Browse all 20 skills</summary>\n\n**Research** · [keyword-research](../../research/keyword-research/) · [competitor-analysis](../../research/competitor-analysis/) · [serp-analysis](../../research/serp-analysis/) · [content-gap-analysis](../../research/content-gap-analysis/)\n\n**Build** · [seo-content-writer](../../build/seo-content-writer/) · [geo-content-optimizer](../../build/geo-content-optimizer/) · [meta-tags-optimizer](../../build/meta-tags-optimizer/) · [schema-markup-generator](../../build/schema-markup-generator/)\n\n**Optimize** · [on-page-seo-auditor](../on-page-seo-auditor/) · [technical-seo-checker](../technical-seo-checker/) · [internal-linking-optimizer](../internal-linking-optimizer/) · **content-refresher**\n\n**Monitor** · [rank-tracker](../../monitor/rank-tracker/) · [backlink-analyzer](../../monitor/backlink-analyzer/) · [performance-reporter](../../monitor/performance-reporter/) · [alert-manager](../../monitor/alert-manager/)\n\n**Cross-cutting** · [content-quality-auditor](../../cross-cutting/content-quality-auditor/) · [domain-authority-auditor](../../cross-cutting/domain-authority-auditor/) · [entity-optimizer](../../cross-cutting/entity-optimizer/) · [memory-management](../../cross-cutting/memory-management/)\n\n</details>\n\nThis skill helps identify and revitalize outdated content to reclaim lost rankings and traffic. It analyzes content freshness, identifies update opportunities, and guides the refresh process for maximum SEO and GEO impact.\n\n## When to Use This Skill\n\n- Content has lost rankings or traffic over time\n- Statistics and informa"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn73qjxwmbna25qq8q051epqt980sys5\",\n  \"slug\": \"content-refresher\",\n  \"version\": \"2.0.0\",\n  \"publishedAt\": 1771042842826\n}"},{"path":"references/content-decay-signals.md","content":"# Content Decay Signals\n\nComprehensive decay detection system with automated monitoring setup, severity scoring, refresh playbooks by content type, and ROI estimation for content refresh investments.\n\n## Decay Signal Detection System\n\n### Primary Signals (High Reliability)\n\nThese signals directly indicate content performance decline and should trigger immediate investigation.\n\n#### 1. Organic Traffic Decline\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 10-20% decline | Month-over-month | Add to monitoring list |\n| Warning | 20-40% decline | Month-over-month | Schedule refresh within 2 weeks |\n| Critical | 40-60% decline | Month-over-month | Refresh this week |\n| Emergency | >60% decline | Month-over-month | Investigate immediately (may be technical issue) |\n\n**Detection method**: Compare current month's organic sessions to same month previous year (to account for seasonality) and to previous month (for trend detection).\n\n**False positive check**: Before attributing traffic decline to content decay, rule out:\n- Seasonal variations (compare year-over-year, not just month-over-month)\n- Algorithm updates (check if decline coincides with known Google updates)\n- Technical issues (crawl errors, indexation problems, site speed regression)\n- Tracking code changes (analytics misconfiguration)\n\n#### 2. Ranking Position Drops\n\n| Severity | Threshold | Detection Window | Action |\n|----------|-----------|-----------------|--------|\n| Watch | 1-3 positions lost | 2-week average | Monitor |\n| Warning | 3-5 positions lost | 2-week average | Investigate cause |\n| Critical | 5-10 positions lost | 2-week average | Schedule immediate refresh |\n| Emergency | Dropped off page 1 to page 3+ | Any timeframe | Priority refresh or rewrite |\n\n**Detection method**: Track primary keyword positions weekly. Use 2-week rolling averages to smooth daily fluctuations.\n\n#### 3. Click-Through Rate Decline\n\n| Severity | Threshold | Context | Action |\n|----------|-----------|---------|--------|\n| Watch | CTR below expected for position | Position stable, CTR dropping | Review title and meta description |\n| Warning | CTR dropped 20%+ vs. baseline | With stable impressions | Rewrite title tag and meta description |\n| Critical | CTR dropped 40%+ vs. baseline | May indicate stale SERP appearance | Full refresh of title, description, and structured data |\n\n**Expected CTR by position** (organic, desktop, approximate):\n\n| Position | Expected CTR Range | Below This = Investigate |\n|----------|--------------------|-------------------------|\n| 1 | 25-35% | <20% |\n| 2 | 12-18% | <10% |\n| 3 | 8-12% | <6% |\n| 4-5 | 5-8% | <4% |\n| 6-10 | 2-5% | <2% |\n\n---\n\n### Secondary Signals (Moderate Reliability)\n\nThese signals suggest potential decay but may have other causes. Use them to corroborate primary signals.\n\n#### 4. Engagement Metric Decline\n\n| Metric | Decay Indicator | Possible Cause |\n|--------|----------------|---------------|\n|"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt... Skill: Content Refresher Owner: aaron-he-zhu Summary: Identifies and updates outdated content to restore and improve search rankings. Analyzes content freshness, adds new information, updates statistics, and opt... Tags: latest:2.0.0 Version history: v2.0.0 | 2026-02-14T04:20:42.826Z | auto **Major update with improved usability, triggers, and documentation.** - Added explicit natural language triggers and use case k","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1251,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T19:10:43.006Z","emptyReason":null},"items":[{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}