The Has JSON-LD Apartment factor returns 1 when RankGear finds a JSON-LD @type of Apartment in your page’s raw HTML, and 0 when it does not. It pattern-matches the source text rather than validating a schema graph, so a matching string can register even when it sits outside a valid JSON-LD script.
| Factor ID | RG-SCJ-013 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of Apartment in the raw source of your page. It is a simple presence check: the Apartment type describes a single residential unit — a rented or owned apartment with its own address, accommodation, and offer details — and this factor records only whether that type is declared, not whether the surrounding markup is complete or valid.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Apartment", allowing flexible whitespace around the colon and an optional schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not affect the result. A match returns 1; no match returns 0.
What RankGear looks for
"@type": "Apartment"
"@type":"schema:Apartment"| Value | Meaning |
|---|---|
| 1 | A JSON-LD Apartment type string was found in the page source. |
| 0 | No Apartment type string was present. |
How to optimize it
Declare Apartment only for a genuine residential unit, and give it an accurate address, accommodation, and offer details. Treat this factor as an observation of what your markup already contains rather than a target to chase: adding the type where no real apartment exists misrepresents the page and does nothing for the underlying content. If your page legitimately describes an apartment listing, a well-formed Apartment entity is the honest way to earn the 1.
Important considerations
- RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph, so it confirms presence, not correctness.
- A matching string outside a valid JSON-LD script — in a comment, inline text, or unrelated code — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- All structured data must match visible, truthful content on the page.
- This is a correlation-based prioritization signal, not a guarantee: declaring the
Apartmenttype relates to patterns within a measured result set and does not by itself cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.