Skip to content
All guides

Social media

A Bluesky Account for a Bot: Fresh Profile, Clear Label

A legitimate Bluesky bot needs an account that is clearly automated: no borrowed human history, the automation label switched on and an app password for its software.

Contents

What the bot is for decides the account

A bot on Bluesky can be genuinely useful: a library account that posts new arrivals, a transit project that shares service notices, a hobby bot that posts a photograph from an open archive each day. Each needs an account to post from, and the choice of that account says a lot about whether readers will trust what it posts.

The working rule is simple. A bot should look like what it is. Readers should be able to tell at a glance that posts come from software, and nothing in the account's past should suggest that a person is speaking.

Write a one-line purpose before choosing an account: what the bot posts, how often, and whether it ever replies. That line tells you which listing details matter and becomes the first sentence of the bio.

The automation label

Bluesky's account settings include an Automation label. When it is switched on, the account is marked as automated and the label appears next to its name, so people see it before they read the posts. It is a label the account holder sets, and the account settings show it as On or Off.

Switch it on for any account that posts automatically. A bot that passes itself off as a person runs against the Be Authentic principle in Bluesky's Community Guidelines, which does not allow content meant to deceive or mislead, and readers who discover an unlabelled bot have every reason to distrust it. Say the same thing in plain words in the display name or bio, together with who runs the bot. If the bot's purpose changes later, update the bio as well; the label says the account is automated, while the bio says what it is for.

Fresh account, not a used one

A used account brings followers who followed a person, likes that person gave and blocks that person made, and Bluesky keeps likes and blocks public. Turning such an account into a bot would present software as the continuation of someone's voice. Choose a fresh account with an empty profile, so the record starts with the bot's first automated post.

Account age matters little for a bot. Control matters a great deal: the listing should deliver mailbox access, or state that the email is unconfirmed, so you can move the email to the project's own address. Bluesky's password resets and two-factor codes go to that mailbox, and you will be the one maintaining the bot for as long as it runs.

Connect the software with an app password

Bluesky's help centre recommends generating an app password in the settings to sign in to third-party apps. Give the bot's software its own app password instead of the main password. If the code leaks or the hosting changes, you revoke that one app password and create another, while the main login stays private.

Keep the main password and the email for yourself, switch on email two-factor, and note which app password belongs to which deployment. If a collaborator maintains the code, store the deployment's app password in the project's secret store rather than passing the main login around.

Review the app password list from time to time. One entry per deployment makes it obvious when an old server is still connected, and a name you do not recognise is a reason to revoke it at once.

A worked example: a garden's plant of the week

A hypothetical botanical garden wants a bot that posts a plant of the week from its own photo archive, with no replies to anyone. It chooses a fresh account from a listing that states email access, moves the email to the garden's address, switches on the automation label, writes a bio saying the account is automated and run by the garden, and gives the posting script an app password.

The garden passed over an older listing with an active posting history. That history had nothing to do with plants, and repurposing it would have handed a bot an audience that never asked for one. The fresh account starts small and honest, which is what a weekly archive bot needs. The garden also states the posting rhythm in the bio, so followers know what to expect and an unusual burst of posts would stand out to the team straight away.

When not to buy for a bot

Do not buy accounts to run many bots that boost each other, post the same message widely or reply to strangers unprompted. The Community Guidelines prohibit spam and artificially manipulating engagement or social signals, and no listing makes that acceptable. Do not buy to replace a bot account that Bluesky has suspended either; creating new accounts to evade enforcement is prohibited as well.

Bluesky's Community Guidelines also list selling, transferring or sharing accounts among prohibited practices, so follow Bluesky's terms with any account from the category. rStock remains independent of Bluesky and carries no endorsement from it. The account arrives as a delivery record on your order page. Check that the profile is empty and that the email line matches the listing, and open a dispute within the window shown there if it does not. Compare fresh Bluesky accounts on rStock for a bot that is labelled from its first post.

Frequently asked questions: A Bluesky Account for a Bot: Fresh Profile, Clear Label

Keep reading