Has JSON-LD House

This factor reports whether RankGear finds an @type of House in a page’s raw rendered HTML, returned as a simple present (1) or absent (0). It is a text pattern match on the source, not a validation of the underlying JSON-LD graph — so a match confirms the string is there, not that the markup is valid or that it helps a page rank.

What it measures

This factor reports whether RankGear finds an @type value of House anywhere in the raw source of the page. It is a presence signal for the schema.org House type — the markup used to describe a single residential dwelling — and returns 1 when that type string appears and 0 when it does not.

How RankGear measures it

RankGear searches the raw HTML for the "@type": "House" string, allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not change the result. Because it works against source text rather than a parsed JSON-LD graph, any matching string — even one outside a valid structured-data block — can produce a 1.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "House",
  "name": "123 Maple Street",
  "address": { "@type": "PostalAddress", ... }
}
</script>

How to optimize it

Use the House type only for a real residence, with accurate address, occupancy, room, and offer information where appropriate, and with properties that match the visible content of the page. Treat this factor as an observation of what your markup contains, not a target to chase: adding the string without genuine, matching residence content does not represent the page honestly and can misdescribe it to search engines. Where House is not the right description of the entity, a different schema.org type is the correct choice.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid or well-formed.
• A matching string that sits outside a valid JSON-LD block can still produce a 1.
• Capitalization differences do not affect detection — matching is case-insensitive.
• Validate the complete structured data independently with a schema validator; this factor does not do that for you.
• Presence of the type correlates with, and does not cause, ranking position — it is a prioritization signal within a measured result set, not a guarantee that a page will rank.

Related factors

• Has JSON-LD HotelRoom
• Has JSON-LD HousePainter

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