LinkedIn suits batching better than most platforms. Very little of what works there is reactive, consistency matters more than immediacy, and the writing is long enough that doing it in one sitting is genuinely more efficient.
Write in one session, schedule in another
LinkedIn posts are 3,000 characters and the good ones take thought. Writing six properly in one session produces better work than writing one a day between other things, because you can see them as a set and cut the weak one.
Keep scheduling separate. Mixing the two means optimising posting times instead of finishing sentences.
Importing a batch
BulkPublish’s bulk composer at /compose/bulk reads a CSV with a content column, plus optional scheduled_at and media_urls.
For LinkedIn specifically, watch the quoting. These posts are long and contain commas, quotes and line breaks:
- Wrap any field containing a comma in double quotes
- Double any literal quote marks inside a field
- Line breaks inside a quoted field parse correctly
- Save as UTF-8
Exporting from a spreadsheet handles all of this. Hand-editing a CSV with 3,000-character fields is where it goes wrong.
What LinkedIn accepts
| Post length | 3,000 characters |
| Post types | Post, Gallery, PDF Carousel, Article |
| Images | Up to 20, 10 MB each |
| Video | Up to 500 MB and 30 minutes |
Which formats belong in a batch
Text posts and galleries: yes, this is what batching is for.
PDF Carousels: partly. The PDF has to be designed, which isn’t a batch operation, but if you make several in a design session then queueing them together works well.
Articles: not really. They’re long-form and usually tied to something specific.
What not to queue
Anything reactive. Commentary on something current is the one kind of LinkedIn post that has to be written now.
Anything with a number about your own company. Headcount, pricing, growth figures. These change, and a post published six weeks after writing can be wrong on the day it goes out.
Anything you might change your mind about. A queue is a set of opinions you’re committing to in advance.
Keep the queue shallow
Four to six weeks. LinkedIn’s native scheduler allows three months, and that’s more rope than most people should take: a post written in January and published in March is a post nobody re-read.
The related discipline is knowing how to pull a queued post quickly. If that’s hard, stale posts stay in.
Read the batch as a set
The specific LinkedIn failure is six posts that are all the same shape: same opening move, same structure, same kind of conclusion. It’s invisible per post and obvious when you read them in order.
Cross-posting from a LinkedIn batch
The LinkedIn version is usually the fullest, so it’s the right one to write first and cut down from. The sharpest single claim in a 3,000-character post is often a better short post than one written from scratch.
Plan limits
- Posts: Free: 3/day. Pro: 30/day. Business: unlimited.
- Channels: Free: 3 (1 per platform). Pro: 30 (2 per platform). Business: 75 (5 per platform).
Your posting quota is checked across the whole batch before anything is queued, so an oversized batch tells you up front.
The short version
Write in one session, schedule in another, and keep the queue to four to six weeks. Quote your CSV properly, because long posts contain commas. Don’t queue anything reactive or any number about your own company. And read the batch in order, since six posts of the same shape only look identical when they’re side by side.