We dont want a Twitter Card inserted but it is taken automatically



We havent defined / choosen (no meta tag) any card to be taken for our tweets, but a few weeks ago, Twitter started to insert a photo with every tweet automatically, taken randomly from the bottom of our webpage msmag.ch (always the same image for every tweet). We then decided last week to at least insert a meta tag to choose the respective image. Actually, we prefer not to insert any card type and use only text tweets without Cards. If thats possible, what kind of meta tag does that need to prevent inserting cards/images automatically? If we are forced to choose a card type, can you please check whats wrong with our meta tag; it still takes the wrong image (checked with Card Validator) and not the one we have defined:

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:creator" content="@msmag" />
<meta name="twitter:image" content="http://msmag.ch/ITNews-min.jpg" />
<meta name="twitter:description" content="Fundierte Studien, Marktdaten, Prognosen, Trends und Erkenntnisse zum ICT-Markt Schweiz. Events für ICT-Anbieter und ICT-Verantwortliche / CxOs." />
<meta name="twitter:title" content="Expertise und Know How im ICT-Markt" />


This is probably a case where you site has OpenGraph markup and the cards crawler is using that to create a card. If you recently changed the image that you’re requesting for the card to display, then it may take up to a week for the cache to expire and be refreshed.

When I run curl -L -v http://msmag.ch/ITNews-min.jpg I do not get back a JPEG so there’s no way the image can be displayed. I suspect something is cached.


Hi all,

a customer of my employer has notified the same Problem as @msmresearch last week.
He does not want to use the card feature, unfortunately any link to a .html or .jsp page is now displayed as summary-card. He is using twitter for years and told us it has never been shown up like this.

@andypiper your hint about OpenGraph led us to one possible workaround. Since the customer uses “og:description”, which is handled by twitter in the same way as “twitter:description” https://dev.twitter.com/cards/markup. This meta-Tag may be deleted to cause the following error on card-validator https://cards-dev.twitter.com/validator
ERROR: Invalid value (message: Field description failed to validate because: text expects tag property, but not found in Map().)
Therefore, no card would be displayed.

But this is not exactly what we want. It sould not be necessary to delete the og:description-Meta-Tag. Since https://dev.twitter.com/cards/markup defines no openGraph equivalent for “twitter:card” it should be necessary for a card to be put as meta-information into the html-page. I have searched the page-source and there is no such tag within. In the end I have counted 22-Meta-Tags in total. Unfortunately https://cards-dev.twitter.com/validator has found 24-Meta-Tags including “twitter:card”.
INFO: twitter:card = summary tag found

Does anyone has a clue how “twitter:card” can be found by https://cards-dev.twitter.com/validator without being in the page source?


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