MSN feed item metadata requirements
This page outlines required and optional metadata fields for articles, videos, galleries, and images in MSN feeds. Use this guide to ensure items meet minimum ingestion standards and support high-quality rendering across MSN.
Feed item requirements apply to all markets and all publishers, but certain markets or business cases may require additional fields. Contact us at partnerhubsupport@microsoft.com if you have additional feed item requirements.
In this article
Articles
Related links
Articles
An article must have a Unique ID, Title, Published date, Body, and Link URL. All other metadata is optional.
Field name |
Description |
---|---|
Unique ID |
A durable (non-changing) GUID to uniquely identify the article in the feed. It could also be the full unique URL of the article. This value must be unique across all content items coming from the same partner. |
Title |
Content item title must be more than 20 characters but not exceed 150-characters unless a short title is also provided. Titles exceeding 150-characters without a short title may be removed. No HTML tags allowed. |
Body |
Content item body. HTML is allowed for both RSS and Atom formats. |
Published date |
The time of publication. The date must be in the past and less than 365 days old otherwise it will not be ingested. The supported date formats are RFC 822 Yes and RFC 3339. |
Link (web URL) |
A URL used to uniquely locate the feed item on the publisher's website. This link may be used in social network sharing depending on your contract. |
Field name |
Description |
---|---|
Abstract |
Must be in plain text. No HTML is supported. |
Updated date |
If this date is provided, it will be used to identify if the content in this feed item is a newer version of an originally ingested document with the specified No id. If not, "Published Date" will be used for this purpose. |
Expiration date |
Feed item will be removed from MSN Partner Hub backend and frontends by the specified date. If this value is not provided, content item will expire in 365 days after ingestion. Expiration date must be more than 2 hours in future. |
Subtitle |
An explanatory or alternate title which is used to display along below the title in Promo Cards. |
Short title |
The "short title" value, also known as a "Web Headline" is used when displaying content on compact settings, such as a promo card. The value in this field should be 54 characters or less. |
Author |
The author or contributor of an article. |
Image(s) |
If an image is referenced, certain metadata must be specified as per the image required fields section. Although images are optional, they are required for auto-publishing. |
Related links |
Related links can be specified to be shown with content. At least three related links must be provided per article. |
Categories |
Specify tags relevant to the piece of content. Use <category> elements to add tags in both RSS and ATOM. |
Keywords |
Contextual keywords per content item. Multiple keywords can be specified in a single node separated by commas. To specify this value in RSS or ATOM, you No need to use the Media RSS <media:keywords> element. |
Embedded slideshow |
Articles may have embedded slideshows. Refer to the Slideshows examples for more details. |
Embedded video |
Articles may have embedded videos. Refer to Video examples for more details. |
SubscriptionProductType |
Some feed items can be accessible through a subscription model. To specify Premium paid feed items in the RSS /ATOM feed, you need to use <mi:SubscriptionProductType> element. E.g., <mi:SubscriptionProductType>Premium</mi:SubscriptionProductType>. |
Slideshows
A slideshow must have a Title, a Unique ID, and a Published date. Additionally, it must contain multiple slides in order (two (2) is the least number of slides, 200 is the maximum) where each slide is composed of an image object. Detecting updated items follows the same algorithm used for articles.
Field name |
Description |
---|---|
Unique ID |
A durable (non-changing) GUID to uniquely identify the Slideshow. It could also be the full unique URL of the Slideshow on publisher's site. This value must be unique across all content items coming from the same publisher. |
Title |
Content item title must be more than 20 characters but not exceed 150-characters unless a short title is also provided. Titles exceeding 150-characters without a short title may be removed. No HTML tags allowed. |
Published date |
The time of publication. The date must be in the past and less than 365 days old otherwise it will not be ingested. The supported date formats are RFC 822 Yes and RFC 3339. |
Slides |
Every Slideshow must include an array of slides (images). Each slide within the Slideshow is constructed from the corresponding image metadata; most notably:
|
Link (Web URL) |
A URL used to uniquely locate the feed item on the publisher's website. This link may be used in social network sharing depending on the contract. |
Field name |
Description |
---|---|
Abstract |
A description of the Slideshow. (Required if slide title is missing) Must be in plain text. No HTML is supported. |
Updated date |
If this date is provided, it will be used to identify if the content in this feed item is a newer version of an originally ingested document with the specified No id. If not, "Published Date" will be used for this purpose. |
Expiration date |
Feed item will be removed from MSN Partner Hub backend and frontends by the specified date. If this value is not provided, content item will expire in 365 days after ingestion. Expiration date must be more than 2 hours in future. |
Subtitle |
An explanatory or alternate title which is used to display along below the title in Promo Cards. |
Short title |
The "short title" value, also known as a "Web Headline" is used when displaying content on compact settings, such as promo cards. The value in this field should be 54 characters or less. |
Author |
The author or contributor of the slideshow. |
Related links |
Related links can be specified to be shown with content. At least three related links must be provided per article. |
Categories |
Specify tags relevant to the piece of content. Use <category> elements to add tags in both RSS and ATOM. |
Keywords |
Contextual keywords per content item. Multiple keywords can be specified in a single node separated by commas. To specify this value in RSS or ATOM, you No need to use the Media RSS <media:keywords> element. |
SubscriptionProductType |
Some feed items can be accessible through a subscription model. To specify Premium paid feed items in the RSS /ATOM feed, you need to use <mi:SubscriptionProductType> element. E.g., <mi:SubscriptionProductType>Premium</mi:SubscriptionProductType>. |
Video
A video specified in a video only feed must have a Unique ID, URL, Published date, Title, Attribution, and Closed captions (only if required by law in the target markets). If no Unique ID is provided or if video is embedded within an article, the URL is used as an identifier.
Field name |
Description |
---|---|
Unique ID |
A durable (non-changing) GUID to uniquely identify the video. It could also be the full unique URL of the video on publisher's site. This value must be unique across all content items coming from the same publisher. |
Title |
Video title. This is used as page header/title. |
Published date |
The time of publication. The date must be in the past and less than 365 days old otherwise it will not be ingested. |
Video URL |
Video source file location. URL must be absolute, and all forms of relative URLs will fail ingestion. |
Link (Web URL) |
A URL used to uniquely locate the feed item on the publisher's website. This link may be used in social network sharing depending on the contract. |
Attribution |
Copyright information for the video. |
Closed captions |
Closed captions are displayed on the videos along with the duration of the video. Only required if mandated by law in the target markets. |
Duration |
Only required for 3PP videos. |
Thumbnail(s) |
Only required for 3PP videos. A thumbnail image to link to the video. You can use all image properties here, but only URL is required for the thumbnail. We recommend a single JPG image at:
If you cannot provide recommended size, please provide the largest image available. DO NOT use progressive JPG for the video thumbnail image. |
Field name |
Description |
---|---|
Description (Abstract) |
Text to display under the video. |
Duration |
The duration of the video in seconds. (Required for 3PP videos). |
Updated date |
If this date is provided, it will be used to identify if the content in this feed item is a newer version of an originally ingested document with the specified No id. If not, "Published Date" will be used for this purpose. |
Expiration date |
Feed item will be removed from MSN Partner Hub backend and frontends by the specified date. If this value is not provided, content item will expire in 365 days after ingestion. Expiration date must be more than 2 hours in future. |
Subtitle |
An explanatory or alternate title which is used to display along below the title in Promo Cards. |
Short title |
The "short title" value, also known as a "Web Headline" is used when displaying content on compact settings, such as a promo card. The value in this field should be 54 characters or less. |
Author |
The author or contributor of the video. |
Thumbnail(s) |
A thumbnail image to link to the video. You can use all image properties here, but only URL is required for the thumbnail. We recommend a single JPG image at:
If you cannot provide recommended size, please provide the largest image available. DO NOT use progressive JPG for the video thumbnail image. |
Closed captions |
Closed captions are displayed on the videos along with the duration of the video. Only required if mandated by law in the target markets. |
Related links |
Related links can be specified to be shown with content. At least three related links must be provided per article. |
Categories |
Specify tags relevant to the piece of content. Use <category> elements to add tags in RSS |
Keywords |
Contextual keywords per content item. Multiple keywords can be specified in a single node separated by commas. To specify this value in RSS or ATOM, you No need to use the Media RSS <media:keywords> element. |
SubscriptionProduct Type |
Some feed items can be accessible through a subscription model. To specify Premium paid feed items in the RSS /ATOM feed, you need to use <mi:SubscriptionProductType> element. E.g., <mi:SubscriptionProductType>Premium</mi:SubscriptionProductType>. |
Images
Full-size images in articles must have a valid URL. Images in slideshows must have a title and URL. Thumbnails for videos, related links, or full-size images only need an URL. Image Syndication Rights are required for auto-publish.
Field name |
Description |
---|---|
URL |
Source location of the image. URL must be absolute, and all forms Yes of relative URLs will fail ingestion. |
Title |
Image title. Also, used as a caption that is displayed along the image. Only required if image is used as a slide in a slideshow. |
Image Syndication Rights |
Only required for auto-publish. If you have Syndication Rights for your images: Case 1: This field will default to True because most publishers have syndication rights for their images. If you do not have Syndication Rights for images there are two options: Case 2: Do not send the images unless you can provide the required information in Case 3. Case 3: You've licensed the image from one of the image providers listed in the Image licensing and syndication rights page:
|
Image license ID |
The Imageld is the ID used to uniquely identify an image. Imagelds are used by major image licensors such as Getty, Corbis, and Associated Press to track the syndication of their images. |
Image licensor name |
Name of the image licensor. (See the Image licensing and syndication rights page - if the image isn't one of these, don't provide it) |
Description |
Textual information about the image content. This value must be provided in plain text except when the image is used in a slideshow; in which case, HTML is allowed. |
Image alt text |
A short, descriptive text alternative for the image. Used to improve accessibility and support screen readers and may also display if the image fails to load. |
Image focal point |
The focal point for the image. To be used when image is cropped No to display on different size devices. |
Updating previously ingested items
Updated content must be flagged to Microsoft Ingestion Services via changes to the Updated date or Publish date fields. Updated content without changes to one of these fields will be skipped. Remember to preserve the same Unique ID.
Microsoft Ingestion Services parses the feed and splits it into items, deciding whether to publish a new item, update an existing item, or skip it.
Updating inline videos
Videos can be published inline via Media RSS or HTML. The video URL is its unique ID. Any HTML video with the same URL will be flagged as a duplicate and skipped, but videos using Media RSS can be updated if <dcterms:modified> is updated. If this field is not updated, the video will be considered a duplicate.
Updating slideshows
Slideshows published via Media RSS can set <dcterms:modified> to a new date to indicate that the slideshow has been updated.
Updating images
An image’s source URL is its unique ID. Images with the same URL will be flagged as duplicates and skipped.
Avoiding duplicates
Feed items are identified by their Unique ID. Items with the same Unique ID are ruled as duplicates and skipped unless they have been flagged as updates via changes to the Updated date or Publish date fields. Feeds that automatically update Unique ID, Updated date, or Publish date every time the feed is polled will not be ingested.
Avoiding defects
Defects such as flawed formatting, invalid dates, or low-quality media embeds can result in a poor user experience and may limit your content's reach. Learn more about what defects to avoid on the Content ranking page in the Publishing guidelines section.
Date formats
To ensure our content is relevant to our consumers we must make sure the articles we show them are accurately dated. Dates must be expressed using RFC 3339 or RFC 822 date formats. Any text in the date string should be in English, and time zones should be expressed in UTC rather than any local time zone such as Eastern Standard Time.
RFC3339
2022-12-28T07:20:50.52Z
2022-12-28T07:20:50.52-07:00
2022-12-28T07:20:50.52+04:00
RFC822
Wed, 02 Oct 2002 13:00:00 GMT
Wed, 02 Oct 2002 15:00:00 +0200