Error in Google SDTT: "All values ​​specified for the URL must point to the same page."

I'm trying to create some JSON-LD structured data for a list of products on ecom, but I get an error when using the Google Structured Data Testing Tool.

So far I have this:

{ "@context": "http://schema.org", "@type": "OfferCatalog", "name": "Fresh Fruit", "itemListElement": [ { "@type": "ListItem", "position": 1, "item": { "@type": "Offer", "price": "1.20", "priceCurrency": "GBP", "availability": "http://schema.org/InStock", "url": "http://example.com/green-apples/", "itemOffered": { "@type": "Product", "name": "Green Apples", "url": "http://example.com/green-apples/" } } } ] } 

It is mostly checked, but the Google tool raises the following error:

All values ​​specified for the URL must point to the same page.

The error displays line 11 ( "@type": "Offer", ).

The URL fields seem to collide with the @context , because if I change the context to a string with non-url or http://example.com , it checks (although this obviously causes problems). (The comments below show that this is a red herring)

What am I missing here? It seems like something dazzlingly obvious.

+9
url json-ld google-rich-snippets
source share
7 answers

This is certainly a bug in the validator. I checked with the examples provided by google: https://developers.google.com/search/docs/guides/mark-up-listings . If you click on the second example, you will see that it has the same error.

The error is displayed even if you use 1 element:

 { "@context": "http://schema.org", "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "item": { "@type": "Recipe", "url": "http://example.com/desserts/pies/#apple-pie", "name": "Apple Pie", "image": "https://example.com/300px-Apple_pie.jpg", "author": { "@type": "Person", "name": "Carol Smith" }, "datePublished": "2009-11-05" } } ] } 
+1
source share

I think this is due to clicking on accelerated mobile pages and their structured data.

Please check my thoughts here: all values ​​given for the URL should point to the same page . My guess was about a problem in Googles SDTT

So, to fix the problem with your structure data, please use the correct version of ItemList (there are separate and combined tagged ItemList, please check here ):

  • If your items are on the same page, please use the version with items inside, Combined.

  • Otherwise, if you point to different pages inside, and your elements are not on the same page, DO NOT put the element element with a type and another description inside, separately marked.

+6
source share

I think the problem arises when we mix two types of list, that is, the Summary page + several pages with full information and one all-in-one list.

Google stated on the page - https://developers.google.com/search/docs/guides/mark-up-listings

  • If this is a summary page , the ListItem should include only the type , position, and url properties.
  • If this is an all-in-one list, ListItem should include all the additional schema.org properties for the data type it describes (for example, Recipe or Course objects).

But Google should consider the product list of the eCommerce category, where people display product numbers with more than 3 properties on the summer page, and this is obvious for e-commerce, as price and image are 2 important elements on the product list page, with the exception of 3 listed above .

Therefore, we need to raise this issue on Google in order to resolve this issue.

+2
source share

Now is the year 2018.

Yasha Pal's answer above is close, but not entirely correct.

This is not a Google Checker Tools error.

The error is valid and you need to fix it.

You use the "One Page" approach (there are two approaches: "Summary Page" and "One Page")

The One Page Approach requires each URL to be exactly the same, and each one must have an anchor.

The Google developer doc clearly mentioned this.

I wrote explanation details there

If your page contains several links to another page, then you should use the "Combined page" approach and it had a different data structure (I think it is much simpler)

+2
source share

No, this is not a bug in Google SDTT,

I have helped many people fix their structured data, including dynamic arrays. Read the instructions. Google clearly states: " All values ​​for the URL must point to the same page ." Think about it, Google is trying to tell you something.

This means something: "Hey, you are using a list of elements other than the example we have given, there are more than two elements in your list of elements."

Decision:

Use anchors! Voila!

Please use this example snippet and you won’t be mistaken. And one more piece of advice; use the Fetch Url option from SDTT:

 <script type="application/ld+json"> /*structerd data markup compiled by http://www.iwanross.co.za */ { "@context": "http://schema.org", "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "item": { "@type": "Recipe", "url": "https://www.smokingchimney.com/#beetroot", "name": "Beetroot Side Salad for the braai", "image": "http://www.smokingchimney.com/recipe-pages/images/1x1/Beetroot-Salad- for-the-Braai-800x451.jpg", "author": { "@type": "Person", "name": "Marna Ross" }, "datePublished": "2018-10-05" } }, { "@type": "ListItem", "position": 2, "item": { "@type": "Recipe", "url": "https://www.smokingchimney.com/#carrot", "name": "Carrot Cake", "image": "http://www.smokingchimney.com/recipe-pages/images/16x9/carrot-cake- recipe-picture-1024x576.jpg", "author": { "@type": "Person", "name": "Marna Ross" }, "datePublished": "2018-10-05" } }, { "@type": "ListItem", "position": 3, "item": { "@type" : "Recipe", "url":"https://www.smokingchimney.com/#overnight", "name": "Overnight Steak Marinade", "image": "http://www.smokingchimney.com/recipe-pages/images/1x1/Overnight-steak- marinade-700x465.png", "author": { "@type": "Person", "name": "Marna Ross" }, "datePublished": "2009-10-05" } } ] } </script> 
+1
source share

You don’t need to bind each URL, can you also add parameters to the URL? i = 1

like:

https://website.com/d/link?i=1

https://website.com/d/link?i=2 ....

0
source share

Use the OfferCatalog type instead of the ItemList. https://schema.org/OfferCatalog

0
source share

All Articles