Why don’t my Twitter Cards show on Twitter?

Your website must be authorized by Twitter for each type of Twitter Card you want to publish. The NGFB Pro version supports the Summary, Large Image Summary, Photo, Gallery, Player and Product Cards. For each type card your website produces, you must submit a sample URL to Twitter’s validation tool:

  1. Make sure the ‘Enable Twitter Cards’ option is checked on the NGFB General settings page.
  2. Go to Twitter’s Card Validator.
  3. ‘Cancel’ the Card Catalog popup (these are just examples).
  4. Choose the ‘Validate & Apply’ tab.
  5. Enter an example URL from your website for the Twitter Card you would like to get approved. The Twitter Card type will depend on your webpage content (see following). For example, you could submit a standard post without images (Summary Card), one with a Featured image (Large Image Summary Card), a post with an embedded video (Player Card), an e-commerce product page (Product Card), etc.
  6. If the Twitter Card type has not been approved yet, you may click on the ‘Request Approval’ button.
  7. Fill-in and submit the form.

NGFB Pro automatically creates the required Twitter Card meta tags based on the content of your webpages.

  • Product : Product information from a supported e-commerce plugin.
  • Player : An embedded video in the content from YouTube, Vimeo, or Wistia.
  • Gallery Card : A WordPress Media Library gallery or NextGEN Gallery nggalbum, nggallery, nggtags shortcodes.
  • Photo Card : A WordPress Attachment Page or NextGEN Gallery ImageBrowser webpage.
  • Large Image Summary Card : An image defined in the Post or Page NGFB Social Settings metabox, a Featured, Attached, or NextGEN Gallery singlepic shortcode image.
  • Summary : All other webpages.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>