blog-decay

by AgriciDaniel2.4k

Install

Use withClaudeCursorCodex

The file stays in the publisher's repository. PlugMCP does not host or rewrite it.

Download skill brain/.raw/sources/claude-blog-skill/skills/blog-decay/SKILL.md on GitHub

Related skills

View all

A
autoresearchRun a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may ac
C
canvasCreate, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or me
O
obsidian-basesExplain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables

Detect content decay from Google Search Console exports by comparing current and previous page performance, flagging quarter-over-quarter traffic drops, dropped pages, and refresh, consolidate, prune, or query-shift actions. Use when the user says "/blog decay", "content decay", "traffic drop", "QoQ decline", "GSC decay", or "refresh declining posts".

name: blog-decay description: Detect content decay from Google Search Console exports by comparing current and previous page performance, flagging quarter-over-quarter traffic drops, dropped pages, and refresh, consolidate, prune, or query-shift actions. Use when the user says "/blog decay", "content decay", "traffic drop", "QoQ decline", "GSC decay", or "refresh declining posts". argument-hint: "<current-gsc.json> <previous-gsc.json> [threshold] [metric]" user-invokable: true license: MIT

Blog Decay

Use /blog decay to find pages whose Google Search Console performance has declined quarter-over-quarter. The command compares a current-period export against a previous-period export, flags pages with a 20% or larger decline by default, and recommends the next content action.

Default Offline Workflow

Run the local analyzer against two GSC page exports:

python3 scripts/content_decay.py current.json previous.json

Useful options:

python3 scripts/content_decay.py current.json previous.json --threshold 0.30
python3 scripts/content_decay.py current.json previous.json --metric impressions
python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md

The script accepts JSON lists of page rows with page or url, clicks, and impressions. It also accepts the object shape returned by when the rows are under a top-level key.

Decline	Severity
20% to 39.9%	warning
40% to 59.9%	high
60% or more	critical

Action	Use when
refresh/update content	The page still has demand and likely needs freshness, title, internal link, or section updates.
investigate query shift	Clicks fell while impressions held up, suggesting CTR, rank, SERP, or query mix changes.
consolidate/redirect	The page dropped out or the loss is severe enough that merging into a stronger URL may recover value faster.
prune	The page had very low prior demand and may not justify rewrite effort.

blog-decay

Install

Related skills

Blog Decay

Default Offline Workflow

Optional Live GSC Export

Decay Model

Recommended Actions

Cross-references