This factor reports whether RankGear finds a FinancialProduct JSON-LD @type declaration in a page’s raw source (1 if present, 0 if absent). It is a text-pattern check on the HTML, not a validation of the underlying structured-data graph — so a match confirms the string is there, not that the markup is valid.
| Factor ID | RG-SCJ-086 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
RankGear reports whether an @type value of FinancialProduct appears in the page’s raw source. FinancialProduct is the schema.org type used to describe a financial offering — an account, loan, card, or similar product with a provider, fees, terms, and eligibility. The factor answers a single yes/no question: does the page declare this type at all?
How RankGear measures it
RankGear searches the raw HTML for the @type declaration, allowing flexible whitespace around the value and an optional schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found anywhere in the source the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "FinancialProduct"
"@type":"schema:FinancialProduct" (schema: prefix allowed)
"@TYPE": "financialproduct" (case-insensitive)| Value | Meaning |
|---|---|
| 1 | A FinancialProduct @type string was found in the raw HTML. |
| 0 | No matching FinancialProduct declaration was found in the source. |
How to optimize it
Use FinancialProduct only for a genuine financial product, and only when the marked-up properties match what the page actually shows — accurate provider, fees, terms, eligibility, and offer information. Because the detector matches source text rather than validating a graph, a returned 1 tells you the string is present, not that the structured data is correct. Treat the value as an observation of what your markup declares, then confirm the graph itself is valid and truthful before relying on it.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a 1 is not proof of well-formed structured data.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or a script that never parses — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently rather than trusting presence alone.
- Presence of this markup correlates with, but does not cause, ranking position; RankGear reports it as a prioritization signal within a measured result set, never as a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.