Ingredient-Based Search for Recipe Sites

We've added a cool new feature for Recipe sites: the ability to search for posts based on the ingredients in the recipe.

Suppose you are looking for something to do with the leftover broccoli and green onions you have in the fridge. Here's an example of our current, standard search for "broccoli, green onion".

broccoli_green_onion

That's not too bad. It found lots of posts that use those words.

But now let's see what it looks like when you do that same search using an ingredient search:

 
broccoli_green_onion_ingredients-1

It found the five recipes that include those ingredients, shows their full ingredient list, highlighting the matches. Pretty neat!

For this to work, we depend on the ingredient list declared in the LD_JSON on your page using the Recipe schema. This is the same way you communicate your Recipe to Google. We currently only support this feature for sites in English. If you have a multi-language site, we only support it on the English section of your site.

To start an ingredient search on a supported recipe site, you'll find a new "Ingredients" button at the top of the search panel:

 

Screen Shot 2020-03-30 at 4.20.41 PM

Tap that button and then search by entering one or more ingredients. Use commas to separate the ingredients.

You can also just start typing ingredients right away, and we'll suggest the option to switch to search "using this ingredient."

Screen Shot 2020-03-30 at 4.33.37 PM

If we've added ingredient search to your site and you don't want it, it's easy to turn it off. Go to your Slickstream console, open the Config page, choose the Site Wide settings, expand the Search/Favorites Panel section, and you'll find a new setting there to turn it off:

ingredient-search-setting

If you occasionally see a few strange ingredients listed, we're sorry about that. We're doing our best to pull individual ingredients out of your recipes. It's hard to get it right 100% of the time. While we can't fix everything, if you think we're doing a particularly poor job on your site, we'd really like to hear about it.