Hi @vdn-staff,
The Twitter card meta can now be read correctly :). So you took a step in the right direction!
I believe the issue now is that the twitter:image
links are scheme relative, but I’d assume they’d fix that locally… alas and unfortunately, they don’t.
On the 4th of November 2016, Twitter staff said:
You need to include a fully qualified domain and protocol (i.e. https://yoursite.com) before the image path. The fetcher grabs that image separately, so it can’t do relative lookups.
The SEO Framework never outputs scheme relative links. And your website forces HTTPS (which is good!), so I’d assume another plugin is conflicting here which rewrites URLs to become relative.
I would suggest, when possible, to alter the URL rewrite settings of the rewrite plugin to set all local URLs to HTTPS.
Twitter will refresh its image cache for your website, as there was none before. So all newly shared links should be correctly output on Twitter.
I hope this helps! Best of luck ??