One post, sized for every network.
Threads, Facebook and Pinterest get theirs too — one master, nine versions, none written twice.
Written once, in plain markdown.
Every post starts life as one master — a plain markdown page with a title, the words, and the images sitting in the text exactly where a reader should meet them. The engine drafts it from something true about your product: the feature that just shipped, the question two customers asked this week, the date coming up on your calendar. Or you write it yourself, on the days you have something to say.
Either way, the master is the only thing anyone edits. Every network’s version is cut from it, so fixing a number in one place fixes it everywhere. And the queue doesn’t run dry: routines you set in plain words — a weekly tip, a monthly changelog — keep new masters arriving, and calendar moments like Black Friday drop their drafts in with time to spare.
Nine networks, nine real limits.
X stops at 280 characters. Bluesky at 300. A Pinterest pin wants an image, a title under a hundred characters and a link. LinkedIn rewards a longer, plainer telling, and Medium and your blog take the whole article, images and all. Nine text networks — Instagram, Threads, LinkedIn, Facebook, X, Bluesky, Pinterest, Medium, your own blog — and not one of them gets a pasted copy. YouTube takes video, not text posts, so an idea aimed there goes out as a Short.
Each version is written to fit its network, not chopped to fit — the short ones end on purpose, never mid-sentence. And every version shows its count against the real limit, so before anything books a slot you can see exactly what each network will get.
Images that know where they're going.
In the master, an image lives inline — the chart sits between the two paragraphs that explain it. Where the destination can honour that, it does: on Medium and on your own blog the image stays in the text, at its place in the article, not dumped at the top.
The socials don’t work that way, so the same image travels differently: it detaches and rides along as the attachment — the picture under the Facebook post, the frame on the pin, the image beneath the X version. One upload, handled right for every destination — never re-uploaded by hand, never forgotten on one network.
One yes books every slot.
When the master reads right, you approve it once. Every version books its own slot on the calendar with a visible time next to it — you see exactly when each network gets its copy before anything moves. Until that yes, nothing does.
Your own blog goes first, and it keeps the credit. The article lands on your domain, SiteOps waits until the page is actually live, and only then do the copies follow. Medium is the one guided step — its API is closed to new tools, so SiteOps prepares the article and hands you a one-click Import that sets the canonical link back to your site. The syndication brings the readers; the search credit stays home.
Fair questions.
Do I have to write the posts myself?
Only when you want to. SiteOps drafts masters from what's true about your product — the feature you shipped, the question customers keep asking, the moment coming up on your calendar — and routines keep new drafts arriving on whatever rhythm you set. When you do have something to say, write the master yourself; it goes through the exact same review either way.
Is it the same text pasted onto every network?
No. Each network gets its own version cut from the master: 280 characters on X, 300 on Bluesky, a longer and plainer telling on LinkedIn, an image with a short title and a link on Pinterest, the full article on Medium and your own blog. Every version says the same thing at that network's natural length — and you can read each one before it books a slot.
Won't posting on Medium hurt my own site's rankings?
It would if the copies competed with the original — that's why they don't. Your blog publishes first, and Medium's own Import-story flow sets a canonical link from the URL you paste, telling search engines the original lives on your domain. Medium closed its publishing API to new tools, so SiteOps prepares the article and hands you a one-click Import rather than posting automatically; the canonical link — and the search credit — still stays home.
Can a post go out without my approval?
Not until you decide it can. Out of the box every master waits for your yes, and approving is what books the slots. If you later raise the autopilot dial, routine posts can earn the right to go out on their own — after a full day sitting visibly on the calendar, where one tap pulls them back. Anything that spends money never earns that right.