More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Content Decay Scan

    1

    Find the aging posts quietly bleeding traffic, tell real decay apart from seasonal noise and algorithm updates, and rank refreshes by the revenue each one would actually recover.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Content Decay Scan

    Content Decay Scan

    Example session with this skill installed

    Our SaaS blog has about 120 posts. Traffic is down roughly 15% this year and nobody knows which posts are responsible. Here's a sample of five pages with their numbers — scan them and tell us where to start.

    • Read your context and instructions
    • Compiled the content decay scan

    SAMPLE DATA (peak → current sessions/mo, position, last updated, conversion):
    A. "remote team tools guide" — 3,100 → 2,050; #3 → #7; 20 months ago; 1.8% × $49 trial value
    B. "how to run a standup" — 1,900 → 1,820; #2 → #2; 14 months ago; no conversions ever
    C. "2024 product changelog roundup" — 800 → 120; #5 → #18; 24 months ago; n/a
    D. "pricing page mistakes" — 1,400 → 1,050; #4 → #6; 8 months ago; 3.2% × $49
    E. "async communication guide" — 2,200 → 1,300; #5 → #9; 11 months ago; 1.5% × $49

    DIAGNOSIS FIRST — B's position is unchanged and the slide is inside noise: not decay, exclude. C is dated event content: supposed to fade, exclude from the queue. A, D, E show slow multi-month slopes with rivals climbing: true decay.

    SCORES — A: 74 (big trend loss, very stale). E: 68. D: 55 (smaller loss, fresher, but conversion is strong).

    RECOVERABLE REVENUE — A: (3,100−2,050) × 0.018 × $49 × 0.7 ≈ $648/mo. E: (2,200−1,300) × 0.015 × $49 × 0.6 ≈ $397/mo. D: (1,400−1,050) × 0.032 × $49 × 0.6 ≈ $329/mo.

    QUEUE — Fix now: A, then E. Fix soon: D. Watch: nothing in this sample. Let go: C — merge its still-relevant sections into A and 301 it; B stays untouched.

    BRIEF, PAGE A — What's wrong: tool pricing and screenshots from two years ago; two listed tools were acquired and shut down; rivals added an AI-meeting-notes section in 2025 that we lack entirely. Update: pricing, screenshots, dead links. Add: the AI section + a comparison table (SERP intent has shifted to comparing). Optimize: title to match current query language; internal links from three newer posts. Effort: moderate rewrite, ~3 days. Check-in: 90 days after refresh, position and sessions vs the numbers above.

    NEXT STEP — Export the same five fields for all 120 posts and the full radar follows the same shape.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Old content rarely breaks — it fades, one ranking position at a time, until the quarter's numbers expose the bleed. This skill runs the full diagnosis. Step one is the discipline most audits skip: separating true decay from its four lookalikes — seasonality, algorithm updates, SERP layout changes that cost clicks without moving position, and cannibalization between your own pages — with shape-of-decline shortcuts (cliff vs slope vs stable-position-click-loss) that usually name the cause before you touch a rewrite. Step two gathers the per-page raw material from Search Console, analytics, and the CMS, with thresholds you set in writing up front. Step three scores every page 0–100 across five weighted signals: traffic trend, ranking movement, freshness, link health, and conversion drift. Step four is the money step: each page's recoverable revenue is estimated from lost sessions, conversion rate, and a calibrated recovery-odds table, then bucketed into fix-now, fix-soon, watch, and let-go — turning "here are 40 decaying pages" into "refresh these six to recover roughly this much per month." Step five writes writer-ready refresh briefs from a fixed template (what's wrong with evidence, what to update, what to add, what to optimize, and an honest effort call), demonstrated on a complete worked example with real arithmetic. The let-go bucket gets explicit merge, redirect, or leave decisions — never delete a page with backlinks — and a measurement protocol closes the loop with 90-day check-ins and rules against refreshing during core-update rollouts or rewriting the same page twice in six months. An edge-case section covers tracking changes faking decay, migration-stitched histories, and top-of-funnel pages that never converted by design.

    • It needs history: with under six months of per-page data, seasonality and trend can't be separated reliably and the skill will say so.
    • Revenue estimates are only as good as your conversion data; without it, the queue ranks by traffic recovery instead of money.
    • Recovery odds are calibrated judgment from the situation table, not a guarantee — your own 90-day check-in data should refine them over successive scans.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Probably not — decay is a slope, not a cliff. A sharp drop on a specific date across many pages usually means an algorithm update or a tracking change, and the skill's first step checks exactly those causes before any page gets flagged for a rewrite.

    Per page: URL, monthly organic sessions for 6–12 months, current and historical position for its primary keyword, publish and last-update dates, and conversion data if you have it. Search Console plus an analytics export covers it; a CSV is fine.

    Almost never outright. The let-go bucket gets a merge, redirect, or leave decision per page — a page with backlinks that returns a 404 is link equity thrown away, so dead pages are folded into stronger ones with a 301.

    New in Marketing & SEO