There are other things in this use case that will save you a lot of trouble in the future if you can understand now:
Notice how there is no comma after "customer service". That's because there is no more information to share in this collection. But there is a comma after the closing curly brace because there is more data to provide specifically the "sameAs" attribute.
Now that we know a little bit about syntax, let’s start creating our structured data markup.
Online generators are great if you’re a beginner or as a way to create a baseline markup and save time. My favorite is Merkle’s Schema Markup Generator , which is the one I’ll be using for this section of the guide.
Next, you need to select your page and tag type. In this finland mobile database example, I have selected s:gofishdigitalomas our page and Organization as our tag type.
After filling out some information, our tool created some fantastic baseline markup for the homepage:
Hopefully, after our grammar lesson, you’ll be able to read most or all of this example without any problems!
Create custom structured data markup using a text editor
Baseline markup will be nice, but we can go beyond the online generator presets, take full control, and write beautiful custom structured data for our pages. On s:schemargOrganizationthe , you'll see all the available properties that fall under the organization markup type. That's a lot more than the online tools offer, so let's roll up our sleeves and get some serious work done!