XooCode(){

DataFeedItem

DataFeedItem is an Intangible for a single element inside a DataFeed. It adds 4 direct properties:

  • dateCreated (Date or DateTime): when the item was first added to the feed.
  • dateModified (Date or DateTime): last update.
  • dateDeleted (Date or DateTime): when the item was removed from the feed (tombstone marker).
  • item (Thing): the actual payload — a typed entity being fed (Observation, Product, Event, etc.).

Full example of schema.org/DataFeedItem json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/DataFeedItem
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DataFeedItem",
  "@id": "https://dunmore.gov.example/open-data/air-quality/feed/2026-04-15T09",
  "dateCreated": "2026-04-15T09:00:00-04:00",
  "dateModified": "2026-04-15T09:05:00-04:00",
  "item": {
    "@type": "Observation",
    "measuredProperty": "PM2.5",
    "observationDate": "2026-04-15T09:00:00-04:00",
    "observationAbout": { "@type": "Place", "name": "Dunmore Memorial Park Monitoring Station" },
    "value": 8.2,
    "unitText": "µg/m³",
    "marginOfError": 0.4
  }
}
</script>

Tombstone pattern

Deletions in a feed are expressed by leaving the item in place and setting dateDeleted. This lets consumers know a previously-published item has been retracted without scanning for absence.

Minimal valid version

The smallest markup that still produces a valid DataFeedItem entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/DataFeedItem (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DataFeedItem",
  "dateCreated": "2026-04-15T09:00:00-04:00",
  "item": { "@type": "Observation", "value": 8.2 }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

  • Dataset / feed consumer (via parent DataFeed)
    Google docs

Common DataFeedItem mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Deletion by omission

    Wrong
    Dropping items from the feed when retracted
    Right
    Leaving the item with dateDeleted populated

    Consumers cannot distinguish 'not yet emitted' from 'withdrawn' without an explicit tombstone.

About the example data

A single hourly air-quality reading inside the Dunmore feed.

Comments

Loading comments...

Leave a comment