Findberry

Webflow's native Site search needs a Premium Site plan or above. It shows up to 60 results with no pagination, and sites on the Starter or Basic Site plan see sample results only. Findberry is a hosted search engine you add by pasting HTML, so it runs on any site that can use custom code.

Connecting Findberry and Webflow puts a search box on any page through a Code Embed element. You can also load Findberry's script on every page through head and body code. Findberry builds its index by crawling your published site and documents nothing Webflow-specific, so pages generated from the Webflow CMS are crawled like any other published page, up to your Findberry plan's page cap. Search results carry no ads on any plan, the free one included.

Findberry describes its audience as web developers and website owners. On Webflow, that fits knowledge bases, documentation sites, product catalogs and publishing sites. It also fits a site on the Basic Site plan that wants working search, since native Site search shows sample results only on that plan.

How to integrate Findberry with Webflow

What is Findberry? Findberry is a cloud-based internal site search service from Blumentals Solutions SIA, a small software company based in Latvia. After signup it shows personalized HTML for your site and starts crawling your website in the background. You can restyle the results with your own HTML template and CSS.

Two methods connect Findberry to Webflow. Code Embed or site-wide custom code covers the whole install, because Findberry needs only HTML on your page. Webflow webhooks and the Data API are optional and are your own build: Findberry documents no API, so a webhook can alert your team after a publish but can't make Findberry re-index.

Findberry's features and pricing table lists five plans, from Free to Ultra, and shows which options each plan includes:

• Page caps: Each plan caps the number of indexed pages, from 50 on Free to 6,000 on Ultra, and every plan allows unlimited search queries.
• Re-indexing: Every plan includes automatic and on-demand indexing, with a monthly re-index limit of 5 on Free, 10 on Basic and 20 on Pro, and no limit on Max or Ultra.
• Design and branding: All plans include a fully customizable design, and Basic and above also remove Findberry's branding from results.
• Search controls: Search stats and page filtering start on Basic, while multiple domains or sub-locations and customizable keyword weights start on Pro.

Paid plans can be tested for 10 days before the first monthly payment, according to the same table.

Add Findberry with a Code Embed or site-wide custom code

A Code Embed element places the Findberry search box on a page or a Collection page template. Findberry's setup overview says setup needs no script programming or API work, only HTML and optional CSS. To use custom code, you need a Core, Growth, Agency or Freelancer Workspace, or an active Site plan.

Place the search box on a page

Use this path when the search box belongs in one spot, such as a header or a help center landing page. On a Collection page template, the embed appears on every page generated from it.

To add the embed:

1. Sign up at findberry.com and copy the personalized HTML that appears after signup.
2. In Webflow, open the Add panel and add a Code Embed element to the canvas.
3. Paste the HTML into the embed, then save and close the modal.
4. Click Publish.

Custom code renders in preview, but its effects go live only after you publish, and it won't run in expand canvas view. Turn the Code Embed into a component to reuse the same search box across pages.

Load the script from site or page custom code

If Findberry's HTML includes a separate script, you can load it on every page from Site settings, before the closing body tag. Keep the visible search box in a Code Embed where it should appear.

To add the script site-wide:

1. Go to Site settings > Custom code.
2. Paste the script into the Footer code field and click Save changes.
3. Click Publish.

The script now loads on every published page.

To add the script to one page:

1. In the Pages panel, hover the page and click the Page settings icon.
2. Under Custom code, paste the script into the Before </body> tag field and click Save.
3. Click Publish.

Each custom code field holds 50,000 characters, and page-level code loads after site-wide code. If results don't display, check embed placement and look for JavaScript conflicts. Since August 2020, newly published Webflow sites include jQuery v3.5.1, so importing another jQuery version can cause unexpected behavior. On localized sites, secondary locales inherit the primary locale's page-level code until you edit a field, and Reset to primary re-syncs it.

The search box depends on Findberry's hosted service staying active. Findberry's support FAQ says that if a payment fails and stays unpaid for 20 days, the service stops and visitors see a message that search has been turned off. If you cancel, remove the embed so a dead search box doesn't stay on your published pages.

Alert your team after publishes with webhooks

This method is a build you write and host yourself. Findberry documents no public API or webhook intake, and its setup overview describes setup without one, so a Webflow webhook can't trigger a Findberry re-index. A webhook can tell your server when the published site changes, so your team knows when to run an on-demand re-index in Findberry. Findberry doesn't document whether on-demand re-indexes count toward the monthly re-index limit. Budget for a developer and a server that can receive signed POST requests.

The Webflow Data API at https://api.webflow.com/v2 can also size your index before you pick a plan. List pages with GET /v2/sites/{site_id}/pages (List Pages) and count published CMS items with GET /v2/collections/{collection_id}/items/live (List Live Items), then compare the total to your Findberry page cap. Every request carries an Authorization: Bearer <token> header, and each endpoint names the scopes it needs.

Detect publishes that may need an index review

A site_publish webhook fires when you publish the whole site or a single page. Pair it with collection_item_published if editors publish single CMS items without a site publish.

To register and handle the webhook:

1. Use a token with the sites:write scope to create the webhook, plus sites:read to receive site_publish events. Check the scopes reference for the scope each collection item event needs.
2. POST /v2/sites/{site_id}/webhooks with the triggerType and your endpoint URL, per the create webhook reference.
3. On each delivery, compute an HMAC SHA-256 of timestamp + ":" + JSON.stringify(request_body). Sign with the webhook's own secretKey if you created it with a site token, or with your OAuth app's client secret if an app created it. Compare the result to x-webflow-signature, and reject any x-webflow-timestamp more than 300,000 ms old.
4. Return 200, then alert your team to run an on-demand re-index in Findberry.

A site_publish delivery looks like this:

{
  "triggerType": "site_publish",
  "payload": {
    "siteId": "62749158efef318abc8d5a0f",
    "publishedOn": "2023-07-31T12:34:56.789Z",
    "domains": ["my-website.webflow.io"],
    "publishedBy": { "displayName": "Some One" }
  }
}

The site publish event payload can also carry publishScope (page or site) and pageId, which tell you whether only one page changed. A non-200 response gets retried up to three more times at 10-minute intervals, per the webhooks guide. List registrations with GET /v2/sites/{site_id}/webhooks and remove one with DELETE /v2/webhooks/{webhook_id}, which returns 204.

What you can build with Findberry and Webflow

Findberry suits sites that need search without writing search code, and its plan options decide what each build can do:

• Product catalog search: Customizable keyword weights, on Pro and above, let product terms rank higher in the shop's search box. Results appear on a page styled with the shop's own HTML template and CSS.
• Help center search: A documentation site with hundreds of CMS articles puts the search box on its Collection page template. Pro's 1,000-page cap covers an archive of that size.
• Agency portfolio search: One search covers the agency's main site and a case-study archive in a sub-location, using the multiple domains option on Pro and above.
• Publishing archive search: A media site indexes its article and podcast pages together. Search stats, from Basic up, show which queries return nothing, so editors see what visitors can't find.

If your index outgrows Findberry's 6,000-page top tier, build full-text search with Elasticsearch instead.