Has JSON-LD Organization

Abstract illustration of an organization entity node linked to identity attributes inside a JSON-LD knowledge graph, in RankGear indigo and coral.

Has JSON-LD Organization is a yes/no signal that returns 1 when a page’s rendered HTML contains JSON-LD declaring Organization (or schema:Organization) as an @type, and 0 when it does not. It only detects the type string — it does not validate that the JSON-LD graph is complete, that the entity is real, or that any supporting properties are present.

Factor IDRG-SCJ-190
FamilyStructured data — JSON-LD
MeasurementBoolean presence (0 / 1)
Measured zoneComplete rendered HTML

What it measures

This factor indicates whether the page contains JSON-LD that explicitly declares Organization or schema:Organization as an @type. It is a simple presence check for the organization type inside the page’s structured-data markup, not an assessment of how well that markup is built.

Back to Top

How RankGear measures it

RankGear searches the complete rendered HTML using a case-insensitive pattern for the quoted type value. A match scores 1 and no match scores 0. It does not validate the JSON-LD graph, the required context, the entity identity, or any supporting properties. More specific organization subtypes do not automatically satisfy this exact detector.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Co",
  "url": "https://example.com"
}
</script>

The detector matches the quoted type value itself — "Organization" or "schema:Organization" — regardless of case. A more specific subtype such as "LocalBusiness" or "Corporation" will not trip this particular check unless the Organization type string is also present.

ValueMeaning
1The rendered HTML contains JSON-LD with Organization (or schema:Organization) as an @type.
0No Organization type string was found in the page’s JSON-LD.
Back to Top

How to optimize it

Use Organization markup where it accurately identifies the business or institution, commonly on a home or organization-information page. Connect a stable entity with an accurate name, URL, logo, contact information, identifiers, and authoritative sameAs profiles where appropriate. Reuse consistent identifiers across the site’s schema graph. Treat the 1 / 0 result as an observation of whether the type is present, not as a target to force onto pages where an organization entity does not belong.

Back to Top

Important considerations

  • Prefer a more specific subtype when it accurately describes the entity — and remember this detector keys on the Organization type string, so subtypes alone will not satisfy it.
  • Do not add unsupported profiles or identity claims.
  • Presence does not guarantee a knowledge panel or an enhanced result.
  • Keep organization details consistent with visible content and trusted external records.
  • This is a prioritization signal that relates to position within a measured result set — it does not, on its own, cause or guarantee a ranking.
Back to Top

Related factors

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

Back to Top