How can a 1200 pixel image for AMP not be on desktop?

Hi @considerthis1,

Can you please be more specific on the query so that it will be very helpful for us to understand the issue clearly.

Please let us know.

@ampforwp she is referring to the search console errors that say featured images on an amp page need to be 1200 px minimum

Hi,
Well, after a lot of testing it appears that the Featured Item function behaves differently than it used to.
When I put a 1200 pixel image into my Featured Item box, it displays properly on Facebook and Twitter when the page is linked…

It looks as if I have to change all my featured items, which will take a bit of time, but not as much as I’d previously imagined when I thought I had to change both the featured image and the image at the top of my pages…

Here’s the page I did when I was testing:
https://off-grid-insights.com/featured-image-1200-pixels-problem/

Hi, it works fine using Individual AMP Pages Custom amp editor. Turning off the automatic rich data structure in plugin.
Copy and paste the html of the post. Then insert the following script in custom amp editor html mode.
This would be marking for “newsarticle”. Example:
=========================

<script type = “application / ld + json”>
{
“@context”: “https://schema.org&#8221;,
“@type”: “NewsArticle”,
“mainEntityOfPage”: {
“@type”: “WebPage”,
“@id”: “https://google.com/article&#8221;
},
“headline”: “Article headline”,
“image”: [
“https://example.com/photos/1×1/photo.jpg&#8221;,
“https://example.com/photos/4×3/photo.jpg&#8221;,
“https://example.com/photos/16×9/photo.jpg&#8221;
],
“datePublished”: “2015-02-05T08: 00: 00 + 08: 00”,
“dateModified”: “2015-02-05T09: 20: 00 + 08: 00”,
“author”: {
“@type”: “Person”,
“name”: “John Doe”
},
“publisher”: {
“@type”: “Organization”,
“name”: “Google”,
“logo”: {
“@type”: “ImageObject”,
“url”: “https://google.com/logo.jpg&#8221;
}
},
“description”: “A most wonderful article”
}
</ script>
==================
https://developers.google.com/search/docs/data-types/article
===================
These are the technical specifications for the images:
Repeated field of ImageObject or URL

The URL to an image that is representative of the article or AMP story.

Due to format differences in search results, the following image guidelines only apply to general AMP pages, not AMP stories. AMP stories have different requirements for images.

Only a marked-up image that directly belongs to the article should be specified.
Images should be at least 1200 pixels wide.
Every page must contain at least one image (whether or not you include markup). Google will pick the best image to display in Search results based on the aspect ratio and resolution.
Image URLs must be crawlable and indexable.
Images must represent the marked up content.
Images must be in .jpg, .png, or .gif format.
For best results, provide multiple high-resolution images (minimum of 800,000 pixels when multiplying width and height) with the following aspect ratios: 16×9, 4×3, and 1×1.
============
https://developers.google.com/search/docs/data-types/article
===========
the tool to check:
https://search.google.com/structured-data/testing-tool
==============
Its recommended that the canonical (non-amp) mobile version include the same structured data.
==================
To compress images: https://compressor.io/
Regards

Hi Chusbas, I just found your very helpful reply. Thank you.
the only trouble is it’s above my comprehension level.
I don’t know the difference between AMP pages and stories…

I’ll read the article you link. But so far today, when I was going to diligently change all my featured images, I found that the whole image, at 1200 pixels wide, does not show when posted on Twitter or Facebook… the width shows… but not the height… so my images are cut off leaving the embedded wording cut off…

I’m unclear how to comply, and still have images that are fully visible…

I’m trying this video re Google Assistant and AMP to try to understand … more
https://www.youtube.com/watch?v=tcFe0Rj2pW4

I’m unclear, does AMPforWP automatically input the JASON-LD markup language for our pages… based on… ???

The aspect ratio for a 1200-wide image is 1200×675 in height. The plugin can automatically incorporate the script. You can see a section below in the last row, when editing a post. However, when using that automation, I have received errors in the google test. Maybe the plugin developer can guide us in these problems. a greeting.

https://calculateaspectratio.com

chusbas…
Do you know if I apply the given ratios to my images, will the full image show? Right now my images show the full width, but not the full height, so many of my images have the crucial bit cut off…

Oh how cool, you already answered… I’ll go apply this. Thank you so so much

okay, I see what you’re saying. When Google says 1200 or greater… then for my fingernail picture… which really can’t be cropped to be 675 high and still show the whole fingernail… does that mean I should … I’m so unclear… Do I have to make the picture much bigger to get the height to show… or, is this why catalog pictures often have white space added on the sides of images???

Google says: For best results, provide multiple high-resolution images (minimum 800,000 pixels by multiplying width by height) with the following aspect ratios: 16 × 9, 4 × 3 and 1 × 1. You can use the web page that I have attached. The images must have those dimensions to be shown completely.

I think I’m getting there… We’ll see. I’m about to test the image…

Whew… so a part of it seems to be changing my images in my Schema Structured Data… which still says the image has to be 300×300 but which only displays if the image is 1200 x something… 1200×672 looks GREAT.

Thank you So SO much Chusbas ??