A Mastodon permalink that opens in a browser does not promise that the same post appears in search. Mastodon sets visibility per post, and a public post can be posted as Quiet public: it stays reachable on the author's profile and by direct permalink but is kept out of search, live and explore features. That is a deliberate visibility choice, not necessarily a deletion or a federation failure. Record which explanation the available evidence supports and stop when it supports none.
Find public social profile clues with our TraceSeek app.
Start with what the permalink actually proves
An opening permalink shows that the post exists at that address for you, at that moment. It does not show that the post is indexed, that every server holds a copy, or that the author intended it to be found by strangers. Treat the permalink as one artifact and the search result as a separate observation, then ask which visibility label the author applied.
- Open the permalink and note the visibility label shown next to the post, if any
- Note the account, date and server shown on the page as plain observations
- Write down whether you found the post from a search or from a supplied link
Quiet public is a visibility setting, not a defect
Visibility is chosen per post. A public post can appear in public feeds and profiles, while a Quiet public post remains public on the profile and at its permalink but is absent from search, live and explore features. Quiet public was previously called Unlisted. So if the account otherwise allows full-text discovery, a single post can still be missing from search because of the label on that post rather than because of anything the search engine or another server did. [Mastodon: per-post visibility and quiet public]
Separate search absence from other causes
A post absent from search can have more than one explanation, and the explanations lead to different next steps. Quiet public is a deliberate exclusion. A remote server may also have never fetched or indexed a copy, which is a coverage issue unrelated to the label. Deletion would generally mean the permalink no longer opens the post at all. Setting these side by side keeps one observation from being stretched into a conclusion it cannot carry.
| observation | limit | next step |
|---|---|---|
| Permalink opens; label reads Quiet public | Absence from search is expected for this post; says nothing about other posts | Record the label and stop; do not ask anyone to change it |
| Permalink opens; label reads Public; search still omits it | Search coverage is not guaranteed; the cause is not visible from here | Note the gap as unknown and stop |
| Permalink no longer opens the post | Could be deletion, a changed address or a restricted view; do not guess which | Record that the artifact is unavailable and stop |
Do not treat a permalink as a permission bypass
Followers-only and private-mention posts carry their own permission restrictions, and a permalink does not bypass them. If the post is restricted, absent, mismatched or ambiguous, the honest move is to record that precise limit and stop. Do not look for cached copies, alternate mirrors, or other routes around a restriction, and do not press the author or others for access. Quiet public content is public but deliberately excluded from discovery; it is not an invitation to redistribute it more widely. [Mastodon: per-post visibility and quiet public]
Keep observation, limit and decision apart
A short written record helps. Under observation, list only what you saw: the permalink opened, the label shown, the search you ran. Under limit, say what the observation cannot establish, such as why a public post is missing from a particular index. Under decision, state the practical choice, for example treating the post as not search-findable and relying on the supplied link only. This keeps a gap in coverage from turning into a claim about intent, reach or the author's conduct.
- Use three columns or three short paragraphs, one each for observation, limit and decision
- Never fill the limit column with a guess; write unknown instead
- Date each entry so later readers know when the check was made
A hypothetical example
Suppose a hypothetical researcher receives a Mastodon permalink from its author as part of a public discussion. The permalink opens and the post is labeled Quiet public. The researcher searches for a distinctive phrase from the post and finds nothing. The correct reading is that the post was intentionally excluded from search features while remaining public, not that it was deleted or that the server failed. The researcher cites the permalink, notes that search does not surface it, and does not attempt to locate copies elsewhere or ask the author to change the setting. [Mastodon: per-post visibility and quiet public]
A couple more questions
The permalink opens but search finds nothing. Was the post deleted?
Not necessarily. If the post is labeled Quiet public, it is still public at its permalink and on the profile but is deliberately absent from search, live and explore features. A post that no longer opens is a different case; record it as unavailable rather than concluding why.
The account allows full-text discovery, so why is this one post missing from search?
Visibility is set per post. Quiet public excludes that individual post from search even when the account's other settings would otherwise permit discovery. The account-level setting and the post-level label are separate.
Can I use the permalink to view a followers-only or private-mention post?
No. Those posts carry separate permission restrictions, and a permalink does not override them. If a post is restricted or you cannot determine its status, record that limit and stop rather than seeking another route.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.