---
title: "Threaded Posts"
description: "Post a main message plus reply segments — ideal for putting links in replies to avoid algorithmic down-ranking"
---

# Threaded Posts

Sometimes one post isn't enough. Maybe you want to share a link without having it penalized by the algorithm. Maybe you're writing a longer thought that spans multiple tweets. Threaded posts let you compose a main post plus one or more reply segments — and Octopost handles the per-platform mechanics so it works naturally everywhere you post.

## Why thread?

The big reason: **links get down-ranked on most social platforms**. A tweet with a URL in it typically reaches fewer people than a tweet without one. The standard workaround is to post the main thing, then drop the link as a reply. Threading in Octopost lets you do that in one compose action — one click, goes everywhere, algorithm stays happy.

Other good reasons:

- Longer thoughts that don't fit in 280 characters
- Adding context, credits, or "further reading" as a follow-up
- Splitting a story into a narrative chain

## Using threads in the web app

On the compose page, type your main post as you normally would. Below the main textarea, click **+ Add reply post** to add a reply segment. Each reply gets its own textarea, its own media attachment slot, and can be reordered or removed. You can add up to 24 reply segments.

When you add replies, you'll see a small hint below them showing how each platform will handle the thread. You can attach images or video to any segment, just like the main post.

Threaded posts are treated as **one unit** throughout Octopost. Your queue shows one entry. Your schedule shows one entry. Your content calendar shows one card. The whole thread publishes atomically when it's time.

## How each platform handles threading

| Platform | Mechanism |
|----------|-----------|
| Twitter/X | Native reply chain (reply to the previous tweet) |
| Bluesky | Native reply chain (AT Protocol reply refs) |
| Mastodon | Native reply chain (`in_reply_to_id`) |
| Threads | Native reply chain (`reply_to_id` in container) |
| Facebook | Main post, then comments on it |
| Instagram | Main post, then comments on it (requires Business/Creator account) |
| LinkedIn | Main post, then comments on it |
| YouTube | Video upload, then comments on it |
| Slack | Native threaded message (`thread_ts`) — bot-token accounts only; webhook accounts fall back to numbered posts |
| Discord | Message reference on a webhook |
| Telegram | `reply_to_message_id` |
| TikTok | Numbered `(1/N)` separate posts |

Only TikTok falls back to numbered `(1/N)` separate posts — every other platform uses its native mechanism.

## Character counts in threads

Each segment has its own character count. When you're composing a thread across platforms with different limits, each segment is checked against the tightest limit of the native-threading platforms you've selected (usually Twitter's 280). You can always go longer if you've only selected platforms with higher limits.

## Scheduled and queued threads

Threads work identically in all posting modes:

- **Publish now** — Main post and all replies go out immediately in order.
- **Schedule** — The entire thread publishes at the scheduled time.
- **Queue** — The entire thread counts as one queue slot. When the queue picks it up, the whole thing goes out.
- **Needs approval** — Approving a pending thread approves all its segments at once.

You can edit a queued or scheduled thread at any time before it publishes — add replies, remove replies, change order, tweak content.

## The canonical "link in reply" pattern

```
Main post:  "I shipped a new macOS app for managing Claude rules."
Reply 1:    "https://rulebook.app"
```

Main message gets the engagement boost, the link lands as a reply on Twitter, Threads, Bluesky, Mastodon — no algorithmic penalty. Platforms without reply chains just see the main post (once the comment-threading support lands, they'll get the link as a comment on the main post).

## API usage

```json
{
  "content": "I shipped a new macOS app for managing Claude rules.",
  "platforms": ["twitter", "threads", "bluesky", "mastodon"],
  "segments": [
    { "content": "https://rulebook.app" }
  ]
}
```

See the [Posts API reference](/docs/api/posts) for the full field details, and the [MCP guide](/docs/mcp) for the equivalent agent tool parameters.

## Limits

- **Max reply segments:** 24 (25 posts total including the main post)
- **Per-segment character limit:** 5,000 chars server-side; client UI enforces the tightest active platform limit
- **Per-segment media:** same as main post (4 images or 1 video on most platforms)