Structured data needs to conform to a particular format. As is the case for any computer language, you must adhere to a correct syntax if you want the machines to crunch it properly.
Schema markup provides such a universally recognized format for structuring data on the Web.
If I want to tell search engines that my first name is Michal, I need to look up how to annotate it. Looking up “name” in the schema.org vocabulary brings me to the givenName property:
4 schema given name
You need to use this in its exact form in your code. Using variations like FirstName, firstName, or given_name won’t work. Standardization is the key to structured data, and the schema.org vocabulary provides it.
Take, for example, an airline flight: schema.org has a lexicon to notate the type of aircraft, the departure gate, and even a description of the meal service:
5 flight schema
That’s it for the theory. Let’s take a look at how all of this works on your website.
The three ways of structuring data
There are three main formats you can use to structure data on the Web.
The workload like this whatsapp number list allows both the vendor and the affiliate to focus on. Clicks are the number of clicks coming to your website’s URL from organic search results.
JSON-LD
Microdata
RDFa
JSON-LD
JSON-LD is the format that Google recommends. It’s also the easiest to implement because there’s no need to “tag” HTML elements, as is the case with other structured data formats. Instead, you add JSON-LD as one big block of code that tells Google, “Hey, here are the main things you should know about the stuff mentioned on this page.”
Here’s an example of a very simple Organization markup using JSON-LD:
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Organization",
"name": "Ahrefs",
"url": "https://ahrefs.com/",
"description": "Ahrefs is a software company that develops online SEO tools and free educational materials for marketing professionals.",
"email": "support@ahrefs.com"
}
</script>