Decay Reversal Service

The surface we map

Decay Reversal Service works on the content assets you already own but that have decayed over time: your highest-traffic-but-faded blogs, podcasts, docs, case studies, and social archives. The object is the value already sitting on your own surfaces and quietly losing reach, not net-new content.

Your analytics flag a declining asset; they do not fix it. An execution retainer writes something new alongside it. This service revives the existing asset and republishes it in the formats its topic is now better served by, which is the work that sits between the dashboard that spots the decay and the agency that ignores it.

The standard we hold to

The premium here is not an evidence quote, it is a measured outcome. For each candidate asset we record concrete signals (publication and last-modified dates, structural signals, dated references, search demand against current visibility) and classify the decay type rather than guess at it. Where signals are insufficient to estimate baseline traffic, the asset is marked unknown rather than given a confident number.

The accountability is the guarantee: a measured 2x traffic lift on guarantee-eligible revived assets, checked within 30 days of your publication confirmation. We are explicit that the analysis is AI-first with a human edit pass, with the founder reviewing every revival batch before delivery, because the trust breaks the moment we are vague about it.

What signals we analyze

• Publication date and last-modified timestamp
• Word count and structural signals (subheadings, summary, internal navigation)
• Content recency signals (dated technology, deprecated tools, outdated data, year-stamped statistics)
• Topic search demand versus current organic visibility
• Internal link density within and across surfaces
• Format-match between asset and topic (some long-form posts are better served today as video, threads, or carousels)
• Customer-flagged priority URLs (optional intake field, up to 10 per engagement)

How it works

You complete intake, name your content surfaces with their root URLs, state your goals, flag any priority assets, and grant GA4 read access for lift measurement. The pipeline crawls the selected surfaces, scores each asset, and classifies decay type:

1. stale_information. Factual content has aged (dated references, deprecated tools, outdated data).
2. thin_promotion. Content is solid but never reached its audience (no derivatives, no internal linking).
3. structural_decay. Content is good but disorganized (weak intro, no clear takeaway, missing subheaders).
4. format_obsolete. Long-form text on topics now better served by video, threads, or carousels.

For each decayed asset we recommend two to three revival formats, estimate baseline traffic or mark it unknown when signals are insufficient, and rank by priority. The founder reviews and edits every revival batch before delivery.

What you receive

Month 1

A baseline report showing the current state of every selected surface, plus the first revival batch (3 assets for Starter, 5 for Standard), each shipped in two to three formats with publication-ready copy.

Months 2 and onward

A monthly review report showing lift measurements for the previous month's revived assets, followed by the next revival batch.

Publication

You publish revived assets on your own surfaces and click Mark as Published in your dashboard. That click starts the 30-day lift measurement window.

Success criterion

A 2x traffic lift on each revived asset, measured within 30 days of your publication confirmation. The primary measurement is GA4 read access at Property-level Viewer permission; the fallback is a customer-provided CSV export or screenshot at month-end. Both paths qualify for the guarantee. The guarantee applies only to assets with at least 100 monthly visits at baseline.

Limitations

• Assets under 100 monthly visits at baseline ship under a quality-only guarantee (delivered as specified, no traffic-lift commitment), because the baseline noise floor swamps any signal at that volume.
• A format_obsolete asset may need migration rather than refresh. We cannot resurrect a topic the audience has fully migrated away from.
• The 30-day window starts at your publication confirmation, not our delivery. Delaying publication shifts the measurement window and the guarantee timeline with it.
• This is content revival, not content strategy. We do not create net-new surfaces or pivot your positioning.

Anonymized example

Example only. Fictitious URLs and titles. Real reports contain customer-specific data and are delivered only to the engaged customer.

{
  "decayed_assets": [
    {
      "asset_url": "https://example-saas.com/blog/scaling-postgres-2022",
      "asset_title": "How We Scaled Postgres in 2022",
      "decay_type": "stale_information",
      "decay_severity": "high",
      "decay_signals": [
        "references Postgres 13 throughout despite Postgres 17 release",
        "monitoring tool cited (PgHero) superseded by industry-standard (pganalyze)",
        "performance numbers stamped 2022, never refreshed"
      ],
      "estimated_baseline_traffic": "medium",
      "recommended_formats": [
        {"format": "long_form_rewrite", "rationale": "Refresh tool references and add Postgres 17 specifics."},
        {"format": "linkedin_carousel", "rationale": "Lessons-learned narrative performs well for technical leadership."}
      ],
      "estimated_lift": "2x",
      "priority_rank": 1
    }
  ],
  "tier_recommendation": "starter",
  "baseline_quality_notes": "Crawl yielded sufficient signal for confident classification. Highest uncertainty is on traffic estimates for case studies; recommend GA4 access before guarantee assertions.",
  "flagged_concerns": []
}