How to Refresh Old WordPress Posts with AI Without Losing Their Angle
Keep an older post’s original reader promise while using AI to flag stale passages, verify sources, make focused edits, and check the public WordPress page.
A refresh should keep the reason the post exists. If an article helps a beginner build a first page, a new interface screenshot or changed menu label may need work; the beginner’s task does not automatically change. A full rewrite can accidentally turn that guide into a broad roundup. The first editorial decision is what must stay.
Write an angle lock in three lines
- Reader: who is the page for, and what can they already do?
- Promise: what result should they reach after following the page?
- Boundary: which adjacent questions belong in a separate guide?
Copy these lines into a working note before changing the title or body. For a hypothetical older page-builder tutorial, the promise might be “A new WordPress editor can publish one basic page and check it on a phone.” Pricing history, advanced theme templates and agency workflows would sit outside that promise. If the original angle is inaccurate or the product is no longer viable, record that as a larger editorial decision instead of quietly preserving a broken premise.
Inspect the live page and its evidence
Read the entire article once. Mark dated figures, product capabilities, screenshots, interface steps, examples, broken media and links. For each substantive claim, note the source that would establish it today. Product documentation is stronger for current controls than an old blog quote; a measured performance claim needs a defined test or study. If the evidence is unavailable, remove the claim or leave it visibly unverified in the working draft.
If Search Console is available for the property, filter its Performance report to the page and inspect the queries that lead to it. Google documents this page-and-query view. Those queries can reveal a question the article should already answer. They do not prove a rewrite will gain traffic. No Search Console numbers are assumed in this example.
Give AI a passage-level task
Original reader: [reader]. Original promise: [one sentence]. Do not change this promise unless a cited fact makes it untenable. Here is the full current post: [paste]. List passages that may be stale, unsupported, repetitive, or off-topic. Quote each passage exactly and name the source needed to verify it. Propose the smallest repair: keep, correct, replace example, move, or delete. Do not invent product controls, tests, prices, dates, or personal experience. Do not rewrite the whole post.
Read the AI list against the original page. It may flag a strong passage because the wording is old-fashioned or propose a fashionable new section with no role in the reader’s task. Keep the passage if it is accurate and useful. Check actual sources before accepting any proposed replacement. AI is useful here as a second reader that points to places for investigation, not as a source of product facts.
Make the smallest changes that answer the same promise
| Finding | Editorial action |
|---|---|
| Current step, clear example | Keep it. |
| Menu label changed in the current interface | Verify against vendor documentation, then correct the step and screenshot. |
| Old price or market-share figure with no current source | Remove it unless it is necessary and can be verified. |
| Reader question needs several new steps | Add a focused section without changing the main task. |
| New subject serves a different reader | Plan a separate post or reconsider the article’s angle explicitly. |
Update the opening quick answer only after the body has passed this check. It should state the same result the revised steps actually deliver. Then review the excerpt and search description; both can continue to promise the old version even when the body has changed.
Compare revisions and inspect the visitor page
WordPress revisions let an editor compare saved versions and see additions and removals. Use that comparison to look for accidental deletion of a useful example, changed product terminology, or a new claim with no source. Then open the ordinary public URL. Check the quick answer, headings, screenshots, working links and any links inserted automatically after saving.
Do not change a publication date solely to make the article look fresh. Google’s people-first content questions ask whether a page offers a satisfying answer and specifically challenge date changes without substantial content changes. If the update is substantive, describe the changed information accurately and keep the page’s visible dates consistent with the site’s actual settings.
A refresh is complete when the original reader can still get the promised result using current, supported steps. If the promise can no longer be met, the honest answer is a newly scoped article or a clear warning, not a smoother version of an obsolete guide.
Frequently asked questions
How do I update an old WordPress blog post for SEO?
Start with the current public page and its reader task. Check dated claims, product steps, screenshots and links against current sources, then revise the parts that no longer help the reader. Review the excerpt and search snippet after the body changes.
How can AI help refresh an old article without rewriting everything?
Give AI the full article and a short statement of its original reader and promise. Ask it to quote passages that may be stale, unsupported or repetitive and to suggest the smallest repair. Verify each proposed replacement before accepting it.
When should I completely rewrite an old blog post?
A full rewrite may be justified when the original premise is obsolete, the product or task has changed, or the page cannot deliver its promised result. If the article still works, a targeted correction is often clearer and preserves useful examples.
Should I change the publication date when updating a post?
Do not change the date only to make the page look fresh. Make substantive updates, describe them accurately and keep visible dates consistent with the site’s actual publishing settings.
Can Search Console show what an old post needs to answer?
For a page with enough data, filter Search Console’s Performance report to that URL and inspect its queries. Compare recurring questions with the current article. The query rows point to possible gaps; they do not prove that adding a heading will increase traffic.
How do I check that a WordPress content refresh is live?
Compare the saved revision with the prior version, then open the ordinary public URL. Check the quick answer, headings, screenshots, links and excerpt. If a cache still serves the old copy, clear the relevant site or CDN cache and verify again.
