When you use hashtags in Threads, the post count shown next to a tag often does not match the number you expect. This mismatch happens because Threads now federates content with ActivityPub, the protocol that connects Threads to Mastodon and other services. Posts from external servers are counted differently than native Threads posts. This article explains why the numbers differ and what you can do to get accurate counts.
Key Takeaways: Threads Hashtag Federation and Count Discrepancies
- ActivityPub federation: Posts from Mastodon and other servers appear in Threads hashtag feeds but may not update the local count immediately or at all.
- Indexing delay: Federated content can take hours or days to be indexed by Threads search, leading to lower visible counts than actual activity.
- Private vs public posts: Only public posts from federated servers are included in Threads hashtag counts; followers-only or unlisted posts are excluded.
Why Threads Hashtag Counts Do Not Match Actual Posts
Threads uses hashtags as a way to group conversations. When you tap a hashtag, you see a feed of posts that include that tag. The number displayed next to the tag is the total count of posts that Threads has indexed. However, Threads does not index every post from every federated server in real time.
The mismatch has three main causes:
Federated Content Indexing Lag
Threads receives posts from Mastodon, Pixelfed, and other ActivityPub servers through federation. These posts are not instantly added to Threads search index. The indexing process can take several hours or longer. During that window, the hashtag count shows only native Threads posts and previously indexed federated posts. New posts from external servers are invisible to the count until the next index update.
Visibility Rules Exclude Some Posts
Threads only counts public posts in its hashtag feeds. Posts from federated servers that are set to followers-only, unlisted, or direct messages are not included. If a popular hashtag has many private or unlisted posts on Mastodon, those never appear in the Threads count. The number you see is limited to public posts that Threads has managed to retrieve and index.
Duplicate or Deleted Posts
A single post from a federated server may be counted multiple times if it appears in different server caches before being deduplicated. Conversely, deleted posts from external servers may not be removed from the count immediately. This can inflate or deflate the number temporarily.
Steps to Check and Understand Hashtag Counts in Threads
- Open the hashtag feed
Tap any hashtag in a Threads post or search for it using the search bar. The feed shows recent posts and the total count at the top of the screen. - Compare the count with the visible posts
Scroll through the feed. Count the posts you see. If the number shown is much larger than the posts in the feed, it likely includes federated content that is not fully loaded. - Check the same hashtag on Mastodon
Open the same hashtag on a Mastodon server, such as mastodon.social. Compare the total number of public posts. The Mastodon count is usually higher because it includes all federated posts without Threads indexing delays. - Wait 24 hours and recheck
Indexing often completes within one day. If the count still mismatches, the discrepancy is likely due to visibility rules or permanent exclusion of certain post types. - Use a third-party search tool for accuracy
Services like FediDB or Mastodon search APIs can show the true post count for a hashtag across the fediverse. This confirms whether Threads is undercounting or overcounting.
Common Issues with Threads Hashtag Counts
Threads hashtag count shows zero but posts appear in the feed
This happens when the hashtag is new or has not been indexed yet. The feed may still show posts because they are loaded from a real-time cache, but the aggregated count has not been updated. Wait a few hours and the count should appear.
Threads hashtag count is higher than the number of posts I see
The count includes posts from federated servers that are not displayed in your local feed due to server moderation or block rules. If a Mastodon server is blocked by Threads, its posts are excluded from the feed but may still be counted until the index is refreshed.
Threads hashtag count never updates after I post
Your post may not be public. Check your Threads profile settings. Only public posts are indexed for hashtag counts. If your account is set to private, your posts are excluded from the count entirely.
Threads vs Mastodon: Hashtag Count Behavior Compared
| Item | Threads | Mastodon |
|---|---|---|
| Indexing speed | Up to 24 hours for federated posts | Near real-time for local and federated posts |
| Post visibility included | Only public posts | Public and unlisted posts (configurable) |
| Deduplication | Inconsistent across server caches | Handled per server instance |
| Deleted post removal | Delayed by up to 48 hours | Removed within minutes |
| Third-party accuracy | Low for federated content | High when using Mastodon API |
You can now identify why Threads hashtag counts appear mismatched. The main factors are indexing delays, visibility rules, and deduplication inconsistencies. To get the most accurate count, check the hashtag on Mastodon directly or use a fediverse search tool. For your own posts, ensure they are public and allow time for indexing. If you rely on hashtag analytics for marketing, consider cross-referencing Threads data with Mastodon search results.