MediaWiki / knowledge-base search that isn’t Cirrus-only
Knowledge-base search for MediaWiki without going all-in on Cirrus/Elastic — Seekmodo’s content vertical approach.
CirrusSearch is powerful — and heavy. Many MediaWiki operators want relevance, typeahead, and fewer “I know this page exists” failures without owning another Elasticsearch footprint beside the wiki.
Seekmodo’s MediaWiki connector targets knowledge-base and documentation wikis with the same retrieval patterns we use for WordPress content search: better discovery for humans, optional cloud ranking, and MCP when agents need to query the same index.
How wiki search fails in practice
Internal wikis accumulate years of procedure pages, orphaned drafts, and similarly titled how-tos. Classic search returns either nothing (wrong capitalization, outdated page title) or a long list ranked by mysterious wiki defaults. Support teams learn to bookmark instead of search. New hires never find the canonical runbook.
Public-facing MediaWiki sites have the same problem with higher stakes: readers bounce to Google and land on a competitor’s mirror of your docs.
What Seekmodo changes
The MediaWiki extension pairs the wiki with a Seekmodo tenant, indexes readable pages, and serves improved search / typeahead experiences appropriate to the content vertical. Cloud plans add AI ranking, analytics, pinning, and synonyms so editorial teams can keep critical pages on top for known queries.
You are not required to run Cirrus’s full Elastic estate to get modern relevance — which is the point for lean ops teams.
Knowledge base vs commerce
Commerce search optimizes for SKUs and conversions. Knowledge-base search optimizes for the right article, section, or policy page. Seekmodo’s content vertical treats titles, redirects, and updated pages as first-class. MCP tools can expose the same index to support copilots so agents cite live wiki pages instead of stale exports.
Enhanced Native and cloud
As with other connectors, start with on-install improvements where applicable, then enable cloud when you want analytics and ranking depth. Fallback behavior keeps search available if the gateway is down. See what Enhanced Native means for the shared product philosophy.
When to keep Cirrus
Keep CirrusSearch when you already operate Elastic for wiki search at scale, depend on Cirrus-specific features, or cannot send page text to a managed SaaS index. Choose Seekmodo when MediaWiki is one property in a multi-CMS estate, you want search-volume pricing, or you need MCP for support agents without a custom Elastic query layer.
A simple acceptance test for wiki owners
Collect twenty “I know this page exists” queries from your team. Run them on stock MediaWiki search, then on Seekmodo after indexing completes. Success means the canonical page appears in the top results without requiring the exact current title string, and typeahead helps when titles are long or namespaced. Failures that remain are often permission or namespace exclusions — fix those in index rules before blaming ranking. Re-test after any large import of archived pages.
For public wikis, also check that noindexed or private namespaces stay out of the public tenant index.
Next step
Read /solutions/mediawiki-search-extension and /plugins/mediawiki. Polish notes for mediawiki.org live in our GTM pack; version bumps on-wiki happen only on real releases. Start a trial from /pricing when you are ready for cloud ranking.