“Has JSON-LD AccountingService” returns 1 when RankGear finds the string "@type": "AccountingService" in a page’s raw HTML, and 0 when it does not. It is a raw string match, not a validator — RankGear never parses or checks the surrounding JSON-LD graph, so a match that sits outside a valid script block still counts as present.
| Factor ID | RG-SCJ-003 |
|---|---|
| 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 AccountingService in the page’s raw source. It is a presence check for one specific schema.org business type — it says nothing about how complete, accurate, or valid the surrounding markup is, only that the type string appears.
How RankGear measures it
RankGear searches the raw HTML for "@type": "AccountingService", allowing flexible whitespace around the colon and quotes and optionally a schema: prefix on the type value. The match is case-sensitive and returns 1 on the first match, or 0 when no match is found anywhere in the source.
What RankGear looks for
"@type": "AccountingService"
"@type" : "schema:AccountingService"| Value | Meaning |
|---|---|
| 1 | The AccountingService type string was found in the raw HTML. |
| 0 | The string was not present (or its capitalization did not match exactly). |
How to optimize it
Use AccountingService only for a genuine accounting business, with accurate identity, service area, contact, and location details in the markup. Treat the 1/0 as an observation of whether the type is present, not a target to game: adding the string without a real, matching business misrepresents the page and offers no lasting benefit. If you legitimately are an accounting service, emitting valid JSON-LD with this @type is the straightforward way to make the factor read 1.
Important considerations
- RankGear pattern-matches the raw source; it does not parse or validate the JSON-LD graph.
- A matching string outside a valid JSON-LD
<script>block can still produce 1. - The detector is case-sensitive — capitalization must match the implementation exactly.
- The type and all of its properties should accurately reflect the visible content of the page.
- Correlation is not causation: the presence of this type relates to how comparable pages are structured within a measured result set. It is a prioritization signal, not something that by itself causes or guarantees a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.