Has Schema Event

Abstract illustration of a scheduled event card wrapped in a schema markup tag, in RankGear indigo and coral.

RG-SCH-008 reports whether a page’s body markup contains the legacy Schema.org Event type URI — a simple present-or-absent signal (1 or 0). It matches the HTTP form http://schema.org/Event only, so HTTPS URIs and bare JSON-LD type names can register as 0. Presence relates to position within a measured result set; it is a prioritization signal, not a cause of ranking.

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

What it measures

This factor detects the legacy Schema.org Event type URI in a page’s rendered markup. Its presence indicates the page has declared an Event entity — the structured-data type used to describe a scheduled happening such as a concert, webinar, class, or conference session.

Back to Top

How RankGear measures it

RankGear scans the body HTML (with script blocks excluded) and case-insensitively searches for the literal string http://schema.org/Event. If that URI appears anywhere in the measured markup, the factor returns 1; otherwise it returns 0. The check is a string match on the legacy HTTP type URI — it does not parse or validate any of the event’s properties.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/Event">
  <span itemprop="name">Nova Analytics Summit</span>
  <time itemprop="startDate" datetime="2026-09-14T09:00">Sep 14, 2026</time>
</div>
ValueMeaning
1The string http://schema.org/Event was found in the body markup — a legacy Event type URI is present.
0The URI was not found. The page has no Event markup, or it uses the HTTPS form or a bare JSON-LD @type that this check does not match.
Back to Top

How to optimize it

Add Event markup only for a real, scheduled event, with accurate dates, location, status, and offers. Because the check matches the legacy http://schema.org/Event URI, a page that only uses the HTTPS form or a JSON-LD @type of Event may score 0 even though its structured data is valid. Treat this factor as an observation about which URI form is present rather than a target to chase — do not add or rewrite Event markup on pages that describe no scheduled event.

Back to Top

Important considerations

  • HTTPS URIs and bare JSON-LD types can score 0 — the check matches the legacy http://schema.org/Event string specifically.
  • Event properties are not validated; the factor only confirms the type URI is present, not that dates, location, or offers are correct.
  • Keep the markup current — update cancelled or rescheduled events so the structured data reflects reality.
  • Markup must match the visible details on the page; do not describe an event the reader cannot see.
  • Presence correlates with position inside a measured result set and does not guarantee or cause a ranking.
Back to Top

Related factors

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

Back to Top