What X currently allows
Classify the action before you compare features, filters, or speed.
The Short Answer: Do Not Automate the Follow Decision
Last reviewed: August 2, 2026. This guide covers software that makes your account follow other people. A service that delivers followers to you is a different problem. If your account has started following strangers without your knowledge, go to the recovery section below.
X’s current account-behavior guidance says automated proactive following and automated unfollowing are not allowed. Its Developer Guidelines summarize the boundary as no bulk, aggressive, or automated following. X also prohibits follow churn and using automation to duplicate another account’s followers in its Authenticity policy.
The useful distinction is not software versus no software. It is discovery versus relationship action. Software can help search public conversations, preserve source URLs, and organize a shortlist. A person should still decide whom to follow and initiate that action deliberately inside X, or through a specifically user-initiated official-API interaction where current rules and developer access allow it.
| Activity | Practical reading | What to do |
|---|---|---|
| Search or read public posts to find relevant accounts | Read-only research is a different action class, but access terms and result limits still apply. | Use a focused query and keep the source URLs. |
| Review a profile, then manually follow it in X | Normal account use, still subject to anti-spam rules. | Make an individual relevance decision. |
| Show a recommendation, then let the user initiate one follow | Different from a proactive bot, but implementation and developer access still matter. | Use X itself or an allowed, specifically user-initiated official-API interaction. |
| Automatically follow every account matching a keyword | Automated proactive following. | Do not use it. |
| Automatically copy another account’s followers | Specifically named in X’s Authenticity policy. | Do not use it. |
| Follow accounts, wait for follow-backs, then unfollow the rest | Follow churn. | Do not use it. |
| Automatically follow back every new follower | Current developer guidance does not create an automated-follow-back exception. | Review and follow back manually when it makes sense. |
How auto-follow tools work—and why there is no safe speed
API capability, rate capacity, and behavior permission answer different questions.
Why an API Follow Endpoint Does Not Make an Auto-Follow Bot Safe
The X API has a Follow User endpoint and OAuth exposes a follows.write scope. That proves an authenticated application can send a follow request. It does not prove software may select targets and run that action automatically.
X currently lists 50 requests per 15 minutes for the per-user manage-follows endpoint. X separately lists 400 follows per day as an account ceiling and may apply an account-specific follower-to-following ratio after an account reaches 5,000 following. Those are technical limits, not a recommended operating rate. See the API rate-limit table and account follow limits.
If you are deciding whether official authenticated API access or a public-source research tool fits the job, use CarryFeed’s separate guide to X API, MCP, pricing, and account-action boundaries.
| Layer | What it tells you | What it does not tell you |
|---|---|---|
| API capability | Whether an authenticated request can perform one follow action. | Whether software may choose targets or run a schedule. |
| Rate limit | How many requests an endpoint or account can accept in a window. | Whether the behavior is approved or undetectable. |
| Behavior policy | Whether the workflow is allowed under current platform rules. | That a vendor’s implementation or approval is current. |
What an Auto-Follow Tool Actually Does
The auto-follow products reviewed for this guide commonly combine three jobs: collect possible accounts, execute follows without a fresh decision for each account, and later unfollow some accounts that did not follow back.
Filters can make the candidate list narrower. A tool may check bio words, language, recent activity, follower count, profile images, keywords, hashtags, a competitor’s audience, a CSV, or a search result. Better filtering can improve a shortlist. It does not change the nature of an automated relationship action.
| Stage | Typical action | Better boundary |
|---|---|---|
| Discovery | Collect accounts from keywords, hashtags, another account’s followers, or a CSV. | Create candidates with public-source reasons to review them. |
| Execution | Follow every candidate that passes a filter or schedule. | Require a fresh human decision for each relationship action. |
| Cleanup | Record follow-backs and unfollow some of the rest. | Do not create a follow/unfollow loop to inflate counts. |
There Is No Official Safe Speed for an Auto-Follow Bot
Auto-follow vendors often recommend small batches, random delays, daily budgets, or breaks between follow and unfollow runs. Those settings do not convert a prohibited workflow into an approved one.
The faulty logic is simple: X allows up to 400 follows per day, the tool stays below 400, therefore the tool is safe. The first statement describes a technical account ceiling. The conclusion ignores separate rules against automated proactive following, follow churn, indiscriminate following, and follower duplication.
The same problem applies to the API quota. Fifty follow requests per 15 minutes is an endpoint capacity, not a published spam-detection threshold. The current official pages reviewed for this guide do not identify an interval at which an automated relationship action becomes acceptable.
Treat phrases such as undetectable, human-paced, natural intervals, and zero ban risk as marketing unless the vendor can point to a current official rule or written approval that covers the exact behavior.
Keywords, competitor followers, and follow-back claims
A narrower filter can improve a research queue without making an automated action acceptable.
Can You Auto-Follow Keywords or Another Account’s Followers?
The useful part of keyword targeting is discovery through X itself or an access method permitted for the use case. A keyword match is still noisy. Someone may mention customer onboarding because they sell onboarding software, because they are complaining about a bank, or because they reposted somebody else. Use the match to build a review queue, not to trigger a follow.
Copying another account’s audience is often described as audience cloning. X’s Authenticity policy explicitly names duplicating another account’s followers, particularly through automation, as prohibited behavior. It is also weak targeting: following an account does not explain why the person followed, whether they remain active, or whether they share your narrower interest.
Start from current public conversations and a clear relevance rule instead of copying an entire relationship graph.
Do Twitter Auto-Follow Bots Work? What the Evidence Can Actually Show
Auto-follow marketing usually reports the easiest number: follow-backs. That number does not show whether anyone read a post, returned next week, joined a useful conversation, subscribed, or bought.
The vendor pages reviewed for this guide do not establish a generalizable 2026 follow-back or lead-conversion rate. Frequently repeated figures trace back to vendor samples or marketing articles without enough information about account types, targeting, observation windows, or the definition of a qualified lead.
That does not prove the result is zero. It means a precise average would create false confidence. Treat an unexplained percentage as a sales example, not a forecast.
- Ask how many accounts were included and what kinds of accounts they were.
- Ask for the dates, observation window, and number of attempted follows.
- Ask how protected, inactive, unavailable, or suspended accounts were handled.
- Separate a follow-back from a reply, qualified conversation, signup, or revenue.
- Ask whether the vendor selected or excluded any accounts after seeing the results.
- Do not use a screenshot without the source table, definitions, and denominator.
Audit access before you connect
Inspect the credential path, action trigger, permissions, and exit route before trusting a growth claim.
Check the Access Method Before You Trust the Product
An auto-follow product must act through your account somehow. The connection method tells you which credentials and account powers are exposed, but no connection method turns a prohibited workflow into an approved one.
OAuth is safer than handing a vendor your password, but it is not a compliance badge. Read the permission screen. A follows.write permission means the app can follow and unfollow people for you. X also says OAuth authorization alone is not sufficient consent for every automated action in its Automation Rules.
| Access method | What to inspect | Stop sign |
|---|---|---|
| OAuth | Exact scopes, action trigger, token storage, revocation, and whether every action was clearly described. | The vendor treats OAuth as proof that every automated workflow is allowed. |
| X password | Do not continue. X recommends third-party authorization through OAuth instead. | The service asks you to type or send your X username and password. |
| Session cookie or logged-in browser | Treat cookies and tokens as credentials and ask whether the service scripts the website. | The setup asks you to export a cookie or promises human-like browser behavior. |
| Browser extension | Permissions to read and change data on x.com, remote data transfer, and the exact action performed. | The extension uses your session to press Follow repeatedly. |
How to Evaluate a Twitter Auto-Follow Tool: Eight Questions
Evaluate the workflow before looking at growth screenshots. A vendor that only answers with daily limits, randomized delays, or customer follower counts has not answered the permission or account-access question.
- Who chooses each account? A filter should create candidates, not silently approve every match.
- Who initiates each follow? Look for a fresh, specific user action rather than a schedule or background job.
- Does it use the official X API? Browser scripting and session-cookie automation create additional policy and security problems.
- Which OAuth scopes does it request? follows.write, post, DM, and account-management permissions need separate explanations.
- Does it automatically unfollow? That can turn a discovery feature into follow churn.
- Does it copy another account’s followers? X specifically calls out this behavior.
- How are credentials and tokens stored and deleted? A vague security slogan is not an answer.
- How do you disconnect it? You should be able to stop every job, revoke access, and delete stored account data without contacting sales.
If you already connected an auto-follow bot
Treat unexplained follows as an account-access incident, not a targeting mistake.
Do not create another burst of account activity to clean up the first one. Stop the automated relationship actions, then secure the account.
- Pause every follow and unfollow job. Disable schedules and remove any browser extension that performs the actions.
- Review Apps and sessions. Revoke anything you no longer trust or use by following X’s connected-app instructions.
- Change your password if you gave it to a third party. If you exported a cookie or suspect a stolen session, log out all other sessions as well.
- Review active sessions, connected apps, the current following list, and posts, replies, or DMs you did not initiate. X does not provide a complete follow/unfollow audit trail here.
- Follow the on-screen recovery path if the account is limited. X may ask you to verify an email address or phone number, or temporarily limit account features. Read X’s locked and restricted account guidance.
- Do not evade the restriction by switching bots, creating replacement accounts, or restarting the same pattern at a slower speed.
A human-reviewed alternative
Let a tool prepare public evidence, then make the relationship decision yourself.
The original job was not to make software click Follow. It was to find relevant people without spending all day searching. Keep that job and change the workflow.
The sequence below is a reusable research template, not a claimed performance test. The example topic is illustrative. Every candidate still needs a current public source and a human decision.
Start by writing a relevance rule: find English-language SaaS operators who recently wrote an original public post about activation or onboarding and whose work gives us a specific reason to keep reading. Then use X’s own Advanced Search or a public research surface to build a candidate set.
CarryFeed’s Twitter Advanced Search can help compose keyword, account, date, hashtag, and media clues and keep the generated query visible. It is an independent, read-only public research surface, not an official X API client. Operator support and result availability can vary by the active public upstream, so verify the query and open the original source.
If date is the strongest clue, use the date-search workflow. If expected public posts are missing, check the reasons in Why Twitter Search Misses Posts before treating an empty result as proof that nothing exists.
- Define relevance before searching: topic, recency, content type, and a source-backed reason to review the person.
- Search public conversations rather than copying an entire follower graph.
- Keep a small table with candidate, direct source URL, why relevant, and the human decision.
- Inspect the candidate in the Twitter Profile Viewer and check whether the topic recurs in available recent public activity.
- Use Twitter Statistics only for its bounded sample of up to 40 recent original public posts when available. It excludes replies and reposts and is not private account analytics.
- Make the follow decision manually inside X. For the wider measurement loop—replies, profile conversion, follows, and return value—use the separate 30-day Twitter/X growth system.
| Candidate | Source post | Why relevant | Human decision |
|---|---|---|---|
| @handle | Direct public URL | One concrete sentence tied to the source | Follow, add to a List, revisit, or skip |