This factor reports whether RankGear finds a RealEstateAgent @type value in a page’s raw HTML — a simple 1 (present) or 0 (absent). It is a text match on the source, not a validation of the JSON-LD graph, so treat a 1 as “the string is there,” not “the schema is correct.”
| Factor ID | RG-SCJ-223 |
|---|---|
| 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 RealEstateAgent in the raw source of the page. RealEstateAgent is the schema.org type used to describe a real estate agent or agency, so its presence indicates the page has declared itself as that kind of entity in structured data. The result is a single yes/no signal, not a quality score for the markup.
How RankGear measures it
RankGear searches the raw HTML for the text "@type": "RealEstateAgent", allowing flexible whitespace around the tokens and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. A match returns 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "RealEstateAgent",
"name": "Cedar & Vine Realty",
"areaServed": "Austin, TX"
}
</script>| Value | Meaning |
|---|---|
| 1 | A RealEstateAgent @type string was found in the raw HTML. |
| 0 | No matching string was found in the raw HTML. |
How to optimize it
Use RealEstateAgent only for a genuine real estate agent or agency, and keep the markup honest: accurate credentials, service area, listings, location, and contact information. Every property described in the structured data should reflect content a visitor can verify on the page itself. Because this factor only checks for the string, the goal is correct, truthful markup — not merely getting a 1 to appear. Treat the score as an observation of what is present, not a target to game.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 does not confirm the structured data is well-formed or complete.
- A matching string that sits outside valid JSON-LD — for example in a comment, a code sample, or unrelated markup — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently (for example with a schema validator) before relying on it.
- This is a prioritization signal that relates to position within a measured result set. It correlates with placement; it does not by itself cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.