Card validator doesn't display image


#1

Card URL:
https://www.downpour.com/catalog/product/view/id/20977?sp=199549

*.downpour.com is whitelisted for summary card

INFO: Page fetched successfully
INFO: 22 metatags were found
INFO: twitter:card = summary tag found
INFO: Card loaded successfully

Image doesn’t render in card validator.


#2

What troubleshooting steps have you checked from the pinned topic?


#3

All, from the following post:


#4

<meta property="og:image" content="//d1exhaoem38lup.cloudfront.net/6/5/6598/6598-square-400.jpg"/>

That is not a complete https URL.

Are you using an absolute and full URL (including the http protocol piece), not a relative one?


#5

Andy,

First off, thank you for the reply. I’ve updated both our Open Graph and Twitter Card tags to use a secure protocol. The Twitter card validator now displays the image.

Happy Friday,

-Chris S.


#6

Hi Andy,
Same problem here https://orioniconlibrary.com/ where the Card Validator from two weeks now returns an old image since the new card config is for player, and for https://orioniconlibrary.com/app is set to summary_large_image and the Card Validator return “WARN: No metatags found”. The urls are absolute in all cases. Any idea what could happen? Thanks in advance.


#7

It looks like the validator probably cannot see your meta tags as they are in the format:

<meta data-react-helmet="true" name="twitter:card" content="summary_large_image"/>

If you switch this to <meta name="twitter:card" content="summary_large_image"> I suspect this will be picked up correctly.


#8

Hi Andy,
Everything updated to avoid extra data-* attributes.
There is an open issue related in react-helmet.
I tried several times the card validator but return the same result as before. Any ideas?

Thanks again,


#9

It looks like your server is also not returning a Content-Type header.

Does your server return a 200 response code and a valid Content-Type header?


#10

with curl I receive a HTTP/1.1 200 OK


#11

Yes, but no Content-Type header.


#12

Awsome, solved adding Content-type also. Thanks Andy!


#13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.