#1

Description of issue:

Hi, we’re experiencing an issue where an image is not showing up in a Twitter share. We have all the required meta tags in place as specified in the Card documentation.

Also, Facebook’s share debugger seems to load the image just fine. The share image is hosted on Cloudinary.

URL affected (must be public):

https://areena.yle.fi/1-50996116

Image URL: https://images.cdn.yle.fi/image/upload/f_jpg,c_fill,w_1920,h_1080,q_auto/v1650574864/13-1-50996116-1649838023751

Troubleshooting steps attempted [note that we will not prioritise posts unless there is evidence of following the troubleshooting guides]:

I went through all of the troubleshooting steps mentioned in the link above, and the issue remains unsolved. Please see my findings below:

  • Card Validator indicates that the card’s metadata can be fetched successfully:
    INFO:  Page fetched successfully
INFO:  23 metatags were found
INFO:  twitter:card = summary_large_image tag found
INFO:  Card loaded successfully
  • When the page source is viewed, the right metadata tags are in place
  • The page contains twitter:card meta tag specifying a valid card type (summary_large_image)
  • Executing curl -v -A Twitterbot https://areena.yle.fi/1-50996116 in command line returns the correct meta tags. Server also returns a HTTP 200 response code and a valid Content-Type header (text/html; charset=utf-8).
  • Metadata is not added with JavaScript
  • Site and the image is fully accessible for Twitterbot/1.0 user-agent. There is no robots.txt in the site root, and the robots.txt on the image host is all commented out.
  • We are not using Wordpress (or other CMS/blogging platform) plugin
  • We are putting a specific URL into the Validator, and that URL is presented above.
  • We are using a supported Card type summary_large_image. There is no typo.
  • Image conforms to all the requirements. It’s 16:9 JPEG image, 1920 pixels wide and 1080 pixels tall, weighs about 0.12 megabytes. It has correct headers (content-type: image/jpeg). The image is referenced to with an absolute URL (with protocol piece as well).
  • We’re not seeing any validator error messages.
  • We’re using fully qualified DNS domain names.
1 Like
#2

This is really weird. Thanks for doing all the checks here.

The only thing I can currently think of is that the URL format is “unusual” with the comma-separated parameters in it. I don’t see other obvious reasons for this not to be working.

#3

Thank you for checking in, Andy. We have been using these Cloudinary transformation URLs containing commas for many years, and we’ve yet to come across with any issues.

Would it be possible for you to run some checks on your end? Do you happen to have any logging in place, that could help in figuring this out? If you need anything from me, just ask away. I hope we could sort this out as soon as possible.

#4

I was successfully able to get both the page and the image but I don’t have visibility to logs that would show why the image is not showing up. Have you used the transformation URLs for cards in the past? In that case, I’m happy to accept that is not the problem - it was just something that I spotted and thought could be a possible cause.

Does this happen to multiple pages, or only for this one page and image?