{"id":16,"date":"2026-10-31T09:00:00","date_gmt":"2026-10-31T08:00:00","guid":{"rendered":"https:\/\/agreatarchie.nl\/blog\/how-to-update-old-blog-posts"},"modified":"2026-10-31T09:00:00","modified_gmt":"2026-10-31T08:00:00","slug":"how-to-update-old-blog-posts","status":"publish","type":"post","link":"https:\/\/agreatarchie.nl\/blog\/how-to-update-old-blog-posts","title":{"rendered":"How to Update an Old Blog Post Instead of Publishing a New One"},"content":{"rendered":"<p>Knowing how to update old blog posts matters because the alternative \u2014 publishing a new post on the same topic \u2014 usually means competing with yourself. A new post starts from zero: no rankings, no backlinks, no history. The old post already holds assets you spent effort earning: an indexed URL, links from other sites, internal links from your own pages, and a record with search engines of what it is about. A substantial update keeps all of that and fixes what time has done to the content. In most cases where a topic needs new information, the refresh is faster, cheaper and more effective than the rewrite-from-scratch \u2014 and it is the work most blogs skip entirely.<\/p>\n<h2>Update or publish new? The decision<\/h2>\n<p>Update the existing post when the topic and the searcher&#8217;s intent are the same, when the old post ranks now or ranked before, and when what it needs is correction, completion or modernising. The facts have moved on, a tool has changed, a section is missing \u2014 these are update jobs.<\/p>\n<p>Publish a new post when the angle, audience or intent is genuinely different: a beginner&#8217;s version and an advanced one, a guide and a case study. And when an old post covers a dead topic, or was too thin to save, the honest options are to merge it into a stronger page or remove it \u2014 not to leave it quietly rotting, and not to publish a twin beside it. If the old post&#8217;s real problem is that it was never written for search properly in the first place, our breakdown of <a href=\"\/blog\/seo-copywriting-mistakes\">SEO copywriting mistakes<\/a> lists the usual causes, and <a href=\"\/blog\/seo-copywriting-cost\">how much SEO copywriting costs<\/a> sets out what a proper rewrite involves.<\/p>\n<h2>Choosing which posts to refresh<\/h2>\n<p>Work from evidence, in Google Search Console. Look for posts with impressions but declining clicks \u2014 search engines still show them, readers are drifting away. Posts sitting around positions five to twenty are the priority: close enough that a serious update can move them onto the first page or up it. Add posts whose facts have visibly aged, and any post with backlinks worth protecting, since its links keep paying as long as the page deserves them. Rank candidates by that combination \u2014 closeness to page one, the value of the topic, the staleness of the content \u2014 and refresh the top of the list properly rather than all of them thinly.<\/p>\n<h2>How to update an old blog post, step by step<\/h2>\n<ul>\n<li><strong>1. Read it as a stranger.<\/strong> Does it still answer the search it ranks for, in the order a reader needs? Note every place it fails before touching anything.<\/li>\n<li><strong>2. Fix the facts.<\/strong> Dates, prices, names, tools, claims, screenshots \u2014 anything time has overtaken. Wrong facts are the one part of a refresh that is never optional.<\/li>\n<li><strong>3. Close the gaps.<\/strong> Add the subtopics competitors now cover and the questions readers now ask that the original missed. This is where most ranking gains live: the update makes the post the most complete answer again.<\/li>\n<li><strong>4. Rework the title, introduction and meta description<\/strong> if the intent has shifted or the click-through is weak \u2014 keeping them honest to what the post now contains.<\/li>\n<li><strong>5. Repair and extend the links.<\/strong> <a href=\"\/services\/technical-seo-audit\">Replace dead links<\/a>, add internal links to newer related posts, and go to those newer posts and link back. A refresh that improves the page&#8217;s connections improves two pages at once.<\/li>\n<li><strong>6. Refresh the supporting material.<\/strong> Images, examples and data should match the current version of the thing described, not the version from the year of publication.<\/li>\n<li><strong>7. Update the date \u2014 if the work earns it.<\/strong> A substantial update justifies a new date; a cosmetic one does not.<\/li>\n<li><strong>8. Resubmit the URL<\/strong> in Search Console so the revised page is re-crawled promptly rather than whenever the crawler next passes.<\/li>\n<\/ul>\n<h2>What a content refresh should not do<\/h2>\n<p>Do not change the URL. Do not make three small edits and call the post updated \u2014 a content refresh that changes little signals little. Do not rewrite so completely that the page stops matching the intent it ranked for; evolution beats replacement. And do not, under any circumstances, publish a near-duplicate alongside it: two of your own pages chasing one search is how both end up ranking below a competitor&#8217;s single, better one.<\/p>\n<p>This is exactly the work our <a href=\"\/services\/content-refresh\">content refresh service<\/a> exists to do \u2014 auditing a library, choosing the candidates by evidence, and updating them properly. Whether you hand it over or run it yourself, make it a habit rather than a rescue mission: an archive that is maintained stops being a pile of posts you wrote once and becomes a library that keeps earning.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Should I change the URL when I update a post?<\/h3>\n<p>No \u2014 keep the URL exactly as it is. The existing address carries the backlinks, internal links and ranking history that make updating worthwhile in the first place; changing it discards them. The rare exception is a URL that is itself wrong or misleading, and then the old address must redirect properly to the new one.<\/p>\n<h3>Should I update the published date on a refreshed post?<\/h3>\n<p>Only when the update is substantial and real \u2014 facts corrected, sections added, a genuine revision a reader would notice. Changing the date on an untouched post misleads readers and search engines, and it spends trust you will want later. When the work is real, updating the date is honest and helps readers judge the content.<\/p>\n<h3>How often should I refresh old content?<\/h3>\n<p>Review your most valuable and nearly-ranking posts about quarterly, audit the whole library roughly once a year, and fix anything that has become factually wrong the moment you spot it, whatever its age. Fast-moving topics need the quarterly rhythm; stable explainers can wait for the annual pass.<\/p>\n<h3>When is a new post genuinely the better choice?<\/h3>\n<p>When the angle, the audience or the search intent is truly different from the existing post \u2014 a different question being answered, not the same question reworded. Two pages can then coexist without competing. If a searcher would be equally well served by either page, you do not have two topics; you have one post to update.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to update old blog posts instead of publishing new ones: when a refresh beats a new post, how to choose the candidates, and the steps that make it count.<\/p>\n","protected":false},"author":0,"featured_media":42,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-16","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo-copywriting"],"_links":{"self":[{"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":0,"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/media\/42"}],"wp:attachment":[{"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agreatarchie.nl\/blog\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}