How to add FinancialProduct schema to a token page
FinancialProduct is the correct schema type for tokens. Not Product. Not Article. Not Thing. This walkthrough covers the required properties, the full JSON-LD template, validation, and the 5 errors we catch most often during audits.
Why FinancialProduct beats alternatives
Tokens are financial instruments. The schema.org vocabulary has a specific type for financial instruments: FinancialProduct. Use it.
Common wrong choices: Product (treats the token as a consumer good, breaks shopping signal), Article (treats the page as content, not an entity), Thing (generic, contributes nothing). Each of these tells AI engines the wrong story about what the page is.
FinancialProduct inherits from Intangible and Thing, so it picks up all the standard properties (name, url, image, description) but adds finance-specific fields (offers, feesAndCommissionsSpecification, interestRate). For tokens specifically, the offers slot is where you can describe the current price, the feesAndCommissionsSpecification can describe staking rewards or trading fees, and the additionalProperty array carries the blockchain-specific data Google doesn't yet have native fields for.
Required and recommended fields
Required: name, url, description, tickerSymbol. Without all four, the schema is incomplete and most validators will flag it.
Name is the human-readable token name ('Wrapped Ether'). tickerSymbol is the canonical ticker ('WETH'). Description is your 25-word answer to 'what is this token and what does it do.' URL is the canonical page URL.
Recommended: additionalProperty for chain context, sameAs for entity disambiguation, identifier for contract address, dateCreated for token launch date.
additionalProperty is where blockchain data lives. Use it for: Blockchain ('Ethereum'), Token Standard ('ERC-20'), Contract Address (the 0x... string), Total Supply, Circulating Supply.
sameAs is your entity disambiguation. Link to CoinGecko, CoinMarketCap, the primary block explorer (Etherscan, Solscan), and your Wikipedia article if you have one.
Complete JSON-LD template
Paste into the <head>. Replace placeholders. Don't ship example data.
{
"@context": "https://schema.org",
"@type": "FinancialProduct",
"@id": "https://yoursite.com/tokens/yourtoken/#token",
"name": "Your Token",
"tickerSymbol": "YT",
"url": "https://yoursite.com/tokens/yourtoken/",
"image": "https://yoursite.com/tokens/yourtoken/logo.png",
"description": "YT is YourProtocol's governance token. Controls fee parameters for $200M+ in TVL across 5 supported chains.",
"category": "Cryptocurrency",
"dateCreated": "2024-03-15",
"identifier": [
{"@type": "PropertyValue", "propertyID": "contract", "value": "0xA0b86..."}
],
"additionalProperty": [
{"@type": "PropertyValue", "name": "Blockchain", "value": "Ethereum"},
{"@type": "PropertyValue", "name": "Token Standard", "value": "ERC-20"},
{"@type": "PropertyValue", "name": "Total Supply", "value": "1,000,000,000"},
{"@type": "PropertyValue", "name": "Circulating Supply", "value": "210,000,000"}
],
"sameAs": [
"https://www.coingecko.com/en/coins/your-token",
"https://coinmarketcap.com/currencies/your-token/",
"https://etherscan.io/token/0xA0b86..."
]
}5 errors we catch most often
From auditing 312 token pages in April 2026, these 5 errors appear most often.
1. Missing tickerSymbol. Half the audited pages had no ticker in the schema. The ticker is the most-quoted property in AI engine answers about tokens. Always include it.
2. Blockchain in description but not additionalProperty. Saying 'Ethereum' in the description prose is not the same as declaring it as a structured property. AI engines pull structured properties more reliably than they paraphrase descriptions.
3. Fabricated aggregateRating. Five stars from 12,000 reviews on a token page is a lie. Google catches it. AI engines downweight the entire schema if any field looks fabricated. Omit aggregateRating unless you have a legitimate source.
4. Stale circulating supply. Hardcoded supply numbers go stale within weeks. Either regenerate the schema daily via a build script, or omit the supply property entirely. Don't show old numbers.
5. Wrong @type at the top level. Pages with @type: 'Product' or 'Article' show up frequently. The wrong type is worse than no schema because it actively misclassifies the page.
Validation steps before deploy
Step 1: Schema.org validator. Strictest of the three validators. Will catch type mismatches and required-field omissions Google ignores.
Step 2: Google Rich Results Test. Will tell you if Google parses the schema, even though token pages don't get rich result snippets.
Step 3: Crawlux schema audit. Catches crypto-specific anti-patterns the generic validators miss. Run a free first audit from the form above.
Step 4: Manual AI engine test. A week after deploy, ask ChatGPT and Perplexity 'what is <TOKEN>.' If they quote your description verbatim, the schema is doing its job. If they paraphrase generically or pull from CoinGecko, your schema isn't being read as the canonical source yet.
Common questions
Is FinancialProduct schema indexed by Google?
Yes. Google indexes it for entity classification. Token pages don't get visible rich result snippets in SERPs but the schema affects how the page is categorized.
Should I add FinancialProduct schema to non-token pages?
Only if the page is about a financial instrument. Your homepage isn't a FinancialProduct. Your protocol overview page isn't either. Use FinancialProduct on the dedicated page per token.
Can I use both FinancialProduct and Product?
No. Pick one type per entity. Mixing them creates ambiguity that AI engines resolve by ignoring both.
How often should I update the schema?
When supply changes by 25%+ or when token positioning changes (new use case, new chain, new partnership). Otherwise quarterly is enough.
Do I need ratings or reviews in the schema?
No. Omit aggregateRating for tokens. There's no legitimate review platform with token-level ratings, and fabricated ratings hurt the schema's trustworthiness.
Audit your crypto site in 60 seconds
8-module deep scan. AI visibility, schema, technical SEO, backlinks. One domain free forever.