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

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

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.

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.

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.

Propiedades obligatorias
description

Text

Corresponde a la descripción del video.

name

Text

Corresponde al título del video.

publisher.logo

ImageObject

Corresponde al logotipo del editor. Consulta la guía específica en los lineamientos para logotipos de AMP.

publisher.logo.url

URL

Corresponde a la URL del logotipo.

publisher.name

Text

Corresponde al nombre del editor.

thumbnailUrl

Campo repetido de URL

Corresponde a una URL que dirige al archivo de imagen de la miniatura de video.

Lineamientos de imagen adicionales:

  • Cada página debe contener al menos una imagen (independientemente de si incluyen lenguaje de marcado o no). Google elegirá la mejor para mostrar en los resultados de la Búsqueda según la relación de aspecto y resolución.
  • Las URL de las imágenes se deben poder rastrear e indexar.
  • Deben representar el contenido con lenguaje de marcado.
  • Deben estar en formato .jpg, .png o .gif.
  • Para obtener mejores resultados, proporciona varias imágenes en alta resolución (mínimo de 50,000 píxeles al multiplicar el ancho por el alto) con la siguiente relación de aspecto: 16 × 9, 4 × 3 y 1 × 1.

Por ejemplo:

"image": [
  "https://example.com/photos/1x1/photo.jpg",
  "https://example.com/photos/4x3/photo.jpg",
  "https://example.com/photos/16x9/photo.jpg"
]
Propiedades recomendadas
contentUrl

URL

Corresponde a una URL que dirige al archivo multimedia de video real.

Asegúrate de seguir nuestras Recomendaciones de video.

duration

Duration

La duración del video en formato ISO 8601.

embedUrl

URL

Corresponde a una URL que dirige a un reproductor para el video específico. En general, esta información se encuentra en el elemento src de una etiqueta <embed>.

Asegúrate de seguir nuestras Recomendaciones de video.

expires

Text

Si corresponde, indica la fecha en que dejará de estar disponible el video. Debe mostrarse en formato ISO 8601. No incluyas esa información si el video no va a caducar.

interactionCount

Text

Indica la cantidad de reproducciones del video.