We know structured data plays a crucial role in search engine relevance, prominence and visibility.
JSON-LD allows webmasters to embed structured data directly into their HTML code, these are published facts.
By implementing JSON-LD, webmasters can enhance their website's SEO performance and curate content for AI.
These rich snippets can include additional information such as organizations, articles and products.
They provide intelligent agents with more relevant, informative and crawl-able search results.
SEO is rarely quality data - fact.claims is a simple solution to reduce the GIGO (Garbage-in, Garbage-out).
A modern SEO-optimized website will likely already host published facts, in the form of SEO snippets.
However, to be considered grounded our fact.claims must be pinned to an ipfs:// URL and become immutable.
For that reason, it's wise to take a little more care over the facts we declare:
Let's start withschema.org- they host definitions for organizations, events, people, articles, products and much more.
@prefix schema: <http://schema.org/> .
<https://www.example.com/> a schema:Organization ;
schema:name "Example Company" ;
schema:url "https://www.example.com/" ;
schema:logo <https://www.example.com/logo.png> ;
schema:contactPoint <https://www.example.com/customer_service> ;
schema:sameAs <https://www.facebook.com/example>, <https://www.twitter.com/example> .
<https://www.example.com/customer_service> a schema:ContactPoint ;
schema:telephone "+1-123-456-7890" ;
schema:contactType "customer service" .
@prefix schema: <http://schema.org/> .
<https://www.example.com/article> a schema:WebPage ;
schema:content <https://www.example.com/article> .
<https://www.example.com/article> a schema:Article ;
schema:headline "Example Article Headline" ;
schema:description "Brief description of the article." ;
schema:datePublished "2022-04-01"^^schema:Date ;
schema:dateModified "2022-04-01"^^schema:Date ;
schema:author <https://www.example.com/article/author> ;
schema:publisher <https://www.example.com/article/publisher> .
<https://www.example.com/article/author> a schema:Person ;
schema:name "John Doe" .
<https://www.example.com/article/publisher> a schema:Organization ;
schema:name "Example Publisher" ;
schema:logo [
a schema:ImageObject ;
schema:url <https://www.example.com/publisher-logo.png>
] .
@prefix schema: <http://schema.org/> .
<https://www.example.com/product> a schema:Product ;
schema:name "Example Product" ;
schema:image [
a schema:ImageObject ;
schema:url <https://www.example.com/product-image.jpg>
] ;
schema:description "Description of the product." ;
schema:brand <https://www.example.com/product/brand> ;
schema:offers <https://www.example.com/product/offers> .
<https://www.example.com/product/brand> a schema:Brand ;
schema:name "Example Brand" .
<https://www.example.com/product/offers> a schema:Offer ;
schema:priceCurrency "USD" ;
schema:price "100.00"^^schema:Float ;
schema:availability schema:InStock ;
schema:seller <https://www.example.com/product/offers/seller> .
<https://www.example.com/product/offers/seller> a schema:Organization ;
schema:name "Example Seller" .
@prefix schema: <http://schema.org/> .
<https://www.example.com/action> a schema:Action ;
schema:name "Example Action" ;
schema:description "Description of the action." ;
schema:potentialAction <https://www.example.com/action/about> .
<https://www.example.com/action/about> a schema:CommunicateAction ;
schema:actionOption "Call to Action" ;
schema:expectsAcceptanceOf <https://www.example.com/action/offer> .
<https://www.example.com/action/offer> a schema:Offer ;
schema:name "Example Offer" ;
schema:url <https://www.example.com/action/offer> .