This factor reports whether RankGear finds a JSON-LD CreditCard type declaration in a page’s raw HTML. It returns 1 when the "@type": "CreditCard" string is present and 0 when it is not — a text-pattern signal, not a full validation of the structured-data graph.
| Factor ID | RG-SCJ-066 |
|---|---|
| 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 CreditCard in the page’s raw source. It is a simple presence check: the page either declares the CreditCard schema type somewhere in its HTML, or it does not. It does not grade the quality, completeness, or accuracy of the credit-card markup — only that the type string appears.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration of CreditCard, allowing flexible whitespace around the value and optionally accepting a schema: prefix. Matching is case-insensitive, so differences in capitalization do not affect the result.
What RankGear looks for
"@type": "CreditCard"
"@type" : "creditcard"
"@type":"schema:CreditCard"| Value | Meaning |
|---|---|
| 1 | A CreditCard @type string was found in the raw HTML. |
| 0 | No CreditCard @type string was found. |
How to optimize it
Use the CreditCard type only for a genuine credit-card product, and describe it accurately: issuer, fees, terms, eligibility, and offer details should all be present and should match what the page shows visitors. Because this is a presence check rather than a target to chase, treat a 1 as confirmation that your markup is being detected — not as a score to inflate. Adding the type to a page that does not offer a real credit-card product misrepresents the page and adds no value.
Important considerations
- The detector pattern-matches the source text; it does not validate a complete JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate your full structured data independently with a dedicated schema validator; this factor alone does not confirm the markup is correct.
- This is a prioritization signal that relates to position within a measured result set. Presence of
CreditCardmarkup correlates with patterns RankGear observes — it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.