Has JSON-LD Website

Abstract illustration of a website node declared as JSON-LD WebSite schema, in RankGear indigo and coral.

Has JSON-LD Website reports whether RankGear finds an @type of WebSite in a page’s raw HTML — a 1 when the string is present, a 0 when it is not. It is a case-insensitive text match on source, so a 1 confirms the pattern exists, not that the JSON-LD is a valid, well-formed graph.

Factor IDRG-SCJ-267
FamilyStructured Data – JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of WebSite in the raw source. It is a single presence check: the WebSite type is the JSON-LD node that describes the site as a whole — its name, canonical URL, publisher, language, and any supported search action — so the factor is asking, in effect, “does this page declare a site-level JSON-LD entity?”

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "WebSite", allowing flexible whitespace around the colon and optionally permitting a schema: prefix (as in "@type": "schema:WebSite"). Matching is case-insensitive. If the pattern is found the factor returns 1; otherwise it returns 0.

Back to Top

What RankGear looks for

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

# also matches (case-insensitive, optional schema: prefix):
"@type":"website"
"@type": "schema:WebSite"
ValueMeaning
1A "@type": "WebSite" string was found in the raw HTML (case-insensitive, optional schema: prefix).
0No such string was present in the source.
Back to Top

How to optimize it

Use the WebSite type only for the genuine website, with an accurate name, canonical URL, publisher, language, and — where it applies — a supported search action. Make sure every property reflects content a user can verify on the page. Treat this factor as an observation of whether that declaration exists, not a target to game: emitting the string without a truthful, complete entity behind it adds no real signal and risks producing invalid structured data.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not parse or validate the JSON-LD graph.
  • A matching string that sits outside valid JSON-LD — in a comment, a code sample, or an escaped example — can still produce a 1.
  • Capitalization differences do not affect detection; the match is case-insensitive.
  • Validate the complete structured data independently — a 1 here is not confirmation that the markup is correct.
  • Correlation is not causation: this is a prioritization signal that relates to position within a measured result set, not a switch that makes a page rank.
Back to Top

Related factors

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

Back to Top