[{"data":1,"prerenderedAt":30},["ShallowReactive",2],{"blog-body-content-refresh-playbook-en":3},{"content":4,"toc":5},"\u003Cp>Refreshing an old post is usually faster than writing a new one and frequently produces a larger return. The existing page already has history — some age, some links, some record of how it performs for real queries — and updating it can move it without starting from zero.\u003C\u002Fp>\n\n\u003Cp>The difficulty is deciding which posts deserve the work, and then resisting the urge to rewrite them from scratch. Most refreshes fail because they turn into rewrites, and a rewrite discards the history that made the post worth refreshing in the first place.\u003C\u002Fp>\n\n\u003Ch2 id=\"which-posts-deserve-the-work\">Which posts deserve the work\u003C\u002Fh2>\n\n\u003Cp>Not every page is worth touching. Sort them by looking at three signals together, because any one alone will mislead you.\u003C\u002Fp>\n\n\u003Cul>\n  \u003Cli>\u003Cstrong>Impressions without clicks.\u003C\u002Fstrong> The page appears in results and people do not choose it. This usually means the title or the description is failing, and it is often the cheapest fix available.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Ranking between roughly five and twenty.\u003C\u002Fstrong> Close enough that an improvement in depth or relevance could move it onto page one, far enough that nothing is currently working.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Decaying traffic.\u003C\u002Fstrong> A page that used to perform and no longer does. Something changed — the query, the competition, or the accuracy of the content.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Cp>Pages ranking first with stable traffic need nothing. Pages ranking past thirty usually need a different page, not a better one. The middle band is where refreshing pays.\u003C\u002Fp>\n\n\u003Ch2 id=\"the-four-types-of-refresh\">The four types of refresh\u003C\u002Fh2>\n\n\u003Cp>Match the action to the diagnosis. They take very different amounts of effort.\u003C\u002Fp>\n\n\u003Col>\n  \u003Cli>\u003Cstrong>Metadata refresh.\u003C\u002Fstrong> The content is fine and the click-through rate is low. Rewrite the title and description only. Twenty minutes.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Structural refresh.\u003C\u002Fstrong> The content is good but poorly organised — sections in the wrong order, no clear headings, the answer buried. Reorder and re-head, keeping the prose. One hour.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Substantive refresh.\u003C\u002Fstrong> The content is thin or outdated. Add missing sections, replace stale examples, remove anything that no longer applies. Two to four hours.\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Consolidation.\u003C\u002Fstrong> Several posts compete for the same topic. Merge them into one, redirect the others. Half a day.\u003C\u002Fli>\n\u003C\u002Fol>\n\n\u003Cp>Most people jump straight to the third option when the first would have solved it. Diagnosing before acting is the difference between an hour of work and a lost afternoon.\u003C\u002Fp>\n\n\u003Ch2 id=\"updating-without-losing-rankings\">Updating without losing what you have\u003C\u002Fh2>\n\n\u003Cp>The main risk in a refresh is losing the elements that earned the page its current position. Three rules reduce it.\u003C\u002Fp>\n\n\u003Cp>Keep the URL. If the address must change, redirect the old one permanently and update every internal link that points at it — a redirect that is only linked from one place passes much less than a direct link.\u003C\u002Fp>\n\n\u003Cp>Keep the parts that are working. Before editing, note which sections match queries the page already ranks for. Those sections are earning impressions; changing them risks the position they hold. Add around them rather than through them.\u003C\u002Fp>\n\n\u003Cp>Do not change everything at once. If the refresh produces a drop, you want to know which change caused it. Metadata edits and content edits in the same week leave you guessing.\u003C\u002Fp>\n\n\u003Ch2 id=\"rewriting-the-opening\">Rewriting the opening\u003C\u002Fh2>\n\n\u003Cp>The introduction is usually the most worthwhile single edit, because it is where an outdated premise does the most damage. A post written two years ago often opens with context that no longer needs explaining and a promise that no longer matches what the page delivers.\u003C\u002Fp>\n\n\u003Cp>Read the first paragraph and ask whether it still names the problem the way a searcher would describe it today. Vocabulary shifts. Terms that were current become dated. If the opening uses the old vocabulary, the page reads as out of date to both readers and search engines, regardless of how accurate the body is.\u003C\u002Fp>\n\n\u003Cp>Then check the promise. If the article now contains more than the opening claims, update the claim — a page that delivers more than it promises is consistently underrated by everyone who skims it.\u003C\u002Fp>\n\n\u003Ch2 id=\"adding-what-was-missing\">Adding what was missing\u003C\u002Fh2>\n\n\u003Cp>Find what people actually asked that the page does not answer. The most reliable sources are the queries the page already receives, the questions in any comments it has, and the questions you have been asked directly about the same subject since publishing.\u003C\u002Fp>\n\n\u003Cp>Add those as sections, in the reader's words. A page that answers fourteen real questions ranks better than one that answers five conceptual ones, and it is also a page people bookmark rather than visit once.\u003C\u002Fp>\n\n\u003Cp>What to remove matters as much as what to add. Anything that is now wrong, anything that references a tool or method that no longer exists, and anything that was only there to fill space. Removing a weak section often improves a page more than adding a strong one, because the weak section was costing the reader's patience before the good part.\u003C\u002Fp>\n\n\u003Ch2 id=\"consolidating-competing-posts\">Consolidating competing posts\u003C\u002Fh2>\n\n\u003Cp>When two or three posts cover the same ground, combining them usually beats improving any one of them. Keep the URL with the better history, make it the merged page, and redirect the others to it permanently.\u003C\u002Fp>\n\n\u003Cp>Do the merging properly rather than by concatenation. Merge the outlines first, remove the duplicated sections, and only then write the resulting page. Concatenating two articles produces a long article with two introductions and the same point made twice, which is worse than either original.\u003C\u002Fp>\n\n\u003Cp>Then update internal links so that everything that pointed at the retired URLs now points at the surviving one directly, and remove the old URLs from the sitemap.\u003C\u002Fp>\n\n\u003Ch2 id=\"what-to-record\">What to record\u003C\u002Fh2>\n\n\u003Cp>Keep a short log per refresh: the date, what changed, and why. Refresh decisions are difficult to reconstruct later, and without a record you will eventually reverse a change whose original reason you have forgotten.\u003C\u002Fp>\n\n\u003Cp>The record also builds something more useful than a single improved page. After a year it tells you which types of refresh actually move your site — and that is a far better guide for the next hundred edits than any general advice, including this article.\u003C\u002Fp>\n\n\u003Ch2 id=\"when-to-retire-instead\">When to retire instead\u003C\u002Fh2>\n\n\u003Cp>Some pages should be removed rather than improved. A page that has never received impressions after several months, that duplicates something else, or that describes a product or service you no longer offer is a liability: it dilutes the site's focus and it can waste crawl attention.\u003C\u002Fp>\n\n\u003Cp>Retiring means removing the page and returning a proper not-found response, or redirecting it to the closest relevant page if there is a genuine one. What it does not mean is leaving the page in place with no internal links — an orphan page with thin content is not neutral, it is a small ongoing cost.\u003C\u002Fp>",[6,9,12,15,18,21,24,27],{"id":7,"text":8},"which-posts-deserve-the-work","Which posts deserve the work",{"id":10,"text":11},"the-four-types-of-refresh","The four types of refresh",{"id":13,"text":14},"updating-without-losing-rankings","Updating without losing what you have",{"id":16,"text":17},"rewriting-the-opening","Rewriting the opening",{"id":19,"text":20},"adding-what-was-missing","Adding what was missing",{"id":22,"text":23},"consolidating-competing-posts","Consolidating competing posts",{"id":25,"text":26},"what-to-record","What to record",{"id":28,"text":29},"when-to-retire-instead","When to retire instead",1791511468168]