Opened 10 years ago

Closed 9 years ago

#415 closed enhancement (duplicate)

Update WordPress logo used in og:image element to improve social media distribution

Reported by: niallkennedy's profile niallkennedy Owned by:
Milestone: Priority: normal
Component: General Keywords:


Facebook likes images larger than 1200 pixels wide. Big photos lead to big link attachment stories for WordPress links shared on Facebook, which could lead to blog posts appearing in the news feed of more people.

Bump the WordPress logo used in the og:image RDFa element to a PNG over 1200 pixels wide.

The og:image element is also used by Twitter and LinkedIn stories. Twitter requires the image is under 1 MB in size. Should not be a problem for the WordPress logo.

Change History (6)

#1 @Otto42
10 years ago

Really? 1200px of the logo? Seems like epic overkill. I mean, we can do it, but that is kinda sorta crazy. Maybe we need a different image for this case?

Ideas welcome.

#2 @dd32
10 years ago

Really? 1200px of the logo?

Yeah, they're figuring that a 300px image already needs to be 600px for 2x screens, and that 4x screens can't be too far off, so might as well do forward-thinking.

#3 @Otto42
10 years ago

Well, nothing against 1200px images, or using large images, but using the logo alone seems a bit absurd for this. I'm thinking we need a different image here, is what I'm saying.

If you examine the stories auto-posted on, they all show that logo image on the side. If we were to use a larger image, Facebook says the result would look like this:

And that would look strange with just the logo there.

We could even vary it up and have a selection of various images, one chosen randomishly for each post. It would certainly make our various posts in the FB page look better.

Note that for posts where we actually have images, like the 3.8 release post, the inline images are automatically used for the og:image urls, so those don't use the logo. The logo is only the default choice for posts without images.

#4 @niallkennedy
10 years ago

og:image is an RDFa array, allowing multiple suggested values for a page. If the story extractor is not happy with the images it finds, via meta[property=og:image] or a regular img element, it may keep looking for a larger image.

The post images should not be downsized unless over 5 MB (or 1 MB if you want Twitter to use og:image as its fallback, or specify a separate twitter:image to target separately). If you use a large WordPress image as the last option, after the post images, then it can act as a fallback before the body is scanned for img elements of a desired size.

3.8 launch example:

VideoPress 640px poster frame passed to imgPress to upside to 692

A image with a 122px width downsized to 90px for some reason

Large images associated with the post downsized

#5 @Otto42
10 years ago

Some of my old SFC code is creating those og:images, and the reason they're resized comes from the Jetpack photon code. Neither plugin knows about the other, which is why the resizing isn't handled properly. That's relatively minor, I'll look into making the og:image handler there smarter.

In posts with no images, the og:image defaults to because, hey, no other images in the post to choose from. A choice of alternate defaults could be implemented if I had some other images to use.

#6 @Otto42
9 years ago

  • Resolution set to duplicate
  • Status changed from new to closed

Moving this to #975, since the situation has changed a bit. We don't use the same plugin sets anymore.

Note: See TracTickets for help on using tickets.