Has Schema Person

Abstract illustration of a person identity marked up as structured data, in RankGear indigo and coral.

Has Schema Person is a yes/no check for the legacy Schema.org Person type declared with the http://schema.org/Person URI in a page’s rendered body. It returns 1 when that exact URI is present and 0 when it is not — it confirms the markup exists, not that the identity behind it is accurate or complete.

Factor IDRG-SCH-016
FamilySchema.org
MeasurementBinary presence (0 / 1)
Measured zoneBody HTML without scripts

What it measures

This factor detects the legacy Schema.org Person type URI on the page. Person markup describes an individual — an author, founder, practitioner, or public figure — and lets search engines connect a name on the page to a structured identity. The check reports only whether the older http://schema.org/Person form of that type is declared; it does not read or judge the identity properties attached to it.

Back to Top

How RankGear measures it

RankGear searches the page’s body HTML case-insensitively for the string http://schema.org/Person. A match anywhere in that measured zone returns 1; no match returns 0. The search runs over the body with scripts removed, so this factor targets the type URI as it appears in rendered markup rather than inside a JSON-LD script block.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/Person">
  <span itemprop="name">Jane Doe</span>
  <span itemprop="jobTitle">SEO Lead</span>
</div>
ValueMeaning
1The http://schema.org/Person URI was found in the body HTML.
0The URI was not found. HTTPS forms and bare JSON-LD type names are not counted here.
Back to Top

How to optimize it

Use Person markup only for a real individual, and populate it with accurate, privacy-conscious identity and professional properties. Keep the marked-up details aligned with what a visitor actually sees on the page. Treat the result as an observation of whether this specific legacy URI is present, not as a target to chase — a 0 simply means this exact form was not detected, which is expected on pages that use the HTTPS URI or a bare JSON-LD Person type.

Back to Top

Important considerations

  • HTTPS URIs (https://schema.org/Person) and bare JSON-LD type names are not recognized by this specific check.
  • The identity details inside the markup are not validated — presence of the type does not confirm the properties are correct.
  • Avoid exposing unnecessary personal information; mark up only what is appropriate to publish.
  • Markup should match the visible content of the page.
  • This is a correlation-based signal within a measured result set. Declaring Person markup does not by itself cause a page to rank; the factor tracks the presence of the type as one prioritization signal among many.
Back to Top

Related factors

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

Back to Top