Fediscovery and Mastodon Search: Building Better Fediverse Search Engines

Finding content on the fediverse has been one of its most persistent challenges. Unlike centralized platforms with global search indexes, the fediverse’s distributed architecture makes comprehensive search technically difficult and politically contentious. Fediscovery and related projects are building solutions. This guide explains how fediverse search works today and where it is heading.

What You’ll Know by the End

  • Why fediverse search is fundamentally different from centralized platform search
  • How Fediscovery’s approach works and what it offers
  • The privacy and consent considerations that shape search design
  • Alternative search and discovery methods that work today
  • How to make your own content more discoverable

Why Fediverse Search Is Different

On Twitter/X or Bluesky, search queries hit a single global index. Every public post is searchable. On the fediverse, there is no single index. Each Mastodon instance has its own database, and that database only contains content the instance has seen through federation.

This means:

  • Searching on your instance only searches what your instance knows about: If no one on your server follows someone on a remote server, that remote content is invisible to your search.
  • Full-text search is opt-in: Mastodon made full-text search opt-in per user, respecting the community norm that not all content should be indexed.
  • Hashtags remain the most reliable discovery mechanism: Because hashtags are explicitly public and federate well, they work better than free-text search for finding content.

How Fediscovery Works

Fediscovery is a project that aims to build opt-in, privacy-respecting search infrastructure for the fediverse.

Core Principles

Opt-in indexing: Users must explicitly allow their posts to be indexed by Fediscovery. This respects the fediverse community’s strong feelings about consent and searchability.

Decentralized infrastructure: Rather than building one central search engine, Fediscovery aims for a federated search model where multiple providers can participate.

Standards-based: Fediscovery builds on existing ActivityPub conventions and proposes extensions that any implementation can adopt.

What It Enables

  • Cross-instance search for opted-in content
  • People discovery across the federated network
  • Hashtag aggregation that goes beyond what a single instance sees
  • Potential integration with Mastodon’s built-in search UI

Current Status

Fediscovery is in active development. Some instances have begun testing integration. The rollout is gradual, and effectiveness depends on how many users and instances opt in.

Alternative Discovery Methods

While Fediscovery develops, several other approaches to fediverse discovery are available:

Hashtag Follows

Many Mastodon clients and instances support following hashtags directly. This creates a feed of all posts using that hashtag that your instance sees. It is the most effective current discovery tool for topic-based content.

Mastodon instances track trending hashtags, links, and posts. These are moderated by instance admins and provide a curated view of what is popular on the network.

Relay Servers

Relays are services that share content between instances. An instance subscribed to a relay sees all public content from other subscribing instances, improving the federated timeline and search results.

Directories

Mastodon’s profile directory (available on many instances) lets users opt into being listed, making their accounts discoverable by topic and activity level.

Third-Party Tools

Several community tools aggregate fediverse content for discovery purposes. Check our tools guide for current options.

Search and discovery inherently create tension with privacy:

  • Users who want to be found benefit from comprehensive search
  • Users who value contextual integrity may not want their posts surfaced in contexts they did not intend
  • The fediverse community has historically prioritized consent over discoverability

This tension is why Mastodon’s search has been conservative compared to centralized platforms. Fediscovery’s opt-in approach tries to thread this needle by giving users explicit control.

Practical Guidelines

  • Enable the “discoverable” flag on your profile if you want to be found
  • Opt into search indexing if your instance and client support it
  • Use hashtags generously on posts you want others to find
  • Understand that unlisted and followers-only posts should never be indexed

Making Your Content Discoverable

Regardless of how search evolves, you can take steps to improve your discoverability today:

  1. Use relevant hashtags: They are the primary discovery mechanism and will remain important even as search improves
  2. Set your profile to discoverable: This opts you into instance directories and search features
  3. Write a detailed bio with keywords: People searching for your topics should find relevant terms in your profile
  4. Post publicly when you want reach: Only public posts can be indexed or appear in federated timelines
  5. Engage with hashtag communities: Consistent participation in topic hashtags builds your visibility over time

Impact on Timeline Experience

Better search and discovery directly impact your timeline experience. When you can find more relevant accounts to follow, your home timeline improves. When your instance has better federated data (through relays or search integration), your federated timeline becomes more useful.

Common Mistakes

  • Expecting Google-like instant results: Fediverse search is evolving and will remain more limited than centralized search for the foreseeable future
  • Not using hashtags because “search should work”: Hashtags are essential today and will complement, not be replaced by, full-text search
  • Assuming all content is searchable: Only opted-in, public content is indexed by opt-in search services
  • Ignoring the discoverable profile flag: This is a simple step that significantly improves your visibility
  • Conflating search with surveillance: Opt-in search respects consent while improving discoverability

Frequently Asked Questions

Does Fediscovery index private posts? No. Fediscovery only indexes public posts from users who have opted in to search indexing. Private, followers-only, and unlisted posts are never included.

Can I opt out of Fediscovery? Yes. Indexing is opt-in by default. If your instance integrates with Fediscovery, you control your participation through your account settings.

Will search replace hashtags? Hashtags will remain valuable even with improved search. They provide explicit categorization that complements free-text search. Both tools work best together.

How does this affect my instance’s resources? Integrating with search infrastructure adds some resource overhead. Instance admins can evaluate this based on their server capacity and community needs. See our developer notes for technical considerations.

Is there a search API for developers? Mastodon’s API includes search endpoints. Fediscovery aims to extend this with cross-instance capabilities. Developers should check current API documentation for available endpoints.

When will cross-instance search be widely available? Adoption depends on instance admin decisions and user opt-in rates. Gradual rollout is expected throughout 2026 and beyond. Follow our articles hub for updates.