Reporter: @leonidasmi
From: https://yoast.atlassian.net/browse/IM-2115

The schema should describe the content that's on/in the page

According this master rule from @jonoalderson, we should add URLs in ImageObjects same to the ones we use in src of the images in the content. Currently, we’re not doing that always.

Steps to replicate the issue to be fixed:

1. Create a post and upload an image in it. The post should have no feature image for the bug to have an effect (I think)
2. Select a resized version of it via the image block (thumbnail, medium, large) and NOT use the full size image. For example, select the thumbnail.
3. Visit the fronted

What we expect:

{
   "@type":"ImageObject",
   "@id":"https://example.com/test/#primaryimage",
   "url":"https://example.com/wp-content/uploads/2023/02/example-300x300.png",
   "contentUrl":"https://example.com/wp-content/uploads/2023/02/example-300x300.png",
   "width":300,
   "height":300
},

because the post will have a <img src="https://example.com/wp-content/uploads/2023/02/example-300x300.png"> image in its content

What we got instead:

{
   "@type":"ImageObject",
   "@id":"https://example.com/test/#primaryimage",
   "url":"https://example.com/wp-content/uploads/2023/02/example.png",
   "contentUrl":"https://example.com/wp-content/uploads/2023/02/example.png",
   "width":1500,
   "height": 1500
},

and that’s violates the The schema should describe the content that's on/in the page master rule.

Make sure to test the potential fix with images that are over 2900px, because WP is scaling down those and we need to make sure we fix those cases as well.

Thread for even more context: https://yoast.slack.com/archives/C03KU0EHCNQ/p1676019977503349