Re: When to Update Old Blog Posts on a Nashville Law Firm Site

Three years ago, a Nashville firm published a solid practice area post. It ranked, it drew traffic, everyone moved on. Lately the traffic has been sliding, not off a cliff, just a quiet, steady drift downward that nobody notices until someone pulls the numbers. This is content decay, and the instinct it triggers, “update everything on a schedule”, is the wrong response. Not every old post deserves a refresh, and treating them all the same wastes effort on posts that don’t need it while ignoring the ones that do.

This guide is about deciding which old posts to update and when, using signals rather than a blanket rule, and about choosing the right kind of update once you’ve decided.

Content Decay Isn’t a Cliff, It’s a Drift

Content decay rarely announces itself. A post doesn’t usually collapse overnight; it drifts, losing a little traffic at a time as competitors publish fresher material, as the topic evolves, as search results shift around it. Because it’s gradual, it’s easy to miss, which is exactly why it’s dangerous. By the time a decayed post is obviously underperforming, it’s been leaking value for a while. Recognizing decay as a slow drift rather than a sudden failure is what lets you catch it early.

Four Signals That Say “Update Now”

Rather than updating on a calendar, watch for four signals that a specific post actually needs attention. A steady traffic decline on a post that used to perform. A change in the underlying law or facts, a shift in Tennessee statute or a significant new decision, that makes the content outdated or inaccurate. A competitor who has published something clearly fresher and more complete on the same topic. And a shift in the search results themselves, new formats, new intent, that the old post no longer matches. When one or more of these fires, that’s your signal, not the calendar.

A Decision Framework for a Nashville Firm: Refresh, Rewrite, Merge, or Retire

Once a post is flagged, the choice isn’t just “update or don’t.” It’s which of four moves fits. Refresh, when the post is fundamentally sound but needs current information and light improvement. Rewrite, when the core is worth keeping but the execution needs to be rebuilt. Merge, when the post overlaps another and the two would be stronger as one. Retire, when the topic is no longer relevant and the post isn’t worth saving. For a Nashville firm working through a backlog of old practice area posts, running each flagged post against these four options prevents the reflex of refreshing things that should be merged or retired.

What a Real Update Looks Like

An important caution: a real update is not changing the date and republishing. Simply altering a publish date without genuinely improving the content can undermine trust rather than build it, and it doesn’t fix the decay. A real update means adding current information, improving accuracy and depth, updating examples, and making the post genuinely better than it was, so that it earns its position again. The date changes as a byproduct of real work, not in place of it.

Treating Legal Changes as a Content-Refresh Trigger, Not Just a Traffic Drop

Here’s a trigger most content-decay guides underweight because they think only in traffic terms: a change in the law itself. For legal content, an update to the relevant law or a significant new decision can make a post outdated even if its traffic hasn’t dropped yet. That means the refresh decision shouldn’t hang on traffic alone. A post can be quietly wrong before it’s quietly underperforming. Treating legal and factual changes as their own refresh trigger, independent of the traffic signal, keeps a firm’s content accurate rather than merely popular. The point isn’t a specific tracking mechanism; it’s that accuracy is its own reason to update.

FAQ

Should I update all my old posts regularly?
No. Update based on signals, traffic decline, changed law or facts, a fresher competitor, or a shifted search results page, rather than on a blanket schedule that wastes effort on posts that don’t need it.

Is changing the publish date enough to count as an update?
No. Changing the date without genuinely improving the content doesn’t fix decay and can undermine trust. A real update adds current information and makes the post genuinely better.

How do I choose between refreshing and rewriting?
Refresh when the post is fundamentally sound and needs current information. Rewrite when the core is worth keeping but the execution needs rebuilding. Merge or retire when the post overlaps another or is no longer relevant.

Does a legal change mean I should update, even if traffic is fine?
Yes. Accuracy is its own reason. A change in the relevant law can make a post outdated before its traffic drops, so treat legal changes as a refresh trigger independent of traffic.

Sort your blog posts by publish date and traffic trend to find your top few refresh candidates, then run each one through the four options in order: is it a refresh, a rewrite, a merge, or a retire? Decide the type before you touch the post.