Creating 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.

Structuring your Articles

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

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

Implementation

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.

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 can appear only as standard blue links in Google Search results.

To create an AMP page with structured data:

  1. Learn more about AMP on Google Search and follow the AMP Project specifications.
  2. Read 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.

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.

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.

Video objects

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

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.