Every blog has a graveyard. Posts that were useful when they were written now carry outdated advice, broken links, screenshots of interfaces that no longer exist and a tone that no longer matches the rest of the site. They still get a trickle of visitors, and some of those visitors leave confused or disappointed. Meanwhile the team keeps publishing new posts, because new feels more productive than repair.
Updating old content is often the better investment, and AI can make the work quicker. It can help you audit a pile of posts, spot sections that need attention, restructure rambling text and draft fresh passages for you to check. It cannot tell you what is true today, so the judgement stays with people. This guide shows you how to choose which posts to update, how to use AI at each step, how to keep accuracy intact and how to record what you changed.
Key takeaways
- Start with an audit: pick posts that have a purpose, some existing visibility and a clear problem to fix.
- Use AI to review structure, find gaps and draft rewrites, but verify every fact, link and instruction yourself.
- Keep what already works. Do not rewrite a good post from scratch just because the tool can.
- Change the web address only when there is a strong reason, and redirect properly if you do.
- Log each update so you can learn what improves results and know when the next review is due.
Why updating beats starting again
An existing post already has a web address that may have been linked to, shared and crawled. It has history, even if modest. Replacing it with a brand new page means starting from nothing, while improving it lets you keep that foundation and fix what is weak.
Benefits of updating
- Accuracy: readers get correct, current advice.
- Trust: a site that keeps its pages in good order looks cared for.
- Efficiency: improving a draft is usually quicker than writing a new article from nothing.
- Focus: you reduce the number of weak, overlapping pages that compete with each other.
- Learning: comparing before and after results teaches you what your readers value.
When not to update
Some posts are best left alone or removed. A post that is tied to a date, such as an event recap, may be accurate as a record. A post on a topic you no longer cover may be better merged into a related page or retired with a proper redirect. Updating everything wastes effort that could go to pages that matter.
Auditing your archive
An audit is a spreadsheet with one row per post and a few columns that help you decide. You do not need special software. Export a list of posts from your content system, then add data from your analytics and search tools.
Columns to include
| Column | Why it helps |
|---|---|
| URL and title | Identifies the post |
| Publish and last updated dates | Shows age and last attention |
| Topic and purpose | Reminds you why the post exists |
| Search impressions and clicks | Shows existing visibility |
| Visits and engagement | Shows whether readers find it useful |
| Conversions or next steps | Shows whether it supports business goals |
| Known problems | Outdated, thin, overlapping, broken links |
| Decision and owner | Keep, update, merge, remove |
AI can help you fill in the topic and known problems columns by summarising each post in a sentence and listing sections that look dated. Paste the text of one post at a time, and ask for a short summary and a list of claims that may have changed. Do not share unpublished or confidential material in a tool that you have not checked. See our guide on protecting company data when using AI tools for sensible limits.
Deciding what to do with each post
Once the audit is filled in, sort posts into four groups. This keeps the work focused and prevents you from treating every page the same way.
| Decision | When it fits | Typical work |
|---|---|---|
| Light refresh | Good post, small issues such as dates, links or examples | Fix facts, tidy wording, update visuals |
| Major rewrite | Right topic, weak execution or changed landscape | Rework structure, add new sections, rewrite many passages |
| Merge | Several thin posts on the same question | Combine into one stronger page and redirect the others |
| Retire | No purpose, no value, off topic | Remove and redirect to the closest relevant page, or let it return a removed status |
How to prioritise
- Start with posts that already attract some visibility but underperform.
- Next take posts that support important products, services or topics.
- Then handle posts with known errors or risky advice, which can be urgent regardless of traffic.
- Leave low value posts until last, or retire them.
Using AI to review a post
Before editing, ask AI to act as a reviewer. A structured review prompt is more useful than asking it to improve the post, because it makes the model point to specific issues instead of rewriting everything.
What to ask the model to check
- Which statements look time sensitive and might be out of date.
- Which sections are unclear, repetitive or too long.
- Which questions a reader might still have after finishing.
- Where an example, table or step by step list would help.
- Where the tone changes or the language feels stiff.
- Which headings do not describe the content beneath them.
Ask for the results as a table with the section, the problem and a suggested fix. Then work through the table yourself. For tips on writing clear instructions, read our guide to writing better prompts.
Refreshing facts and sources
This is the part that matters most, and it is the part AI is least able to do for you. A model has no live view of the world and may not know what has changed. It may also state outdated or invented details confidently. Treat any fact it provides as unverified until you check it.
A fact refresh routine
- Highlight every date, number, name, process step, policy and product detail in the post.
- For each, check an authoritative current source, such as an official page or your own up to date records.
- Replace outdated statements, or remove them if you cannot confirm a replacement.
- Open every link and confirm it still works and still supports the claim.
- Replace any screenshot that shows an old interface, or remove it.
Be careful with topics that change often or carry risk, such as legal, financial and health topics. Keep statements general, and add that the content is general information, not advice. Our explainer on AI hallucinations shows why this check is not optional, and the guide to checking AI output for mistakes gives a fuller process.
Rewriting and restructuring
With facts sorted, improve how the post reads. The best approach is surgical: keep passages that work, and rewrite only what does not. AI can help with specific, bounded tasks.
Good tasks for AI
- Tighten a long paragraph without changing its meaning.
- Convert a block of text into a numbered list or a table.
- Suggest a clearer heading structure.
- Draft a new section to fill a gap you have identified, based on notes you supply.
- Rewrite stiff sentences in plain language.
- Write a short summary or takeaways box from the finished post.
Tasks to keep for yourself
- Deciding what the post should now say about a changed topic.
- Adding first hand experience, examples and opinions.
- Approving any new factual statement.
- Final tone and voice.
When asking for a rewrite, tell the model to preserve the facts and the author’s voice, and to mark anything it changes so you can review. Compare the new text with the old, line by line. Models sometimes make subtle changes that alter meaning, so a side by side comparison is worth the time. If your aim is to avoid bland output, our guide to writing blog posts with AI without generic content applies equally to updates.
Checking that the post still matches intent
Over time, what people expect from a topic can shift. A post that once suited a basic definition search may now compete with pages that offer tools, comparisons or walkthroughs. Check what currently appears for your main topic and whether your post still fits.
A quick intent check
- Search for the post’s main topic in a private window.
- Look at the formats and angles of the top results.
- Compare them with your post: is it too short, too broad, too narrow or the wrong format?
- Decide whether to adjust the post, or accept that it serves a different purpose.
Do not copy competitors. Use the check to spot what readers seem to want, then find an angle you can deliver better, such as clearer steps, a useful template or more honest trade offs.
Links, titles and technical details
Updates are a natural moment to tidy the supporting details. These changes are small but add up.
| Element | What to do |
|---|---|
| Title | Make sure it describes the current content accurately. Avoid adding a year unless the post really is date specific. |
| Meta description | Rewrite it to match the improved post |
| Internal links | Add links to newer relevant pages and from newer pages back to this one |
| Broken links | Fix or remove, replacing with a better source where possible |
| Images and alt text | Update visuals and write accurate descriptions |
| Web address | Keep it unless there is a compelling reason to change it |
If you must change a web address, set up a permanent redirect from the old address to the new one, and update internal links. Otherwise, visitors and search engines may hit a dead end. Adding links from related pages helps both readers and discovery. For example, a post about writing for search could link to AI keyword research where it is relevant.
Republishing and dates
Be honest about dates. If you made a substantial update, showing a last updated date helps readers judge freshness. Do not change a date without changing the content, because that misleads readers and can damage trust.
Good practice
- Show both original and updated dates where your system allows.
- Add a brief note describing what changed if the update is significant.
- Do not republish as a new post, which creates duplicate content and splits any value.
- Save a copy of the old version in case you need to compare or roll back.
- Have a second person proofread before publishing.
Tracking results
Record the details of each update in your audit sheet: the date, what changed, who did it and why. After several weeks, compare the page’s visibility, clicks and engagement with the period before the update. Allow time, because search results often take weeks to settle.
| Outcome | Possible reading | Next step |
|---|---|---|
| Clicks and visits rise | The update improved relevance or snippet appeal | Note what you changed and apply it elsewhere |
| No change | Too early, or the page needs a bigger change | Wait, then reassess intent and depth |
| Decline | Possible loss of useful content or a mismatch with intent | Compare with the earlier version and restore what mattered |
| Better engagement only | Readers are happier even if visibility is flat | Add internal links and promote the page |
Be careful about drawing strong conclusions. Many things change at once: seasonality, competitors and search results themselves. Look for patterns across several pages instead of judging one post alone.
Update checklist and prompt bank
Use the checklist for each post you refresh.
- The purpose of the post and its reader are clear.
- The audit row is complete with a decision and owner.
- All time sensitive facts have been checked against a current source.
- All links work and support what they are attached to.
- Screenshots and images are current, or removed.
- Structure, headings and summaries have been improved where needed.
- New passages have been written or approved by a person.
- No invented statistics, quotes or product claims remain.
- Title and description match the updated content.
- Internal links to and from related pages are in place.
- The update has been logged and a next review date set.
Prompt bank you can adapt
- Review this post and list statements that may be out of date, with the sentence and why you think so. Do not rewrite anything.
- Suggest a clearer heading structure for this post, keeping the same meaning. Show old and new headings side by side.
- Rewrite this paragraph in plain language. Keep every fact exactly as written and do not add new claims.
- List five questions a reader may still have after reading this post, based only on the text provided.
- Turn this section into a numbered list of steps. Do not change the order or the meaning.
Frequently asked questions
How often should I review old posts?
It depends on how fast your topic changes. Fast moving subjects may need a check every few months, while stable topics may need only a yearly look. Set review dates for each important post when you publish or update it.
Will updating a post improve its search performance?
It can, but there is no guarantee. Improvements that make the page more accurate and useful give it a better chance. Track results over time and avoid expecting instant changes.
Should I change the date every time I edit?
No. Change the visible updated date only when you have made a meaningful change to the content. Minor typo fixes do not need a new date.
Can AI rewrite an entire old post?
It can produce a rewrite, but a wholesale rewrite risks losing what worked and introducing errors. A targeted approach, reviewing then editing specific sections, tends to give better results.
What if I cannot verify something in an old post?
Remove it or replace it with something you can support. A shorter accurate post is better than a longer one with doubtful claims.
Which AI tool should I use for content updates?
Any capable assistant can help with review and rewriting if you give clear instructions. If you are deciding on a tool, our guide on how to choose an AI tool sets out the questions to ask.
Conclusion
Updating old posts is steady, unglamorous work, and it pays off. It improves accuracy for readers, cuts down on duplicate and weak pages and builds on the value your site has already earned. AI makes the process faster by reviewing structure, spotting gaps and drafting changes, but the facts, the voice and the final approval belong to people.
Begin with a small audit of your twenty most important posts. Choose three to update this week, run each through the checklist, and record the changes. After a month, look at the results and decide how to continue. If you want to strengthen your wider process, our guides to writing blog posts with AI and checking AI output for mistakes are good companions to this one.



