Why these are two jobs, not one
A follower cleanup feels like it should shrink your audience. On Mastodon it does not work that way. A public post is public at its own permalink, and account-level relationship changes do not rewrite the visibility of posts that already exist. The platform sets privacy per post rather than across the whole account.
Mastodon public posts can be seen at their permalink without logging in, and privacy is set per post rather than across the whole account. Source
That single fact drives the whole workflow below. Removing a follower is a relationship action. Reviewing old public posts is a content action. They use different controls, produce different results, and should be checked with different evidence. Treating one as a substitute for the other is the most common mistake in this task.
Step 1: Decide what you actually want to change
Before touching any control, write down the outcome you want. Most people want one of three things:
- Stop a specific account from following me. This is a relationship change.
- Stop a specific account from interacting with me or seeing my future posts in their feed. This may need a block, not a removal.
- Reduce what is publicly readable from my history. This is a post-by-post review, not a follower action.
If you cannot name the outcome in one sentence, stop. Cleanup done without a target tends to remove the wrong thing and leave the real exposure untouched.
Step 2: Remove the follower through the relationship controls
Mastodon provides relationship settings where an account owner can manage connections. Use those controls to remove a follower rather than improvising with profile edits or post deletion.
Mastodon relationship settings let an account owner select accounts to unfollow or remove from their followers. Source
The relationship manager can filter connected profiles by relationship and account status, which helps when you are working through a list rather than a single account.
The relationship manager can filter connected profiles by relationship and account status. Source
Work slowly here. Confirm the account you are acting on before you confirm the action. A removal is a change to a relationship, and it should be the only change you make in that step.
Step 3: Distinguish removal from blocking and from deleting a post
These three actions are not interchangeable. Use the decision table to pick the right one.
| Goal | Appropriate action | What it changes | What it does not change |
|---|---|---|---|
| Stop one account from following you | Remove the follower | The follow relationship | Visibility of existing public posts; the account’s ability to view a public permalink |
| Stop an account from interacting with you or following again | Block | The relationship and interaction between the two accounts | The public readability of posts that are already public |
| Remove a specific post from public view | Delete or change the visibility of that post | That post’s availability | Who follows you; other posts |
| Reduce your future public audience | Change your posting defaults | Default visibility of new posts | The visibility of posts already published |
A removal is not a block. A block is not a deletion. A deletion is not a follower cleanup. If you find yourself hoping one action will cover two rows of this table, you have found the gap that needs a second step.
Step 4: Review old public posts on their own terms
Old public posts need their own pass. Open the posts you care about at their permalink and check what a logged-out visitor would see. Do not assume that because you removed a follower, an old post is now harder to reach.
Do not assume that because a post is old, it is effectively private. Do not assume that because a post is public, it is permanently indexed everywhere. Neither assumption is a substitute for looking.
When you review, sort posts into three buckets:
- Keep public. The post is accurate, current, and you are comfortable with it being readable at its permalink.
- Needs a visibility change. The post is fine in substance but should not be public now.
- Needs deletion. The post should not exist in its current form.
Make the change per post. Then re-check the permalink. If the post is still readable without login, the change has not taken effect the way you intended, and you should investigate before moving on.
Step 5: Set the default for your next post deliberately
Post visibility is chosen per post, so the default you carry into your next post matters. Before you publish anything new, decide which visibility you want and confirm it on the composer. Do not rely on the setting you used last week, and do not assume a follower cleanup changed your defaults. It did not.
A simple habit: after any relationship cleanup, write your next post with the visibility you intend, check it at the permalink, and only then return to the rest of your review.
Common mistakes
- Assuming follower removal recalls old posts. It does not. A public post remains readable at its permalink. Removal changes the relationship, not the archive.
- Assuming follower removal reaches cached or copied material. It does not. You cannot recall what another party has already saved, quoted, or screenshotted, and no platform control guarantees that.
- Treating a block as a cleanup tool for history. A block changes the relationship between accounts. It is not a post-visibility control.
- Deleting a post as a substitute for a relationship decision. If the problem is a follower, deleting posts leaves the follower in place and removes content you may have wanted to keep.
- Editing a profile and calling it done. An edited or empty profile does not establish that stored data is gone, and it does not change post visibility.
- Skipping the logged-out check. If you never view the permalink without logging in, you do not know what a visitor sees.
- Confusing a matching handle with a confirmed identity. The same username on two platforms is a lead, not proof that both accounts belong to the same person. Photos, biographies, and handles can match without establishing identity.
Protecting your own footprint after the cleanup
Once the relationship and post review are done, turn to your own known public handles. A username search is not a complete account inventory, and it will not tell you that an account has been renamed or abandoned. What it can do is surface public matches that you can then check yourself.
TraceSeek, the app covered by TruthsSeek, runs a username search across 3,000+ platforms. The first scan is free, requires no registration or login, and the product states a scan time of 20-30 seconds. Those are product statements, not independent measurements. The app does not change platform settings, does not remove followers, does not alter post visibility, and does not verify identity. A match it returns is a lead for you to review, not proof of ownership.
If you want to understand how matches are framed and what they can and cannot establish, read the methodology notes at /methodology/. For the underlying visibility mechanics, the existing guide at /guides/mastodon-post-visibility-public-followers-and-private-mentions/ covers public, followers-only, and private mentions in more depth.
A practical closing sequence:
- Confirm the follower removal took effect in your relationship list.
- Re-check each post you changed at its permalink without logging in.
- Confirm your next post’s visibility before publishing.
- Review your known public handles and note any match you cannot explain.
- Keep a recovery method you control until any account closure you are considering is fully complete.
Key facts
- Mastodon relationship settings let an account owner select accounts to unfollow or remove from their followers.
- The relationship manager can filter connected profiles by relationship and account status.
- Mastodon public posts can be seen at their permalink without logging in, and privacy is set per post rather than across the whole account.
- TraceSeek searches 3,000+ platforms, and its first scan is free with no registration or login required.
- A public username match is a lead, not proof that two accounts belong to the same person.