Article

Proper structured data in your news, blog, and sports article page can enhance your appearance in Google Search results. Enhanced features include entry in a top stories carousel and rich result features such as headline text and larger-than-thumbnail images.

By structuring your content according to this guide, your content may be automatically turned into an action on the Google Assistant. You can learn more about Content Actions on the Actions on Google docs.

Examples

See JSON-LD code for an Article object example in the Structured Data Testing Tool.

<script type="application/ld+json"> { "@context": "http://schema.org", "@type": "NewsArticle", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://google.com/article" }, "headline": "Article headline", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "datePublished": "2015-02-05T08:00:00+08:00", "dateModified": "2015-02-05T09:20:00+08:00", "author": { "@type": "Person", "name": "John Doe" }, "publisher": { "@type": "Organization", "name": "Google", "logo": { "@type": "ImageObject", "url": "https://google.com/logo.jpg" } }, "description": "A most wonderful article" } </script>

See JSON-LD code for a Video object example in the Structured Data Testing Tool.

<script type="application/ld+json"> { "@context": "http://schema.org", "@type": "VideoObject", "name": "Introducing the self-driving bicycle in the Netherlands", "description": "This spring, Google is introducing the self-driving bicycle in Amsterdam, the world’s premier cycling city. The Dutch cycle more than any other nation in the world, almost 900 kilometres per year per person, amounting to over 15 billion kilometres annually. The self-driving bicycle enables safe navigation through the city for Amsterdam residents, and furthers Google’s ambition to improve urban mobility with technology. Google Netherlands takes enormous pride in the fact that a Dutch team worked on this innovation that will have great impact in their home country.", "thumbnailUrl": "https://www.example.com/thumbnail.jpg", "uploadDate": "2016-03-31T08:00:00+08:00", "duration": "PT1M54S", "publisher": { "@type": "Organization", "name": "Google Nederland", "logo": { "@type": "ImageObject", "url": "https://example.com/logo.jpg", "width": 600, "height": 60 } }, "contentUrl": "https://www.example.com/video/123/file.mp4", "embedUrl": "https://www.example.com/embed/123", "interactionCount": "5647018" } </script>

Implementation

Your page is eligible for different features depending on how you code your page:

• AMP with structured data: [Recommended] AMP pages with structured data can appear in a carousel of 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 or appearing in a top stories carousel.

AMP with structured data

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.
   If you have duplicate pages for the same content, we recommend placing the same structured data on all page duplicates, not just on the canonical page. For more information on placement, see the Structured Data General Guidelines.
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-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. The only properties supported for non-AMP structured data are the headline and image properties (and related sub-properties such as image.url), as well as the dateModified and datePublished properties.
2. Read the additional page 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.

Structured data type definitions

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

Article objects

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

AMP

The following properties apply to AMP pages.

Properties
author	Person or Organization, required The author of the article.
author.name	Text, required The name of the author.
dateModified	DateTime, recommended The date and time the article was most recently modified, in ISO 8601 format.
datePublished	DateTime, required The date and time the article was first published, in ISO 8601 format.
description	Text, recommended A short description of the article.
headline	Text, required The headline of the article. Headlines should not exceed 110 characters.
image	Repeated field of ImageObject or URL, required The URL to an image that is representative of the article. Additional image guidelines: 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": "http://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" ] }
mainEntityOfPage	URL, recommended The canonical URL of the article page. Specify mainEntityOfPage when the article is the primary topic of the article page.
publisher	Organization, required The publisher of the article.
publisher.logo	ImageObject, required The logo of the publisher. See the AMP logo guidelines for details.
publisher.logo.height	Number, required The height of the logo, in pixels.
publisher.logo.url	URL, required The URL of the logo.
publisher.logo.width	Number, required The width of the logo, in pixels.
publisher.name	Text, required The name of the publisher.

Non-AMP

The following properties apply to non-AMP pages.

Properties
dateModified	DateTime, recommended The date and time the article was most recently modified, in ISO 8601 format. Add the dateModified property if you want to provide more accurate date information to Google. The Structured Data Testing Tool doesn't show a warning for this property, as it's only recommended if you decide that it's applicable to your site.
datePublished	DateTime, recommended The date and time the article was first published, in ISO 8601 format. Add the datePublished if you want to provide more accurate date information to Google. The Structured Data Testing Tool doesn't show a warning for this property, as it's only recommended if you decide that it's applicable to your site.
headline	Text, recommended The headline of the article. Headlines should not exceed 110 characters.
image	Repeated field of ImageObject or URL, recommended 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": "http://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. Video objects are not supported on non-AMP pages.

Properties
name	Text, required The title of the video.
description	Text, required The description of the video.
thumbnailUrl	Repeated field of URL, required A URL pointing to the video thumbnail image file. 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 50K pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1. For example: "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ]
publisher.name	Text, required The name of the publisher.
publisher.logo	ImageObject, required The logo of the publisher. See AMP Logo Guidelines for additional guidance.
publisher.logo.url	URL, required The URL of the logo.
duration	Duration, recommended The duration of the video in ISO 8601 format.
contentUrl	URL, recommended A URL pointing to the actual video media file. This file should be in .mpg, .mpeg, .mp4, .m4v, .mov, .wmv, .asf, .avi, .ra, .ram, .rm, .flv, or other video file format. All files must be accessible via HTTPS. Metafiles that require a download of the source via streaming protocols, such as RTMP, are not supported. Providing this file allows Google to generate video thumbnails and video previews and can help Google verify your video.
embedUrl	URL, recommended A URL pointing to a player for the specific video. Usually this is the information in the src element of an <embed> tag.
interactionCount	Text, recommended The number of times the video has been viewed.
expires	Text, recommended If applicable, the date after which the video will no longer be available, in ISO 8601 format. Don't supply this information if your video does not expire.

Additional page guidelines

Pages should follow these guidelines to ensure a proper search experience.

Pagination and canonicalization

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.

Subscription and paywalled content

If you offer subscription-based access to your website content, or if users must register for access, implement structured data for subscription and paywalled content.

AMP logo guidelines

Logos for AMP pages must follow these guidelines:

General

• Files must be raster, such as .jpg, .png, or .gif, not vector, such as .svg.
• Animation is not allowed.
• Use full wordmark or full logo; not an icon.
• The graphic must be legible on a white or light background.
  

Size requirements

• The logo should 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 in the 600x60px rectangle.
  
• The text in word-based logos should be at most 48px tall and centered vertically against the 60px image height. Additional space should be added to pad the height to 60px.
  
• Logos with a solid background should include 6px minimum padding around the wordmark.