Develop With Faith
May 29, 2026

Site Search for Sermon Libraries: Algolia vs Pagefind vs Built-In

A church with ten years of weekly sermons has a search problem most ministries do not realize they have. The archive contains an enormous amount of teaching, and the default WordPress search returns three barely-relevant results when someone types "anxiety" into the box.

We get asked which search tool is right for sermon libraries often enough that an honest comparison is overdue. The short version is that the right answer depends on three things: how many sermons you have, what platform you are on, and how often the search actually gets used.

What Makes Sermon Search Harder Than Blog Search

Sermons are unusual content. Each one is long, often 30 to 60 minutes of speech transcribed into 5,000 to 10,000 words. They cover overlapping themes, reference scripture frequently, and are usually most valuable when someone can find a specific topic across years of content.

A default search needs to handle several things at once. Full-text indexing of long documents. Relevance ranking that surfaces the right sermon rather than just the most recent one. Filtering by speaker, series, scripture reference, and date. Decent typo tolerance, because visitors search for "ecclesiastes" with three different spellings.

Most generic search tools do one or two of these well and fail at the rest. The three options below each handle the problem differently.

Pagefind: Free Static-Site Search That Actually Works

Pagefind is a relatively new open-source search tool built for static sites. It runs as a build step, generates a small JavaScript index, and provides search that runs entirely in the visitor's browser. No server, no API costs, no monthly fee.

For a sermon library of up to a few thousand entries on a static site (Astro, Eleventy, Hugo, Next.js with static export), Pagefind is genuinely excellent. Setup is a single command added to your build process. The index for 500 sermons typically lands around 2 MB, downloaded incrementally only when someone uses the search.

npx pagefind --site dist

The search UI is a 7 KB JavaScript component you drop into the page. It handles full-text matching, typo tolerance, and basic filters out of the box. We have built sermon archives with Pagefind that outperform WordPress search on every dimension while costing nothing per month.

The honest limitation is that Pagefind only works on static sites. If your sermon archive is in WordPress, Pagefind is not the right tool. The other limitation is scale — at 10,000+ entries, the index size starts to matter. For most ministry archives, this is not a real constraint.

Algolia: Worth the Money at the Right Scale

Algolia is a hosted search service with industry-leading relevance, instant results, and excellent typo tolerance. It powers search on a huge percentage of e-commerce and documentation sites. For sermon libraries, it is the gold standard.

The catch is the pricing. Algolia's free tier covers up to 10,000 records and 10,000 monthly searches. Past that, it moves to a paid plan that typically runs $50 to $200 a month for ministry-scale usage. Algolia also offers nonprofit discounts on request, but the discount varies.

What you get for the cost is search that feels alive. Results update as the visitor types, ranking is genuinely good, and the API supports faceted filtering across speaker, series, date, and tags without writing custom code. For ministries where the sermon archive is a primary entry point — visitors searching for help with grief, marriage, doubt, vocation — that quality difference is real.

We recommend Algolia when the sermon archive is a major traffic source, when the search is used hundreds of times a month, and when the ministry can absorb $50 to $100 in monthly cost as a stewardship investment in being findable.

Setup involves running an indexer (we usually write this as a small Node script that pulls from the CMS), wiring up the React or vanilla JS InstantSearch component, and configuring relevance settings. Allow a day of development for a polished implementation.

Built-In Search: When It Is Fine

WordPress search has a bad reputation and partially deserves it. The default search ranks by date, ignores relevance, and returns results that often miss obvious matches. But the situation has improved.

Plugins like SearchWP and Relevanssi turn WordPress search into something genuinely usable. SearchWP costs $99 a year, indexes custom fields and taxonomies, and handles relevance ranking properly. Relevanssi has a solid free tier and a paid version around $100 a year.

For sermon archives under a few hundred entries on WordPress, SearchWP plus a few hours of configuration delivers search that is good enough. Not as instant or polished as Algolia, but workable. The advantage over Algolia is that everything stays inside WordPress — no external service, no separate indexing job, no API costs.

The built-in search of other platforms varies. Squarespace and Wix have basic search that is acceptable for small sites and frustrating at scale. Ghost has decent built-in search. Webflow search requires either a plugin or external integration.

A Decision Framework

Three questions get you to the right answer.

What platform is your site on? Static site (Astro, Eleventy, Next.js, Hugo) means Pagefind is the obvious first choice. WordPress means SearchWP for most cases, Algolia if the archive is a major focus. Other platforms point you toward Algolia or platform-specific tools.

How many sermons, and how active is the archive? Under 300 sermons with light traffic — a built-in or static-site tool is fine. Over 1,000 sermons or significant traffic — invest in Algolia.

How important is the archive to ministry impact? If sermon search is a primary way new visitors find your community, treat it as core infrastructure. If it is a nice-to-have for existing members, a good-enough tool is genuinely good enough.

A Note on Transcripts and Findability

Whatever search tool you pick, the quality of the content being searched matters more than the search engine. A sermon archive with only titles and dates is unfindable no matter how good the search. An archive with full transcripts, scripture references, and clear topic tags is findable even with mediocre search.

If your archive does not have transcripts, that is the first investment to make. Services like Otter, Rev, and Whisper-based open-source tools generate clean transcripts for around 25 cents a minute. Once that text exists, every search tool above performs dramatically better, and the same transcripts double as accessible text for hearing-impaired visitors and SEO content for search engines.

Sermons are some of the most useful content a ministry produces. Making them findable years after delivery is one of the quieter ways a website serves the community. If you are weighing search options for your archive and want help choosing, reach out through our contact page.

← Back to all posts