Tumgik
#Chocolate Makery
chocolatemakery · 2 years
Text
The Chocolate Makery Etsy is offline for the next week as part of the Etsy strike to protest increased fees after two straight years of Etsy reporting record profits. Find out more at etsystrike.org/petition
4 notes · View notes
byronnjp · 4 years
Photo
Tumblr media
Diseño e Impresión de envase para dulce de Maní con Chocolate 🥜🍫 #somoslosmejores #3dprinting #3dprint #wooden #pla #vase #envase #marketing #byronmultimedia #makery #hechoenecuador #creality #peanut #chocolate #3ddesign (en Santo Domingo de Los Colorados) https://www.instagram.com/p/B8W6BklHlZS/?igshid=1lcui4b7korm
0 notes
sophiecorrigan · 6 years
Photo
Tumblr media
Today is the first day of @joannehawker's #Marchmeetthemaker challenge! I might not manage to post each day, but thought I'd give it a try this year as I find it fascinating to learn about other makers and artists myself! 😄 So hello! This is me, I'm Sophie and I'm a freelance illustrator from t'North of England. I have an MA in children's book illustration (so technically I'm a master of kids books, which is hilarious). My hobbies include tea, chocolate, hanging out with my birdies and singing badly, but loudly. I draw cute animals a lot, and Attenborough is my bae. I'm currently working on a number of exciting children's and gift book projects for different publishers, while building my online shops and prepping for my first ever print fair in March! I'm not great with photos, but I'm trying to channel Patti Smith in this one ✌ I hope all my arty-makery friends join in! 😀
3 notes · View notes
oliveratlanta · 5 years
Text
What to expect at South Downtown’s ‘Pop Up Row,’ which opens with eight shops today
Tumblr media
Newport US initiative aims to enliven historic storefronts, signaling the start of district’s planned makeover
In the early 1900s, a section of downtown’s Mitchell Street was developed to accommodate travelers coming to and from Atlanta’s main railroad hub, the Terminal Station.
The lodging options are gone, but the name, Historic Hotel Row, lives on.
And as of today, Hotel Row has been injected with new activity that Newport US RE, the developer planning to transform dozens of South Downtown buildings, is calling “Pop Up Row.”
From now until July 31, a selection of the former hotel buildings will be open to pop-up patrons. Some of them still bear the names of inns that operated a century ago—Scoville, Sylvan, and Gordon Lofts, for instance.
Tumblr media
Newport US RE
A rendering shows the pedestrian-friendly vision for Mitchell Street.
But Pop Up Row obviously offers more than just a history lesson; visitors should expect live music, artwork, food trucks, and other shopping options.
The pop-ups will operate from noon until 7 p.m. today, starting with a kickoff party.
After that, Pop Up Row will be open Tuesday through Friday from 11 a.m. to 8 p.m. and Saturday from 11 a.m. to 6 p.m.
Atlanta-based musician DJ Opdiggy will provide tunes for the event, and food trucks from Just Loaf’n, South of Philly, Cousins Maine Lobster, and Rio’s Italian Ice will be on-site, too.
Pop-up tenants include:
Atlanta Makery: a gift shop featuring “apothecary, apparel, accessories, leather goods, stationary, art, gifts for men, baby items, and edible gifts like local honey, jams, and chocolate,” according to a Newport press release.
The Bookery: an intown bookstore run by the folks behind Mableton’s Book House, which has been operating since 1976.
Cat Eye Creative: a pop-up artist space showcasing an array of locally made work, as well as studio space for a rotating roster of creatives.
Eighth & Style: a “brand experience agency that specializes in creating relatable, experience-rich environments for both influencers and brands.”
Ennyluap: an Atlanta-based fashion brand.
Kea Beverages: a place to get cold-pressed juices, kombucha, and nitro coffee on tap, all sourced from local produce.
The Mast: an art gallery welcoming creatives from all over the state, where a rotation of exhibits “of all mediums” will be on display.
Otis Damon Millinery: a hat-maker focused on hand-crafting “timeless pieces” customized for wearers.
Those chosen for Pop Up Row receive free rent and utilities, plus a $500 start-up allowance. Pop Up Row occupies spaces from 211 to 233 Mitchell Street, just south of Five Points MARTA Station.
Visitors, of course, can also check out existing Mitchell Street businesses, such as Friedman’s Shoes and My Fair Sweets.
Tumblr media
Newport US RE
A broader look at Newport’s intentions for the area.
Before too long, as officials have said, Newport’s $500 million overhaul of the eight South Downtown blocks it owns will begin to transform Mitchell Street by restoring Historic Hotel Row and stripping away two lanes of the four-lane street to make it more pedestrian-friendly.
Newport vice president April Stammel recently told Curbed Atlanta it’s possible Pop Up Row participants could become longterm tenants, following temporary closures of spaces for renovations, which are expected to begin in earnest later this summer and fall.
Newport’s South Downtown portfolio features 48 historic buildings and sites along Peachtree, Mitchell, and Broad streets, plus Martin Luther King Jr. Drive. The company has invested more than $100 million in the project thus far.
source https://atlanta.curbed.com/2019/4/11/18306205/south-downtown-newport-mitchell-street-pop-up-row
0 notes
malindians · 4 years
Text
Mikate Ya Maji Ilojazwa Nutella - Malindi Recipes
Mikate ya maji iliyojazwa nutella (crepes), ni miepesi kuliko kawaida. Nutella inatandaza kwa mkate hii na kuipatia ladha murua kabisa. Aina hii ya vyakula huliwa wakati wowote ule.
Nutella ni nini?
Nutella ni mchanganyiko wa chocolate na Hazel(hazelnut). Jinsi inavyotengeneza katika viwanda haiko tofauti sana na vile inavyotengenezwa majumbani. Nutella inatengenezwa kutumia sukari, mafuta ya nazi, hazel, unga wa cocoa, maziwa ya unga, soya, vanila, lecithin and unga wa whey.   Kwanini watu wanapenda mikate ya Maji Mikate ya maji(crepes) ya aina hii inawezwa kupaka chochote kile, chachu au tamu. Kulingana na upishi, inaweza kuwa miepesi kuliko mikate ya maji mingine, mitamu na yenye kushibisha. VIPIMO: ⚫Unga wa cake kikombe 1⅓ ⚫Maziwa kikombe 1 ⚫Maji ½ kikombe ⚫Sukari ¼ kikombe ⚫Yai 1 ⚫Chumvi 1/4 kijiko chai ⚫Mafuta ya kula kwa ajili ya kupakaza chuma ⚫Nutella kwa ajili ya kujaza ⚫Chocolate ya nutella iloyeyushwa (ukipenda) MAELEKEZO:- 1. Katika bakuli ya kati tia Mahitaji yote kisha piga hadi mchanganyiko uwe smooth. 2. Tia chuma chako ulichokipaka mafuta jikoni katika moto wa kiasi. 4. Minina unga wako wa mikate ya maji ktk chuma chako,chota 1/4 kikombe ya unga kwa kila mkate. 5. Zungusha chuma chako kueneza unga wako na kufanya duara. 6. Pika mkate wako kwa sekunde 30 au hadi chini ipate rangi. 7. Geuza upande wa pili kwa kutumia spatula kisha acha na upande wa pili upate kuiva,epua ktk sahani, Rudia kumaliza unga wote. 8. Paka Nutella juu ya mkate wako isiwe nyingi sana kisha zungusha kama picha inavyoonyesha. Utarudia kwa zote 9. Pambia kwa kunyunyiza chocolate uloyeyusha (ukipenda) Note: Unga wa crepe au mikate ya Maji hasa unayojaza inatakiwa uwe mwepesi zaidi Fungua comments uone namna ya kukunja na hiyo nutella kwa wasioijua Rejea post za nyuma kuona namna gani unaweza kutengeneza unga wa cake nyumbani { "@context": "https://schema.org/", "@type": "Recipe", "name": "Mikate ya maji iliyojazwa nutella (crepes)", "image": , "author": { "@type": "Person", "name": "Komzinski" }, "datePublished": "2018-03-10", "description": "Mikate ya maji iliyojazwa nutella (crepes), ni miepesi kuliko kawaida. Nutella inatandaza kwa mkate hii na kuipatia ladha murua kabisa.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": , "recipeInstructions": , "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Mapishi mix" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": , "contentUrl": "http://www.example.com/video123.mp4", "embedUrl": "http://www.example.com/videoplayer?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } Read the full article
0 notes
wendyjudithqe · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
janiceclaudetteo · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
elenaturnerge · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
mariaajameso · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
samiaedithg · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
miettawilliemk1 · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
chocolatemakery · 2 years
Text
I feel like covering my twitch page with Chocolate Makery stuff is counterproductive? Then again, if that's what I'm about...
2 notes · View notes
byronnjp · 4 years
Video
Envase de dulce 🥜🍫 Maní con Chocolate #byronmultimedia #makery #3ddesign #modelling #3dprint #pla #wooden #peanut (en Santo Domingo de Los Colorados) https://www.instagram.com/p/B8W7FTWnzSp/?igshid=16717fsbghxoq
0 notes
mariathaterh · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
evanstheodoredqe · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes
rodrigueztha · 6 years
Text
Structured data for recipes: getting content read out loud
Do you have a recipe site? If so, you might already be using structured data to mark up your recipes so they can get highlighted in the search results. Good work! But, Google recently made some changes that might make your implementation incomplete. It also expanded the possibilities of structured data for recipes by bringing guidance into the mix. The result? Google Home can now read your structured data powered recipes out loud!
Want rich snippets for your site? Try our Structured data training »
$149 - Buy now »
Info Structured data, recipes and Google Home
Google is betting big on voice search. While voice search is still in its infancy, there are signs that we are moving towards a future where we are relying much less on our screens. There are many instances where talking to your digital assistant makes much more sense than typing commands. What’s more, the AI in digital assistants will become smarter and more apt at entering into a natural dialogue with you. We’re talking about a real natural language interface here.
A lot is going on right now. Take for instance that Google Duplex demo, showing a digital assistant calling a hairdresser to make an appointment. Joost wrote a post about Google Duplex and the ethics and implications. If AI is this smart, we need to take note.
To get voice search and actions to work, Google relies on structured data. Structured data makes it immediately clear what all the different parts of a page mean so search engines can use that to do cool stuff with. Google Actions, the big database featuring things you can let Assistant do, uses structured data. For instance, here is Google’s page on recipe actions — which is the same as the regular structured data for recipes documentation. If you want to learn all about structured data, please read our Ultimate Guide to Structured Data.
New rules, new results
Earlier this month, Google announced a new and improved way of targeting people who search for recipes. By adding the correct structured data, you can get your recipes read out load. Google even said that by implementing this you might: “receive traffic from more sources, since users can now discover your recipes through the Google Assistant on Google Home.”
But, when throwing random recipes from some of the largest recipe sites in the world into the Structured Data Testing Tool, you’ll find that hardly any fully comply with these new rules yet. What’s more, even the implementation of the recipe Schema.org itself is widely different between sites. That being said, there’s still a lot to win, even for the big boys.
As of now, Google recommends four new properties in addition to the ones you probably already use:
keywords: additional terms to describe the recipe
recipeCategory: in which category does the recipe fit?
recipeCuisine: from which region is the recipe?
video: use this if you have a video showing to make the recipe
You’ll see the recommendations in Google’s Structured Data Testing Tool:
Guidance: reading it out loud
How cool would it be if your Google Home could assist while you were cooking? Not by setting timers and the like, but by reading the recipe for you. That’s now possible thanks to guidance. In addition to the four new recommended properties for structured data for recipes, Google states that:
“To enable your recipe for guidance with the Google Home and Google Assistant, make sure you add recipeIngredient and recipeInstructions. If your recipe doesn’t have these properties, the recipe isn’t eligible for guidance, but may still be eligible to appear in Search results.”
To get your Google Home to pronounce the steps of your recipes correctly, you need to set the value of recipeInstructions using HowToStep or HowToSection. The latter, of course, should be used if your recipe instructions consist of multiple parts or sections. You can also keep everything in one block of recipeInstruction, but then you are at the mercy of Google as it has to try and work everything out itself. If you have distinct steps, please use HowToStep and/or HowToSection.
Hello keywords, we meet again
In a move straight out of 1997, we see keywords pop up again. Google now recommends using the keyword property to add context for your recipes. Now, this shouldn’t be confused with the recipeCategory and recipeCuisine properties. It is an extra way of describing your articles using words that don’t relate to a category or type of cuisine. We’ll just have to wait and see if the spammers can keep themselves under control.
Getting into that carousel
One of the coolest ways to discover content is the swipeable carousel you see when you search for certain types of content on mobile. To greaten the chance of your site appearing in this overview you can add an ItemList with one or more ListItems to your content.
Now, Google is quick to add that it might not be necessary to add this if you only want to appear in the regular search carousel. If you throw several well-known recipes sites into the Structured Data Testing Tool you will see that hardly any have added ItemList to their pages. Still, they rank high and appear in the carousel. If, however, you want to have site-specific entries — like your list of 5 best chocolate cheesecake recipes, or another type of landing page with recipes — into that carousel you need to add the ItemList structured data. There are several ways of doing this; you can find out more on Google’s documentation pages.
Applying structured data for recipes
If you look at Schema.org/Recipe, you might be starting to go a little bit green around the gills. Where do you even start? It’s massive! These are all the properties you could add, but that doesn’t mean that you should. Google requires just a couple but recommends a lot more.
These are the required properties:
@context: set to Schema.org
@type: set to Recipe
image: can be a URL or a ImageObject
name: name of the dish
That’s it! But, as you might have guessed, this won’t get you very far. By providing Google with as much data about your recipe as possible, you increase the chance that Google ‘gets’ your recipe. After that, it can apply the rich results and corresponding Actions accordingly.
Here are the recommended properties:
aggregateRating: average review score for this recipe
author: who made it? Use Schema.org/Person
cookTime: the time it takes to cook the recipe
datePublished: when was the recipe published?
description: a description of the recipe
keywords: terms to describe the recipe
nutrition.calories: the number of calories. Use Schema.org/Energy
prepTime: how long do the preparations take?
recipeCategory: is it breakfast, lunch, dinner or something else?
recipeCuisine: where in the world is the recipe from originally?
recipeIngredient: every ingredient you need to make the recipe. This property is required if you want Google Home to read your recipe out loud.
recipeInstructions: mark up the steps with HowToStep or HowToSection with embedded ItemistElement with a HowToStep.
recipeYield: for how many servings is this?
review: add any review you might have
totalTime: how long does it all take?
video: add a video showing how to make the recipe, if applicable
To show you how this all translates to code, we need an example. So, here’s Googles example recipe in JSON-LD format. You’ll see that it is all obvious and pretty easy to understand. If you want to implement JSON-LD code on your page, Google Tag Manager might be your best bet.
<!doctype html> <html amp lang="en"> <head> <meta charset="utf-8"> <title>Party Coffee Cake</title> <link href="http://example.ampproject.org/recipe-metadata.html" /> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "Recipe", "name": "Party Coffee Cake", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2018-03-10", "description": "This coffee cake is awesome and perfect for parties.", "prepTime": "PT20M", "cookTime": "PT30M", "totalTime": "PT50M", "keywords": "cake for a party, coffee", "recipeYield": "10 servings", "recipeCategory": "Dessert", "recipeCuisine": "American", "nutrition": { "@type": "NutritionInformation", "calories": "270 calories" }, "recipeIngredient": [ "2 cups of flour", "3/4 cup white sugar", "2 teaspoons baking powder", "1/2 teaspoon salt", "1/2 cup butter", "2 eggs", "3/4 cup milk" ], "recipeInstructions": [ { "@type": "HowToStep", "text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan." }, { "@type": "HowToStep", "text": "In a large bowl, combine flour, sugar, baking powder, and salt." }, { "@type": "HowToStep", "text": "Mix in the butter, eggs, and milk." }, { "@type": "HowToStep", "text": "Spread into the prepared pan." }, { "@type": "HowToStep", "text": "Bake for 30 to 35 minutes, or until firm." }, { "@type": "HowToStep", "text": "Allow to cool." } ], "review": { "@type": "Review", "reviewRating": { "@type": "Rating", "ratingValue": "4", "bestRating": "5" }, "author": { "@type": "Person", "name": "Julia Benson" }, "datePublished": "2018-05-01", "reviewBody": "This cake is delicious!", "publisher": "The cake makery" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "5", "ratingCount": "18" }, "video": [ { "name": "How to make a Party Coffee Cake", "description": "This is how you make a Party Coffee Cake.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "http://www.example.com/video123.flv", "embedUrl": "http://www.example.com/videoplayer.swf?video=123", "uploadDate": "2018-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionCount": "2347", "expires": "2019-02-05T08:00:00+08:00" } ] } </script> </head> <body> <h1>The best coffee cake you’ll ever try!</h1> </body> </html>
Conclusion: Got a recipe site? Add structured data now!
Recipe sites are in a very cool position. It seems that they get everything first. By marking up your recipes with structured data, you can get Google to do a lot of cool stuff with your recipes. You can get them to pronounce it via Google Home or try to find other ways of interacting with them with Actions via the Assistant database. And this is probably only the beginning.
Read more: ‘Structured data: the ultimate guide’ »
https://ift.tt/2KNxM7D
0 notes