Has JSON-LD AmusementPark

This factor reports whether RankGear finds an @type value of AmusementPark in a page’s raw source. It returns a simple presence signal (1 or 0) — it does not parse or validate the JSON-LD graph, so a match is evidence the string is on the page, not proof the markup is well-formed.

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

What it measures

This factor reports whether RankGear finds an @type value for AmusementPark in the raw source. It is a single yes/no observation about whether the page declares itself as an amusement-park entity via schema.org’s AmusementPark type.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "AmusementPark", allowing flexible whitespace around the tokens and optionally permitting a schema: prefix on the type value. The detector is case-insensitive and returns 1 on any match, 0 otherwise. It matches text only — it does not parse or validate the surrounding JSON-LD graph.

What RankGear looks for

"@type": "AmusementPark"

// also matches, e.g.:
"@type":"schema:amusementpark"
ValueMeaning
1An @type of AmusementPark was found in the raw source (whitespace-flexible, case-insensitive, optional schema: prefix).
0No matching AmusementPark type string was found.

How to optimize it

Use AmusementPark only for a real venue, with an accurate identity, address, hours, and visitor information behind it. The type and every property should reflect content that is actually visible on the page. Because RankGear pattern-matches raw source rather than validating the graph, treat a 1 as confirmation the string is present — not as a substitute for valid, well-formed JSON-LD that a search engine can consume.

Important considerations

  • RankGear pattern-matches raw source; it does not parse or validate the JSON-LD graph.
  • A matching string outside a valid JSON-LD script can still produce 1 — the detector sees text, not structure.
  • Capitalization differences do not affect this detector; it is case-insensitive.
  • The type and all properties must accurately reflect visible content.
  • Presence of this type correlates with pages in a measured result set; it does not on its own cause or guarantee a ranking. Treat it as one prioritization signal among many.

Related factors

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