Has JSON-LD DataFeed

Abstract illustration of a JSON-LD DataFeed presence check streaming data records, in RankGear indigo and coral.

Has JSON-LD DataFeed reports whether RankGear finds a DataFeed @type declaration in a page’s raw HTML. It returns 1 when the string is present and 0 when it is not — but it pattern-matches source text, so a match is not proof of a valid, complete DataFeed graph.

Factor IDRG-SCJ-067
FamilyStructured Data — JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of DataFeed in a page’s raw source. It is a single presence check: the DataFeed schema type describes a genuine data feed — a named collection of data-feed elements from a stated provider — and this factor simply notes whether that type declaration appears in the markup.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "DataFeed", allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. It is a text match against source, not a parse of the JSON-LD graph.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DataFeed",
  "name": "Daily produce prices",
  "provider": { "@type": "Organization", "name": "Example Markets" },
  "dataFeedElement": [ /* DataFeedItem entries */ ]
}
</script>
ValueMeaning
1A DataFeed @type string was found in the raw HTML (case-insensitive, schema: prefix allowed).
0No matching DataFeed @type string was present in the source.
Back to Top

How to optimize it

Use DataFeed only for a genuine data feed — one with an accurate name, a stated provider, its contents, and real data-feed elements — and keep those properties matched to the content a visitor can actually see. Do not add the type to earn the 1: this is an observation about what markup exists, not a target to chase. If your page is not publishing a data feed, the correct value here is 0.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid or complete.
  • A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated text — can still produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently rather than relying on this presence check alone.
  • Presence correlates with pages that carry data-feed markup within a measured result set; it is a prioritization signal, not a guarantee of a ranking.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top