Has JSON-LD SomeProducts

This factor reports whether RankGear finds a JSON-LD @type of SomeProducts in a page’s raw source. It is a binary presence check (1 = found, 0 = not found), and because it matches source text rather than validating the structured-data graph, a hit only means the string is present — not that the markup is valid or complete.

What it measures

This factor reports whether RankGear finds an @type value of SomeProducts in the page’s raw source. SomeProducts is a schema.org type used to describe a group of related products — a product family or line rather than a single item. The check answers one question: is that type declared anywhere in the markup RankGear retrieved?

How RankGear measures it

RankGear searches the raw HTML for "@type": "SomeProducts", allowing flexible whitespace around the colon and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so capitalization differences in the source do not affect detection. If the pattern is found the factor returns 1; otherwise it returns 0.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SomeProducts",
  "name": "Trail Running Shoes",
  "model": "TR-2024",
  "offers": { "@type": "Offer", "price": "129.00", "priceCurrency": "USD" }
}
</script>

How to optimize it

Use SomeProducts only for a genuine group of related products, and give it accurate names, identifiers, models, offers, and relationships. Every property should reflect content a user can actually verify on the page. Do not add the type to score a 1 — treat this factor as an observation of what is present, not a target to chase. If your page truly describes a product group, valid SomeProducts markup is the honest way to express that; if it does not, adding the type misrepresents the page.

Important considerations

• The detector pattern-matches source text; it does not parse or validate a JSON-LD graph, so a 1 is not proof the structured data is well-formed.
• A matching string sitting outside valid JSON-LD — in a comment, an example, or escaped text — can still produce a 1.
• Capitalization differences in the source do not affect detection.
• Validate the complete structured data independently with a dedicated schema validator before relying on it.
• This is a correlation-based prioritization signal within a measured result set, not a cause of ranking. Presence of the type does not make a page rank or guarantee any position.

Related factors

• Has JSON-LD SoftwareApplication
• Has JSON-LD SportingGoodsStore

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