---
name: blog-refresher
description: Refresh and improve existing blog posts to outrank competitors using a 6-phase content audit and SERP gap analysis. Use when the user wants to update, refresh, or improve an existing blog post, recover lost rankings, or asks why a post fell behind competitors.
metadata:
  version: 1.0.0
  author: illyism
  source: https://il.ly/skills/blog-refresher
title: blog-refresher
canonical_url: https://skilld.dev/gh/illyism/seo-skills/blog-refresher
last_updated: 2026-10-14T13:01:44.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install illyism/seo-skills/blog-refresher`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/blog-refresher`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/illyism/seo-skills/blog-refresher) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/blog-refresher`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/blog-refresher --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/blog-refresher --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Blog Refresher

You update existing blog posts so they outrank the pages above them. Analyze the post, compare it with the top-ranking competitors, find the gaps, and write an improved version that keeps the original voice.

Use real research tools: web search or a SERP API for rankings, and a page fetcher for competitor content. Do not rely on memory for what ranks or what competitors say. Use today's date for anything time-sensitive.

Keep messages short and actionable until the final refreshed content.

## The 6-phase framework

1. **Current state analysis**: assess the existing post
2. **Competitor research**: analyze the top 5–10 SERP results
3. **Gap identification**: what competitors have that the post lacks
4. **Improvement plan**: a structured upgrade strategy
5. **Approval checkpoint**: present findings and wait for approval
6. **Content recreation**: write the refreshed version

## Phase 1: Current state analysis

### Content audit checklist

```
BASIC METRICS
□ Word count
□ Last updated
□ Current ranking for the main keyword (if Search Console or rank data exists)
□ Page traffic per month (if analytics exists)

STRUCTURE
□ Number of H2s and H3s
□ Lists, tables, images, media
□ Internal and external links

QUALITY
□ Readability (grade level)
□ Content depth: shallow / medium / deep
□ Unique insights
□ CTAs present
```

### Initial assessment

```
EXISTING POST ANALYSIS
Title:
URL:
Primary keyword:

STRENGTHS: what works, unique angles, strong sections to keep
WEAKNESSES: outdated information, missing topics, weak sections, poor flow
QUICK WINS: easy updates, stats to refresh, broken links to fix
```

## Phase 2: Competitor research

### Step 1: Read the SERP

Extract the top 10 titles, the featured snippet, People Also Ask questions, related searches, and the dominant content format.

### Step 2: Pick 5 competitors

Prioritize direct competitors, pages ranking #1–3, recently updated content, and pages with visible engagement.

### Step 3: Audit each competitor page

```
URL / Ranking position
Word count
H2 sections and H3 breakdown
Unique elements: features, data, examples, visuals, interactive tools
Last modified date
```

## Phase 3: Gap analysis

Build a table that compares the post with each competitor:

| Element | Your post | Comp 1 | Comp 2 | Comp 3 | Comp 4 | Comp 5 | Priority |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Word count | | | | | | | |
| Featured snippet format | | | | | | | |
| [Topic 1] | | | | | | | |
| [Topic 2] | | | | | | | |
| Statistics / data | | | | | | | |
| Examples / cases | | | | | | | |
| Visuals | | | | | | | |
| FAQ section | | | | | | | |
| Schema markup | | | | | | | |

Then list missing topics by priority:

- **High:** covered by 4+ competitors
- **Medium:** covered by 2–3 competitors
- **Low:** covered by 1 competitor
- **Emerging:** angles nobody covers yet

Finish with each competitor's unique angle and the post's opportunity to differentiate.

## Phase 4: Refresh strategy

```
IMMEDIATE
□ Update outdated statistics to the latest available data
□ Fix broken links
□ Add missing high-priority topics
□ Format the answer for the featured snippet
□ Refresh examples and screenshots

STRUCTURE
□ Reorder H2s for better flow
□ Add an FAQ from People Also Ask
□ Add comparison tables
□ Improve the intro hook

OPTIMIZATION
□ Target word count
□ Internal links to add
□ Authoritative external sources to cite
□ Image alt text
□ Schema markup
```

### Proposed outline

- 3 new title options (current year or new angle, snippet-focused, differentiated)
- The new H2 structure, each marked Keep / Modified / New with what changes
- Target word count and new elements (table, FAQ, diagram)

## Phase 5: Approval

Present the plan before writing:

```markdown
## Content refresh plan: [Post title]

### Summary
The post ranks #[X] and has fallen behind on [areas]. This refresh adds [N] sections and updates [N] outdated elements.

### Key findings
1. Content depth: competitors average [X] words vs [Y]
2. Missing topics: [top 3 gaps]
3. Outdated elements: [main issues]
4. Opportunity: [unique angle]

### Gap table
### New outline

Shall I write the refreshed version? Any sections to prioritize?
```

Do not promise specific ranking or traffic gains.

## Phase 6: Writing the refresh

**Keep what works**

- Sections that already rank well
- The original voice and tone
- The URL (or plan a 301 redirect)
- Existing anchors that other pages link to

**Improve**

- Add a visible "Last updated: [date]"
- Cite the year next to every statistic
- Go deeper than competitors on the topics that matter
- Add original data, examples, or diagrams competitors lack

**Make it scannable**

- Paragraphs of 2–3 sentences
- More H3s
- Lists and tables where they help
- Jump links for long posts

### SEO checklist

```
□ Title tag 50–60 characters
□ Meta description 150–160 characters
□ Primary keyword in the first 100 words
□ Related terms used naturally
□ Snippet-ready answer near the top
□ FAQ answers People Also Ask
□ Internal links to and from related posts
```

## Output format

```markdown
# [New title]

_Last updated: [date]_

[New intro]

[Jump links]

[Refreshed sections]

## Frequently asked questions

## Conclusion

---

### Refresh summary for the publisher
- Meta description: [new]
- Schema: [types to add]
- Internal links: [pages to link]
- Images needed: [list]
- URL: [keep / redirect plan]
- Word count: [old] → [new]
- Sections added: [list]
```

## Quality check

- Every gap from Phase 3 is addressed or consciously skipped
- All data and examples are current and sourced
- The original voice is intact
- No keyword stuffing
- The post gives more practical value than each competitor analyzed
