Has JSON-LD FinancialService

Has JSON-LD FinancialService is a 0 / 1 flag for whether the raw HTML declares an @type value of FinancialService in JSON-LD structured data, the Schema.org type for banks, lenders, insurers, and similar money-handling businesses. Important caveat: it pattern-matches source text rather than validating a JSON-LD graph, so a matching string outside valid markup can still return 1.

What it measures

This factor reports whether RankGear finds an @type value of FinancialService in the raw source. FinancialService is the Schema.org type for a business that provides financial services — a bank, credit union, lender, insurer, brokerage, or comparable money-handling operation — and its markup typically carries the entity name, services offered, location, contact details, and regulatory or licensing information in a machine-readable form.

How RankGear measures it

RankGear searches the raw HTML for "@type": "FinancialService", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not affect the result. The factor returns 1 when the pattern is found and 0 when it is not. Because this is a text search rather than a parse of the structured-data graph, it confirms that the string appears in the source, not that it sits inside valid, complete JSON-LD.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FinancialService",
  "name": "Example Credit Union",
  "address": { ... },
  "telephone": "+1-555-0100"
}
</script>

# matched pattern (case-insensitive, flexible whitespace, optional schema: prefix):
#   "@type" : "FinancialService"
#   "@type":"schema:FinancialService"

How to optimize it

Treat this as an observation, not a target. Use FinancialService only for a genuine financial-service business, and describe it accurately: list the real services offered, and provide correct location, contact, and regulatory or licensing information, with properties that match the visible content of the page. Do not add the type to a page that does not represent a financial-service entity merely to set the flag to 1 — the string can be detected without describing a real, valid entity, which helps no one.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph.
• A matching string that sits outside valid JSON-LD can still produce a 1.
• Capitalization differences do not affect detection; matching is case-insensitive.
• Validate the complete structured data independently with a dedicated tool rather than relying on this presence flag.
• Structured data correlates with, and does not guarantee, ranking outcomes; it is a prioritization signal measured within a result set, not a cause of position.

Related factors

• Has JSON-LD FinancialProduct
• Has JSON-LD Find Action

Part of the Factors reference · how RankGear measures · glossary.