This factor reports whether RankGear finds an @type value of AutoRental in a page’s raw rendered HTML. It is a binary presence check (1 = found, 0 = not found) that reads source text directly — it does not parse or validate the underlying JSON-LD graph, so a match confirms the string is present, not that the markup is well-formed or accurate.
| Factor ID | RG-SCJ-025 |
|---|---|
| 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 for AutoRental in the raw source. AutoRental is the schema.org type used to describe a vehicle-rental business, so its presence signals that a page has declared itself as a car-rental entity in structured data.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "AutoRental", allowing flexible whitespace around the tokens and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection. Any single match sets the value to 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AutoRental",
"name": "Example Car Rental",
"address": { "@type": "PostalAddress", "addressLocality": "Denver" },
"telephone": "+1-555-0100"
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of AutoRental (optionally schema:AutoRental) was found in the raw HTML. |
| 0 | No matching AutoRental type string was found in the raw HTML. |
How to optimize it
Use AutoRental only for a real vehicle-rental operation, and populate it with accurate location, offers, policies, and contact information. Because RankGear pattern-matches source text rather than validating a graph, treat a value of 1 as confirmation that the type string is present — not as proof that the structured data is complete or valid. If your business is not a vehicle-rental operation, this factor is not applicable and a 0 is expected.
Important considerations
- RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph.
- A matching string outside a valid JSON-LD script can produce a 1, so presence of the string is not the same as valid, machine-readable markup.
- Capitalization differences do not affect detection.
- All structured data must match visible, truthful content on the page.
- This is a prioritization signal that relates to position within a measured result set; presence of the markup correlates with, but does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.