Has JSON-LD AutoDealer

Has JSON-LD AutoDealer reports whether the page’s raw HTML contains an @type of AutoDealer in its JSON-LD structured data. It returns a simple yes/no (1 or 0) — and because RankGear matches the source text rather than parsing a schema graph, a bare string match can register even outside a valid script.

Factor IDRG-SCJ-022
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 AutoDealer in the raw source of the page. AutoDealer is the schema.org type that describes a business selling new or used vehicles, letting search engines associate a page with a dealership entity and its inventory, location, contact, and offer data. The result is a binary observation: the type string is present, or it is not.

How RankGear measures it

RankGear searches the raw HTML for "@type": "AutoDealer", allowing flexible whitespace around the colon and optionally a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not affect detection.

What RankGear looks for

"@type":\s*"(schema:)?AutoDealer"   // case-insensitive, flexible whitespace
ValueMeaning
1An @type of AutoDealer was found in the raw HTML.
0No AutoDealer type string was present.

How to optimize it

Use AutoDealer only for a genuine dealership, and populate it with accurate inventory, location, contact, and offer data so the markup describes a real business. Because RankGear pattern-matches source text rather than validating a JSON-LD graph, treat a score of 1 as confirmation that the type string exists — not as proof the surrounding structured data is well-formed. Validate the full graph in a dedicated structured-data testing tool before relying on it.

Important considerations

  • RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph, so a passing result does not confirm the markup is valid.
  • A matching string that sits outside a valid JSON-LD <script> block can still produce a 1.
  • Capitalization differences do not affect detection; matching is case-insensitive.
  • All structured data must match visible, truthful content on the page.
  • This is a prioritization signal that relates to position within a measured result set. Presence of the type correlates with, but does not cause or guarantee, any ranking.

Related factors

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