A company blog does not break the way a store breaks - it never goes down on a Friday night, it quietly loses the traffic it used to bring in. That is why WordPress blog maintenance looks from the outside like the easiest flavour of keeping a site alive, while in practice it is the one where problems are hardest to spot. There is no checkout refusing payments, no courier integration throwing errors. There is an archive that grows every month and that nobody ever looks at. Looking after a company blog on WordPress is mostly about that archive.
Technically a blog is WordPress, a theme, a handful of plugins and - this is the difference - dozens or hundreds of posts, plus a media library, categories, tags, comments and the accounts of people who once wrote here. An outage on that setup is cheap. Neglect gets expensive, because every old post is a separate front door from Google, and when those doors start closing nobody tells you. No customer calls to say an article from two years ago still quotes a price that no longer exists.
Below I go through what a blog actually needs every month, what rots when nobody does it, and what that costs - including the cases where a monthly retainer makes no sense and a quarterly review is enough.
WordPress blog maintenance - what the monthly work really is
The list is shorter than for a store, but every item looks different, because it is about content rather than sales.
- Updates checked on the post template, not on the home page. On a blog it is the single post template, the post listing and the category pages that drift after a theme update. The home page can look perfect while paragraph spacing has collapsed inside articles or the table of contents has stopped generating.
- Backups that include the database. A blog’s content lives in the database, not in the files - a file-only backup saves your theme and recovers exactly zero posts. I wrote separately about backups that actually restore.
- A Search Console review. That is what monitoring means on a blog. Not a pinger checking whether the site responds, but the report of excluded URLs, 404s and posts that lost clicks over the last few weeks.
- Comments and forms. Comment spam bloats the database and publishes links to places you do not want to be associated with. The newsletter signup form stops sending more often than anyone notices, because nobody tests a form they never use themselves.
- The media library. Every post adds images, and WordPress adds several resized copies of each one. After two years of publishing this is the heaviest part of the site and the usual reason why the one post that gets traffic is also the slowest to load. What to do about it is in the piece on image optimisation with WebP and AVIF.
- A review of the content-side plugins. Related posts, share buttons, table of contents, galleries - these are the plugins authors abandon most often. A plugin with no update for a year is not a feature problem, it is an open door.
- Author accounts. Someone left the company two years ago and their administrator account still works and still signs posts. Both are worth cleaning up.
What rots in a neglected blog and how it shows up in Google
The usual scenario does not look like a failure. It looks like a slow slide spread over a year or more.
It starts with the content. A post from three years ago still ranks for its phrase, but it quotes prices, plugin versions and regulations that no longer apply. Google keeps it there, because links and history do their job, yet the reader arrives, sees “as of 2023” and leaves. That post now does more damage than its absence would, because it shows a company that stopped minding its own words.
Then come the URLs. Someone changed a post title and its address along with it; someone else deleted three old texts during a tidy-up. The effect is visible only in Search Console: the number of 404s goes up, and with them go clicks nobody missed, because nobody was counting them. If your posts have stopped appearing in results at all, start with the diagnostics in the piece on why a site is not showing up in Google.
The third layer is a messy archive. Years of publishing produce dozens of tags used exactly once, and each of them is a separate page with one link and no content of its own. Google then sees a site with more empty pages than useful ones, and treats it accordingly.
On top of that sit the small things that mean nothing alone and together read as an abandoned place: outbound links to pages that no longer exist, a sitemap not refreshed in months, an RSS feed returning an error, an on-site search box that cannot find the site’s own posts.
Redirects and archive hygiene - the part everyone forgets
This is work that appears in no standard “WordPress maintenance” package, and on a blog it matters more than half of what does appear there.
Rule one: changing a title is not the same as changing a URL. Polish titles as much as you like; change a post’s address only when you have a genuinely good reason, and always leave a 301 redirect from the old URL to the new one. The redirect costs a minute. Skipping it costs all the visibility that post spent years collecting.
Rule two: deleting a post also requires a decision about where its old URL should lead. A default 404 is the worst option and redirecting everything to the home page is barely better. The sensible target is the closest surviving post on the same subject.
Rule three: two weak texts on one topic are worth less than a single strong one. When I tidy an archive, I usually merge the content into the stronger post and redirect the weaker URL to it. That is the same work as writing something new, only cheaper and with a search history already attached.
And finally, tags. Do not invent new ones with every post. Fifteen tags used regularly are worth more than a hundred used once, and the once-used ones should either be folded into existing tags or kept out of the index.
A blog versus a company site - smaller scope, different risk
There is a common belief that a blog is a lighter version of a company site, so its maintenance can be lighter too. The first half is true. The second is not.
There genuinely are fewer moving parts. No payments, no orders, no warehouse or accounting integrations, and post-update testing comes down to checking a post, the listing and the contact form rather than an entire purchase path. The full scope for an ordinary company site is in the piece on what WordPress maintenance should include.
But the risk sits somewhere else. A company site has a few pages and one way in - when it goes down you know within the hour, because enquiries stop arriving. A blog has hundreds of ways in, one per post, and each of them can go dark on its own with no signal at all. Downtime on a blog is cheap. A year without maintenance can cost more than a week of a site being offline, except the bill arrives late and nobody connects it to the cause.
So on a blog I shift the weight of the work from reacting to reviewing. When I take a site under ongoing support, on a store I mostly make sure sales never stop, and on a blog I make sure the archive does not rot - two different jobs under the same name.
What blog maintenance costs, and when a quarterly review is enough
A company blog sits in my lowest maintenance tier - from 1,000 PLN net a month (Polish market rates). That covers technical upkeep, backups, the review and a pool of time for fixes; on a blog that pool usually goes not into repairs but into archive hygiene and refreshing older posts.
A monthly rhythm makes sense when the blog is genuinely alive: you publish regularly, more than one person writes, and the posts bring enquiries you can count. Then there is something to do every month and you can see what you are paying for.
If the blog gets one new post a quarter and traffic is modest, I will say plainly that a retainer does not pay for itself. A quarterly rhythm run in-house works better, with a short checklist: updates with a backup before and a post checked afterwards, a look at the 404s in Search Console, comment spam cleared, a glance at plugins with no recent update, and a read of the three most visited posts hunting for details that are no longer true. That is an hour, maybe two, per quarter.
The line between the two is simple. If you have not opened Search Console once in the last six months and cannot say which post brings you the most visits, the question is not which package to buy - it is that nobody is looking after the blog at all. In that case I start with a one-off clean-up, and only afterwards is it clear whether ongoing maintenance is needed.
Frequently asked questions
Does a blog need its own maintenance if it sits on the same site as the offer pages? Technically it is one WordPress install and one backup, so you do not need a separate contract. The scope of work differs, though: on the offer pages you watch a handful of pages and a form, while a blog adds an archive that grows on its own and needs a regular review. Just make sure the agreed scope names the content-side tasks, not only updates and backups.
What should I do with old posts that are out of date? In this order: check in Search Console whether the post still brings visits. If it does, update the content at the same URL, because the URL is worth more than the text. If it brings nothing and duplicates another post, merge the content and redirect the old URL to the one that stays. Deleting without a redirect is the worst of the available options.
Should I turn comments off on a company blog? If there has not been a single genuine comment in a year and all you moderate is spam, then yes - switch them off and take that time back. On a blog where readers actually ask questions I keep comments, but always with moderation before publishing and a spam filter, because open unmoderated comments fill up with links within days.
How often should plugins be updated on a blog that publishes once a month? The update rhythm depends on when patches ship, not on how often you publish. On a blog with no sales a monthly review is enough, but security patches - especially for plugins exposed to logged-out visitors, such as forms and comments - go in immediately. A blog gets attacked exactly like a store, because bots do not check whether there is money to be made.
Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.