Read every block of structured data on a page, or paste your own: whether it parses, what it says the page is, and what that type is missing.
More checksUtilitiesDomain and email
No JSON-LD yet? Make it with the schema creator.
The page has no JSON-LD. Structured data tells search engines and assistants in their own terms what a page is: a business, a product, an article, a question and its answer.
Missing fields are the ones search engines look for first on each type, not every field the type allows. Valid markup is not a promise of rich results.
application/ld+json
{
"@context": "https://schema.org",
"@type": "RoofingContractor",
"name": "Acme Roofing",
"url": "https://example.com/",
"telephone": "+1-512-555-0142",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701"
},
"openingHours": "Mo-Fr 08:00-17:00"
}The closest type schema.org has, not just Organization, and every value in it is also on the page for a person to read.
Rules from the rulebook, and how many of the sites clickd has read miss each.
Structured data from schema.org, usually as JSON-LD in the page’s head, that says what the page is: a product, an article, a business, an event.
Not directly. It decides which rich results a page may show, and it tells assistants plainly what the page is about.
JSON-LD. Google recommends it, and it sits apart from the page’s markup, so it is easy to keep right.
One page is one part. A read checks every page against the whole rulebook and says what to fix first.
See allbirds.com’s report