Why does Google says that an item needs an url property in schema.org? - schema.org

When I put an example from the ItemList page in the Structured Data Testing Tool by Google, it says that an item needs an url property.
The example:
<script type="application/ld+json">
{
"#context": "http://schema.org",
"#type": "ItemList",
"name": "Top 5 covers of Bob Dylan Songs",
"itemListOrder": "http://schema.org/ItemListOrderAscending",
"numberOfItems": 5,
"itemListElement": [
{
"#type": "ListItem",
"position": 5,
"item": {
"#type": "MusicRecording",
"name": "If Not For You",
"byArtist": {
"#type": "MusicGroup",
"name": "George Harrison"
}
}
}
]
}
</script>
I simplified it to have a minimal example, but the error is the same with the exact example from the page.
I tested this code and there is no error here:
{
"#type": "ListItem",
"position": 5,
"item": {
"#type": "MusicRecording",
"name": "If Not For You",
"byArtist": {
"#type": "MusicGroup",
"name": "George Harrison"
}
}
}
Can anybody explain this to me?

A ItemList in general is a list collection of sites like a breadcrumb, overview of bandsites, etc.
If you only want a list without links to deatils sites you can use only ListItem with Items. This is the different of your samples ItemList and ListItem.

Related

How do i add Likes Received to Structured Data in JSON-LD for Product Type

I've been trying to figure out a way to add how many likes were received to a product using structured data. Is what I have below correct? Or would the second example be more correct?
Is my usage of ["Product","InteractionCounter"] for the type correct in the first example?
I'm trying to have the google show a likes counter much like the aggregateRating property of Product.
I'm also not sure what the url in offers is supposed to point to or if it's necessary. Any ideas?
<script type="application/ld+json">
{
"#context": "https://schema.org",
"#type": ["Product","InteractionCounter"],
"name": "CC-1",
"description": "Wedding Cake",
"interactionType":{
"#type":"LikeAction",
"name": "Likes",
"description": "Likes Received"
},
"interactionService": {
"#type":"WebSite",
"url": "https://example.com/index.php?page=gallery"
},
"userInteractionCount": 55
}
</script>
OR
<script type="application/ld+json">
{
"#context": "https://schema.org",
"#type": "Product",
"name": "CC-1",
"description": "Wedding Cake",
"additionalProperty": {
"#type": "PropertyValue",
"name": "Likes",
"description": "Likes Received",
"value": 55
}
}
</script>
This is what I have right now:
<script type="application/ld+json">
{
"#context": "https://schema.org",
"#type": ["Product","InteractionCounter"],
"name": "CC-1",
"description": "Wedding Cake with bla bla bla",
"category": "Wedding Cakes",
"brand": {
"#type": "Brand",
"logo": "https://example.com/images/logo.png",
"slogan": "Cakes Are Nice"
},
"offers": {
"#type": "Offer",
"url": "https://example.com/anvil",
"priceCurrency": "CAD",
"price": "119.99"
},
"image": "https://example.com/collection/wedding_cakes/mid_def/CC-1",
"interactionType":{
"#type":"LikeAction",
"name": "Likes",
"description": "Likes Received"
},
"interactionService": {
"#type":"WebSite",
"url": "https://mimozas.com/index.php?page=gallery"
},
"userInteractionCount": "55 PLACEHOLDER"
}
If the product is the subject of content, then it makes sense to indicate likes as part of the type Product. My suggestion for you:
{"#context":"https://schema.org",
"#type":"Product",
"name":"CC-1",
"description":"Wedding Cake",
"subjectOf":{
"#type": "InteractionCounter",
"interactionType":{
"#type":"LikeAction",
"name":"Likes",
"description":"Likes Received"
},
"interactionService":{
"#type":"WebSite",
"url":"https://example.com/index.php?page=gallery"
},
"userInteractionCount":"55"
}
}
And be careful about inverted commas.
My addition after expanding the question.
I'm trying to have the google show a likes counter much like the
aggregateRating property of Product.
Google has no direct support for the type InteractionCounter - read more Explore the search gallery. However, in the rich test results of my suggestion, there are no errors or warning messages from Google:
Probably needs experimentation.

ItemList error in SDTT: "All values provided for url must point to the same page"

I'm trying to add the ItemList Schema.org markup on an article page that lists top 10 software with (external) links pointing to them.
When I tested the following JSON-LD markup on SDTT, I got the error message saying
All values provided for url must point to the same page
I don't really understand why the individual list items should use the same URL?!
{
"#context": "http://schema.org",
"#type": "ItemList",
"name": "Title of the page",
"description": "Description goes here",
"itemListElement": [
{
"#type": "ListItem",
"position": 1,
"item": {
"name": "Product 1",
"image": "https://www.product-1.com/image",
"URL": "https://www.product-1.com"
}
},
{
"#type": "ListItem",
"position": 2,
"item": {
"name": "Product 2",
"image": "https://www.product-2.com/image",
"URL": "https://www.product-2.com"
}
}
]
}
</script>
I used a slightly different markup without the "item": { as put in https://developers.google.com/search/docs/guides/mark-up-listings, but this time I'm getting an error message that says
All values provided for url must have the same domain
Can you please help me solve this problem?
{
"#context":"https://schema.org",
"#type":"ItemList",
"name": "Title of the page",
"description": "Description goes here",
"itemListElement":[
{
"#type":"ListItem",
"position":1,
"name": "Product 1",
"image": "https://www.product-1.com/image",
"URL": "https://www.product-1.com"
},
{
"#type":"ListItem",
"position":2,
"name": "Product 2",
"image": "https://www.product-2.com/image",
"URL": "https://www.product-2.com"
}
]
}
These errors are about Google’s Carousels feature. This feature requires certain url values:
If used on a summary page, all URLs in the list must point to different pages on the same domain.
If used on an all-in-one-page list, all URLs must point to the page hosting the list structured data.
Your case (linking to external sites) is simply not eligible for getting the Carousels feature in Google Search. You can (and should) keep your JSON-LD like this and ignore these errors in the SDTT.

Google not showing full breadcrumbs on SERP as coded with JSON-LD schema markup

I have implemented breadcrumb schema markup with JSON-LD on my website. I have up to 5 positions (levels) of breadcrumbs and my code has validated correctly with the Structured Data Testing Tool.
However I note that Google is not showing the full breadcrumbs on the search results pages. For example for a page with 3 positions (as example code below), Google shows only 2 such as:
https://www.example.com > Jumpers > Mens
Is there anything wrong with my code?
This code would be located on https://www.example.com/jumpers/mens/designer:
<script type="application/ld+json">
{
"#context": "https://schema.org",
"#type": "BreadcrumbList",
"itemListElement": [{
"#type": "ListItem",
"position": 1,
"name": "Jumpers",
"item": "https://www.example.com/jumpers"
}
,{
"#type": "ListItem",
"position": 2,
"name": "Mens",
"item": "https://www.example.com/jumpers/mens"
}
,{
"#type": "ListItem",
"position": 3,
"name": "Designer",
"item": "https://www.example.com/jumpers/mens/designer"
}]
}
</script>

ListItem Schema [schema.org/ItemList] error: "All values provided for url must have the same domain."

I am facing issue with this ListItem schema validation on https://search.google.com/structured-data/testing-tool/u/0/
Getting error
All values provided for url must have the same domain.
I have provided same domain in every URL field.
{
"#context": "http://schema.org",
"#type": "ItemList",
"name": "Tech News",
"url": "http://m.gadgetsnow.com/tech-news",
"itemListElement": [
{
"#type": "ListItem",
"position": "1",
"url": "http://m.gadgetsnow.com/tech-news/are-tvs-going-out-of-fashion/articleshow/58375579.cms",
"name": "Are TVs going out of fashion?",
"image": {
"#type": "ImageObject",
"contentUrl": "http://m.gadgetsnow.com/photo/58375579.cms",
"width": "360",
"height": "270",
"url": "http://m.gadgetsnow.com/photo/58375579.cms"
}
},
{
"#type": "ListItem",
"position": "2",
"url": "http://m.gadgetsnow.com/tech-news/reliance-jio-discounts-are-not-going-anywhere-for-now-heres-why/articleshow/58374335.cms",
"name": "Reliance Jio discounts are not going anywhere for now, here's why",
"image": {
"#type": "ImageObject",
"contentUrl": "http://m.gadgetsnow.com/photo/58374335.cms",
"width": "360",
"height": "270",
"url": "http://m.gadgetsnow.com/photo/58374335.cms"
}
}
]
}
You may try using the correct version of ItemList. There are Separately and Combined marked up ItemLists as referred here.
If your items are on the same page, please use the version with items inside, the Combined one.
Otherwise, if you point to different pages inside and your items are not on one page, please DON’T put item element with type and other
description inside, the Separately marked up one.
Additional references:
Error in Google SDTT: "All values provided for url must point to the same page."
Schema.org and ContactPoint use with validation failure: “All values provided for http://www.example.com/ must have the same domain.”
There are no bugs. Be careful if the validator gives errors, a big chance that rich snippets will not work.
So what's the problem? The first thing to note is that in the ListItem object, either url or item can be used. As the schema.org documentation says, item is used for:
an artist’s list of data artists (e.g. an 'artist' in a list of 'artists')
And the most important thing that I noticed: if you use item and you want the scheme to be correct, then the domain and its parts should be the same in all ListItem, but the anchors are different, which are separated from the url using the # symbol. Google gives a specific example:
<script type="application/ld+json">
{
"#context": "https://schema.org",
"#type": "ItemList",
"itemListElement": [
{
"#type": "ListItem",
"position": "1",
"item": {
"#context": "https://schema.org/",
"#type": "Recipe",
"url": "http://example.com/big_list_of_recipes#cherry_pie",
}
},
{
"#type": "ListItem",
"position": "2",
"item": {
"#context": "https://schema.org/",
"#type": "Recipe",
"url": "http://example.com/big_list_of_recipes#coffee_cake",
...
}
}
]
}
</script>
As you can see in the list, the same URL is used http://example.com/big_list_of_recipe, but different anchors: #cherry_pie and #coffee_cake.
But still it is not clarity how to specify the URL, which is a separate page for the thing.

Errors in Google SDTT for Schema.org Product, Offer, and PriceSpecification

I'm new with Schema.org markup, so I've actually come up with the following codes for my real estate markup, and Google testing keep saying I shouldn't use offer for priceSpecification. I'm so lost now.
{
"#context": "http://schema.org/",
"#type": "Product",
"name": "Nodorus - Precinct 17",
"image": "http://www.setiaalam.com.my/images/products/p17/nodorus-c.jpg",
"description": "A distinct modern link residence set amidst award-winning green spans, wetland wonders and multiple amenities. Come home to articulately crafted spaces where architecture and nature's beauty infuse home with fresh chic. Rejoice in this cosy new addition to Setia Alam North.",
"additionalType": "Product",
"Offer": {
"#type": "PriceSpecification",
"priceCurrency": "RM",
"priceSpecification": {
"minPrice": "593000",
"maxPrice": "890000"
},
"availability": "http://schema.org/InStock",
"seller": {
"#type": "Organization",
"name": "S P Setia"
}
}
}
If you want to add an Offer for a Product, you have to use the offers property.
So instead of this (which doesn’t make sense, because Offer is not a property):
{
"#context": "http://schema.org/",
"#type": "Product",
"Offer": {}
}
You have to use this:
{
"#context": "http://schema.org/",
"#type": "Product",
"offers": {}
}
The type of the offers value should be Offer, not PriceSpecification.
The PriceSpecification can be added to the Offer via the priceSpecification property.
So the structure could look like:
{
"#context": "http://schema.org/",
"#type": "Product",
"offers": {
"#type": "Offer",
"priceSpecification": {
"#type": "PriceSpecification"
}
}
}