DEV Community: Deal Breaker

How to Grow on LinkedIn in 2026 Ultimate Guide

Deal Breaker — Tue, 13 Oct 2026 10:44:11 +0000

LinkedIn growth in 2026 is two games played at once — broadcast (followers via content) and 1:1 (connections via targeted requests). Win both by picking a narrow niche, optimizing your profile for discovery, posting 3-5x per week, and sending 20-50 relevant connection requests per week to people adjacent to your target audience, so you stay well under LinkedIn's rate limits.

Followers and connections are two different things on LinkedIn, and understanding the distinction is the first step to growing on LinkedIn intentionally.

A connection is a two-way relationship — both people see each other's content and can message each other directly. A follower is one-way — they see your content in their feed, but you don't see theirs, and there's no DM channel unless they connect with you.

Connections max out at 30,000. Followers are unlimited.
If you want more reach, chase followers. If you want more conversations (job leads, client DMs, warm intros), chase connections.
If you're building a personal brand, becoming an industry voice, or trying to reach a big audience, followers are the metric. Switch your profile to "Follow" as the primary button (Settings → Visibility → Followers → toggle on "Make Follow primary").
If you're in sales, job-hunting, or building a B2B network where individual relationships matter, keep "Connect" as primary.

Your profile is the landing page for every post you publish and every connection request you send.

Before you chase growth, make sure the profile is actually ready to convert a visitor into a follower or connection. The goal isn't to look "polished" — it's to make your niche unmistakable in the first 3 seconds so the algorithm and humans both know what you do. A great profile answers three questions instantly: Who are you? What do you do? Who do you do it for?

Photo — clear headshot, face visible, professional but not stiff. Not your logo, not a vacation photo.
Banner — this is free billboard space. Write who you help and what outcome you deliver. Make it readable on mobile.
Headline — not your job title. A benefit-driven line: "I help B2B founders turn LinkedIn into a pipeline engine" beats "Founder at Acme Corp."
About section — first 2 lines are what people see before clicking "see more." Hook them there. Then tell your story and list what you help with.
Featured section — pin 3-4 best posts, a case study, or a link to your calendar/website. This is your proof.

The number one reason people stall on LinkedIn is not knowing what to post. The fix is content pillars: three to four recurring themes you write about over and over.

A content pillar is a theme you return to often enough that people start to associate it with you. Pillars keep you consistent, train the algorithm to show your work to the right audience, and help followers know exactly what they get by sticking around.

Most strong LinkedIn creators run on three to four. Not one (too narrow, you run dry), not ten (too scattered, you teach your audience nothing).
Posting across 15 random topics teaches the algorithm nothing and gives your audience no mental hook to file you under.
Aim for a mix that includes practical how-to content, opinions and hot takes, and personal or story-driven posts, because variety keeps your feed from feeling like a lecture.

Documents (uploaded PDFs, slide decks, multi-page carousels) earn 7.00% average engagement because they maximize the two signals LinkedIn's algorithm weights most heavily: dwell time and saves.

A 10-slide document holds a reader for 60 to 90 seconds; a text post holds them for 10 to 15. LinkedIn's LiRank model uses a "Long Dwell" binary classifier as a primary feed-ranking signal: posts that generate extended reading time are pushed to second- and third-degree connections; posts scrolled quickly stay local.

According to Socialinsider's 2026 benchmarks (1.3M business posts), documents (PDF carousels) show the highest engagement rate (~7.0%), followed by multi-image posts (~6.5%) and native video (~6.0%), then single images (~5.3%) and text-only posts (~4.5%), with polls (~4.2%) and especially posts with external links (~3.3%) at the bottom.
Documents, by requiring the reader to swipe through slides, mechanically extend dwell time beyond what any text post achieves.
Document posts (carousels) should run 6–10 slides.
Posts in the 1,300–2,000 character range tend to earn more dwell time — long enough to tell a story but short enough to finish.

Posting frequency matters, but not as much as most people think.

For personal profiles, the sweet spot is 3-5 posts per week. Below that, the algorithm deprioritizes you. Above 5, quality usually drops and engagement thins out because your audience can't keep up.

Consistency matters more than frequency — 3 posts a week for 6 months beats 10 posts a week for 3 weeks followed by silence.
The most common mistake is burning out after a sprint. Pick a cadence you can hold for 90 days and build from there.
If you're starting out, commit to 3 posts a week — two tactical, one personal/story — and keep it going.
Grow your audience in a sustainable way: 2 to 5 posts per week

When you comment on someone else's post — someone with 40,000 followers and a post that's already going viral — you're borrowing their distribution.

A sharp comment on a post pulling 200,000 impressions can get seen by 5,000–15,000 people on its own, and the people seeing it are already engaged with your exact topic. They didn't have to find you. You showed up in the conversation they were already having.

Comment before you post. Spend 20–30 minutes commenting on five to ten posts before writing your own content for the day.
Add something. Share an example, a counterpoint, or a lesson. "Great post" is invisible.
Skip the pitch. Value first. The pitch, if any, comes much later and in private.
Ten great comments beat thirty filler ones every time.

Every reply you give to a comment generates a new activity signal and can trigger a second wave of distribution.

If you post and disappear, you waste half the potential. Reserve the first hour after posting to actively reply, with multi-word answers, not just "thanks!".

Publishing and then going offline for three hours is the most common golden hour mistake.
If you edit during the golden hour, you want to be fast and surgical. A five second fix to a typo will not hurt you.
External links in the post itself often suppress reach because LinkedIn wants people to stay on the platform. If you must link, put it in the first comment, then write "link in the comments" in the post.

Warming up LinkedIn prospects before you connect, by reading their content, engaging genuinely with something specific to them, and writing a note that references that engagement, changes the conversion math considerably.

The fix is not a better template. It is making sure you are not a stranger when the request arrives. For high-value accounts, it is worth doing carefully.

The "engage first, connect second" move: Comment thoughtfully on someone's post 2-3 times over a week before sending the request. Mention the comment in your note. Acceptance rates jump significantly when someone recognizes your name.
Who to target: People who engaged with your last 5 posts — commented, reacted, or reshared. They already know you.
People who engaged with posts in your niche from creators you follow. They're your audience — they just haven't met you yet.
Who to avoid: Random 3rd-degree profiles with zero context. Low acceptance, high flagging risk.

The practical takeaway: you cannot grow by sending more, because the cap is fixed. You grow by raising the share that get accepted.

Every account gets roughly 100 to 200 sent invitations per rolling week. The exact number depends on your account age, history, and how LinkedIn scores your behavior.

A 2025 study of 16,492 requests found the average acceptance rate is around 37%, and anything under 20% is a red flag that can get your account restricted.
Most people should send 20-50 per week max — quality beats volume, and low acceptance rates trigger restrictions. Spread them across the week instead of sending 50 in one day.
LinkedIn follows a rolling 7-day window, not a Monday-to-Sunday reset.
Send at the cap every week and you are not growing faster; you are just spending your entire budget, often on people who never accept.

Your LinkedIn public profile is a streamlined version of your profile that shows up in search engine results, and is visible to people who aren't signed in to LinkedIn.

You can promote your profile to show up better in search engine results by creating a personal URL. You can also create a badge for your public profile that you can add to your online resume, blog, or website from the Public profile settings page.

Once you've got a clean URL, use it everywhere, consistently.
Email signature, CV, speaker one-sheets, guest bio blurbs, your website's "about" or "contact" page, your Google Business Profile if you're a service provider, printed materials, and anywhere you're asked for a "website" field on a form that doesn't have its own dedicated LinkedIn slot.
Follow link to easily share a personalized link or button on your web channels, email, or other platforms. This link or button allows anyone to start following you with just a click.
The criteria for access to the Follow link: A history of abiding by our Professional Community Policies and a good standing record on LinkedIn, and Geographic location is outside of mainland China.

Boosting a post will turn the post into an ad.

As a LinkedIn member, you can boost your posts on the LinkedIn feed to increase your visibility, grow your followers, and get more website clicks. You can select your budget and target audience to boost key posts, increasing visibility to target audiences by selecting from facets including location, language, job title, job function, company industries, and job seniorities.

You can boost your personal LinkedIn posts with a Premium Business Suite subscription. We're also gradually releasing this feature to members without a Premium Business subscription.
With the Premium All-in-One subscription (formerly LinkedIn Premium Business Suite), you receive monthly boost credits to enhance your marketing efforts.
Boosting is gradually being released. You might not have access to it at this time, and some functionality might change over time.
Boost credits included with Premium All-in-One can only be used to boost posts from your personal profile. You can't use these credits to boost posts from a LinkedIn Page.

Automated inauthentic activity violates the LinkedIn User Agreement and can result in temporary or permanent restriction of your account.

In order to protect our members' data and our website, we don't permit the use of any third party software, including "crawlers", bots, browser plug-ins, or browser extensions that scrape, modify the appearance of, or automate activity on LinkedIn's website. We also don't permit the use of fake accounts or fake engagement on LinkedIn's website, including any tools or services that try to manipulate LinkedIn's content algorithms. Suspensions rarely arrive with zero warning. Watch for these signals and treat them as a reason to slow down immediately:

Unexpected CAPTCHA prompts during normal browsing or messaging.
Phone or ID verification requests out of nowhere.
"Restricted" labels on search results or messaging limits appearing without explanation.
A sudden drop in connection acceptance or reply rate week over week.

Here's a concrete 30-day plan that grows both followers and connections at the same time.

It assumes you post 3x a week and send ~20 connection requests per week — volumes that keep you well under LinkedIn's limits. After 30 days, you'll have posted ~12 times, sent ~50-60 connection requests, and engaged on ~100 posts. Most people see their first viral-ish post (10K+ impressions) somewhere between days 20-60 if they're consistent.

Week 1: Setup. Rewrite your headline and banner around a specific niche. Pin 3 featured posts (or a case study link). List your 3 core topics — every post for the next month fits one of them. Make a list of 20 creators in your niche. Follow them, turn on notifications for 5.
Week 2: Engage before you post. Comment thoughtfully on 5 posts per day from your creator list. 2-3 sentences, specific, not generic. Publish 3 posts this week — one tactical, one story, one opinion. Send 10 connection requests to people who engaged with your comments this week.
Week 3: Consistency. Publish 3-4 posts. Try a document/carousel post this week. Send 15-20 connection requests — target people who engaged with your posts or your comments. DM 3 people you've been interacting with publicly. No pitch — just continue the conversation.
Week 4: Review and double down. Check analytics: which post type got the most saves and comments? Do more of what worked. Drop what didn't. Send 20 more connection requests. Post 3 times. Keep engaging daily.

Impressions, likes, and follower count are numbers teams can see, not inputs the algorithm uses to decide who sees your next post.

The only LinkedIn metrics worth tracking are follower growth in your ICP, saves and DMs, qualified profile visits, and inbound conversations — not likes or impressions. Likes are cheap and lie. A post with 300 likes from adjacent audiences is worth less than a post with 40 likes from 40 potential buyers. When follower growth stalls, check upstream first.

After every post, track: 1. Saves 2. Meaningful comments 3. Profile visits 4. Shares or sends if you have access to that data 5. DMs, connection requests, and leads that came in after the post
Profile views down means hooks or formats stopped working - audit the last 4 posts.
Save rate down means you're posting opinion, not reference - add a framework or specific numbers.
Comment ratio down means weak CTAs or non-polarising topics - try a contrarian take.

Often, people with more experience, better content, and case studies lose to people who just figured out the rules of this game better and work more consistently.

I grew from 2k to 10k followers in 10 months, and then from 10k to 15k followers in 8 months. I believe you'll be able to move faster after reading these lessons.

Collaborate with local influencers. A huge number of people in your industry do not speak English but need your product or lead magnet.
Block AI comments under your posts. If you won't do it, people who leave good comments will ignore your posts. You are responsible for the quality of discussions under your posts!
Followers is a proxy metric, but it works for trust. The number of followers doesn't pay bills. However, this proxy metric has a huge impact on the decision of your ICP whether it is worth accepting your connection request and reading your first message.
Constantly asking why people add me to connections. A large part of the impact of your posts cannot be easily attributed to likes and comments. Most people who read your posts do not like or comment on them, but they do affect whether you are remembered and chosen.

How long does it take to grow on LinkedIn?

Most people see noticeable growth (a few hundred new followers and a meaningful lift in post reach) after 60-90 days of consistent posting 3x per week. The first 30 days are usually slow because the algorithm is still learning your niche. If you're still flat after 90 days, the issue is almost always content quality or niche clarity — not time.

Plan for 8–12 weeks of consistent posting (3–5 times a week) before you see meaningful follower growth or inbound.
The first month mostly builds the signal the algorithm uses to understand your topic. Months two and three are where compounding starts.
If you already have 5,000+ connections in your ICP, you can see results in 30 to 45 days. If you're starting from scratch, 90 days is a more realistic benchmark.

How do I grow LinkedIn followers as a beginner with zero audience?

Start by engaging before you post. Leave thoughtful comments on 5-10 posts per day from creators in your niche for two weeks. Their audience sees your comments, visits your profile, and follows if your content matches their interests. Then start posting 3x a week on a narrow topic. This "engage first, post second" approach gets you your first 500-1,000 followers faster than cold posting into a void.

Profile: Professional headshot, clear banner, and a headline that states your value proposition (not just your job title).
Content: Comment on big creators' posts. Your goal is visibility in the comments section. 80% Commenting / 20% Posting.
If your comment is smart, people will click your profile and follow you.

Can a LinkedIn company page send connection requests or DMs?

No. LinkedIn does not allow company pages to send connection requests, direct messages, or InMail. All outreach on LinkedIn originates from personal accounts. This is a platform-level constraint, not a strategy preference.

The algorithm trusts personal profiles.
When an employee shares a post, the algorithm reads it as a personal recommendation, not a brand broadcast.
People engage with people, and the feed is built around that fact.

Sync any blog via API to Substack in one-click

Deal Breaker — Mon, 28 Sep 2026 11:33:08 +0000

I created an API library that can sync any blog to Substack in one click. Notes and articles included.

It works with Claude, Codex, Cursor, or any agent.

Substack has no official public posting API. You write somewhere else, then you live in their browser editor. I wanted a client that can post Notes and newsletter articles from a script, a terminal, or an agent — draft, publish, schedule, tag, and delete without that UI.

The library is three products, not one package:

Python client for scripts and apps
CLI (substack-api) for the terminal
MCP server (substack-api-mcp) for Cursor, Claude, and other MCP hosts

Keys and docs live on apisubstack.com. Python client + CLI: substack-api-client. MCP: substack-api-mcp.

Quick start

Generate an ask_* key, then either paste the MCP config into your agent or verify the key over HTTP.

MCP

{
  "mcpServers": {
    "substack-api": {
      "command": "substack-api-mcp",
      "args": [],
      "env": {
        "APISUBSTACK_API_KEY": "ask_YOUR_KEY",
        "SUBSTACK_PUBLICATION_URL": "https://yourname.substack.com",
        "SUBSTACK_SID": "YOUR_SUBSTACK_SID_VALUE"
      }
    }
  }
}

Verify the key

curl https://rest.apisubstack.com/api/v1/keys/verify \
  -H "Authorization: Bearer ask_YOUR_KEY"

Generate API key

You also need:

SUBSTACK_PUBLICATION_URL — *.substack.com or a custom domain
SUBSTACK_SID — the unofficial substack.sid browser session cookie
optional SUBSTACK_USER_ID — otherwise the client resolves it from profile/self

Two things that bite people: the SID expires (refresh it on 401/403), and every Substack endpoint is 1 request per second. Do not poll. Do not hammer drafts from a loop.

Plain text is converted to ProseMirror draft_body for you. Cover images are URL strings only — there is no binary upload in the SDK.

Install

If the Python client, the CLI, or the MCP server is already installed, skip this and jump to the method you need. If nothing is installed yet, install one product.

Python client and CLI (one repo): https://github.com/alxgntv/substack-api-client

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
pip install -e .
# CLI command: substack-api

MCP server (separate product): https://github.com/alxgntv/substack-api-mcp

python3 -m venv .venv
source .venv/bin/activate
pip install -e .
# MCP command: substack-api-mcp

What you can call

Notes go through Substack's global https://substack.com/api/v1 host. Drafts, publish, schedule, and tags go through {publication}/api/v1. create_post() is an SDK flow (create → update → optional tags → publish or schedule), not a single HTTP call.

Method	Python	CLI	MCP
Create note	`create_note()`	`create-note`	`create_note`
Delete note	`delete_note()`	`delete-note`	`delete_note`
Create / publish / schedule	`create_post()`	`create`	`create_post`
Create draft	`create_draft()`	`create --draft-only`	`create_post` (`draft_only=true`)
Delete draft	`delete_draft()`	`delete-draft`	`delete_draft`
AI check (Pangram)	`pangram_detection()`	`pangram-detection`	`pangram_detection`
Verify auth / profile	`get_profile_self()`	`profile`	`test_connection`
Get draft	`get_draft()`	`get-draft`	`get_draft`
Update draft	`update_draft()`	`update-draft`	`update_draft`
Publish now	`publish_now()`	`publish`	`publish_post`
Schedule	`schedule_release()`	`schedule`	`schedule_post`
List tags	`list_post_tags()`	`list-tags`	`list_tags`
Create tag	`create_post_tag()`	`create-tag`	`create_tag`
Attach tags	`set_post_tags()`	`set-tags`	`set_tags`
Get post tags	`get_post_tags()`	`get-post-tags`	`get_post_tags`

Rate limit for every endpoint: 1 request per second.

API reference

Request, response, Python, CLI, and MCP for each method.

Create note

Publish a Substack Note (feed comment). Optional link attachment is created first, then the note is posted.

Python: create_note()
CLI: create-note
MCP: create_note
Rate limit: 1 request per second

Request

POST (+ optional POST) https://substack.com/api/v1/comment/attachment (optional) → https://substack.com/api/v1/comment/feed

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	https://substack.com/ (same as get_profile_self)
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

None

Query params

None

Body

Name	Type	Required	Description
`bodyJson`	`object`	yes	ProseMirror doc object. SDK reuses ensure_draft_body() / ensureDraftBody(), then sets attrs.schemaVersion=v1.
`attachmentIds`	`string[]`	no	Ids from POST /comment/attachment. SDK fills this when attachment_url is passed.
`tabId`	`string`	yes	Captured default: "for-you"
`surface`	`string`	yes	Captured default: "permalink"
`replyMinimumRole`	`string`	yes	Captured default: "everyone"
`(attachment)`	`object`	no	Optional first call POST /comment/attachment: { "url": string, "type": "link" }

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number`	yes	Note / feed comment id
`type`	`string`	yes	Captured value: "feed"
`status`	`string`	yes	Captured value: "published"
`body`	`string`	no	Plain-text body
`body_json`	`object`	no	ProseMirror bodyJson echo
`attachments`	`array`	no	Attached posts/links when attachment_url was used

Notes

Same GLOBAL_API host as get_profile_self (https://substack.com/api/v1), not {publication}/api/v1. Referer is https://substack.com/. Origin stays the publication URL from existing _headers. Optional attachment is sequential: attachment then comment/feed. Captured surface=permalink tabId=for-you. Text-only notes omit attachmentIds. Image/file attachments were not in the capture (type=link only).

Python example

note = client.create_note(
    body="nice",
    attachment_url="https://yourname.substack.com/p/your-post",
)
print(note["id"], note["status"])

CLI example

substack-api create-note \
  --body "nice" \
  --attachment-url "https://yourname.substack.com/p/your-post"

Delete note

Delete an existing Substack Note (feed comment) by id.

Python: delete_note()
CLI: delete-note
MCP: delete_note
Rate limit: 1 request per second

Request

DELETE https://substack.com/api/v1/comment/{id}

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	https://substack.com/ (same as get_profile_self)
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

No request body

Response

Type: object (normalized by SDK)

Fields

Name	Type	Required	Description
`status`	`"deleted"`	yes	SDK-normalized status
`note_id`	`number \	string`	yes
`response`	`object`	yes	Raw Substack body (may be empty {})

Notes

Same GLOBAL_API host as create_note and get_profile_self. No request body. Reuses _request like delete_draft. Substack may return an empty response.

Python example

result = client.delete_note(123456)
print(result["status"])

CLI example

substack-api delete-note --note-id 123456

Create draft / publish / schedule

High-level SDK flow: create draft → update → optional tags → publish or schedule.

Python: create_post()
CLI: create
MCP: create_post
Rate limit: 1 request per second

Request

POST + PUT (+ optional) {publication}/api/v1/drafts → {publication}/api/v1/drafts/{id} → tags / publish / schedule

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

None

Query params

None

Body

Name	Type	Required	Description
`title`	`string`	yes	Post title (SDK maps to draft_title on Substack)
`body`	`string \	object`	yes
`subtitle`	`string`	no	Optional subtitle (default "")
`audience`	`string`	no	Who can read the post (default "everyone")
`section_id`	`number \	null`	no
`should_send_email`	`boolean`	no	Email subscribers on publish (default true)
`schedule_at`	`string \	null`	no
`publish`	`boolean`	no	If true and schedule_at is null → publish now. CLI --draft-only / MCP draft_only=true sets this false
`tags`	`string[]`	no	Tag names to ensure and attach after draft update

Response

Type: object

Fields

Name	Type	Required	Description
`draft_id`	`number \	string`	yes
`draft`	`object`	yes	Latest draft object from update_draft
`publication_url`	`string`	yes	Normalized publication origin
`edit_url`	`string`	yes	{publication}/publish/post/{draft_id}
`status`	`"draft" \	"published" \	"scheduled"`
`post_url`	`string`	no	Public post URL when published
`tags`	`array`	no	Attach results when tags were requested

Notes

This is an SDK orchestration, not a single HTTP call. Underlying Substack calls use the headers above and JSON bodies documented on create-draft / update-draft / publish-now / schedule pages.

Python example

result = client.create_post(
    title="Hello from API",
    body="Plain text becomes ProseMirror draft_body.",
    subtitle="Optional",
    tags=["api-test"],
    publish=True,
)
print(result["draft_id"], result.get("post_url"))

CLI example

substack-api create \
  --title "Hello from API" \
  --body "Plain text body" \
  --tags "api-test,newsletter"

Create draft (low-level)

Create an empty/partial draft without publishing.

Python: create_draft()
CLI: create --draft-only
MCP: create_post (draft_only=true)
Rate limit: 1 request per second

Request

POST {publication}/api/v1/drafts

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

None

Query params

None

Body

Name	Type	Required	Description
`draft_title`	`string`	yes	Title (SDK arg: title)
`draft_subtitle`	`string`	yes	Subtitle (SDK arg: subtitle)
`draft_body`	`string`	yes	ProseMirror JSON string (SDK accepts plain text or object)
`audience`	`string`	yes	Default "everyone"
`type`	`string`	yes	Post type, default "newsletter"
`draft_bylines`	`array`	yes	[{ "id": , "is_guest": false }]
`draft_section_id`	`number \	null`	no
`section_chosen`	`boolean`	yes	Whether a section was selected
`detect_language`	`boolean`	yes	Language detection flag (default true on create)
`translations`	`array`	yes	Usually []
`draft_podcast_url`	`null`	yes	Sent as null for newsletter posts
`draft_podcast_duration`	`null`	yes	Sent as null for newsletter posts

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number \	string`	yes
`publication_id`	`number \	string`	no
`draft_updated_at`	`string`	yes	Timestamp required for later PUT update_draft

Notes

Prefer create_post() for the full flow. Referer: {publication}/publish/post?type=newsletter.

Python example

draft = client.create_draft(
    title="Draft only",
    subtitle="",
    body="Hello",
    audience="everyone",
)
print(draft["id"], draft["draft_updated_at"])

CLI example

substack-api create \
  --title "Draft only" \
  --body "Hello" \
  --draft-only

Delete draft

Delete an existing draft.

Python: delete_draft()
CLI: delete-draft
MCP: delete_draft
Rate limit: 1 request per second

Request

DELETE {publication}/api/v1/drafts/{id}

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

No request body

Response

Type: object (normalized by SDK)

Fields

Name	Type	Required	Description
`status`	`"deleted"`	yes	SDK-normalized status
`draft_id`	`number \	string`	yes
`response`	`object`	yes	Raw Substack body (may be empty {})

Notes

No request body. Substack may return an empty response.

Python example

result = client.delete_draft(123456)
print(result["status"])

CLI example

substack-api delete-draft --draft-id 123456

Pangram AI / AI-slop check

Run Substack's Pangram AI-text detection on a draft body (human / AI-assisted / AI fractions).

Python: pangram_detection()
CLI: pangram-detection
MCP: pangram_detection
Rate limit: 1 request per second

Request

GET {publication}/api/v1/drafts/{id}/pangram_detection

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

No request body

Response

Type: object

Fields

Name	Type	Required	Description
`type`	`string`	no	Detection result type from Substack / Pangram
`header`	`string`	no	Human-readable summary header
`fraction_ai`	`number`	no	Estimated AI-generated fraction
`fraction_ai_assisted`	`number`	no	Estimated AI-assisted fraction
`fraction_human`	`number`	no	Estimated human-written fraction
`details`	`any`	no	Additional Pangram detail payload when present
`disclosure`	`any`	no	Disclosure / availability metadata when present

Notes

No request body. Path param only. Referer: {publication}/publish/post/{id}. Requires a draft with enough text for detection.

Python example

result = client.pangram_detection(123456)
print(result.get("header"), result.get("fraction_ai"), result.get("fraction_human"))

CLI example

substack-api pangram-detection --draft-id 123456

Verify auth / profile

Test session cookie and resolve current user profile.

Python: get_profile_self()
CLI: profile
MCP: test_connection
Rate limit: 1 request per second

Request

GET https://substack.com/api/v1/user/profile/self

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	https://substack.com/ (global profile endpoint)
`Referer`	`string`	yes	https://substack.com/ (global profile endpoint)
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

None

Query params

None

Body

No request body

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number`	yes	Substack user id (used in draft_bylines)
`...`	`any`	no	Additional profile fields from Substack

Notes

No request body. Auth is only via Cookie: substack.sid. Used by resolve_user_id() when SUBSTACK_USER_ID is not set. MCP test_connection wraps this call.

Python example

from substack_api_client import SubstackClient, SubstackAuth

client = SubstackClient(
    publication_url="https://yourname.substack.com",
    auth=SubstackAuth(sid="YOUR_SUBSTACK_SID"),
)
profile = client.get_profile_self()
print(profile["id"])

CLI example

substack-api profile \
  --publication-url "https://yourname.substack.com" \
  --sid "$SUBSTACK_SID"

Get draft

Fetch an existing draft by id.

Python: get_draft()
CLI: get-draft
MCP: get_draft
Rate limit: 1 request per second

Request

GET {publication}/api/v1/drafts/{id}

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

No request body

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number \	string`	yes
`draft_title`	`string`	no	Title
`draft_subtitle`	`string`	no	Subtitle
`draft_body`	`string`	no	ProseMirror JSON string
`draft_updated_at`	`string`	no	Optimistic-concurrency stamp for PUT

Notes

No request body. Path param only. Referer: {publication}/publish/post/{id}.

Python example

draft = client.get_draft(123456)
print(draft["draft_title"], draft["draft_updated_at"])

CLI example

substack-api get-draft --draft-id 123456

Update draft

Update title, subtitle, body, audience, section, email flag, or cover_image URL.

Python: update_draft()
CLI: update-draft
MCP: update_draft
Rate limit: 1 request per second

Request

PUT {publication}/api/v1/drafts/{id}

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

Name	Type	Required	Description
`last_updated_at`	`string`	yes	From latest get_draft/create_draft (client fetches it if omitted in SDK)
`draft_bylines`	`array`	yes	[{ "id": , "is_guest": false }]
`detect_language`	`boolean`	yes	Usually false on update
`translations`	`array`	yes	Usually []
`draft_title`	`string`	no	SDK arg: title
`draft_subtitle`	`string`	no	SDK arg: subtitle
`draft_body`	`string`	no	ProseMirror JSON. SDK arg: body (plain text or object)
`audience`	`string`	no	Audience string
`draft_section_id`	`number \	null`	no
`section_chosen`	`boolean`	no	Set true when draft_section_id is set
`should_send_email`	`boolean`	no	SDK arg: should_send_email
`write_comment_permissions`	`string`	no	e.g. "everyone"
`cover_image`	`string \	null`	no

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number \	string`	yes
`draft_updated_at`	`string`	yes	New concurrency stamp
`draft_title`	`string`	no	Updated title

Notes

Binary image upload is not implemented. Only cover_image URL strings are supported.

Python example

updated = client.update_draft(
    123456,
    title="Updated title",
    body="New body",
    cover_image="https://cdn.example.com/cover.jpg",
)
print(updated["draft_updated_at"])

CLI example

substack-api update-draft \
  --draft-id 123456 \
  --title "Updated title" \
  --body "New body"

Publish now

Publish an existing draft immediately.

Python: publish_now()
CLI: publish
MCP: publish_post
Rate limit: 1 request per second

Request

POST {publication}/api/v1/drafts/{id}/publish

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

Name	Type	Required	Description
`send`	`boolean`	yes	Email subscribers (SDK arg: send_email, default true)
`share_automatically`	`boolean`	yes	Default false
`audience`	`string`	yes	Default "everyone"

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`number \	string`	yes
`slug`	`string`	no	Public slug
`is_published`	`boolean`	no	Publish flag

Notes

Referer: {publication}/publish/post/{id}.

Python example

published = client.publish_now(123456, send_email=True, audience="everyone")
print(published["slug"], published["is_published"])

CLI example

substack-api publish --draft-id 123456

Schedule

Schedule a draft: optional prepublish GET, then scheduled_release POST.

Python: schedule_release()
CLI: schedule
MCP: schedule_post
Rate limit: 1 request per second

Request

GET then POST {publication}/api/v1/drafts/{id}/prepublish → {publication}/api/v1/drafts/{id}/scheduled_release

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

Name	Type	Required	Description
`publish_date`	`string`	yes	ISO-8601 UTC — query param on GET .../prepublish (same value as trigger_at)

Body

Name	Type	Required	Description
`trigger_at`	`string`	yes	ISO-8601 UTC schedule time (POST scheduled_release body)
`post_audience`	`string`	yes	Default "everyone"
`email_audience`	`string`	yes	Default "everyone"

Response

Type: any

Fields

Name	Type	Required	Description
`(body)`	`object \	empty`	no

Notes

When run_prepublish=true (default), client GETs prepublish first and raises if errors is non-empty. Content-Type applies to the POST only.

Python example

from substack_api_client import utc_iso
from datetime import datetime, timedelta, timezone

when = utc_iso(datetime.now(timezone.utc) + timedelta(hours=2))
client.schedule_release(123456, trigger_at=when)

CLI example

substack-api schedule \
  --draft-id 123456 \
  --at "2026-08-10T15:00:00.000Z"

List tags

List publication post tags.

Python: list_post_tags()
CLI: list-tags
MCP: list_tags
Rate limit: 1 request per second

Request

GET {publication}/api/v1/publication/post-tag

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

None

Query params

None

Body

No request body

Response

Type: array<object>

Fields

Name	Type	Required	Description
`id`	`string`	yes	Tag id
`name`	`string`	yes	Tag display name
`slug`	`string`	no	Tag slug

Notes

No request body. Referer: {publication}/publish.

Python example

tags = client.list_post_tags()
for tag in tags:
    print(tag["id"], tag["name"])

CLI example

substack-api list-tags

Create tag

Create a new publication post tag.

Python: create_post_tag()
CLI: create-tag
MCP: create_tag
Rate limit: 1 request per second

Request

POST {publication}/api/v1/publication/post-tag

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

None

Query params

None

Body

Name	Type	Required	Description
`name`	`string`	yes	New tag name

Response

Type: object

Fields

Name	Type	Required	Description
`id`	`string`	yes	Created tag id
`name`	`string`	yes	Tag name
`slug`	`string`	no	Tag slug

Notes

Does not attach the tag to a post — use set_post_tags / attach_post_tag.

Python example

tag = client.create_post_tag("product of the day")
print(tag["id"], tag["slug"])

CLI example

substack-api create-tag --name "product of the day"

Attach tags

Ensure tags exist (create missing) and attach them to a post/draft.

Python: set_post_tags()
CLI: set-tags
MCP: set_tags
Rate limit: 1 request per second

Request

GET/POST + POST {publication}/api/v1/publication/post-tag → {publication}/api/v1/post/{id}/tag/{tag_id}

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)
`Content-Type`	`string`	yes	application/json

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes
`tag_id`	`string`	yes	Tag id in attach URL

Query params

None

Body

Name	Type	Required	Description
`(create tag)`	`object`	no	When creating missing tags: { "name": string }
`(attach tag)`	`object`	yes	Empty JSON object {} on POST /post/{id}/tag/{tag_id}

Response

Type: array<object> (SDK normalized)

Fields

Name	Type	Required	Description
`tag`	`object`	yes	Resolved/created tag
`status`	`"attached" \	"already_attached"`	yes
`link`	`object`	no	Raw attach response when newly attached

Notes

SDK args: post_id + tag_names[]. Internally: list/create tags, then attach with empty JSON body.

Python example

attached = client.set_post_tags(123456, ["api-test", "newsletter"])
print(attached)

CLI example

substack-api set-tags \
  --post-id 123456 \
  --tags "api-test,newsletter"

Get post tags

Read tags currently attached to a post.

Python: get_post_tags()
CLI: get-post-tags
MCP: get_post_tags
Rate limit: 1 request per second

Request

GET {publication}/api/v1/post/{id}/tag

Headers

Name	Type	Required	Description
`Cookie`	`string`	yes	substack.sid= (browser session cookie)
`Accept`	`string`	yes	application/json
`Origin`	`string`	yes	Publication origin, e.g. https://yourname.substack.com
`Referer`	`string`	yes	Usually {publication}/publish or the draft editor URL
`User-Agent`	`string`	yes	Browser User-Agent string (client sends a Chrome UA by default)

Path params

Name	Type	Required	Description
`id`	`number \	string`	yes

Query params

None

Body

No request body

Response

Type: array<object>

Fields

Name	Type	Required	Description
`id`	`string`	no	Tag or link id
`post_tag_id`	`string`	no	Attached tag id (used by set_post_tags dedupe)
`name`	`string`	no	Tag name when present

Notes

No request body. Works for drafts and published posts.

Python example

tags = client.get_post_tags(123456)
print(tags)

CLI example

substack-api get-post-tags --post-id 123456

Auth

Product gate: APISUBSTACK_API_KEY is required. Substack itself is authenticated with the unofficial substack.sid cookie.

Cookie: substack.sid
API key: APISUBSTACK_API_KEY (ask_* from apisubstack.com)
Env: APISUBSTACK_API_KEY, SUBSTACK_PUBLICATION_URL, SUBSTACK_SID, SUBSTACK_USER_ID
Verify: GET https://rest.apisubstack.com/api/v1/keys/verify with Authorization: Bearer ask_…

Posting, drafting, deletion, tags. Notes and articles.

<a href="https://apisubstack.com/login" class="ltag-offer__button crayons-btn crayons-btn--primary">Start free — $9/mo after</a>

If you write and publish a newsletter and you want posts out of your editor (or your agent) and into Substack without the browser UI, this is the client.

How The New LinkedIn Algorithm Works in 2025 – The Ultimate Guide to LinkedIn Growth

Deal Breaker — Sat, 08 Mar 2025 05:24:15 +0000

Most people on LinkedIn are making one big mistake. They think growing LinkedIn followers = building a business. But here’s the truth: Only 3% of your perfect prospects will reach out to you first.

Author: https://www.linkedin.com/in/donnellychris/

So what about the other 97%?

If you’re looking to grow on LinkedIn, boost your LinkedIn posts, and increase engagement, LinkedIn is still the best platform for doing so.

Unfortunately, too many people adopt the wrong approach, waste their time, and give up before they’ve even gotten more followers on LinkedIn.

If you’re feeling frustrated and ready to quit, you need this cheat sheet to start seeing real results.

This article inspired by: https://www.linkedin.com/in/donnellychris/

The State of LinkedIn in 2025 — Why Organic Reach is Dropping

LinkedIn’s organic reach has declined dramatically, with the average post receiving 65% fewer impressions than in 2024. While reach is down, engagement per post has actually increased by 12%, meaning the right LinkedIn growth strategy still works.

LinkedIn has also increased advertising space by 16%, which means more promotion posts on LinkedIn and less visibility for organic content.

The key to growing followers on LinkedIn? Posting consistently. Users who post 1–2 times per day see compounding engagement and significantly boost their LinkedIn posts.

Not all content formats perform the same, though. Carousels and PDFs outperform other formats by 1.9x, while video reach has plummeted by 200% year over year.

Additionally, LinkedIn comments have evolved. AI-generated comments no longer work, and longer, more thoughtful comments now drive the most engagement.

The Science of LinkedIn Comments — How to Get More Engagement

LinkedIn prioritizes meaningful engagement over low-effort interactions.

AI-generated comments receive 5x less response from post authors and 7x less response from audiences.

Longer comments perform better. A comment with over 10 words has 2x more impact, while comments over 15 words have 2.5x more impact.

If you comment on 10–20 posts per day, you’ll grow LinkedIn followers, boost your LinkedIn post, and increase profile views by 50%.

Want your posts to stay visible longer? Engage with your own content. Go back to old posts, continue discussions, and keep the conversation going.

The more LinkedIn comments you receive and the more you engage, the more likely your content is to get promoted in the feed.

How to Format Your Posts to Grow on LinkedIn

Not all post formats are created equal when trying to grow LinkedIn followers.

Carousels are the highest-performing format and should have a strong title and at least 10 slides.
Infographics work best when they’re educational and data-driven. Visual content boosts your LinkedIn posts significantly.
Videos should follow the TikTok model: use a 3-second hook and focus on either education or inspiration.
Polls help you get more followers on LinkedIn by sparking discussions.
Text & Photo posts are best for personal storytelling and building connections.
Text-only posts should be short, direct, and pre-validated for impact.

If your goal is LinkedIn growth, prioritize carousels and cheat sheets, as they perform significantly better than other formats.

How to Boost Your LinkedIn Post and Get More Followers

Post in the right format — Carousels and cheat sheets perform best for promotion posts on LinkedIn.
Write longer posts — 800–1000 words perform 26% better.
Use shorter sentences — 10–12 words per sentence increase readability by 30%.
Include strong ideas and data — Posts with data visualization perform 36% better.
Start with a two-sentence hook — This boosts engagement by 20%.
Like your own post — This small trick can increase reach by 5%.
Engage with older posts — Even posts that are 2–3 days old can continue growing with active discussion.
Maximize dwell time –

Infographics and carousels increase dwell time and perform 1.9x better.
Longer captions have the same effect, boosting engagement.

Warm up your account before posting — Spend 15 minutes engaging with others before posting your own content.
Reply to comments for 15–30 minutes — Keep the discussion alive, ask follow-up questions, and stimulate deeper conversations.

If you follow this system, you will boost your LinkedIn posts, get more followers on LinkedIn, and improve your overall LinkedIn growth strategy.

But what if you’re just starting out on LinkedIn and don’t have an audience yet?

A cold start is one of the biggest challenges when trying to grow on LinkedIn. You can create high-quality content, but without initial engagement, the algorithm won’t push your posts to a larger audience.

This is where Upvote.club comes in.

Upvote.club helps creators and professionals kickstart engagement on LinkedIn by connecting them with real users who like, comment, and share their posts. Instead of waiting months to get followers on LinkedIn, you can accelerate your LinkedIn growth and start seeing results immediately.

Using Upvote.club ensures that your posts get the initial traction they need, leading to:

✅ More LinkedIn comments, boosting visibility.

✅ Higher reach and engagement, making LinkedIn’s algorithm favor your content.

✅ A stronger network, helping you grow followers on LinkedIn faster.

If you’ve been struggling with low engagement and slow follower growth, Upvote.club can provide the momentum you need to break through.

How to Sell on LinkedIn Without Sounding Salesy

The biggest mistake people make? Trying to sell too soon.

Instead, follow this approach:

Don’t Sell… SERVE 🤲

S → Show up consistently.

E → Educate.

R → Relate to their needs.

V → Value relationships over transactions.

E → Engage with authenticity.

The best way to grow on LinkedIn is to serve your audience first.

Final Thoughts

Selling on LinkedIn is a full process, but it is achievable.

How are you getting on with selling on LinkedIn?

Let me know in the comments! ⬇️

Join Free LinkedIn Sales Training

I’m hosting “How To Sell On LinkedIn”

Sign up here: https://lnkd.in/eMYw-JvF

I’ve also asked Will McTighe from SayWhat to pick two attendees and create incredible conversion content for them live on the call.

30 X/Twitter promotion Tools: The Complete Guide to Growing to 10K Followers in 2024

Deal Breaker — Sun, 05 Jan 2025 03:00:07 +0000

Since Elon bought Twitter 2 years ago, the platform has gained a second life. Where Twitter was dying before, now it’s clearly coming alive and attracting more and more active audience to the platform. That’s cool.

At the end of the article i will give most valuable strategy: how to get more followers on X/Twitter.

When I was preparing this material, I encountered the fact that good tools for X/Twitter promotion seemed to have died or become very outdated.

At the very end, I’ll propose a scheme that, in my opinion, is the most effective in 2024 for growing X/Twitter to 10k followers. Fist i must say it’s not easy. X/Twitter has a rather easy algorithm to rank in once your posts have been deemed relative to the topic, however just like running a website each account has their own authority levels.

💡 Golden Tip:

Content still is king showcase your expertise, but the most effective way to promote on X/Twitter is to collect reactions to your posts. The more engagement, the faster the growth. Repeat this like a mantra.

We’ll break down our tools into several groups:

Twitter/X Account Promotion Tools
Content Creation for Twitter/X
Twitter/X Analytics
Twitter/X Advertising
AI Tools for Twitter/X (can’t do without them)

Promotion Tools

upvote.club — A fresh tool that works like this: you perform task, like, share, repost, follow, get points, and then spend these points to create your own tasks. Creators claim that audience quality is top priority, and bots are ruthlessly filtered out. Works very well, with really a lot of quality and live audience. Very cheap points and free task creation. For modest money, you’ll get maximum engagement on your posts.
twiends — An even simpler principle: you add your X/Twitter account, other people see it on the network, subscribe to you, and you subscribe to them. Want more account views? Pay, starting from $15 per week for 700 views. Generally a decent tool that really works, but quite expensive. Managed to get +20 subscribers in a week.
socialplug — Essentially an ordinary store where you can buy X/Twitter followers or engagement for posts, likes, shares, reposts. Quality mostly resembles bots, but sometimes it gives an effect. Generally, I don’t really recommend buying followers because it doesn’t really give anything.
megafone.network — Principle similar to upvote.club, you add your post, people come and do the action you requested: like, comment, repost. But the price is higher, account setup costs money + each action. Around $5 per action. I spent $10 +40$ and got likes from actually quality guys — that was pleasing. But globally, I didn’t see a significant effect.
owlead — Essentially a mass follower tool via Chrome extension. Very simple principle: you install the extension, choose your audience, it goes and likes and follows them, they follow you back. Working scheme? Yes, it works. Is it worth using? So-so, you choose.
Like4Like — Ooooold tool, an old site that’s somewhat very inconvenient. Same principle as upvote.club — like for like. I tested it, but I don’t like the audience here, maximally similar to bots, but there’s a lot of them. Up to you whether you want such followers in your account.
X/Twitter Blue Checkmark — Obviously why it was created. Yes, so you pay for it, but it also gives a super bonus. Your posts are shown X2 times more often, and yes, you collect more engagement.

Content Creation for X/Twitter

Ofcource better make content manully, you can write content manually. But since it’s 2024, let’s optimize this process a bit and add AI to your hands.

Answerim — Helps answer relevant high quality tweets using AI. Works like this: add your product, brand, or site. The system does a scoring of your product using AI. You set a theme through keywords, the system finds relevant tweets or topics worth commenting on. There’s an auto-commenting button that allows automatic AI commenting on posts and threads. Works very cool. But I recommend monitoring responses to understand which AI wrote good ones and which bad ones to correct them.
Twitter Hunter — A cool tool that finds the most popular tweets on your needed theme. Does a rewrite through AI and publishes under your name, really works. But I recommend mixing with real posts and, for example, Answerim, so it doesn’t look like your account is run by AI alone.
typefully — Essentially a complete content management system for X/Twitter. You can create posts, edit them with AI of course. Create threads, schedule posts, scheduling system. All this reasonably costs money, from $15 per month. Can you do this in Google Docs? Of course, but it’s not sexy. And Typefully is sexy.
ViralExamples — an extreeemely useful newsletter about what content to write to go viral. I really highly recommend it, it’s a must-have. There are many tools that collect tweets and select relevant by topics.

X/Twitter Advertising — post promotion

The main problem with buying X/Twitter ads today is still bots. Many who write about X/Twitter advertising even now complain about the dominance of bots that loose budgets.

X Advertising Portal — The official X/Twitter advertising cabinet what helps you find a target audience. After Elon bought it, many things changed. It became easier to set up ads, new formats appeared. The main advantage is you can start with $50 per day, no need to immediately invest thousands. Targeting here is weaker than Facebook, but the audience is more solvent.
Quick Promote — This is just a button in X/Twitter interface. The simplest way to promote a tweet. Directly from the interface, you can choose a post and throw a budget at it. No complex settings, everything is simple and fast. Ideal for tests.
Upvote.club – works similar to X/Twitter advertising. You need to create a tweet and order the reactions you want for it. The difference is that advertising will show your tweet where needed and people will give reactions and your audience will grow, while here your tweet will be liked, followed etc. and your audience will grow from that.

Twitter Analytics

Twitter Graph — A GitHub library that does an incredible thing: you throw in any account and get and it shows you variety of people: old friends, work colleagues, funny accounts, etc. Gradually, my timeline has become this messy mix that makes X/Twitter so enjoyable.
TwitterAnalytics — Built-in X/Twitter analytics, shows basic metrics: reach, engagement, subscriber growth. Free and good for start, but functionality is limited. But you blue checkmark
SocialBlade — Top service for analytics, shows growth dynamics, compares with competitors, gives insights on the best posting time. Costs from $30 per month, but really helps understand what works and what doesn’t.
Followerwonk — Cool thing for subscriber analysis. Shows demographics, interests, when they are most active. Helps understand your audience and adjust content for them.
Tweet Binder — cool tool for analyzing hashtags and trends. You can track any hashtag, see who writes about it the most, what’s the reach, and when activity peaks. Helps understand which hashtags actually work and which are just noise.
Fedica — visualizes your followers’ geography on a map. Seems simple, but really helps understand where your main audience is and when it’s better to post content. It can also analyze the best posting time based on your followers’ time zones.
Twitonomy — provides super detailed analytics for your tweets. Shows which words get more engagement, who your most active followers are, how often you use links/images and how this affects reach. Has a free plan, but with limitations.
Trendsmap — realtime analytics of trends by geolocation. You can see what people are talking about in different cities and countries right now. Perfect for news accounts or if you want to always stay on trend. Paid (from $25 per month), but saves tons of time on searching for current topics.
BlackMagic.so — a cool AI that analyzes your account and suggests what to write to get maximum reach. It can also find trends in your topic area. Expensive (from $50 per month) but really works.

AI Tools for Twitter

TweetGPT — integrates directly into X/Twitter’s interface, helps generate post ideas and even write them. Runs on GPT-4, so the content quality is decent. Has a free plan, but with limitations.
Answerim — Helps answer relevant tweets using AI. Works like this: add your product, brand, or site. The system does a scoring of your product using AI. You set a theme through keywords, the system finds relevant tweets or topics worth commenting on. There’s an auto-commenting button that allows automatic AI commenting on posts and threads. Works very cool. But I recommend monitoring responses to understand which AI wrote good ones and which bad ones to correct them.

Huge list of Ai services for twitter:

Most Effective Grow X/Twitter Strategy in 2024

I spent 4 weeks talking with influencer marketing agencies, and 9 out of 10 told me that they support each post their influencers publish with likes, comments, reposts, save etc. Within the first hour. They go all-in on the post as an agency. They call it golden hour strategy.

Also, I found a tweet by Natia Kurdadze where she mentions that X Blue gives a 2x boost to posts on an account, while: Likes give a 30x boost, Comments give a 50x boost, Reposts give a 20x boost, Visual content gives a 2x boost

Golden strategy to grow your audience [step-by-step guide]

Get the blue checkmark — this is the base to grow your audience
Choose the theme you want to write about — for example, marketing. Dive into this theme in Twitter Hunter.
Create a content mix: 40% your unique content, 30% through AI (like TweetGPT), 30% replies in other threads via Answerim. Do not forget create a tweets threads it’s working.
For a quick start, use upvote.club to gain initial engagement. Throw every post you create there
Analyze through SocialBlade what worked, what didn’t
For well-performing posts, pour more engagement through upvote.club. Buy all actions: like, share, repost, comment

💡 With this scheme, you need 3–4 months to build up to the first 10k subscribers on X/Twitter.

The main thing — don’t chase the number of subscribers, but work on content quality and engagement. X/Twitter in 2024 is not about mass following, but about creating a community around your expertise.

P.S. If I forgot some service, write to me in the comments.

If you like this article please give a clap 👏

ASK: how do you feel about starting selling github repo?

Deal Breaker — Mon, 04 Oct 2021 15:15:25 +0000

Hello to dev.to community. We are improve our marketplace code.market step-by-step, and now we wannа give to developer option:

Selling private github repository via our platform

This is a little bit custdev: Would this option be useful or not? I would love catch your detailed answer in the comments.

Thank you 🙏