Posts fan-out
Publishing the same idea to six networks usually means writing it six times — or pasting one text everywhere and watching X cut it off at 280 characters while Instagram refuses it for having no image. The fan-out exists so you write once. A post in SiteOps is one logical thing: a scenario (the creative brief — why this post exists and who it talks to), a master markdown body, and the media attached to it.
From that master, the engine drafts one version per connected network, each shaped to that network's real rules: 280 characters on X, 300 on Bluesky, 500 on Threads, 2,200 on Instagram (which also requires media), 3,000 on LinkedIn, a 500-character description and 100-character title on a Pinterest pin. Articles go to your own blog and to Medium, where markdown renders in full and the Medium copy carries a canonical link back to your site — your blog stays the original in search engines' eyes.
Nothing publishes on its own. The versions wait in review; you read them, tweak any of them, and approve once. That single approval books every enabled version onto the calendar, staggered about two hours apart so the same post doesn't hit every network in the same minute.
Set it up, step by step
0 of 8 done
- Posts
- Generate posts
- Posts
- the post's row
- Settings
- Publishing
- Calendar
If something does not work
- Approve is refusing and naming Instagram or Pinterest — why?
- Those networks will not take bare text — Instagram has no text-only post, and a pin without a picture is not a pin. If no picture came back for this one, ask for another take of the post. A fresh take rewrites the words, and its pictures are made again. Or switch that version off.
- A post says “Pictures on the way” and I cannot approve it — why?
- Its words are written and its pictures are being made — it lands in review when they arrive. You can read it now and approve it when it is whole. If you would rather not wait, open it and press “Don't wait — use the title cover”: it comes to review under a title cover.
- A post says “Held for you” and carries a title cover — what happened?
- Its pictures did not come, and the line on the post says why: they didn't arrive in 8 hours, the picture studio could not make them, the picture studio cannot make pictures yet, or you chose not to wait. It carries a title cover for now. Approve it as it is, or wait — pictures that arrive before you approve are put in, and approving stops them. If they arrive just as you approve, the post is not approved: it says its pictures have just arrived, and shows them a moment later, so you look at them first. When none are coming, the post has a “Try the pictures again” button instead. Press it, and the line says you asked for its pictures again while the picture studio tries. If the picture studio is not answering, the screen says so and nothing changes — try again later. If you change its pictures yourself, that button goes: a fresh take rewrites the words, and its pictures are made again. A post that is not held can carry a title cover too: the line under its cover says why, and the same button stands on it. Press it, and that line goes while the picture studio tries: the post is held for you, and its line says you asked for its pictures again.
- I edited one version after approving — why does it say 'edited — approve again'?
- Any edit puts that version back to draft so nothing ships text you didn't sign. Press approve again: it re-books the same calendar items with the fresh text — re-approving reslots, it never duplicates, and versions that already went live are left untouched.
- I turned a channel off on the post but it published there anyway.
- Turning a channel off skips its pending booking — but a version that had already gone out stays out; SiteOps never pretends a live post away. Check the version's state on its tab: 'already live' means it published before the switch.
- My social versions don't show the image inside the text.
- That's the two delivery routes, not a loss. Only the article homes — your blog and Medium — render an inline image where its tag sits. Feed networks don't render markdown, so the tag is stripped and the same file is attached beside the text instead.
- Every version went out at a different time — is that a bug?
- It's the stagger: versions book about two hours apart so the same post doesn't hit every network in the same minute. The publish plan shows each exact time before you approve; afterwards, Move all rebooks every waiting version from a new time, or drag single ones in the Calendar.