Has Schema Web Page

Abstract illustration of a web page's schema.org WebPage type URI being matched against its exact legacy form, in RankGear indigo and coral.

Has Schema Web Page checks whether a page declares the legacy Schema.org WebPage type using the http://schema.org/WebPage URI. It returns 1 when that exact string is present in the page’s body markup and 0 when it is absent — a presence signal only, not a check that the structured data is valid or complete.

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

What it measures

This factor detects the legacy Schema.org WebPage type URI in a page’s markup. WebPage is the generic Schema.org type for a web page treated as a document — it describes the page itself and lets you connect it to its parent site and to the primary entity the page is about. RankGear records only whether the specific legacy URI is present; it does not evaluate how the type is used or how much detail the markup carries.

Back to Top

How RankGear measures it

RankGear performs a case-insensitive search of the body HTML (with <script> contents excluded) for the literal string http://schema.org/WebPage. It returns 1 when that string is found and 0 when it is not. Because scripts are excluded from the measured zone, this factor keys on inline markup such as microdata or RDFa rather than JSON-LD embedded in a script tag.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/WebPage">
  <meta itemprop="name" content="Page title">
</div>
ValueMeaning
1The literal http://schema.org/WebPage URI appears in the body markup.
0The URI is absent — including the https:// variant or a JSON-LD "@type": "WebPage" declaration.
Back to Top

How to optimize it

Use WebPage (or a more specific subtype) to describe the page accurately and to connect it to its site and its primary entity. Treat this factor as an observation about the exact legacy URI a page uses, not a target to chase for its own sake: if your structured data strategy already relies on JSON-LD or the https:// URI, a 0 here reflects that choice rather than a defect. Add or normalize the http://schema.org/WebPage markup only when it genuinely fits how you describe the page.

Back to Top

Important considerations

  • The https://schema.org/WebPage URI and a bare JSON-LD "@type": "WebPage" declaration do not satisfy this detector — it matches the http:// literal only.
  • Presence does not validate the type’s required or recommended properties; a matched string can still be incomplete markup.
  • Structured data must match visible, truthful content on the page.
  • Validate the complete markup with current platform tools rather than relying on this presence check alone.
  • This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with, but does not cause or guarantee, any ranking.
Back to Top

Related factors

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

Back to Top