FinancialService schema for a real merchant services brokerage: a case study

Schema.org gives you FinancialService as a type. Most sites that use it stop there. Combined with LocalBusiness, ProfessionalService, and a properly populated hasOfferCatalog, it becomes one of the highest-density entity declarations you can put on a small business site.

This is a walkthrough of how I structured the entity graph for Steele Solutions, a family-run merchant services brokerage in Branson, Missouri.

The starting type chain

{
  "＠context": "https://schema.org",
  "＠graph": [{
    "＠type": ["LocalBusiness", "FinancialService", "ProfessionalService"],
    "＠id": "https://steelesolutions4u.com/#org",
    "name": "Steele Solutions",
    "url": "https://steelesolutions4u.com/",
    "description": "Branson Missouri merchant services firm..."
  }]
}

The triple ＠type is intentional. LocalBusiness gets you into Google's local pack discovery. FinancialService is the topical type that signals "this is a financial-services business, not a retailer." ProfessionalService reinforces it for the Knowledge Graph reconciliation pass.

hasOfferCatalog: the service spine

hasOfferCatalog is where most small business schemas fall over. The spec asks for an OfferCatalog with itemListElement containing Offer objects, each wrapping a Service. Most sites either skip it, or list a single Offer with no URL.

For Steele, every service maps to a real URL on the site:

"hasOfferCatalog": {
  "＠type": "OfferCatalog",
  "name": "Steele Solutions Service Catalog",
  "itemListElement": [
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "POS Systems", "url": "https://steelesolutions4u.com/pos-systems/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Credit Card Processing", "url": "https://steelesolutions4u.com/credit-card-processing/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "ATM Placements", "url": "https://steelesolutions4u.com/atm-placements/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Small Business Lending", "url": "https://steelesolutions4u.com/business-lending/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "CSSI Cost Segregation Studies", "url": "https://steelesolutions4u.com/cssi-cost-segregation/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Dual Pricing and Cash Discount Programs", "url": "https://steelesolutions4u.com/dual-pricing/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Free POS Placement", "url": "https://steelesolutions4u.com/free-pos/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Square Account Setup via Authorized Referral", "url": "https://steelesolutions4u.com/apply/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Business CPR Framework", "url": "https://steelesolutions4u.com/business-cpr/"}},
    {"＠type": "Offer", "itemOffered": {"＠type": "Service", "name": "Cryptocurrency Payment Acceptance via Shift4", "url": "https://steelesolutions4u.com/services/"}}
  ]
}

Ten services. Every Service item has both a name and a URL. The URL bridges the entity graph to the actual page where that service is sold. Google AI Overview and Perplexity both treat the URL on itemOffered as the authoritative source for that service offering.

areaServed: explicit geography

Most merchant services sites declare their city and stop. But a brokerage like Steele's serves multiple states. The schema reflects that exactly:

"areaServed": [
  {"＠type": "City", "name": "Branson", "containedInPlace": {"＠type": "State", "name": "Missouri"}},
  {"＠type": "City", "name": "Springfield", "containedInPlace": {"＠type": "State", "name": "Missouri"}},
  {"＠type": "City", "name": "Joplin", "containedInPlace": {"＠type": "State", "name": "Missouri"}},
  {"＠type": "City", "name": "Bentonville", "containedInPlace": {"＠type": "State", "name": "Arkansas"}},
  {"＠type": "City", "name": "Rogers", "containedInPlace": {"＠type": "State", "name": "Arkansas"}},
  {"＠type": "Place", "name": "Lake Taneycomo"},
  {"＠type": "Place", "name": "Table Rock Lake"},
  {"＠type": "Place", "name": "the Ozarks"}
]

17 areas total in the final version, blending City (with containedInPlace chaining to State) and Place for non-political geographic features. This is what fuels the discovery for queries like "credit card processing Branson MO" or "ATM placement Eureka Springs AR."

paymentMethod: GoodRelations URIs

This one is criminally underused. Schema.org doesn't have its own enum for payment methods, but it accepts GoodRelations URIs:

"paymentMethod": [
  "http://purl.org/goodrelations/v1#Cash",
  "http://purl.org/goodrelations/v1#Check",
  "http://purl.org/goodrelations/v1#PaymentMethodCreditCard",
  "http://purl.org/goodrelations/v1#DirectDebit",
  "http://purl.org/goodrelations/v1#ByBankTransferInAdvance"
]

Plus a paymentAccepted string field for human-readable variants. Both fields together feed into Google's payment-types facet in the merchant snippet.

Person entities for the founders

Steele Solutions is a husband and wife operation. Both founders get full Person entities in the graph:

{"＠type": "Person", "＠id": "https://steelesolutions4u.com/#jim", ...}
{"＠type": "Person", "＠id": "https://steelesolutions4u.com/#kim", "spouse": {"＠id": "https://steelesolutions4u.com/#jim"}, ...}

Each Person has alumniOf, hasCredential (with recognizedBy linking to the institution's Wikidata QID), knowsAbout, worksFor, memberOf, additionalProperty, and sameAs arrays. Jim's alumniOf chains:

"alumniOf": [{
  "＠type": "CollegeOrUniversity",
  "name": "Indiana University Bloomington",
  "url": "https://www.indiana.edu/",
  "sameAs": [
    "https://www.wikidata.org/wiki/Q1079140",
    "https://en.wikipedia.org/wiki/Indiana_University_Bloomington"
  ]
}]

The Wikidata Q-ID is the load-bearing entry. Google's Knowledge Graph reconciles the Person to the institution using the Q-ID, which gives Jim's bio explicit verifiable-entity provenance.

hasCredential with recognizedBy

Most schemas declare credentials as flat strings. The better pattern is EducationalOccupationalCredential with recognizedBy pointing to the awarding institution as its own Organization entity:

"hasCredential": [{
  "＠type": "EducationalOccupationalCredential",
  "name": "First National Bank of Omaha President's Club",
  "credentialCategory": "Sales Performance Award",
  "recognizedBy": {
    "＠type": "BankOrCreditUnion",
    "name": "First National Bank of Omaha",
    "url": "https://www.fnbo.com/",
    "sameAs": [
      "https://www.wikidata.org/wiki/Q5453412",
      "https://en.wikipedia.org/wiki/First_National_Bank_of_Omaha"
    ]
  }
}]

Now the credential is graph-linked to a real Wikidata entity. AI engines and Knowledge Graph can verify Jim's claimed achievement by traversing to the FNBO entity and confirming the institution exists.

sameAs as the verification spine

The org's sameAs array is where third-party verifications live. Steele's includes:

• Google Maps CID (for the Google Business Profile)
• All 10 partner sites (Electronic Payments, ClearPay, Shift4, etc.)
• Wayback Machine archive URL
• Taney County, Missouri public real estate records URL
• Personal property tax records URL

The Wayback URL is the permanent citation. Live URLs can change. Wayback URLs are immutable. When you put https://web.archive.org/web/20260526012306/https://steelesolutions4u.com/ in your sameAs, you give crawlers a citation that survives even if your site goes down.

What this buys you

Schema density is not a vanity metric. Google's structured data testing tool measures it. AI engines weigh it. Bing's Copilot weighs it heavily.

In Steele's case, the dense schema produced:

• Local pack appearance within 7 days of launch for "credit card processing Branson MO"
• Position-3 average for the homepage on indexed queries within 14 days
• Knowledge Panel sidebar (pending Google Business Profile verification)
• AI engine citations on ChatGPT and Perplexity within 21 days of launch

The live example

The complete entity graph is at https://steelesolutions4u.com/entity.json. The schema is also embedded inline on every page of the site so crawlers and AI engines get the full graph regardless of which entry point they hit.

The public verification page at https://steelesolutions4u.com/verification/ cross-references every schema claim with the third-party source backing it.

Tools used

• Schema.org for the type definitions
• Wikidata for institutional Q-IDs
• Internet Archive Wayback Machine for permanent citation URLs
• Google Search Console for index status verification
• IndexNow for accelerated discovery

The full Steele Solutions resources are public at github.com/Janady13/steele-solutions-resources.