FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

Real site search on Webflow with Algolia

When Webflow's built-in site search is enough, when to add Algolia, and how to set it up: the app or custom code, what to index and how to test it.

By Abdul QuadirUpdated 2026-11-066 min read
TL;DR
  • Webflow's built-in search suits a small site where people only need a plain list of matches.
  • Add Algolia when you need filters, typo tolerance, control over results or more than 60 results.
  • The Algolia Search and Sync app connects CMS collections to your own Algolia account without custom code.
  • Custom code with InstantSearch gives full control, but you own the sync and the upkeep.
  • Index only public data, because a search key in the browser can be used by anyone.

The short answer

To add real site search to Webflow, sync your CMS collections to an Algolia index and put a search interface on the page. The quickest route is the Algolia Search and Sync app from the Webflow Marketplace. The most flexible route is custom code with Algolia's open source InstantSearch library.

You only need any of this if Webflow's built-in search falls short. For a small marketing site, it often does not.

Where built-in search stops

Webflow's own site search takes little setup and is easy to style. It needs a Premium Site plan, a legacy CMS Site plan or above. Its limits, from Webflow's help pages, are the reason to look further:

  • It shows up to 60 results, with no pagination across result pages.
  • A site gets one search engine, so every search box covers the same content.
  • You cannot exclude a single Collection item from search.
  • Publishing a single CMS item does not trigger automatic reindexing. That takes a full-site publish.
  • Content behind a User Account is not indexed.
  • Results come from the current locale. If the content does not exist there, the visitor sees no matching results.
  • Indexing can take up to 24 hours on large sites.

A decision rule

First check that people search at all. Webflow can pass search terms to Google Analytics once it is set up, so read the data before you buy anything. Then:

Your situationUse
A small site, few searches, plain matches are fineBuilt-in search
A blog or resource library where people need to filter by topic or typeAlgolia app
A big catalogue, or searches with typos that return nothingAlgolia app
Results that mix collections with their own layoutsAlgolia app, then custom code if it falls short
Results that need your own logic, or data from outside WebflowCustom code

If no row fits, better navigation may help more than search. A clear CMS structure and category pages solve a lot.

Route 1: the Search and Sync app

The app connects CMS collections to your own Algolia account. It is published by Candid Leap, a third party. Webflow reviewed the listing but does not endorse or certify it, so read the permissions on its listing before you install.

  1. Create an Algolia account and copy your App ID and API key.
  2. Install the app on your Webflow site and enter those details.
  3. Pick a collection and map its fields to an index.
  4. Run the first sync.
  5. From then on, the listing says publishing a CMS change re-syncs through webhooks, and a scheduled job keeps the index in step as well.
  6. Add search components on the canvas (search box, results, filters, pagination), or attach Algolia behaviour to your own elements with attributes.

Our Algolia integration page has more, and the search tools page lists other options.

Route 2: custom code

Here a small service listens for Webflow webhooks and writes changed items to Algolia, and InstantSearch builds the interface from ready-made widgets. Webflow Cloud is one place to host that service.

You gain full control over records, ranking and layout. You also take on the upkeep: failed syncs, deleted items and API changes are now yours to catch. Pick this only if the app cannot do what you need, and name who will maintain it. A search index that slowly drifts away from the site is hard to notice, because nothing looks broken. Old pages just keep showing up, and new ones never do. Add a simple alert for failed syncs on day one.

What to put in the index

Good search depends more on the records than the widget. For each collection, decide:

  • Searchable fields. Title, summary and key text. Put title first, because a match there usually matters most.
  • Filter fields. Category, type, author. Clean these before you sync. Two spellings of a tag become two filters.
  • Display fields. URL, image and a short excerpt.
  • Long text. Algolia limits record size by plan. Send a summary rather than a whole long article, or split it. Check Algolia's current limits.

One gap to plan for: the app works from CMS collections, so static pages such as pricing will not appear by themselves. A small collection of search entries that link to those pages is one simple fix.

Keys and privacy

Algolia says a search-only API key is safe in production front-end code. It also warns that anyone can see that key, and could scrape your index or flood it with requests. So:

  • Index only data you are happy to make public. No gated content, member data or private fields.
  • Keep the Admin API key confidential, and out of any page code.
  • Use a restricted search key if you need tighter limits. Algolia's docs explain how.

How to test it before launch

  1. Search your top ten terms from analytics and check the first result of each.
  2. Misspell a few. Algolia's docs say typo tolerance handles up to two typos per word, so see that it behaves on your own terms and brand names.
  3. Search for something you do not have. The empty state should offer a next step.
  4. Publish a new CMS item and an edit, and confirm both reach the index.
  5. Unpublish an item and confirm it leaves the results.
  6. Use the search with a keyboard only, and on a phone.
  7. Run a speed check, as a search script adds weight. Load it only where it is used. See how we approach Webflow speed.

On a site with more than one language, read the app's current docs on locales before you commit. A search box that returns the wrong language is worse than a plain one.

What to do next

Look at your site search data first. If people are searching and failing, try the app on one collection, such as your blog, and test it with real queries before adding more. If you want it set up for you, see Webflow development or tell us what you need.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Yes, on a Premium Site plan, a legacy CMS Site plan or above. It shows up to 60 results with no pagination, and you cannot exclude single Collection items.

Yes. The Algolia Search and Sync app on the Webflow Marketplace syncs CMS collections and adds search components to the canvas. You need your own Algolia account.

Candid Leap publishes it. The listing says Webflow reviewed it but does not endorse or certify it.

The listing says publishing a CMS change re-syncs through webhooks, and a scheduled job runs as well. Test it on your own site with a new item and an edit.

A search-only key is meant for front-end code, but anyone can see it. Index only public data, and keep the Admin API key confidential.

When the site is small, few people search, and a plain list of matches is fine. Check your analytics before adding a tool.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.