The Article Already Had an og:image. Its JSON-LD Didn't Mention It.
I maintain three long-form pages that already emit JSON-LD: a format guide typed as Article , and two technical write-ups typed as TechArticle . Each page also sets a 1200×630 og:image through the site's shared social-metadata helper. A weekly structured-data pass, recorded in the commit this post is based on, found that none of the three JSON-LD nodes had an image property. The picture was…
A recent commit to the Mailward project added a new function called `articleImage()` to the SEO utility module. This function takes a relative path and returns an absolute URL for the shared social image used across multiple long-form pages. The three affected pages, including one about email archive formats, previously lacked an `image` property in their JSON-LD markup.
The JSON-LD documentation recommends including an image property, ideally a high-resolution representative image in one of several aspect ratios. Google does not guarantee rich result features appearing in search results, but recommends high-resolution images. The 1200x630 social image used by Mailward meets the 50,000-pixel minimum.
A new test was added to the project's test suite, checking that the `articleImage()` function returns the same URL as the statically defined `OG_IMAGE` constant and that the `image` property is present in each page's JSON-LD markup. The test does not verify the actual rendering or performance of the rich result.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.