How to Keep Old Blog Posts Accurate After Price Changes

The article you published in 2022 is still ranking. That's the good news. The bad news is it quotes a $89 service call fee you raised to $129 last spring, lists a product line you stopped carrying, and names an insurance partner you parted ways with. A prospect reads it, calls, and gets a different number than the one on the page. Now you're starting the relationship by explaining why your own website is wrong.

This is the unglamorous side of content operations. Writing is the part everyone plans for. Keeping what you already wrote from going stale is the part that gets skipped until it bites. The pages that rank best are usually your oldest ones, which means your most-visited content is also your most likely to be out of date.

Why stale content costs more than a bad look

There are three separate problems, and they compound.

The first is trust. A visitor who spots one wrong price assumes the rest of the page is unreliable too. You don't get credit for the 95% that's accurate.

The second is operational drag. Wrong information generates calls your front desk has to correct, quotes that don't match, and the occasional customer who insists on the old price because "the website said so." Every one of those is friction you created.

The third is search. When a page's facts no longer match reality, the experience degrades quietly. People bounce faster, ask fewer follow-up questions, and convert at a lower rate. Search engines notice behavior even when they can't read your price list. Over time a page that was accurate and useful becomes accurate-looking and useless.

Find the content that actually goes stale

Not every page decays at the same rate. A "history of our town" post can sit untouched for a decade. A "how much does X cost" page starts aging the moment a vendor raises a rate. Sort your library by how time-sensitive the facts are, and you can stop auditing everything and start auditing what matters.

Here's a simple way to tag every published page:

• Volatile — contains prices, fees, promotions, turnaround times, or current-year references. Review every 90 days.
• Semi-stable — describes services, processes, warranties, or staff/credentials. Review every 6 to 12 months or when something operationally changes.
• Evergreen — definitions, explainers, how-things-work content with no dated facts. Review once a year or when it stops ranking.

You can do this tagging in a spreadsheet in an afternoon. Pull your full URL list, add a column for category, and a column for "last reviewed." That spreadsheet is now your maintenance schedule.

Build a change-to-content map

The real fix is not a better audit cadence. It's connecting the moment something changes in the business to the pages that mention it. When you raise a price, you should already know which URLs need editing.

Create a lookup table that maps each volatile fact to the pages that reference it. Maintain it once, update it when you publish something new, and it pays off every time a number moves.

A worked example

Suppose a dental practice in Columbus runs a content program. They build a map like this:

When the practice drops one insurance plan, they don't have to remember every page that mentioned it. They open the map, see three URLs, and fix all three in ten minutes. Without the map, two of those pages would quietly stay wrong for a year.

How to build yours fast

1. List your 8 to 15 most volatile facts — the numbers and lists customers actually ask about.
2. Search your own site for each one. Use a site search (site:yourdomain.com "$149") or your CMS search to find every mention.
3. Record the URLs next to each fact.
4. Add one habit: whenever you publish a new page that cites one of those facts, add the URL to the map.

The map takes an hour to build and turns a dreaded quarterly hunt into a five-minute update.

How often should you audit content for accuracy?

Review volatile pages every 90 days, semi-stable pages once or twice a year, and evergreen pages annually — but trigger an immediate check any time a price, service, or partnership actually changes. The calendar cadence catches slow drift, like a competitor-era stat that's now four years old. The event trigger catches the sharp changes that do the most damage, like a fee increase that makes your published number wrong the same day. You need both. A practice that only does calendar reviews can run a wrong price for 89 days; a practice that only reacts to events misses the gradual rot.

Put the calendar reviews on a recurring task and tie the event trigger to the moments changes happen: whoever updates the price list, signs or ends a vendor relationship, or launches a promotion also pings whoever owns the content map. One line in your internal process — "did this change touch any published pages?" — prevents most stale-content problems.

What should I actually check on each page?

Check every number, every list, every dated reference, and every claim that depends on a current fact. Work from a fixed checklist so nothing slips:

• Prices and fees — do they match today's price list exactly?
• Promotions and offers — is the deal still running, and is the expiration date in the future?
• Services and products — do you still offer everything named? Anything new missing?
• Partners and credentials — insurers, certifications, brands, memberships still current?
• Dated language — "this year," "recently," "new in 2023," or stats that now look old.
• Contact and logistics — hours, service area, phone, booking links.
• Internal links — do they still point to live, relevant pages?

A page passes only when every line checks out. Then update the "last reviewed" date in your spreadsheet so you know it's clean.

Decide between editing, redirecting, and dating

Not every outdated page should be rewritten. Three options:

Edit in place when the page still earns traffic and the facts just need refreshing. Keep the same URL so you don't lose the ranking history. Most volatile pages belong here.

Redirect when the service no longer exists and there's a close replacement. Point the old URL to the new page with a 301 so the authority carries over.

Add a visible date on content where freshness matters to the reader. A "last updated" line sets expectations and, when it's genuinely recent, reinforces that you keep the page maintained. Only use it if you actually update on a schedule — a two-year-old "last updated" date does more harm than no date.

One caution on prices specifically: if your pricing changes often, consider writing ranges or "starting at" figures and pointing to a single live pricing page or quote form. One source of truth is easier to keep accurate than fifteen hard-coded numbers scattered across blog posts.

Make maintenance someone's job

Accuracy fails when it's everyone's responsibility, which means it's no one's. Assign one owner for the content map and the review calendar. If your program is run by an outside team, this is worth asking about directly — a provider like ClearPath Content should be able to tell you how they track which pages reference which facts, not just how many articles they ship a month. Publishing volume without a maintenance system builds a larger pile of pages that will eventually be wrong.

The practical takeaway: your rankings concentrate in your oldest content, and your oldest content is where errors hide. Spend one hour building a change-to-content map, put volatile pages on a 90-day review, and add a single question to whatever process changes your prices. That's most of the work, and it's the difference between a library that compounds in value and one that quietly turns into a liability.