Posting Is Distribution, Not Marketing
A great deal of effort goes into posting: scheduling tools, content calendars, consistency, the right times of day. Almost all of it addresses distribution — how reliably something reaches a feed.
Distribution matters. It is also the easy half, and it is worthless on its own. A well-distributed post that says nothing anyone needed is a well-executed waste of an afternoon, repeated weekly.
The question that goes unasked
Before "how often should we post", there is "what do we have to say that someone would want".
That question is uncomfortable because the honest answer is frequently "not much this week", and most content processes have no way of handling that answer. The calendar says Tuesday, so something goes out on Tuesday, and the something is whatever could be produced by Tuesday.
Readers detect this immediately. Not consciously, but the pattern of posting-because-it-is-time produces a recognisable texture: general observations, mild advice, statements nobody would disagree with. It costs nothing to scroll past, and after a few weeks people stop registering the account at all.
The alternative is not posting less on principle. It is letting the supply of things worth saying set the rhythm, rather than the reverse.
Where the things worth saying come from
They come from the work, and specifically from three places most businesses do not look.
Questions customers actually ask. Not the ones in your FAQ — the ones that arrive repeatedly and get answered individually, in emails, by someone competent. Those answers already exist, already proved useful once, and can be reused almost verbatim.
Things you decided not to do. A business that chose not to build a feature, take a type of client, or follow an obvious trend has a reason. The reason is usually more interesting than anything in the marketing plan, because it contains an actual opinion.
What went wrong and what you changed. Specific, checkable, and almost never posted, because it feels like admitting fault. It reads as confidence.
None of these requires a content strategy. All of them require someone to write things down when they happen, which is a habit rather than a process.
The mechanics that quietly break
Since posting is distribution, the distribution mechanism is worth understanding, because it fails in ways that look like poor performance.
Every scheduling tool posts on your behalf through a delegated grant — an application obtaining "limited access to an HTTP service... on behalf of a resource owner by orchestrating an approval interaction" [1]. That grant is not permanent. Tokens expire, permissions get narrowed in platform policy updates, and the person who authorised the connection may have left.
When it lapses, the failure is rarely loud. The scheduler shows the post as sent. The platform never received it. Engagement for that post is zero, which looks exactly like a post nobody liked, and the conclusion drawn is about the content rather than the plumbing.
The check that actually works is to look at the live profile, on the platform, and confirm the post is there. Anything else is asking the scheduler whether the scheduler worked.
There is a second, subtler version: the post publishes but the link preview does not, because the destination was slow or returned an error to the platform's crawler. The post appears, gets seen, and converts nothing, because the thing that made it clickable is missing.
Where the traffic lands is part of the distribution
This is the part that gets separated from social entirely, and should not be.
A post's job is to move someone somewhere. If the destination is slow, the movement fails at the last step — and mobile feed traffic is the least patient traffic there is. The whole point of the Web Vitals initiative is "to provide unified guidance for quality signals that are essential to delivering a great user experience on the web" [3], and those signals apply with particular force to a visitor who arrived from a feed with no commitment and one thumb on the back gesture.
A business posting diligently to a slow landing page is optimising the first 5% of the journey and losing people at the last.
Measuring the right thing
Engagement metrics measure the post. They are provided by the platform, which has an interest in the post being the unit of analysis, and they are only loosely connected to anything that matters to you.
The useful measure is whether the movement happened: did people arrive, and did the arrivals do anything. That is measured on your side, not theirs.
This does not require elaborate attribution. It requires knowing how many people came from a channel and what proportion of them did the thing the page exists for. Anything beyond that tends to be collected because it is available, which is the habit of gathering data speculatively "in case it is useful later" [2] — a dashboard full of figures nobody has ever used to make a decision.
The audience you do not own
One structural fact is worth holding in mind whenever social effort is being planned: the audience is not yours.
A following on any platform exists at that platform's discretion and under its distribution rules. Reach can be reduced, an algorithm can change what it favours, an account can be restricted for reasons that are difficult to appeal, and none of these events come with notice. Businesses that built substantial audiences on a single platform have watched them become unreachable overnight, through no error of their own.
This is not an argument against social channels. It is an argument about what to do with the attention they produce. The durable move is to convert some proportion of that reach into a channel you control — an email list, a customer record, a direct relationship — where the ability to make contact does not depend on a third party's ranking decisions.
Judged that way, a post that produced twenty subscribers outperformed one that produced two thousand impressions, and most social reporting will tell you the opposite.
A workable posture
Post when you have something. Reuse what already worked in a real conversation. Check the live profile occasionally rather than trusting a scheduler's status. Make sure the place you are sending people loads quickly.
And accept that most of the value of a social presence is not in any individual post. It is in being recognisable when someone finally needs what you do — which is a slow, cumulative effect that no weekly metric will show you, and which is destroyed rather than helped by posting things nobody wanted in order to keep a schedule.
Sources
- [1] RFC 6749 — The OAuth 2.0 Authorization Framework — IETF
- [2] 360REV Use of Data Policy — what we collect — 360REV, Inc.
- [3] Web Vitals — Google (web.dev)