Prune or Merge? What to Do With Thin Cafe Blog Posts

Thomas Garner

Oct 7

12 min read

Flat lay photography of coffee latte with art

Short answer: do not delete your way through an old blog based on a gut feeling that it looks weak. Judge each post against a few plain criteria, keep short posts that still do a real job, merge posts that answer the same question twice, and delete only what is wrong, empty, or actively unhelpful, adding a redirect where one genuinely helps a visitor or a search engine find the replacement.

This question tends to arrive after an owner reads something about thin content hurting a site and looks at their own blog, twelve posts about a seasonal drink, three event recaps, one long guide someone actually put effort into, and panics. The instinct to clean house is not wrong. The instinct to delete everything short is, because length alone is not what makes a post thin, and Google's own guidance on this talks about helpfulness, not word counts.

This post walks through the sort in three parts: the criteria for judging any individual post, the five actions that criteria points you toward, and the risks worth knowing before you touch anything, especially before you set up a single redirect.

The Criteria, Before Any Action

Before deciding what to do with a single post, judge it against four plain questions. Is it accurate, meaning nothing on the page is out of date or simply wrong today. Does it answer a real question a visitor might actually search for, even a small one, rather than existing only because a calendar said post something this week. Does it get any visits or any links from elsewhere, which is a signal worth checking even loosely rather than assuming. And does it duplicate another post on your own blog covering the same ground, which is a different problem than being short or being old.

Notice that word count is not one of these four questions. A three paragraph post that answers one specific question clearly, your hours on a specific holiday, whether you take reservations, what a specific seasonal drink tastes like, can be a genuinely useful page even at a few hundred words. A fifteen hundred word post that rambles without ever answering anything a reader searched for is the actual definition of thin, regardless of its length. Google's own guidance on creating helpful, reliable, people first content frames the standard around whether content serves the reader, not around a minimum word count, and that framing is worth taking seriously rather than treating length as a proxy for it.

Run every post on your blog through these four questions honestly. A post can fail one question and still be worth keeping, a short but accurate post about a discontinued seasonal item might still get the occasional search from someone remembering it fondly. A post can pass the length test and still deserve deletion, if it duplicates a better post you already wrote or contains information that is now simply false. The four questions together, not any one alone, decide what happens next.

It helps to write the answer to each question down rather than judging by feel while scrolling past a post's title in a list. A quick spreadsheet with one row per post and one column per question, accurate, answers a real question, gets visits or links, duplicates another post, turns a vague sense of a messy blog into something you can act on. It also keeps you honest, since a post that felt embarrassing to reread a year later might still answer yes to two or three of the four questions, and a post that reads fine might quietly answer no to all of them.

The Five Actions

Once a post has been judged, it falls into one of five actions. Keep is for posts that are accurate, answer a real question, and stand on their own without overlapping another post, even if they are short. Update is for posts with real bones but outdated details, a menu item that changed, an event date that passed, a fact that needs a fresh pass rather than a full rewrite. Merge is for two or more posts that answer close to the same question, where combining them into one stronger post serves a reader better than making them choose between two thin ones. Redirect is a technical step that usually accompanies a merge or a delete, sending an old URL to wherever its content now lives. Delete is reserved for posts that are wrong, empty, or actively unhelpful, with nothing in them worth folding into anything else.

A decision table helps make this concrete. Accurate, answers a real question, unique: keep as is. Accurate but stale in a detail or two: update. Overlaps closely with another post on the same topic: merge the weaker into the stronger, then redirect the weaker's URL. Inaccurate, empty, or promotional with nothing left worth saving: delete, and redirect only if another page on your site covers the same ground, otherwise let the URL return a clean not found rather than forcing a redirect that leads nowhere useful.

The merge procedure itself is worth spelling out since it is the action owners skip most often, usually because deleting feels simpler. Start by identifying which of the two or more posts is strongest, has the better title, the more complete answer, the better internal links pointing to it already. Fold any useful detail from the weaker post or posts into that strongest one, rewriting rather than pasting so the result reads as one coherent post. Then set a redirect from each of the weaker posts' URLs to the surviving post, so a visitor or a search engine following an old link lands somewhere useful rather than at a dead page.

This process does not need to happen all at once. Sorting every post on a blog with even a modest history into one of these five actions in a single afternoon is unrealistic for most owners. Doing the sort itself first, before acting on any of it, is the useful step, because it turns a vague sense that the blog looks weak into a concrete list you can work through over several sessions.

It is also worth deciding on an order of operations before you start acting on the sorted list. Deletes are the easiest and lowest risk action to knock out first, since a post that is simply inaccurate or empty rarely has anything worth preserving and rarely needs a redirect if nothing else on your site covers the same ground. Merges take longer and benefit from being done when you have a clear stretch of time to write the combined post properly rather than rushing it. Updates can be spread out over weeks, treated almost like a standing task rather than a project, since a stale detail or two is a small fix each time rather than a rewrite.

Setting a Redirect on Each Platform

A redirect is the technical piece that keeps a merge or a delete from breaking an old link. Wix handles this through its URL Redirect Manager, found in the site's SEO tools, where you enter the old path and the new path a visitor should land on instead. Squarespace handles the same idea through its URL mappings settings, where old and new paths are entered as a simple pair, letting the platform route a visitor automatically. Shopify offers URL redirects through its own admin settings, under the section for URL redirects, again a straightforward pairing of an old path to a new one.

The common thread across all three platforms is the same: a redirect is a pairing, not a deletion. It tells the platform where a visitor arriving at an old address should go, and it works whether that visitor is a person clicking an old bookmark or a search engine revisiting a link it has indexed before. Setting the pairing takes a couple of minutes per post once you know where the setting lives on your platform, which makes it one of the lowest effort steps in this whole process relative to how much confusion it prevents.

It is worth testing every redirect once it is set, simply by opening the old URL in a fresh browser tab and confirming it lands where you intended. A typo in either the old path or the new one is an easy, common mistake, and it is far easier to catch immediately than to discover weeks later when a visitor reports a broken link or when the redirect quietly fails to do its job.

Keep a simple running list of every redirect you set, the old path, the new path, and the date, in the same spreadsheet you used to sort the posts in the first place. A blog you have owned for several years can accumulate more redirects than you would expect once you start merging and retiring posts, and a running list saves you from wondering later whether a particular old URL was ever handled or simply forgotten.

The Risks Worth Knowing Before You Touch Anything

The most common mistake is treating deletion as the default action for anything short, when a redirect or a merge would have preserved value that deletion simply throws away. A post might not be attracting much traffic today and still be quietly earning a link from another site, or holding a small but real place in search for a specific question nothing else on your blog answers. Deleting it outright removes both the page and whatever it was doing, however small.

A second real risk is the redirect mistake, either forgetting to set one when a merge or delete calls for it, or setting one incorrectly so it sends a visitor somewhere unrelated. A redirect that points to your homepage by default, rather than to wherever the relevant content now lives, technically avoids a dead link but still leaves the visitor without what they came for. A redirect set to the wrong destination is arguably worse than no redirect at all, since it quietly misleads rather than clearly failing.

A third risk, easy to overlook, is losing traffic you did not realize you had. Before deleting or merging any post, it is worth a quick check of whatever traffic data you have access to, even loosely, rather than assuming a post gets nothing just because it feels old or forgotten. If your own site's data is thin, and for many small cafe sites it is, treat that as a reason for caution rather than a reason to skip the check. A young site's data, including Hillcane's own, is itself a small, dated case, not a benchmark to apply elsewhere, and the same caution applies to reading your own numbers here.

A fourth risk worth naming is doing this work in a single rushed sitting late at night because a checklist somewhere said content pruning was urgent. Nothing about sorting or merging a blog is so time sensitive that it needs to happen before you have had a proper look at each post. Rushing is exactly the condition under which the length only mistake and the redirect mistake both tend to happen, since a tired pass through a long list of posts favors quick judgments over the honest four question check this whole process depends on.

Doing the First Merge

The outcome worth aiming for is not a perfectly pruned blog by the end of one sitting, it is every old post sorted into one of the five actions above, and the first merge completed rather than only planned. Pick the clearest case on your list, two posts that obviously answer the same question, one weaker than the other, and walk through the merge procedure once, end to end, including setting and testing the redirect.

Doing one merge start to finish teaches you more about your own blog's real shape than reading a decision table ever will. You will likely notice, once you are inside the process, that a post you assumed was thin held one detail worth keeping, or that a post you assumed was solid was quietly duplicating something you had forgotten you wrote. That is the real value of sorting honestly rather than deleting on instinct: it makes you read your own blog again, post by post, which is usually the first time that has happened since each post went up.

Frequently Asked Questions

Does Google set a minimum word count for a blog post to avoid being thin?

No. Google's guidance on creating helpful, reliable, people first content frames the standard around whether a page serves the reader, not around a word count threshold. A short post that clearly answers a real question can be a useful page, while a long post that never answers anything a reader searched for is the actual definition of thin regardless of its length.

Should I delete every short post on my cafe blog?

No. Judge each post against whether it is accurate, answers a real question, gets any visits or links, and duplicates another post you already have. A short but accurate post that answers one specific question clearly can be worth keeping even at a few hundred words. Reserve deletion for posts that are wrong, empty, or actively unhelpful with nothing worth saving.

What is the difference between merging and deleting a post?

A merge combines two or more posts that cover close to the same question into one stronger post, then redirects the weaker URLs to the survivor, preserving whatever value those pages had. A delete removes a post entirely, appropriate only when nothing in it is worth folding into anything else, such as content that is now simply inaccurate.

How do I set a redirect after merging or deleting a post?

On Wix, use the URL Redirect Manager in the site's SEO tools to pair the old path with the new one. On Squarespace, use the URL mappings setting to pair old and new paths. On Shopify, use the URL redirects section in admin settings for the same pairing. Test every redirect afterward by opening the old link in a fresh tab.

What is the biggest mistake owners make when pruning a blog?

Treating deletion as the default action for anything that looks short or old, rather than checking first whether the post answers a real question or duplicates another one. A second common mistake is setting a redirect to the homepage by default instead of to wherever the relevant content now lives, which technically avoids a dead link but still leaves a visitor without what they came for.

Can pruning thin posts hurt the rest of my blog?

This post does not claim that keeping thin posts hurts your whole site, and no documentation used here supports that claim. Google's guidance on helpful, reliable, people first content frames the standard around serving the reader, not a minimum word count. The real risk runs the other way: deleting a short post can throw away a link it was quietly earning. Treat any promise of guaranteed ranking recovery from pruning with skepticism.

How do I know if a post duplicates another one on my own blog?

Read your post titles and opening paragraphs together, side by side if you can, and ask whether two of them would come up for the same search a visitor might type. If two posts would compete to answer the same question, that is the sign to merge the weaker into the stronger rather than leaving both to divide whatever attention either could get.

Should I check traffic before deleting an old post?

Yes, even a loose check is worth doing before deleting anything, since a post might be quietly earning a link or a small but real place in search for a question nothing else on your blog answers. If your own site's traffic data is thin, treat that as a reason for caution rather than a reason to skip the check, and remember that a young site's own numbers are a small, dated case, not a benchmark.

How long does sorting a whole blog into these five actions take?

It varies with how many posts you have, and it does not need to happen in one sitting. The useful first step is sorting every post into keep, update, merge, redirect or delete before acting on any of it, which turns a vague sense that the blog looks weak into a concrete list you can work through over several sessions.

How can Hillcane help with pruning or merging a cafe blog?

Hillcane can help sort an existing blog into the five actions, keep, update, merge, redirect, and delete, then walk through the first merge with you, including setting and testing the redirect in Wix's URL Redirect Manager, Squarespace URL mappings, or Shopify URL redirects. The aim is that nothing gets deleted that was quietly doing a job. Reach out at hillcane.co/contact or call (256) 384-2449 to talk it through.

Work with Hillcane

A blog with a few good posts and a dozen thin ones does not need a purge. It needs a sort into keep, update, merge, redirect, or delete, and length is not the test.

Ready to sort your cafe blog instead of guessing what to delete? Reach Hillcane at hillcane.co/contact or call (256) 384-2449.