Has Schema Markup

Has Schema Markup checks whether RankGear detects any supported structured-data mechanism anywhere in a page’s rendered HTML, returning 1 when it finds one and 0 when it finds none. It is a broad presence check — it confirms that structured data exists, not that the markup is valid, complete, or correct.

What it measures

This factor reports whether RankGear recognizes any supported structured-data mechanism on the page. It is a catch-all presence check across every format RankGear knows how to spot, rather than a test for one specific schema type. Because it fires on the first mechanism it recognizes, it sits broader than the individual, format-specific detectors that look for a single markup style.

How RankGear measures it

RankGear returns 1 when the rendered HTML contains any one of the following: microdata (an itemtype, itemprop, or itemscope attribute), a recognized MicroFormat root, an RDFa typeof= declaration, or a type="application/ld+json" script declaration. A single match anywhere in the document is enough to set the factor to 1; if none of these mechanisms is present, it returns 0.

What RankGear looks for

<!-- microdata -->
<div itemscope itemtype="https://schema.org/Article">
  <span itemprop="headline">...</span>
</div>

<!-- RDFa -->
<div typeof="schema:Article">...</div>

<!-- JSON-LD -->
<script type="application/ld+json">{ ... }</script>

<!-- MicroFormat root (e.g. h-card) -->
<div class="h-card">...</div>

How to optimize it

Implement one valid structured-data format that accurately describes the page’s visible content, and test it independently with a dedicated validator. Treat this factor as an observation rather than a target: because it only checks for presence, a value of 1 confirms that markup exists but says nothing about whether that markup is valid or describes the content correctly. Getting the factor to read 1 is the floor, not the finish line — the quality of the markup is what does the work downstream.

Important considerations

• Presence is broader than the individual legacy type detectors — this factor fires on any recognized mechanism, so it can read 1 even when a format-specific detector reads 0.
• JSON-LD content is not schema-validated by this factor; a detected application/ld+json block counts as present regardless of what it contains.
• Formatting variations can affect detection, so unusual or non-standard markup may not be recognized.
• Invalid markup can still produce a 1, because the factor tests for the presence of a mechanism, not its correctness.
• Correlation is not causation: this factor tracks how a measured result set relates to structured-data presence. It is a prioritization signal, not a guarantee that adding markup will move a page’s position.

Related factors

• Has Schema Local Business
• Has Schema Offer

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