How to Warm Up an X (Twitter) Account Safely (2026 Checklist)
EN
Updated July 2026. Fresh X accounts that try to behave like established ones get suspended in week one. The good news: a careful, gradual warm-up — with low daily caps, randomized delays, and a real residential proxy — gets a brand-new account to a working baseline in two to three weeks. This is the warm-up curve we use with HelperX slots; full hub: X account warm-up guide.
Why a warm-up matters
X's anti-abuse stack does not look at any single signal. It looks at the ratio of behaviors over the lifetime of the account: how soon after sign-up did the account follow 200 people, how soon did it start replying, did it post anything original first, does it have a profile picture and a bio, does its IP look like a residential one. A fresh account that opens at full throttle — even at limits that are perfectly safe for a mature account — is the simplest possible heuristic to flag.
The fix is not to slow down forever. It is to ramp. The first three weeks set the tone; after that, you can run with normal caps. For the full hub of related articles, see the X Account Warm-Up Guide.
Prerequisites before automation
Before you touch any automation tool:
- Real profile. Display name, avatar, header image, bio, location, pinned post. An empty profile that starts engaging looks like a throwaway, because that is how throwaways look.
- Residential or mobile proxy. Datacenter IPs are flagged on sight. The proxy should match the account's stated country roughly — a US-bio account on a Vietnamese datacenter IP is a red flag. Full write-up: residential proxies for X automation and proxy setup docs.
- One device, one session. Sign in once from the same browser/device fingerprint you will run from. Switching fingerprints mid-week trips heuristics. Multi-account operators: never share IP or cookies — see multi-account isolation.
- Manual activity first. Spend two or three days using the account like a human: scroll the For You tab, like a few posts, follow ten accounts you actually care about, send a DM. This builds baseline signal. Before automation each day, avoid a pure cold open.
If you must pause mid-warm-up, do not “catch up” with a reply marathon. Resume with the ladder in dormant-then-burst. Broader safety cluster: X Safety & Multi-Account Ops.
Week one: humans only
Run zero automation. The account should do the following manually:
- Post one original post per day. Plain text is fine; an image is better.
- Reply to three to five posts in your niche, in your own words.
- Follow five to ten relevant accounts per day, not more.
- Like fifteen to thirty posts per day across the feed.
Why no automation: the account is being scored against a "is this a real person" model. The fastest way to lose that scoring is to start replying with templated text on day three.
Week two: introduce one module
Connect the account to HelperX. Set up a residential proxy. Enable Reply (Search) only — nothing else yet. Configure it as follows:
- Daily cap: 15. Half of the Free-plan default.
- Work-time window: a 6-hour block matching your stated timezone.
- Delay between replies: 6–12 minutes, randomized.
- Search queries: 2–3 narrow keywords from your niche, not broad terms.
- Reply templates: 8–10 variations, written in your voice. Resist the urge to enable AI generation in week two — humans evaluating your account will see boilerplate AI cadence instantly.
- Post-age filter: only reply to posts under 2 hours old. Old posts get less authentic-looking replies.
Continue the manual posting from week one in parallel. The account should look like a person who occasionally takes 6 hours to write replies, not a 24/7 broadcaster.
Week three: layer in posting
Raise the Reply (Search) cap to 25. Enable Regular Post with one scheduled post per day at a time inside your work-time window. If you also write live posts, do not let the total exceed 3 posts per day in week three.
This is the week to start watching the audit log. Look for:
- Any "error: rate limited" entries. If you see them, halve the daily cap.
- Posts that received zero engagement. That can mean a soft shadow ban — review your last few replies for anything spammy.
- Replies on posts older than 2 hours. Tighten the post-age filter.
After week three
If the account is healthy — replies are getting normal engagement, no rate-limit errors in the log, follower count growing slowly but consistently — you can move to your plan's normal caps. Add Reply to Comments first (it is the lowest-risk module because it only touches your own audience). Add Top Repost on Pro, and Welcome DM last. Welcome DM is the highest-risk module because unsolicited messages are what most spam filters look for first.
Red flags that mean stop
If you see any of these in the audit log, pause every module on the slot for 48 hours and re-evaluate:
- Sudden drop in engagement (likes/reply ratio falls by more than half week over week).
- Followers gained in week N are far below followers gained in week N–1, despite the same activity.
- Posts not appearing in search for your username.
- Two or more "account temporarily limited" prompts on manual login.
- X's "we sent a code" challenge appearing repeatedly during automated runs.
Recovery is usually possible if you stop early. Recovery from a full suspension is not.
Where to go next
Once the account is past week three, the next thing to read is our reply automation safety guide — the configuration defaults that keep things calm at full caps.