Build a News Action

Before your news content is eligible to show up in the Assistant directory, it'll need to be marked up according to this guide.

Make sure your content meets the following requirements:

• Associate your content with Google News: If your content is not already part of Google News, you can follow this quickstart guide to get started.
• Make sure your content is marked up for AMP: To mark up your content for AMP, please refer to AMP documentation in our search docs.
• Mark up your content as structured articles: To mark up your articles, add structured article data to your canonical site as outlined below in this guide.

By following this guide, your content may also be presented as a rich result in Google Search. For more information, see Introduction to Structured Data on the Search docs.

Structuring your Articles

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

<script type="application/ld+json"> { "@context": "https://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>

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

<script type="application/ld+json"> { "@context": "https://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

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.

Guidelines

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

Warning: If your site violates one or more of these guidelines, then Google may take manual action against it. Once you have remedied the problem, you can submit your site for reconsideration.

• Webmaster guidelines
• General structured data guidelines
• Technical guidelines
• AMP logo guidelines (if applicable)
• AMP story metadata requirements (if applicable)

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.

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.

Video objects

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

Required properties
description	Text The description of the video.
name	Text The title of the video.
publisher.logo	ImageObject The logo of the publisher. For AMP specific guidance, see AMP Logo Guidelines.
publisher.logo.url	URL The URL of the logo.
publisher.name	Text The name of the publisher.
thumbnailUrl	Repeated field of URL 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" ]

Recommended properties
contentUrl	URL We recommend that you provide a URL to your video. You can provide a URL by using one or both of the following properties: contentUrl and embedUrl. A URL pointing to the actual video media file. Example "contentUrl": "https://www.example.com/video/123/file.mp4" Make sure to follow our Video best practices. Tip: You can ensure that only Googlebot accesses your content by using a reverse DNS lookup.
duration	Duration The duration of the video in ISO 8601 format.
embedUrl	URL We recommend that you provide a URL to your video. You can provide a URL by using one or both of the following properties: contentUrl and embedUrl. A URL pointing to a player for the specific video. Usually this is the information in the src element of an <embed> tag. Example "embedUrl": "https://www.example.com/embed/123" Make sure to follow our Video best practices. Tip: You can ensure that only Googlebot accesses your content by using a reverse DNS lookup.
expires	Text 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.
interactionCount	Text The number of times the video has been viewed.