MSN content expiration and takedown rules
Understand how to expire or remove content from MSN using supported metadata. This guide explains expiration logic, ingestion behavior for updated or duplicate items, and how to ensure your content takedowns are properly processed.
In this article
Setting expiration and updated dates
Setting expiration and updated dates
To remove content from MSN, include the following in your feed:
-
An expiration date in the past (relative to the current date and time)
-
An updated date that is newer than the last ingested version
-
The same unique ID used in the original feed item
This signals the ingestion system to unpublish the item during the next feed refresh.
For Media RSS feeds, you may also use the following tags at the item root level:
<dcterms:valid>2024-12-31T00:00:00Z</dcterms:valid> <mi:expirationDate>2024-12-31T00:00:00Z</mi:expirationDate>
Both must be paired with a newer <dcterms:modified> or updated date to trigger ingestion.
Understanding item status changes
MSN uses a combination of unique ID, updated date, and expiration date to determine the status of each feed item. The table below outlines how different combinations affect ingestion:
Context |
Action |
---|---|
No existing item with the same unique ID |
New item is created |
Same unique ID + updated date is newer |
Item is updated |
Same unique ID + no change in updated date |
Item is skipped (duplicate) |
Same unique ID + expiration date in the past + updated date is newer |
Item is deleted/taken down |
Avoiding duplicates in feed
To prevent ingestion errors and redundant updates:
-
Do not regenerate new Unique IDs on each feed pull.
-
Only change Updated Date when the item has truly changed.
-
Reuse media asset URLs unless the content has materially changed.
-
For Media RSS, update <dcterms:modified> to trigger re-ingestion.
Re-ingesting unchanged content wastes processing resources and may be skipped entirely by the system.