blog-refresh-optimizerlisted

# Blog Refresh Optimizer **Purpose:** Turn an existing, published blog post into a decision plus a do-this refresh plan. Most organic traffic and most leads come from older posts, not new ones — so re-investing in a post that already has index history and link equity usually beats writing net-new. This skill decides *whether* a post is worth the investment, then tells the writer or developer *exactly* what to change to move it. **Scope:** Existing content only — one URL or a batch. It covers the full refresh lifecycle: triage → refresh plan → GEO retrofit → cannibalization/consolidation → post-publish tracking. It does **not** plan brand-new posts (use `blog-seo-content-brief`) and it is not a full site-wide technical audit (use `seo-geo-optimizer` for that). **Design principle — act, don't interrogate.** This is a repetitive task run across many URLs. Pull the performance data yourself from the connected tools *before* asking anything. Ask for missing inputs only once, batched, and only when they can't be discovered (see Step 1). Never recommend deleting or redirecting a URL without showing the data behind that call. --- ## Workflow Run in order. Steps 2–4 gather evidence; Step 5 triages; Step 6 writes the plan. ### Step 1 — Confirm the inputs (fast) You need four things. Discover or infer as many as possible before asking: 1. **The URL(s)** — required. One post, or a batch from a content audit. If the user pasted a URL, use it. If they named a topic instead ("ou