Article

Adding structured data to your news, blog, and sports article page can enhance your appearance in Google Search results. Enhanced features can include placement in the Top stories carousel, host carousel, Visual stories, and rich result features such as headline text and larger-than-thumbnail images. Your page may be eligible for different features depending on how you code your page:

  • AMP with structured data: [Recommended] AMP pages with structured data can appear in the Top stories carousel, host carousel of rich results, Visual stories, and rich results in mobile Search results. These results can include images, page logos, and other interesting search result features.
  • Non-AMP web page with structured data: Non-AMP article pages that include structured data can increase the likelihood of appearing in search results with rich result features.

Examples

Here's an example of JSON-LD code for an Article object.

Here's an example of JSON-LD code for a Video object.

Implementation

AMP with structured data

A carousel of AMP results for a news article.

AMP pages that have structured data can appear in a carousel of stories in search results. Without structured data, AMP pages may only appear as standard blue links in Google Search results. For more information about AMP in search results, see About AMP on Google Search.

To create an AMP page with structured data:

  1. Follow the AMP Project specifications.
  2. Follow the additional page guidelines to ensure that Google can crawl your page.
  3. Add a structured data element describing the article or video on the page.
  4. Test your structured data using the Structured Data Testing Tool.

Non-AMP page with structured data

Non-AMP pages can be shown as a rich result in a rich result list, or in a carousel of similar non-AMP pages. Rich results can include headlines and images. Although Google can try to extract enough information from your page automatically to qualify for these features, if you include structured data on the page it can help Google better understand your page content and increase the likelihood of a rich or carousel result.

Non-AMP search results can include a headline and an image, as shown here:

Two non-AMP results for a news article, one with an image, one without an image. Non-AMP results for "top sport stories" showing an AMP page with an image and clip.
Two non-carousel results for non-AMP web pages. Carousel results for non-AMP web pages

To add structured data to your non-AMP article page:

  1. Add a structured data element to your page, describing the article or video on the page.
  2. Read the guidelines to ensure that Google can crawl your page.
  3. Test your structured data using the Structured Data Testing Tool.

Google recommends creating an AMP version of your page to provide a better user experience on mobile devices. Read more about the benefits of AMP on mobile devices.

Guidelines

You must follow these guidelines to enable structured data to be eligible for inclusion in Google Search results.

Technical guidelines

  • If you offer subscription-based access to your website content, or if users must register for access, you should add structured data for subscription and paywalled content.
  • For multi-part content, proper pagination markup using rel=next and rel=prev can help our algorithms correctly identify the extent of those articles. In addition, it's important that canonicalization is done correctly, with a rel=canonical pointing at either each individual page, or a "view-all" page (and not to page 1 of a multi-part series). Learn more about pagination and canonicalization.

AMP logo guidelines

The following guidelines apply to logos for all AMP pages, including AMP stories.

  • The file must be a raster file, such as .jpg, .png, or .gif. Don't use vector files, such as .svg or .eps.
  • Don't use animation.
  • The graphic part of the logo should be legible on the background color.

The following guidelines apply to logos used for general AMP pages, not AMP stories. There are different logo requirements for AMP stories.

  • The logo must be a rectangle, not a square.
  • The logo should fit in a 60x600px rectangle, and either be exactly 60px high (preferred), or exactly 600px wide. For example, 450x45px would not be acceptable, even though it fits within the 600x60px rectangle.

  • Publishers should use only one logo per brand that is consistent across general AMP pages.
  • Use full wordmark or full logo; not an icon.
  • The text in word-based logos should be at most 48px tall and centered vertically within the 60px image height. Add additional space to pad the height to 60px.

  • Logos with a solid background should include 6px minimum padding around the graphic.

Structured data type definitions

The following sections describe the properties requirements for Article and Video structured data.

You must include the required properties for your content to be eligible for display as a rich result. You can also include the recommended properties to add more information about your content, which could provide a better user experience.

Article objects

Article objects must be based on one of the following schema.org types: Article, NewsArticle, BlogPosting.

AMP

The following properties apply to AMP pages.

Required properties
author

Person or Organization

The author of the article.

author.name

Text

The name of the author.

datePublished

DateTime

The date and time the article was first published, in ISO 8601 format.

Best practices:

  • The date shouldn't change over time.
  • We recommend including the hour information in addition to the day in the timestamp.
  • The value for dateModified should be more recent than the value for datePublished.
headline

Text

The headline of the article. Headlines should not exceed 110 characters. For AMP stories, the headline should match the text in the first cover page in the AMP Story.

image

Repeated field of ImageObject or URL

The URL to an image that is representative of the article or AMP story.

Due to format differences in search results, the following image guidelines only apply to general AMP pages, not AMP stories. AMP stories have different requirements for images.

  • Only a marked-up image that directly belongs to the article should be specified.
  • Images should be at least 1200 pixels wide.
  • Every page must contain at least one image (whether or not you include markup). Google will pick the best image to display in Search results based on the aspect ratio and resolution.
  • Image URLs must be crawlable and indexable.
  • Images must represent the marked up content.
  • Images must be in .jpg, .png, or .gif format.
  • For best results, provide multiple high-resolution images (minimum of 800,000 pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1.

For example:

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "image": [
    "https://example.com/photos/1x1/photo.jpg",
    "https://example.com/photos/4x3/photo.jpg",
    "https://example.com/photos/16x9/photo.jpg"
  ]
}
publisher

Organization

The publisher of the article.

publisher.logo

ImageObject

The logo of the publisher. See the AMP logo guidelines for details.

publisher.logo.height

Number

The height of the logo, in pixels.

publisher.logo.url

URL

The URL of the logo.

publisher.logo.width

Number

The width of the logo, in pixels.

publisher.name

Text

The name of the publisher.

Recommended properties
dateModified

DateTime

The date and time the article was most recently modified, in ISO 8601 format.

description

Text

A short description of the article.

mainEntityOfPage

URL

The canonical URL of the article page. Specify mainEntityOfPage when the article is the primary topic of the article page.

Non-AMP

The following properties apply to non-AMP pages.

Recommended properties
dateModified

DateTime

The date and time the article was most recently modified, in ISO 8601 format.

datePublished

DateTime

The date and time the article was first published, in ISO 8601 format.

headline

Text

The headline of the article. Headlines should not exceed 110 characters.

image

Repeated field of ImageObject or URL

The URL to an image that is representative of the article. Only a marked-up image that directly belongs to the article should be specified. Images should be at least 696 pixels wide.

Additional image guidelines:

  • Every page must contain at least one image (whether or not you include markup). Google will pick the best image to display in Search results based on the aspect ratio and resolution.
  • Image URLs must be crawlable and indexable.
  • Images must represent the marked up content.
  • Images must be in .jpg, .png, or. gif format.
  • For best results, provide multiple high-resolution images (minimum of 300,000 pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1.

For example:

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "image": [
    "https://example.com/photos/1x1/photo.jpg",
    "https://example.com/photos/4x3/photo.jpg",
    "https://example.com/photos/16x9/photo.jpg"
  ]
}

Video objects

Video objects must be based on the schema.org type VideoObject.

必要屬性
description

Text

影片的說明。

name

Text

影片的標題。

publisher.logo

ImageObject

發佈者的標誌。如需 AMP 專屬規範,請參閱 AMP 標誌指南

publisher.logo.url

URL

標誌的網址。

publisher.name

Text

發佈者的名稱。

thumbnailUrl

URL 的重複欄位

指向影片縮圖檔案的網址。

其他圖片規範:

  • 每一頁都必須包含至少一張圖片 (無論是否已加上標記)。Google 會根據長寬比和解析度選擇最適當的圖片顯示在搜尋結果中。
  • 圖片網址必須可供檢索和建立索引
  • 圖片必須代表加上標記的內容。
  • 圖片必須採 .jpg、.png 或 .gif 格式。
  • 為獲得最佳效果,請提供多張高解析度圖片 (寬度乘以高度至少要 5 萬像素),長寬比分別為 16x9、4x3 和 1x1。

例如:

"image": [
  "https://example.com/photos/1x1/photo.jpg",
  "https://example.com/photos/4x3/photo.jpg",
  "https://example.com/photos/16x9/photo.jpg"
]
建議屬性
contentUrl

URL

指向實際影片媒體檔案的網址。

請務必遵循我們的影片最佳做法

duration

Duration

影片的片長 (採用 ISO 8601 格式)。

embedUrl

URL

指向特定影片播放器的網址。一般來說,這是 <embed> 標記中 src 元素的資訊。

請務必遵循我們的影片最佳做法

expires

Text

採用 ISO 8601 格式的影片到期日,使用者在該日期後將無法再觀看這部影片 (如適用)。如果您沒有為影片設定有效期限,請不要提供這項資訊。

interactionCount

Text

影片的觀看次數。

傳送您對下列選項的寶貴意見...

這個網頁