How do you keep tutorials accurate when the tools in them keep changing? You give every post a "last checked" date, and you let an AI assistant re-check any post that's older than 30 days, every week, and suggest the fixes. You still approve each change. That's the system on this site, and you can copy it whether you blog on WordPress or anywhere else.
Why tutorials go stale
A how-to is only as good as its screens. Apps rename buttons, move menus, change prices and retire whole plans, usually without telling anyone. A post that was perfect in March can send a reader hunting for a button that no longer exists by June.
Most bloggers fix this only when a reader complains, if ever. That's backwards. The reader who got stuck usually just leaves.
The four pieces
1. A "last checked" date on every post
At the top of every post here, under the title, there's a line like this:
Last checked October 14, 2026. Tools change their screens often, so these steps get re-checked and updated regularly.
This is different from the date the post went up. It's the date someone last went through every step against the real tools. It tells readers how fresh the steps are, and it tells your AI assistant which posts are due.
On this site it's a setting at the top of each post's file (checked:). On WordPress, the simplest version is a line you type at the top of the post and update by hand, or an "updated date" setting if your theme has one.
2. A 30-day rule
Any post whose last-checked date is more than 30 days old is due for a check. Thirty days is my choice for tutorials about AI tools, which change fast. A recipe blog could pick six months.
3. A weekly check by an AI assistant
Every Monday morning, a scheduled task runs on its own. (A scheduled task is a job Claude does by itself on a set day and time, the way a calendar reminder goes off.) Here's what it does, in plain steps:
- Lists every published post whose last-checked date is over 30 days old.
- For each one, re-checks every step: the screens, button names, settings, prices, plans and links.
- Fixes what changed, and retakes screenshots that no longer match the real screen.
- Sets the last-checked date to today.
- Looks at what I've built since the last check. If I found a better way to do something a post teaches, it updates that post too.
- Puts all the fixes in one proposed change and waits for my yes. Nothing goes live on its own.
Two firm rules: a typo-sized fix still waits for my yes, and posts I wrote myself are never reworded. For those, the AI assistant just lists the problem and I fix my own words.
4. A "What changed" list readers can see
Every real fix adds one line to the bottom of the post, under "What changed": the date and a plain note, like "Found a faster way to schedule pins, Step 3 rewritten." Readers who come back can see exactly what's new, and it's honest about the fact that tutorials change.
Set up your own
What you need: Claude on a paid plan, a blog, and about 20 minutes.
- Add a last-checked line to your how-to posts. Start with your five most popular ones.
- Pick your rule: 30 days for fast-changing tools, longer for slower topics.
- Create the scheduled task. In Claude, click Scheduled in the left sidebar, then New task, then Set up manually. Give it a name, set Frequency to Weekly, pick a day and time, and paste instructions like these (change the brackets):
Every week, find the posts on [your blog address] whose "last checked" date is more than [30 days] old. For each one, open every tool and page the post mentions and check every step: button names, menus, settings, prices and links. Make a list per post: what changed, and the exact new wording or step. Don't change anything yourself. Send me the list.
That version only reports, which is the right place to start. Once you trust it, you can let it draft the fixes for you to approve.
- Add "What changed" notes whenever you apply a fix.
Why this matters for search and AI answers, too
Google and AI answer tools like to point people to pages that are clearly maintained. A visible last-checked date and a real change log show that someone is looking after the page. It's not a magic ranking trick, but a stale tutorial with wrong buttons is a page people bounce off, and that never helps. (Want to know if AI tools are already quoting you? Here's how to see if ChatGPT and Copilot are citing your blog.)
What I'm honest about
This system is new on this site, and the posts here are still young, so the weekly check hasn't had a 30-day-old post to fix yet. When it does, you'll see it in the "What changed" notes at the bottom of each post.
The decisions stay mine: what's worth teaching, which fix is right, what goes live. The rereading, clicking and comparing is the busywork, and that's what my AI assistant does.
Want more systems like this? Read about the rules I give my AI assistant, see how I turn what I build into blog posts, or join the newsletter for new guides as they come out.