AMP Structured Data errors for `publisher.logo` and `article.image`

As with #7557, #7425 and #7396 we’re facing more and more issues regarding structured data in AMP. Google wants to have a proper publisher.logo (warning) in 60x600px dimensions and an article.image (error). Always!

But it’s not only for AMP! We get the exact same errors and warnings for normal blog posts, so we need a short term solution for LTS, which could be like this:

• replace the default Ghost blog logo with one, that fits the dimensions
• put a text underneath the blog logo update in general settings, that it has to fit the image dimensions
• use the blog cover as a default article.image whenever no post image is supplied. If there’s no blog cover, use a default picture (this needs to be defined, maybe something neutral, that refers to writing?)

For a long term solution, we need image-optimisation. With that we’re able to resize the publisher.logo and offer the possibility to upload a default post image, just like we do with the blog cover or logo in general settings.

Happy for other opinions here!

[ErisDS]

I recommend that we introduce the concept of “system” image sizes, which have one or two sizes used for schema.org, and where people have linked to external images (no longer possible), we should assume they are the right size.

This would allow us to remove all of the code that handles looking up image dimensions, seeing as we are now in control of what dimensions are served, and simplify the logic extensively.

[inputsh]

Pardon me asking, but why was this closed? I’m running the latest version (v3.0.2) and I still see the following markup:

    "publisher": {
        "@type": "Organization",
        "name": "Example",
        "logo": "/path/to/logo.png"
    },

…instead of:

    "publisher": {
        "@type": "Organization",
        "name": "Example",
        "logo": {
          "@type": "ImageObject",
          "url": "/path/to/logo.png",
    },

Interestingly, I can successfully run Structured Data Testing Tool on my homepage with no issues nor warnings, but when I do the same on an article (so, a publisher within "@type": "article"), I get an error around publisher logo: A value for the url field is required.