The Ultimate FinancialIncentive
Schema Generator
Represents financial incentives for goods/services offered by an organization (or individual). Typically contains the name of the incentive, the incentivizedItem, the incentiveAmount, the incentiveStatus, incentiveType, the provider of the incentive, and eligibleWithSupplier. Optionally contains criteria on whether the incentive is limited based on purchaseType, purchasePriceLimit, incomeLimit, and the qualifiedExpense.
Magic Build
Paste your URL below and our AI will automatically fill the FinancialIncentive fields for you.
Configuration
Live GeneratorWhy use FinancialIncentive?
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is FinancialIncentive Schema?
Represents financial incentives for goods/services offered by an organization (or individual). Typically contains the name of the incentive, the incentivizedItem, the incentiveAmount, the incentiveStatus, incentiveType, the provider of the incentive, and eligibleWithSupplier. Optionally contains criteria on whether the incentive is limited based on purchaseType, purchasePriceLimit, incomeLimit, and the qualifiedExpense.
Google uses FinancialIncentive structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add FinancialIncentive Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement FinancialIncentive JSON-LD
Generate
Use the form above to fill in your details and generate valid FinancialIncentive JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
FinancialIncentive schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| alternateName | An alias for the item. | Text | Optional |
| areaServed | The geographic area where a service or offered item is provided. | AdministrativeArea, GeoShape, Place, Text | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| disambiguatingDescription | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. | Text | Optional |
| eligibleWithSupplier | The supplier of the incentivized item/service for which the incentive is valid for such as a utility company, merchant, or contractor. | Organization | Optional |
| identifier | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details. | PropertyValue, Text, URL | Optional |
| image | An image of the item. This can be a URL or a fully described ImageObject. | ImageObject, URL | Recommended |
| incentiveAmount | Describes the amount that can be redeemed from this incentive. QuantitativeValue: Use this for incentives based on price (either raw amount or percentage-based). For a raw amount example, "You can claim $2,500 - $7,500 from the total cost of installation" would be represented as the following: { "@type": "QuantitativeValue", “minValue”: 2500, “maxValue”: 7500, "unitCode": "USD" } QuantitativeValue can also be used for percentage amounts. In such cases, value is used to represent the incentive’s percentage, while maxValue represents a limit (if one exists) to that incentive. The unitCode should be 'P1' and the unitText should be '%', while valueReference should be used for holding the currency type. For example, "You can claim up to 30% of the total cost of installation, up to a maximum of $7,500" would be: { "@type": "QuantitativeValue", "value": 30, "unitCode": "P1", "unitText": "%", “maxValue”: 7500, “valueReference”: “USD” } UnitPriceSpecification: Use this for incentives that are based on amounts rather than price. For example, a net metering rebate that pays $10/kWh, up to $1,000: { "@type": "UnitPriceSpecification", "price": 10, "priceCurrency": "USD", "referenceQuantity": 1, "unitCode": "DO3", "unitText": "kw/h", "maxPrice": 1000, "description": "$10 / kwh up to $1000" } LoanOrCredit: Use for incentives that are loan based. For example, a loan of $4,000 - $50,000 with a repayment term of 10 years, interest free would look like: { "@type": "LoanOrCredit", "loanTerm": { "@type":"QuantitativeValue", "value":"10", "unitCode": "ANN" }, "amount":[ { "@type": "QuantitativeValue", "Name":"fixed interest rate", "value":"0", }, ], "amount":[ { "@type": "MonetaryAmount", "Name":"min loan amount", "value":"4000", "currency":"CAD" }, { "@type": "MonetaryAmount", "Name":"max loan amount", "value":"50000", "currency":"CAD" } ], } In summary: Use QuantitativeValue for absolute/percentage-based incentives applied on the price of a good/service. Use UnitPriceSpecification for incentives based on a per-unit basis (e.g. net metering). Use LoanOrCredit for loans/credits. . | LoanOrCredit, QuantitativeValue, UnitPriceSpecification | Optional |
| incentiveStatus | The status of the incentive (active, on hold, retired, etc.). | IncentiveStatus | Optional |
| incentiveType | The type of incentive offered (tax credit/rebate, tax deduction, tax waiver, subsidies, etc.). | IncentiveType | Optional |
| incentivizedItem | The type or specific product(s) and/or service(s) being incentivized. DefinedTermSets are used for product and service categories such as the United Nations Standard Products and Services Code: { "@type": "DefinedTerm", "inDefinedTermSet": "https://www.unspsc.org/", "termCode": "261315XX", "name": "Photovoltaic module" } For a specific product or service, use the Product type: { "@type": "Product", "name": "Kenmore White 17" Microwave", } For multiple different incentivized items, use multiple DefinedTerm or Product. | DefinedTerm, Product | Optional |
| incomeLimit | Optional. Income limit for which the incentive is applicable for. If MonetaryAmount is specified, this should be based on annualized income (e.g. if an incentive is limited to those making { "@type": "MonetaryAmount", "maxValue": 114000, "currency": "USD", } Use Text for incentives that are limited based on other criteria, for example if an incentive is only available to recipients making 120% of the median poverty income in their area. | MonetaryAmount, Text | Optional |
| mainEntityOfPage | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details. | CreativeWork, URL | Optional |
| name | The name of the item. | Text | Required |
| owner | A person or organization who owns this Thing. | Organization, Person | Optional |
| potentialAction | Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role. | Action | Optional |
| provider | The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller. | Organization, Person | Optional |
| publisher | The publisher of the article in question. | Organization, Person | Optional |
| purchasePriceLimit | Optional. The maximum price the item can have and still qualify for this offer. | MonetaryAmount | Optional |
Example FinancialIncentive JSON-LD
Here's what valid FinancialIncentive structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "FinancialIncentive",
"name": "Example FinancialIncentive",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"additionalType": "Example additionalType",
"alternateName": "Example alternateName",
"areaServed": {
"@type": "AdministrativeArea",
"name": "Example AdministrativeArea",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"description": "A sample description for this FinancialIncentive.",
"disambiguatingDescription": "Example disambiguatingDescription"
}Validate Your FinancialIncentive Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your FinancialIncentive schema for errors and Rich Result eligibility