You followed a hashtag in Mastodon expecting to see all new public posts with that tag in your home feed, but the timeline remains empty or shows only sporadic entries. This issue occurs because Mastodon’s hashtag follow feature relies on the instance’s full-text search index and federation timing, not on real-time streaming. This article explains the technical reasons behind the delay and provides specific fixes to ensure new posts appear reliably in your home feed.
The problem is not a bug in most cases. It is a design trade-off: Mastodon prioritizes server performance over instant hashtag delivery. The search index refreshes on a schedule, and federated posts from remote instances must arrive and be indexed before they qualify for your followed hashtag feed. Understanding this flow helps you apply the correct fix instead of waiting indefinitely.
Below you will learn how to verify your hashtag follow status, adjust instance search settings, and use alternative methods to capture missed posts. You will also discover related failure patterns and how to avoid them.
Key Takeaways: Fixing Hashtag Follow Delivery in Mastodon
- Home feed > Hashtag column: Verify the hashtag is actually followed by checking the purple star icon on the hashtag page.
- Preferences > Search > Full-text search: Enable full-text search on your instance to improve hashtag indexing speed and coverage.
- Federated timeline > Hashtag search: Use the hashtag search on the Federated timeline to manually find posts that the follow feature may have missed.
Why Hashtag Follow Delivery Is Delayed or Missing
When you follow a hashtag, Mastodon does not create a live filter on all incoming posts. Instead, the server periodically queries its search index for posts containing that hashtag and inserts them into your home feed. This index is built from posts that the instance has already fetched and stored. If a post from a remote instance has not yet been federated to your instance, or if it was federated but not indexed, it will not appear in your followed hashtag feed.
Search Index Refresh Interval
Mastodon instances refresh their full-text search index at different intervals. Small instances may refresh every few minutes, while larger ones may delay up to 30 minutes. During peak hours, the index can fall further behind. If you follow a hashtag and immediately expect new posts, you may see nothing for several minutes even if posts exist on other instances.
Federation Timing and Post Visibility
A post created on a remote instance must first be delivered to your instance via the federation protocol. This delivery is not instantaneous. It depends on the remote server’s load, connection speed, and the number of followers you share with the author. If the post’s author has no mutual followers on your instance, the post may never reach your instance at all. In that case, the hashtag follow will never show that post.
Instance Search Settings
Some Mastodon instances disable full-text search to reduce server load. When full-text search is off, the hashtag follow feature relies on a simpler, slower index that only covers public posts from the local database. Remote posts are excluded entirely. This is the most common cause of an empty hashtag feed on instances that otherwise appear healthy.
Steps to Restore Hashtag Post Visibility in Your Feed
- Confirm the hashtag is followed
Go to the hashtag page by searching for it in the search box. Look for a purple star icon next to the hashtag name. If the star is gray, click it to follow the hashtag. If the star is purple but posts still do not appear, proceed to the next step. - Check your instance’s search setting
Open Preferences > Search. Ensure the option Allow full-text search is enabled. If it is disabled, enable it and click Save Changes. This setting is controlled by your instance admin. If you cannot change it, contact your admin and ask them to enable full-text search in the server configuration. - Wait for the search index to refresh
After enabling full-text search, wait at least 15 minutes. The index rebuilds automatically. During this period, existing posts that match the hashtag may appear in batches. Do not expect instant results. - Manually test with a new post
Create a new public post containing the followed hashtag. Check your home feed after 5 minutes. If your own post appears, the feature is working. If it does not appear, the issue is on your instance’s side, not the remote federation. - Use the hashtag search as a fallback
Open the Federated timeline, then click the search icon and type the hashtag. This shows all posts containing the tag that your instance has stored, regardless of your follow status. Compare this list with your home feed to see how many posts the follow feature missed. - Switch to a list as an alternative
Create a new list in Lists > Create list. Add accounts that frequently post about the topic. Lists show every post from those accounts in real time, bypassing the hashtag index delay. This method requires you to manually curate the list but gives immediate results.
If the Problem Persists After the Main Fix
Hashtag Follow Shows Posts From Hours Ago but Not Recent Ones
This indicates the search index is working but is delayed. The index may be rebuilding or the instance may be under load. Wait 30 minutes and check again. If the delay continues, ask your instance admin to check the Sidekiq queue for search index jobs. A backlog in Sidekiq can delay indexing indefinitely.
Posts From a Specific Remote Instance Never Appear
The remote instance may be defederated from your instance, or it may have privacy settings that prevent public posts from being indexed. Check the remote instance’s status by visiting a post from that instance directly. If you can view the post but it does not appear in your hashtag feed, the remote instance likely blocks search indexing. There is no fix on your side. You can follow the account directly instead.
Hashtag Follow Stops Working After an Instance Upgrade
Mastodon version upgrades sometimes change how the search index is built. After an upgrade, the index may need to be rebuilt manually. Contact your instance admin and ask them to run tootctl search deploy on the server command line. This command rebuilds the full-text search index from scratch and usually resolves the issue within 10 minutes.
Hashtag Follow vs List: Which Gives Faster Results
| Item | Hashtag Follow | List |
|---|---|---|
| Update speed | Delayed by search index refresh | Real-time from followed accounts |
| Setup effort | One click per hashtag | Manual account selection per list |
| Post coverage | All public posts with the tag | Only posts from selected accounts |
| Dependency | Full-text search enabled on instance | No special server setting required |
| Best for | Broad topic monitoring with tolerance for delay | Tracking specific known contributors |
You now know why hashtag follow can appear broken and how to fix it. Start by confirming the hashtag is followed and that full-text search is enabled on your instance. If the issue persists, use the Federated timeline search to verify that posts exist and consider using a list for real-time monitoring. For advanced control, ask your instance admin to rebuild the search index with tootctl search deploy after an upgrade.