Audit your blog for things that have gone stale

Old posts quietly go wrong. A statistic from three years ago is now misleading, a “currently” that is no longer current, a price that changed, a tool you recommended that shut down, a “this year” that points at the wrong year. None of it is dramatic, but it accumulates, and it erodes trust with exactly the readers who arrive from search and assume the post is maintained. Finding all of it by re-reading your archive is the kind of task nobody ever gets to. An AI audit across local files does.

Audit first, edit second

The instinct is to ask AI to “update my old posts,” but that invites it to rewrite things that were fine. The better pattern is to separate finding from fixing. Specter syncs your blog to a folder of markdown so an assistant can read every post; you start by asking it to flag, not change:

Read every post in this folder. Produce a report of likely-outdated
content: specific statistics or numbers that may have aged, dates and
"this year"/"currently" phrasings, named tools or products that may
have changed or shut down, and any claim that reads as time-sensitive.
For each, give the post, the exact line, and why it's a flag. Change
nothing.

That gives you a worklist instead of a black-box rewrite. Crucially, an AI may not know the current fact — its knowledge has a cutoff and it can be confidently wrong — so treat the report as “things to verify,” not “things that are settled.” You or a quick web check confirms the actual current value before anything changes.

Apply the fixes you trust

Once you have verified the real numbers, you can make the corrections directly, or hand the confirmed list back for the mechanical edits:

Apply these specific corrections to the posts named: [your verified
list of old value → new value]. Change only those facts and adjust
surrounding wording only as needed to read naturally. Don't touch
anything else.

Review, preview, sync

Read the diff — factual edits especially deserve a second look, since this is your credibility on the line — then run Specter’s dry-run preview to confirm which posts would update before going live. Snapshot the folder with git first. Connect Specter via the first-sync guide if you have not yet.

A fact-freshness audit pairs naturally with refreshing old posts at scale: one keeps the content competitive, the other keeps it correct. Both are only practical because the blog has become a folder your tools can read end to end.

This is a sensitive area in one respect worth stating plainly: AI is good at spotting what might be stale and bad at deciding what is true now. Keep yourself in the loop on the facts, and this becomes one of the highest-trust maintenance passes you can run.