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

로고의 URL입니다.

publisher.name

Text

게시자 이름입니다.

thumbnailUrl

URL의 반복되는 입력란

동영상 썸네일 이미지 파일을 가리키는 URL입니다.

추가 이미지 가이드라인

  • 모든 페이지에는 마크업 포함 여부와 관계없이 하나 이상의 이미지가 있어야 합니다. Google에서 가로세로 비율과 해상도를 기반으로 검색결과에 표시할 최적의 이미지를 선택합니다.
  • 이미지 URL은 크롤링 및 색인 생성이 가능해야 합니다.
  • 이미지가 마크업된 콘텐츠를 나타내야 합니다.
  • 이미지는 .jpg, .png 또는 .gif 형식이어야 합니다.
  • 최상의 결과를 위해서는 가로세로 비율이 16x9, 4x3, 1x1인 여러 개의 고해상도 이미지(너비와 높이의 곱이 최소 50,000픽셀)를 제공하세요.

예:

"image": [
  "https://example.com/photos/1x1/photo.jpg",
  "https://example.com/photos/4x3/photo.jpg",
  "https://example.com/photos/16x9/photo.jpg"
]
권장 속성
contentUrl

URL

실제 동영상 미디어 파일을 가리키는 URL입니다.

동영상 권장사항을 따라 주세요.

duration

Duration

동영상의 길이입니다. ISO 8601 형식으로 나타냅니다.

embedUrl

URL

특정 동영상 플레이어를 가리키는 URL입니다. 보통 <embed> 태그의 src 요소에 있는 정보입니다.

동영상 권장사항을 따라 주세요.

expires

Text

해당하는 경우 동영상을 더 이상 사용할 수 없게 되는 날짜입니다. ISO 8601 형식으로 나타냅니다. 동영상이 만료되지 않는 경우에는 이 정보를 제공하지 마세요.

interactionCount

Text

동영상의 조회 수입니다.

다음에 대한 의견 보내기...