Articles

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.

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

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. Create your AMP page following Google's guidelines and the AMP 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.

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. The only properties supported for non-AMP structured data are the headline and image properties (and related sub-properties such as image.url).
  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 reference

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.

Sample markup

Example 1: JSON-LD

Example 2: Microdata

Property list for article structured data

Properties
mainEntityOfPage

URL; recommended (AMP), ignored (non-AMP)

The canonical URL of the article page. Specify mainEntityOfPage when the article is the primary topic of the article page.

headline

Text; required (AMP), recommended (non-AMP)

The headline of the article. Headlines should not exceed 110 characters.

image

ImageObject; required (AMP), recommended (non-AMP)

The representative image 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.
  • Images should be in .jpg, .png, or. gif format.
  • Image URLs should be crawlable and indexable.
image.url

URL; required (AMP), recommended (non-AMP)

The URL of the image.

image.height

Number; required (AMP), recommended (non-AMP)

The height of the image, in pixels.

image.width

Number; required (AMP), recommended (non-AMP)

The width of the image, in pixels. Images should be at least 696 pixels wide.

publisher

Organization; required (AMP), ignored (non-AMP)

The publisher of the article.

publisher.name

Text; required (AMP), ignored (non-AMP)

The name of the publisher.

publisher.logo

ImageObject; required (AMP), ignored (non-AMP)

The logo of the publisher. See the AMP logo guidelines for details.

publisher.logo.url

URL; required (AMP), ignored (non-AMP)

The URL of the logo.

publisher.logo.height

Number; required (AMP), ignored (non-AMP)

The height of the logo, in pixels.

publisher.logo.width

Number; required (AMP), ignored (non-AMP)

The width of the logo, in pixels.

datePublished

DateTime; required (AMP), ignored (non-AMP)

The date and time the article was first published, in ISO 8601 format.

dateModified

DateTime; recommended (AMP), ignored (non-AMP)

The date and time the article was most recently modified, in ISO 8601 format.

author

Person; required (AMP), ignored (non-AMP)

The author of the article.

author.name

Text; required (AMP), ignored (non-AMP)

The name of the author.

description

Text; recommended (AMP), ignored (non-AMP)

A short description of the article.

Video objects

Video objects must be based on the schema.org type VideoObject. Video objects are not supported on non-AMP pages.

Sample markup

Markup for video

Property list for video structured data

Properties
name

Text, required

The title of the video.

description

Text, required

The description of the video.

thumbnailUrl

URL, required

A URL pointing to the video thumbnail image file. Images must be at least 160x90 pixels and at most 1920x1080 pixels. We recommend images in .jpg, .png, or .gif formats. All image URLs should be crawlable and indexable. Otherwise, we will not be able to display them on the search results page.

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.

publisher.logo.height

Number, required

The height of the logo, in pixels.

publisher.logo.width

Number, required

The width of the logo, in pixels.

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.

Restricted content & First Click Free

If you offer subscription-based access to your website content, or if users must register for access, then search engines may not be able to access some of your site's most relevant content. If Google can't properly crawl and index your content (including text, images and videos), we can't show it in our search results. Implementing First Click Free is one easy way to make sure your content is accessible to Google's search crawlers so it can be displayed in Google search results. Learn more about First Click Free.

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.

Send feedback about...