The Search Block is a standalone search bar you add to any page through the Page Builder. It is not built into the Content Grid — it is its own separate block that you place on the page.

The Search Block comes in three visual variants:

You can also configure whether the sort dropdown is visible and set custom placeholder text to guide your members (e.g., "Search recipes by name, ingredient, or tag...").

This is one of the most important concepts to understand: the Search Block does not display results itself. Instead, Content Grid blocks on the same page react to whatever the member searches for.

Here's how it works:

Each Content Grid block has a Search Behavior setting that controls how it responds:

If your page has Content Grids showing different content types (for example, one grid for recipes and another for meal plans), the Search Block automatically detects this and shows a content type dropdown. Members can choose to search "All" content types or narrow it to a specific type like "Recipes" or "Meal Plans."

When a specific type is selected, only the matching Content Grid responds to the search — the others either hide or remain unchanged, depending on their Search Behavior setting.

Members can search across all your content types:

A search query must be at least 3 characters to trigger results.

For recipes, the search looks at multiple fields to find the best matches:

Results are ranked by relevance. An exact match in the title scores highest, followed by word-boundary matches, prefix matches, and then partial matches. This means if a member searches for "chicken," a recipe titled "Chicken Parmesan" will rank above one titled "Artichoke and Chicken Bake."

Power users can take advantage of advanced search syntax:

If your members have set dietary preferences or disliked ingredients in their profiles, search results are automatically adjusted. Recipes matching a member's dietary preferences get a relevance boost, while recipes containing disliked ingredients are ranked lower.

Members can sort results using these options:

When a member performs a search, results default to relevance ranking — the best matches appear first. However, members can override this by selecting any sort option from the dropdown.

The sort dropdown appears in both the Search Block and in individual Content Grid blocks. Sort selections are saved in the URL, so if a member shares a link, the recipient sees the same sort order.

When the search is focused on recipes (either because recipes are the only content type on the page, or the member selected "Recipes" from the dropdown), the Search Block reveals advanced filter options. These powerful filters help members narrow down recipes to find exactly what they need.

Members can search for recipes that include or exclude specific ingredients:

Members can filter by tags (e.g., "Vegan," "Gluten-Free," "Quick Dinner"):

Filter recipes by difficulty level:

Set minimum and maximum ranges for:

Filter by the number of servings, with adjustable minimum and maximum values.

Members can filter recipes by nutritional content, setting minimum and/or maximum values for:

Filter presets are one-tap filter chips that appear near the search bar, giving members instant access to common filter combinations without having to open the advanced filters.

Your app comes with default presets organized into three categories:

Nutrition Presets:

Time Presets:

Servings Presets:

You can fully customize these presets:

Each preset belongs to a category (nutrition, time, or servings) and has a display label that members see as a clickable chip.

Content Grid blocks can have base tags configured in their settings. Base tags are always applied as a permanent filter — they define what content the grid shows regardless of any search.

For example, you might create a Content Grid with the base tag "Vegetarian" to build a dedicated Vegetarian Recipes section on your page. When a member uses the Search Block while viewing this section, the search operates within the vegetarian subset only. A search for "pasta" would only show vegetarian pasta recipes, not all pasta recipes in your app.

This is a powerful way to create focused content sections where search respects the section boundaries. You could build:

If your app uses category pages, the Search Block behaves intelligently when placed on one. It automatically scopes the search to the current category:

This means members browsing your "Breakfast" category page can search within it without accidentally pulling in dinner recipes.

Every search parameter — the query, filters, sort order, and content type — is saved in the page URL. This has two major benefits: