Has JSON-LD WebPage

Abstract illustration of a JSON-LD WebPage type declaration inside a script tag linked to a single browser-window page node, in RankGear indigo and coral.

Has JSON-LD WebPage reports whether a page’s raw source contains an @type value of WebPage: it returns 1 when RankGear matches that string in the HTML and 0 when it does not. It is a text-pattern presence check — a 1 confirms the string is present, not that a valid JSON-LD graph describes the page.

Factor IDRG-SCJ-266
FamilyStructured data — JSON-LD
MeasurementBoolean (0 / 1)
Measured zoneRaw rendered HTML

What it measures

Has JSON-LD WebPage reports whether RankGear finds an @type value of WebPage in the raw source. A value of 1 means the expected string was located; a value of 0 means it was not. The factor measures the presence of that type string only. It does not parse or validate the surrounding JSON-LD, confirm that the graph is well-formed, or verify that the declared WebPage properties agree with the visible content.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "WebPage", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. Finding at least one match returns 1; otherwise the value is 0. Because the check pattern-matches source text rather than validating a JSON-LD graph, a matching string that appears outside valid structured data can still produce a 1.

Back to Top

What RankGear looks for

<script type="application/ld+json">
  { "@context": "https://schema.org",
    "@type": "WebPage",
    "name": "...", "url": "..." }
</script>

Also matches:  "@type": "schema:WebPage"  (case-insensitive, flexible whitespace)
ValueMeaning
1The WebPage type string was found in the raw HTML (with or without a schema: prefix, any capitalization).
0No matching WebPage type string was found in the source.
Back to Top

How to optimize it

Use WebPage only for the current web page, with an accurate name, URL, description, primary topic, author or publisher, dates, and breadcrumbs. Ensure every property reflects content users can verify on the page. Because the detector matches source text rather than a validated graph, treat a 1 as an observation that the type is declared — not a target to manufacture by inserting the string. Confirm the markup is well-formed and consistent with the page instead of chasing the match for its own sake.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms only that the type string is present.
  • A matching string that sits outside valid JSON-LD can still produce a 1.
  • Capitalization differences and an optional schema: prefix do not affect detection.
  • Validate the complete structured data independently with an appropriate structured-data testing tool.
  • This factor tracks a signal that relates to how pages are prioritized within a measured result set — it is not a guarantee of ranking, indexing, or a rich result.
Back to Top

Related factors

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

Back to Top