Dla tego filmu nie wygenerowano opisu.
Have you guys ever searched something on Google and found results that look a little different? Maybe you're looking for recipes and you get this specific section where you get some star ratings, you get the number of reviews, how long it's going to take to cook that specific recipe and more. Or maybe you've seen results on Google that have different types of star ratings, all these votes, and then also an FAQ attached to it. Or if you've looked for movies or events, you might have seen this type of result on Google. So all of these are rich results.
And there's actually a whole series of them that we can take a look at in this article written by Google. So all these different types of rich results are results that we can be a part of, right? So if we have a book that we're selling, we can show different breadcrumbs, carousels, courses, data sets, events. It goes on and on and on. I'm going to link this specific URL in the description so you guys can check that out. And if we want to take part in these rich results and get our own rich results and rich snippets, we need to use structured data.
So what is structured data? Structured data is a really small piece of code that we can add to our website that helps Google understand the content that we're looking at. Let me show you guys what this actually looks like. And just bear with me. We are going to take a look at some code, but I'm going to break this down with you guys so you can understand exactly what we're talking about when we're talking about structured data. I'm going to take this example, NYC parking, and I'm going to open up the page and I'm going to go to the page source. OK, I'm just going to command fschema. org.
I'm going to copy and paste a couple of things onto Google Docs so we can see exactly what we're working with. I'm going to take this right here. So I'm going to paste that there. And then I'm also going to take another piece of schema, which is this one right here. So let's separate this a little bit. So we see that we have a piece of text that's talking about an aggregate rating. And so if we separate this out a little bit, we're going to see that we have a specific rating value and a rating count.
OK, so if we actually go back to the search result, we see that we have this rating as four point eight and one hundred forty six thousand votes. If we go back into this Google Doc, we're going to see that what's actually present. So that little piece of code that we found right now is exactly what's coming up in the search results. So we have that four point eight and one hundred forty six thousand rating counts or votes. And then another thing that we have here is this FAQ. So is parking suspended today in NYC? And we're going to see if we separate this out a little bit as well.
So we have this question and then we have this answer. So question, let me just make this bold so you guys can see it and then answer. So the question is, is parking suspended today in NYC? And then the answer is the following. Right. So this is exactly what's being brought up in that search result. And this is something that we can play around with. So this is exactly what structured data looks like. It's just a little piece of code. And if we break it down like we just did, it's not as scary as it might seem.
But guys, why do we need to add this type of structured data? I thought search engines were smart enough to understand what we were talking about. So even though search engines have been getting smarter over the years, they still can't read blog posts and view images and understand things as easily as we can from a quick glance. So by using structured data, we provide an additional level of support to help Google understand what we're talking about just a little bit better. I'm going to give you guys an example later that's going to really help you visualize this concept.
But on to the next thing, guys, how do we add this to our website? And what do we even add to our website? So this is where we go to Schema. org. This is an initiative that was started by Google, by Bing and by Yahoo to basically dictate how we add structured data and what that language is going to look like, what that markup looks like. So if we actually go to Schema. org, this is where we're going to find everything relating to structured data. So if you click on the docs, what we're interested in here is the schemas.
And here we can jump directly into we can check out a book, maybe a movie, and we're going to use the recipe example later. So this is going to tell us exactly what we need to provide to have that structured data for the specific type of schema or type of property that we're looking at. So if we want to have a structured data for a book, then this is exactly what we need to provide. So for now, all we need to do is just take a look at this section right here, which says properties from book. Anything under that right now isn't super relevant.
These are all the things that we can add to that structured data for that book. Right. So we have book edition, so edition of the book, the format, the illustrator, the ISBN if we'd like, and the number of pages. Once we have that set up on our website, that's then going to come up in the search engines result page. Another example, let's take a look at movie. So properties from movie. Again, we only need to check it out until all the way down here. And these are all the things that we can talk about for that structured data for a movie. So an actor, it's telling us exactly what it is.
So actually be associated with individual items in a series, the country of origin, the director, duration, music, by all these other things. And then finally, we're going to take a look at this example. So properties from recipe, right? So we have the cooking time, cooking method, nutrition, category, cuisine. And again, we have the description on the right if we're not exactly sure what we need to provide. We also have a separate property of a how to. This is also applicable not just to recipes, but basically to anything where you're teaching someone how to do that specific thing. And then we have another subset of properties for that type of schema.
Now, I know this might look scary, guys, but if we break it down piece by piece, it actually isn't as scary as it seems. We're just providing that a little bit of extra data just to help Google understand exactly what we're talking about. But the question is, how do we actually add this to our website? So directly on schema. org, it'll give us three different ways that we can add that to our website. So if we scroll all the way down to any of the schema types, we're going to have different examples and how they're going to look like in different markups. And markups are just different ways of providing that data.
We don't have to worry about that too much. So we see down here. So we're looking at an example of a recipe and we see that the example we're looking at now, it says no markup. So this is just plain old HTML without any markup. OK, so we have world famous banana bread. There's an image by John Smith. This is the prep time, the cook time, the yield, so on and so forth. So this is the example that I was talking about, guys. Right now, if Google were to see this specific page, they would read that text and they would understand it to a certain extent.
When we set up the structured data and we tell it exactly what each piece of this recipe is, it's going to understand that this is a recipe a lot better. So there's three different ways, three different markups that we could use to present that structured data. We have micro data, RDF, and Jason LD. If we actually check out one of Google's documents about understanding how structured data works and we scroll all the way down, we're going to see that Jason LD is actually the recommended markup, the recommended way that we want to present structured data on our website. So, again, let's go back to that recipe. We want to take a look at Jason LD.
And this is exactly what we saw in that previous example of the parking example. We saw the aggregate rating and the FAQs. This is how it was set up. So now we're breaking down that recipe and we have all these different layers of properties of that specific recipe. And Google can understand this a lot better. So we know that the type of schema is a recipe. The author is John Smith, the cook time, the date published, the description and the ingredients. Right. So now Google understands that this is specifically talking about an ingredient and it's in the structure that they can read and they can understand a lot better.
So even though this might sound really complicated and really technical, it's really important to understand why we use schema and how we add it to our website. So if you have a technical team, definitely talk to them about it. But if you're using something like a WordPress, there's actually quite a few things we can do to add structured data to our website. So let me show you guys a couple of examples here. If you go into the WordPress plugin marketplace and you type in structured data, there's going to be a variety of plugins that are going to help you get structured data on your WordPress website.
The interesting thing about these plugins is that sometimes these plugins are specifically built for one type of schema. Right. So this one right here, it's built specifically for reviews. Right. And then we have another one down here that's built specifically for events. And then you're going to have other ones that are all around structured data schema builders. Right. And so it's important to scroll down and just check out all the different types of schema that are supported. Right. So we see article, book, course, how to, so on and so forth.
So these are really interesting to look at and they can really help you add that structured data to your website. I actually want to show you guys an example because I ended up buying for this specific website, I ended up buying a plugin that would help me out specifically for structured data relating to recipes. And so if we actually I want to show you guys exactly how this works. If we click on edit recipe, this is exactly what that's going to look like and what some of these plugins are going to look like. Right. So we're going to have all these different fields that we're going to have to fill in.
So the name, the summary, the author, the servings, the prep time, all this stuff, the categories, any equipment we want to add, ingredients, instructions, so on and so forth. So once we filled all this in, this is what that recipe is going to look like. It's going to come out like a rich result with all the right things in all the right places. So rich results are definitely really cool. But the step after rich results is getting featured snippets. So if you're interested in that, click on this video. That's how you completely take over keywords and destroy your competitors. Otherwise, I'll see you guys in the next one. .