Blog post management is the routine that keeps a business blog useful after the first few posts are live: a calendar tied to what you sell, a brief for each post, the same publishing fields every time, and a schedule for updating or retiring older posts. It is written for Twin Cities East Metro and St. Croix Valley owners and managers who already run a blog and want it to stay accurate, current and worth reading.

It follows the work in the order it happens. It does not cover how to pick a first topic; our guide to content creation and SEO covers what a local service business should publish first. This is general guidance, and the right pace is the one your team can keep up for years. Google says in its people-first content guidance that it has no preferred word count.

What blog post management covers

Think of every post as passing through seven stages, and give each stage one owner, even when one person holds all of them. The table shows what each stage settles and what to write down so someone else can pick the work up.

Scroll to see all columns

StageQuestion it settlesRecord it here
CalendarWhich service, season or customer question does this post support?A shared sheet with the topic, target page, owner and publish month
BriefWhat does the reader need to know, and what should they do next?One short document per post
Draft and fact checkIs every claim true and sourced?Source links, plus the name of the person who confirmed each technical point
PublishAre the title, description, links, byline and dates right?A checklist completed before the post goes live
UpdateIs anything in the post out of date?A review date on the calendar sheet
MeasureDid anyone find the post, and did they act?Search Console clicks and impressions by page, plus calls and form fills
RetireShould the post be merged, redirected or removed?A note with the reason and the replacement address

Plan a blog calendar around your services and seasons

A calendar earns its keep when each row points to something the business sells. Start with the three or four services you most want more work in, and list the questions a customer asks before hiring for each one. Those questions become posts, and each post links to the service page it supports. A post that supports no service is hard to justify.

Each row on the calendar needs the same few entries:

  • The question. Write it the way a customer would say it on the phone.
  • The service page it supports. If there is no such page, build that first.
  • The season. In our experience, Minnesota heating, snow removal, roofing and lawn companies see their questions change by month, so posts have to be live ahead of them.
  • The writer and the fact checker. Two people if you can manage it, since a second reader catches errors the writer misses.
  • A review date. The month you will reread the post and decide whether it still holds.

Our seasonal marketing calendar for Minnesota service businesses sets out the build, the trigger and the follow-through for each season. Use it to choose the publish month for each row.

Keep the plan small. Google's helpful content page lists warning signs for content made mainly for search engines, including producing lots of content on many topics in hopes that some of it performs. In our experience, twelve posts that each answer a real customer question are easier to maintain than fifty chasing keywords.

Write a brief and check the facts before you publish

A brief is half a page that keeps a post from drifting. Write it before the draft: the question the post answers, who is asking it (a homeowner in Woodbury weighing two repair options, or a property manager in Hudson), the service page it supports, the one next step for the reader, the sources you expect to cite, and the person who can confirm technical details.

The fact check matters more than the draft. Every price, code rule, license requirement and product claim needs a source you opened, a link beside the claim, and a year if the source is a study. Technical statements about your trade go to the person who does that work. Google's people-first page asks you to consider "who, how and why": who created the content, how it was produced, and why it exists. For automated and AI-assisted content, it says sharing details about the process can help readers understand the role automation served.

Drafting tools can help with first passes, and Google names the risk. Its spam policies describe scaled content abuse as mass-producing pages mainly to influence rankings, and one listed example is using generative AI tools to turn out many pages that add nothing for users. In our reading, a draft that a person has corrected with firsthand detail is a different thing from volume, but a schedule that depends on posts nobody on your team has read is the pattern to avoid.

Fill in the same publishing fields every time

Publishing goes wrong in small, repeatable ways: a vague title, a missing link, a date that contradicts the page. A fixed checklist catches them.

  • Title. Google's SEO Starter Guide describes a good title as one that is unique to the page, clear and concise, and an accurate description of what the page contains.
  • Web address. The same guide suggests including words in the URL that may be useful to users. Keep it short and keep it for the life of the post.
  • Internal links. Link to the service page the post supports and to one or two related posts, using link text that says what the destination page covers.
  • Byline. Google's people-first page encourages accurate authorship information where readers might expect it, and warns against made-up creator profiles. Use a real name that leads to real background.
  • Dates. Google's page on byline dates recommends a user-visible date labeled with text like "Published" or "Last updated", and says that if you also use structured data with datePublished and dateModified, the values should match what visitors see. It also says not to specify future dates.

Update, merge or retire older blog posts

Older posts are where most business blogs lose accuracy: a rule that changed, a service you dropped, a seasonal post that still describes last year. Decide each post's fate on a schedule.

Update when the facts change

Refresh a post when a price, rule, product or process in it has changed, and the post still answers a question customers ask. For a seasonal topic such as fall furnace checks or spring lawn work, update the one existing post before the season starts and keep its address, which also matches the approach in our seasonal calendar guide. Change the visible date and the structured date only when the content has substantially changed. Google's helpful content page names a date change without real edits behind it as a warning sign for search engine-first content, and says that adding or removing lots of content just to make a site seem fresh will not help.

Merge when two posts answer one question

When two posts answer the same question, readers and search engines have to choose between them. In our experience this builds up over years of writing "spring" and "early spring" versions of one idea. Pick the stronger address, fold the useful parts of the other post into it, and redirect the weaker address.

Retire and redirect when a post has no future

Retire a post when the service is gone, the advice is wrong and cannot be repaired, or the post never matched anything customers ask. Google's redirects documentation lists removing a page and wanting to send users to a new page as a use for a redirect, and says permanent redirects show the new target in search results. That page lists HTTP 301 and 308 as permanent server-side redirects. In our experience, send each retired post to its closest real equivalent, not to the home page. If nothing close exists, Google's HTTP status code page says that for 4xx responses such as 404 and 410, the indexing pipeline removes a previously indexed URL from the index.

Our guide to website SEO maintenance covers the monthly Search Console check that turns up the posts worth reviewing.

Measure the blog in Search Console

Google's Performance report help page counts a click each time a user clicks through to your site from Search results and an impression each time your site appears, gives click-through rate as clicks divided by impressions, and reports average position for the topmost result from your site. The default view shows the past three months, and you can group the table by queries or by pages.

Group by pages to see which posts earn impressions and clicks, then open one post and switch to queries to see the searches behind it. Three readings are worth acting on:

  • Many impressions, few clicks. The title or description may not match what the searcher wanted. Rewrite them to say what the post answers.
  • Clicks that fall after an edit. Compare the edit date with the drop and check what you changed.
  • No impressions weeks after publishing. Check the page with the URL Inspection tool. Google's SEO Starter Guide says the effect of a change can take anywhere from hours to several months to appear, and suggests allowing a few weeks before judging it.

Read clicks first and position second. In our experience, the position figure for a local search covers more than the ordinary blue links. The report page also cautions that what a searcher sees depends on their time, place, device and search history, so you may not see your own post when you search a query from the report. Pair the report with your call and form records to see which visits became bookings.

Decide who does what, and when to hand it off

A small team can run this with three roles: the owner supplies the facts and approves the post, one person owns the checklist and the calendar, and one person runs a short monthly review of Search Console and the review dates. When a role has no owner, the blog stalls at the same step each time.

If you would rather hand part of this off, our brand and copy work includes blog articles structured as real questions with direct answers, with every technical claim checked with you before it publishes, and you can contact McKinney Creative Ventures to ask whether it fits.