45
Twitterカードを使用すると、写真や動画などのリッチメディアをツイートに添付してウェブサイトへのトラフィックを促進できます。

ウェブページに数行のHTMLを追加するだけで、そのコンテンツへのリンクが含まれるツイートにカードが追加されるようになり、そのツイートを投稿したユーザーのすべてのフォロワーにカードが表示されます。
このサイトを見る
Developer Back Use cases Advertise Publish and curate Analyze Engage Products Accounts and users Tweets Direct Messages Metrics Ad campaigns Publisher tools and SDKs Docs Documentation API reference index Tutorials Changelog More Case studies Enterprise data Developer terms Pricing Billing FAQ Community Forum Blog Apply clip_official Basics Accounts and users Tweets Post, retrieve and engage with Tweets Get Tweet timelines Curate a collection of Tweets Optimize Tweets with Cards Search Tweets Filter realtime Tweets Sample realtime Tweets Get batch historical Tweets Rules and filtering Premium enrichments Tweet data dictionaries Tweet compliance Tweet updates Direct Messages Media Trends Geo Ads Metrics Developer utilities API reference index Publisher tools & SDKs Optimize Tweets with Cards Overview Guides Guides contents Getting started with cards CMS integration Troubleshooting cards Player card approval Getting Started Guide Getting Started with Cards Card and Content Attribution URL Crawling & Caching Card Display Multiple URLs in a Tweet Twitter Cards and Open Graph Getting Started with Cards To get started with implementing Cards markup, specify the type of card for your content by adding the following HTML markup to the HEAD section of the page: Card properties are simple key-value pairs, each defined in an HTML meta tag as seen above. The combined collection of properties defines the overall card experience on Twitter, and each card type supports and requires a specific set of properties. All cards have one basic property in common - the card type value: Card Property Description twitter:card The card type, which will be one of “summary”, “summary_large_image”, “app”, or “player”. Only one card type per-page is supported. If more than one twitter:card value exists in the page, the “last” one in sequence will take priority. Card and Content Attribution Each card has built-in content attribution, which surfaces appropriate Twitter accounts for the content as specified by you. Users will be able to follow and view the profiles of attributed accounts directly from the card. There are two kinds of attribution: Website Attribution: Indicates the Twitter account for the website or platform on which the content was published. Note that a service may set separate Twitter accounts for different pages/sections of their website, and the most appropriate Twitter account should be used to provide the best context for the user. For example, nytimes.com may set the the website attribution to “@nytimes” for front page articles, and “@NYTArts” for articles in the Arts & Entertainment section. Creator Attribution: Indicates the individual user that created the content within the card. This applies to the Summary with Large Image card. Configure card attribution using the following properties: Card Property Description Required twitter:site @username for the website used in the card footer. No twitter:creator @username for the content creator / author. No URL Crawling & Caching Twitter’s crawler respects Google’s robots.txt specification when scanning URLs. If a page with card markup is blocked, no card will be shown. If an image URL is blocked, no thumbnail or photo will be shown. Twitter uses the User-Agent of Twitterbot (with version, such as Twitterbot/1.0), which can be used to create an exception in the robots.txt file. For example, here is a robots.txt which disallows crawling for all robots, except Twitter’s fetcher: User-agent: Twitterbot Disallow: User-agent: * Disallow: / Here is another example, which specifies which directories are allowed to be crawled by Twitterbot (in this case, disallowing all except the images and archives directories): User-agent: Twitterbot Disallow: * Allow: /images Allow: /archives The server’s robots.txt file must be saved as plain text with ASCII character encoding. To verify this, run the following command: $ file -I robots.txt robots.txt: text/plain; charset=us-ascii Content is cached by Twitter for 7 days after a link to a page with card markup has been published in a Tweet. If you encounter issues with cards in Tweets not appearing properly, see the Cards Troubleshooting Guide. Card Display Twitter Cards generated from meta tags only appear when a Tweet is either expanded in the timeline (on web) or viewed on the Tweet’s individual permalink page (by clicking on the date from the timeline, either on web or on mobile). In limited circumstances, Cards may appear in the timeline, such as in images posted to Twitter, Ad formats, and Twitter-run experiments. If you are looking to bring media (photos, videos and Cards) into the timeline, consider one of the following options: Accounts can pin a Tweet to the top of their timeline, which auto-expands the Tweet and displays the Card. (This is possible on web only.). For photos and animated GIFs, upload the media directly with the Tweet or consider using the Twitter API to upload media. For Ad formats with a call-to-action, visit Twitter Ads for Website Cards. Multiple URLs in a Tweet In some circumstances, users may want to Tweet multiple URLs. Only one card may be shown in a Tweet. Here is the order of precedence when processing multiple URLs: Images or media attached to Tweets will have precedence over any card attached to a URL. URLs with cards are processed in order of appearance in the Tweet, first to last Twitter Cards and Open Graph Twitter card tags look similar to Open Graph tags, and are based on the same conventions as the Open Graph protocol. When using Open Graph protocol to describe data on a page, it is easy to generate a Twitter card without duplicating tags and data. When the Twitter card processor looks for tags on a page, it first checks for the Twitter-specific property, and if not present, falls back to the supported Open Graph property. This allows for both to be defined on the page independently, and minimizes the amount of duplicate markup required to describe content and experience. Note that while Open Graph recommends specifying the “og” RDFa Core 1.1 CURIE prefix mapping via , no such markup is required for Twitter cards and its use of the twitter: prefix in a HTML meta element’s name attribute. Open Graph protocol also specifies the use of property and content attributes for markup () while Twitter cards use name and content. Twitter’s parser will fall back to using property and content, so there is no need to modify existing Open Graph protocol markup if it already exists. The example below uses a mix of Twitter and Open Graph tags to define a summary card: Developer policy and terms Follow @twitterdev Subscribe to developer news About Let’s go Twitter Company Values Safety Blog Brand Resources Careers Investors Business About Twitter Ads Targeting Analytics Ads support Business blog Advertise Developers Documentation Forums Communities Developer blog Help Center Using Twitter Managing your account Safety and security Rules and policies Contact us Marketing Insights Success Stories Solutions Collections Marketing Blog Flight School © 2017 Twitter, Inc. Cookies Privacy Terms and Conditions Products Documentation Community Build My apps Twitter Developer Documentation Docs TwitterDevJP Twitterカード Products & Services Best practices API overview Twitter for Websites Twitter Kit Cards OAuth REST APIs Streaming APIs Webhook APIs Ads API Gnip MoPub Tools & Support My apps API console API status Translations 日本語 Twitterカード 埋め込みタイムライン 埋め込みシングルツイート 開発者契約 開発者ポリシー 開発者契約とポリシー Português, Brasil Español Français Resources Libraries Sample code Playbooks Case studies Join the community Events Developer terms Twitterカード English | 日本語 概要 Twitterカードを使用すると、写真や動画などのリッチメディアをツイートに添付してウェブサイトへのトラフィックを促進できます。ウェブページに数行のHTMLを追加するだけで、そのコンテンツへのリンクが含まれるツイートにカードが追加されるようになり、そのツイートを投稿したユーザーのすべてのフォロワーにカードが表示されます。 以下のツイートには、140文字のテキストの下にPlayerカードが表示されています。 Connect & discover: The Twitter story in 1:40 http://t.co/TRRiDAbkUR —Twitter Advertising (@TwitterAds) November 8, 2013 ツイートからのエンゲージメントの促進 以下のカードタイプは、Twitterのウェブクライアントおよびモバイルクライアント用にデザインされた素晴らしいユーザーエクスペリエンスを提供します。 Summaryカード: デフォルトのカードで、タイトル、説明、サムネイル、Twitterアカウントの属性が含まれています。 大きな画像付きのSummaryカード: Summaryカードに似ていますが、画像が目立つように使用されています。 Appカード: モバイルアプリの詳細を含めて直接ダウンロードできるようにしたカードです。 Playerカード: 動画やオーディオ、スライドショーを視聴できるカードです。 カードのメタタグおよびTwitterのウェブクローラの仕組みについては、「スタートガイド」をご覧ください。 ツイートからのアプリのダウンロードの促進 コンテンツをより魅力的な方法で表示するだけでなく、カードはモバイルアプリケーションのダウンロードを促進したり、モバイルアプリケーションに直接リンクすることもできます。詳細は、「モバイル開発者向けカード」をご覧ください。 簡単な5つの手順で始める 早速カードを使ってみましょう。ほとんどの場合、カードの実装には15分もかかりません。 実装するカードタイプを選択 適切なメタタグをページに追加 検証ツールでURLを実行して申請 承認を受けたら、URLをツイートしてツイートの下に表示されるカードを確認 Twitterカードの使用についてご質問がある場合は、Twitterカードに関するフォーラムに投稿してください。よろしくお願いいたします。 Solutions Build Customer service Tell great stories Products Publisher platform Twitter Kit REST APIs Streaming APIs Ads API Gnip Resources Documentation Forums Blog Case studies Developer terms Policy support Tools API status API console Cards validator Manage my apps Community #TapIntoTwitter Official partner Events Flight 2015 Flight 2014 © 2017 Twitter, Inc. Terms Privacy About Jobs Help