OneSearch is a OnePress ecosystem plugin that enables cross-site, brand-aware search across a multi-brand WordPress network. It powers unified discovery across sites, powered by Algolia.
Managing content across multiple brands, regions, or business units often results in disconnected search experiences. This can lead to broken user journeys and lost discovery opportunities.
OneSearch solves this by enabling a federated search layer that bridges multiple sites, powered by Algolia delivering a consistent and brand-respecting experience across the network.
- Unified Search Layer: Execute a single search query across multiple connected sites.
- Brand Awareness: Show source brand site and redirect user to the respective site.
- Governance & Control: Control visibility and indexing scope at the site or post-type level.
- Developer Extensibility: Filters let you adjust the indexed record data, index settings and search parameters.
- Modular Design: Extend and customize indexing and search behavior without core overrides.
See the Setup Guide for detailed installation and configuration instructions.
Yes. For each brand site, you can select which built-in and custom post types to index from the Indices and Search settings.
No. Posts are automatically indexed when they are published, and removed when they are deleted or otherwise unpublished (e.g. trashed, changed to draft, etc.).
Yes. Any updates made to a post are automatically synced with the Algolia index.
Search results are ranked by Algolia's relevance algorithm. However, OneSearch boosts results from the current site you're searching on, ensuring more relevant local content appears first. You can further customize ranking and relevance through Algolia's dashboard.
OneSearch is under active development and maintained by rtCamp.
Contributions are welcome and encouraged!
You can join the development and discussions on GitHub. Feel free to report issues, suggest features, or contribute code.
To learn more about contributing to OneSearch, please read the Contributing Guide.
For development guidelines, please refer to our Development Guide.
