Thanks for the response. In looking through our output versus the example provided by Twitter, here’s what we have:
Sumary Large Image Twitter Example:
Startups.co Output Example (https://www.startups.co/articles/value-time-business-owner):
The big differences are:
(1) We do not include the recommended in the Troubleshooting guide.
(2) We are missing the / at the end of the meta tags (although Twitter’s example for Large Image Summary Cards doesn’t include it either).
(3) Our tags include data-react-helmet=“true” due to our site’s use of React.js.
In reading the other troubleshooting doc, I’m thinking the following could be an issue:
if you execute curl -v -A Twitterbot at the command prompt, does your page still show the twitter:card tags in the section of the page? Does your server return a 200 response code and a valid Content-Type header?
Apologies as I’m not familiar with cURL so I couldn’t do what you did, but I know our site is using prerendering, so I’m wondering if the issue is that the tags (which seem fairly close to Twitter’s examples) are simply getting rendered late due to the JS on our site. If that’s the case, is there another solution for whitelisting? Many site’s use JS rendering and tech like React, so I’d hate to think that all sites using this are unable to be whitelisted.
Speaking with our dev team this morning to get that tag implemented.
Any advice would be helpful.