Content Refresh Checklist: Decide What to Update in a B2B Blog

A content refresh is worth doing when a post still answers a question your buyers have, but answers it badly: the facts are out of date, the answer is buried, or the page leads nowhere. Fix those three things, keep the URL, and record what you changed. Most posts need an hour or two of work. A full rewrite is rarely called for.

The checklist comes first. After it: how to choose which posts to refresh, a worked example, and what to do about dates.

The checklist

Run it top to bottom on one post. Each check has a pass condition; anything that fails goes on the edit list.

Before you edit

#	Check	Pass looks like
1	Purpose	You can state in one sentence who the post is for and what they are deciding
2	Baseline saved	A copy of the current text, plus the page's Search Console queries, clicks and impressions for the last three months
3	Overlap	No other page on your site answers the same question for the same reader
4	Still in range	You still make or supply what the post discusses

If check 1 fails, stop. A post with no identifiable reader cannot be refreshed into one; see the triage table below. If check 3 fails, settle which page owns the topic before touching either. Keyword cannibalization explains how.

For check 2, open the Search Console Performance report, filter to the page and export the queries. Leave a note of anything else that changed in the period, such as a redesign, a migration or a discontinued product, so that it is not later blamed on the writing.

Accuracy

#	Check	Pass looks like
5	Company facts	Every statement about your range, process, documents or terms has been confirmed this month by the person who owns it
6	Technical facts	Standards, grades and specifications cited are the current revisions
7	Numbers	Each figure has a source you can open, or it is removed
8	Outbound links	Every external link loads and still says what the sentence claims

Check 5 is the one that pays. A post from three years ago may quote a size range you have since extended, a finish you no longer offer or a certificate that has lapsed. Send the owner the specific sentences and ask for yes or no on each.

Usefulness

#	Check	Pass looks like
9	Answer first	The first two sentences answer the question in the title
10	Query match	The queries from check 2 are answered somewhere on the page
11	Something to use	The post contains a table, checklist or worked example a buyer could apply
12	Dead weight	No section exists only to add length

Check 10 is where the baseline earns its place. If the post appears for "316 vs 304 fasteners marine" and never mentions marine use, the refresh is a section on that. Check 12 runs the other way: remove the industry-history opening and the paragraph defining what a fastener is. Google's helpful content guidance states that it has no preferred word count, so a shorter post that answers sooner loses nothing by being shorter.

Route

#	Check	Pass looks like
13	Next step	One call to action that fits this reader's stage and says what to send
14	Links in and out	The post links to the product page it supports, and that page links back

For check 13, the CTA examples by buyer stage give wording. For check 14, look at what links to the post as well as what it links to. An article reachable only from page six of the blog archive is hard for buyers to find however good it becomes.

Which posts to refresh first

Not every old post deserves the checklist. Sort them with this table.

What you see	Likely cause	Action
Impressions steady, clicks falling	Title or opening no longer matches what searchers want	Refresh: checks 9 and 10 first
Appears for relevant queries, sits low on the page of results	Answer is thin compared with what ranks	Refresh: checks 10 and 11
Visits, but no inquiries mention it	Wrong reader, or no next step	Refresh: checks 1 and 13
States something no longer true	Product or process changed	Correct today; run the rest later
Two posts, same question	Overlap	Merge into the stronger URL and redirect the other
No impressions, no reader you can name	Never had a purpose	Leave it; spend the time elsewhere
Performs well, facts current	Nothing wrong	Leave it alone

The last two rows matter as much as the first five. A working post gains nothing from being rewritten, and a pointless one is not rescued by better sentences.

When you merge, Google's redirect documentation recommends a permanent server-side redirect from the retired URL to the one you keep, so visitors and search engines both land on the surviving page.

Compare like with like when reading the numbers. A supplier whose buyers order before the building season should compare this spring with last spring, not with winter.

Example: one post through the checklist

Example (fictional supplier). Tarrant Enclosures is an invented maker of steel and stainless electrical enclosures. Its post "Choosing an enclosure material" was published three years ago. The marketer runs the checklist.

• Check 1, purpose: fails at first. The post addresses "anyone choosing an enclosure". Rewritten as: a panel builder choosing between painted steel and stainless for an outdoor cabinet.
• Check 2, baseline: Search Console shows the page appearing for queries about stainless enclosures in coastal and food-processing settings. The post mentions neither.
• Check 3, overlap: passes. The product pages list materials but give no selection advice.
• Check 5, company facts: two failures. The post says the largest cabinet is a size the factory has since exceeded, and lists a galvanised option that was dropped. The production manager corrects both by email.
• Check 7, numbers: one failure. A corrosion-life figure has no source and nobody remembers where it came from. Removed.
• Check 9, answer first: fails. The post opens with two paragraphs on the history of enclosures. Replaced with a two-sentence selection rule.
• Check 10, query match: fails. A section is added on coastal and washdown environments, written from the engineer's answers.
• Check 11, something to use: fails. A table is added: environment, recommended material, what to state in the inquiry.
• Check 13, next step: fails. "Contact us for more information" becomes a request for the installation environment, cabinet size and ingress rating required.
• Check 14, links: fails. The post linked to nothing. It now links to both product pages, and each product page links to it from its materials line.

Eight of the fourteen checks produced an edit. The post lost its first two paragraphs and an unsourced number and gained one section, one table and a specific ask. The URL is unchanged. The change log records each item, who approved the facts and the date.

No result is claimed here, because the example is invented. In a real refresh the baseline from check 2 is what you compare against two or three months later.

After you publish

Write the change log. Reason for the refresh, sections changed, facts confirmed and by whom, links added, date. Six lines. In a year it will explain why the page says what it says.

Check the live page. Open the public URL in a private window. A saved edit and a visible edit are different things, particularly behind a cache.

Ask for a recrawl if the change is substantial. The Search Console URL Inspection tool lets you request that Google crawl the page again. Google's own help page says a request does not guarantee inclusion in the index.

Set a date to look again. Compare the same queries over a matching period, and note anything else that changed. Use the B2B blog metrics guide to connect visits to inquiries. A before-and-after difference tells you something happened and leaves open what caused it.

What to do about the date

Show the date of the last substantial update, and keep the original publication date in your records. Google's guidance on byline dates says a date must reflect when the page was actually published or updated, and that the date visible on the page should agree with the one in the page's structured data.

So a corrected specification, a new section or a rewritten answer is a reason to update the date. Fixing a typo is not. Changing only the date to make an untouched post look new misleads the reader, who is the person you were trying to help.

When a refresh is the wrong tool

If the checklist leaves you wanting to change the reader, the question and the format, you are describing a new article. Write it at a new URL and decide separately what happens to the old one. Update an old post or write a new one gives the rule for that decision.

Blogo does not refresh old posts for you. It handles the step after: it recommends what to write next from your site's pages and Search Console data, as described on what to write next.

FAQ

How often should we refresh a blog post?

When something changes: your product, a standard, what buyers ask, or the page's search performance. A yearly look at every post that brings in visits is a reasonable reminder. Rewriting on a schedule regardless of need is wasted effort.

Does updating old content help SEO?

It can, when the update makes the page a better answer to what people search for. It does nothing when the only change is the date or a few swapped words. Nobody can promise the outcome in advance.

Should we change the URL when we refresh?

No. Keep the URL if the post serves the same question. Changing it breaks every existing link to the page unless you add a redirect, for no benefit to the reader.

Should we delete old posts that get no traffic?

Only if they are wrong or embarrassing. An accurate post nobody reads costs nothing. A post that states something false about your products should be corrected or removed today, whatever its traffic.

How long does a refresh take?

For a post that fails four or five checks, a couple of hours plus the wait for the fact owner's reply. That wait is usually the longest part, so send the questions first.