Has Schema Question

Has Schema Question checks whether a page carries the legacy Schema.org Question type expressed as the URI http://schema.org/Question. RankGear returns 1 when that exact string is present and 0 when it is not — and the match is deliberately literal: the https:// form and a bare JSON-LD "@type": "Question" do not count.

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

What it measures

This factor detects the legacy Schema.org Question type URI on the page. It is a presence check for one specific historical form of the markup — the http://schema.org/Question URI — rather than a judgement about the quality or completeness of any question markup.

How RankGear measures it

RankGear performs a case-insensitive search of the page’s body HTML (with scripts removed) for the literal string http://schema.org/Question, returning 1 when it is found and 0 when it is not.

What RankGear looks for

<div itemscope itemtype="http://schema.org/Question">
  <h3 itemprop="name">How do I install RankGear?</h3>
  <div itemprop="acceptedAnswer" itemscope itemtype="http://schema.org/Answer">
    <div itemprop="text">...</div>
  </div>
</div>
ValueMeaning
1The literal http://schema.org/Question URI appears in the body HTML.
0The URI is absent — including pages that use the https:// form or a bare JSON-LD "@type": "Question".

How to optimize it

Use the Question type only for a genuine question, and pair it with valid answer properties where appropriate. Treat this flag as an observation of which URI form your markup uses, not a target to chase — adding the legacy http:// URI just to flip the value does nothing for correctness or for the reader.

Important considerations

  • https://schema.org/Question and a bare JSON-LD "@type": "Question" do not satisfy this detector — it matches only the literal http://schema.org/Question string.
  • Presence does not validate the required or recommended properties of the type; the flag says the URI is there, not that the markup is complete.
  • Structured data must match visible, truthful content on the page.
  • Validate the complete markup with current platform validation tools.
  • This is a prioritization signal that relates to position within a measured result set; presence of the URI does not by itself cause or guarantee a ranking.

Related factors

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