How often should you post on each platform?

Every team eventually picks a number. Three times a week, say, or once a day, applied everywhere because a single schedule is the only kind a person can actually keep. Then the same cadence gets you ignored on one platform, muted on another, and flagged as a self-promoter on a third, and none of those failures announce themselves.

The uncomfortable part is that the correct answers are not close together. They differ by more than an order of magnitude, and on a few platforms the question itself does not apply.

The range is wider than a single schedule can cover

A workable weekly cadence runs from about one post to roughly thirty-five, depending entirely on where you are posting. That is a spread of around thirtyfold, which is why a house schedule cannot be right everywhere: the frequency that reads as committed on one feed reads as spam on another and as abandonment on a third.

Two platforms at opposite ends of that table make the point. A discussion site rewards you for submitting almost nothing and commenting constantly. A visual discovery feed rewards a steady several-a-day drip of genuinely new material. Running either cadence on the other is not a small miscalibration, it is the wrong activity.

On some platforms there is no optimum to find

The chat platforms have no ranking algorithm, so there is no frequency that gets amplified and none that gets suppressed. The feed is chronological and every post is a push notification on somebody's phone. That changes the question completely: you are no longer tuning for reach, you are deciding whether this particular thing is worth interrupting someone for.

This is the part most cadence advice gets wrong, because it assumes an algorithm exists to be satisfied. Advice that tells you to post daily in a community channel to stay top of mind is describing a feed that works nothing like the one you are posting into.

Consistency is the part you actually control

Pick a cadence you can hold for a quarter rather than the maximum you can hit for a fortnight. This is the least glamorous finding in the whole area and the most reliably supported one: a steady, moderate schedule outperforms a burst followed by silence on essentially every platform, because a gap resets whatever momentum the previous run built.

It is also the only variable fully in your hands. You cannot control how a feed ranks you and you cannot control whether a given post lands. You can control whether there is a post at all next Tuesday, and that turns out to matter more than the fine-tuning most cadence advice obsesses over.

The practical consequence is to set the floor by what survives a bad week. If your schedule assumes nothing goes wrong, it is not a schedule, it is a forecast.

Post where your audience already is

Cadence only matters on a platform your buyers actually use, and that is worth checking rather than assuming. For a software audience the 2025 Stack Overflow Developer Survey, with 49,019 responses, found the community platforms developers participate in are Stack Overflow at 84.2%, GitHub at 66.9%, YouTube at 60.5%, Reddit at 53.7% and Discord at 38.9%.

Notice what that ranking implies about effort. Two of the top four are places where you answer questions rather than broadcast, and the highest-frequency social feeds do not appear at all. Reaching that audience well is mostly not a posting-schedule problem, which is a useful thing to learn before building one.

The same survey found technical documentation was the single most-used learning resource at 67.8%, ahead of every community platform. For a technical product, the highest-return publishing you can do may not be posts at all.

Treat every cadence number as a range

Hold these figures loosely, including the ones above. Very few published cadence numbers come from controlled measurement; most are practitioner consensus repeated until it sounds official, and platforms change ranking behaviour without announcing it. A number stated to the decimal place in this area is a warning sign rather than a sign of rigour.

Two habits follow. Write down the range you are running and why, so that when results move you can tell whether cadence was even a variable. And check any figure you plan to act on against the platform's own documentation, because the gap between what a platform says and what gets repeated about it is routinely large.

A cadence you can actually run

Start narrow and let evidence widen it. The common failure is committing to eight platforms at a frequency that assumes a team you do not have, then quietly dropping to zero on all of them within six weeks.

1. 1

   Pick two platforms, not eight

   Choose where your buyers already spend time. Two platforms posted natively beat eight posted mechanically, and cadence is only meaningful once the platform choice is right.

2. 2

   Set the floor at a bad week

   Choose the frequency you could still hit during a launch or an outage. That is your real cadence. Anything above it is upside, not commitment.

3. 3

   Separate broadcast from reply

   On conversational and community platforms, replying is most of the work and does not count against your posting cadence. Budget it separately or it will not happen.

4. 4

   Ask what a notification costs

   Before posting to a chat channel, ask whether the message is worth a buzz on a phone. If the answer is no, that is the whole decision, and no cadence table overrides it.

5. 5

   Review the range quarterly

   Look at whether the floor held before you look at results. A cadence you did not actually run is not a cadence you tested.