Crypto Schema Generator. JSON-LD that actually fits Web3.
Build valid schema.org JSON-LD for crypto projects across 7 types with crypto-specific fields: tickerSymbol, blockchain, tokenStandard, contractAddress, audit firms, authority sameAs. Live preview, validation warnings, copy-paste ready as pure JSON or inline script tag. Built to match the same checks the Crawlux Token Schema audit module runs against your live domain.
Free · No signup · Works in your browser
Pick your schema type. Fill the fields. Copy the output.
Live JSON-LD preview updates as you type. Switch output between pure JSON and inline script tag. Validation warnings fire before you ship.
Token (FinancialProduct)
Run a free Crawlux audit of your live domain
You generated JSON-LD. Crawlux is our free audit tool — it scans your full domain and shows you whether AI engines actually pick up your schema and cite your project. Covers schema, AI visibility, technical SEO and 5 more areas. Takes about 4 minutes. No signup, no credit card.
200+ Web3 brands audited · No credit card · No setup
Three steps. About 90 seconds per schema.
No signup. No data leaves your browser. Build one schema at a time, drop each into the page it belongs on.
Pick your schema type
Choose from Token (FinancialProduct), Exchange, Organization, dApp/Wallet (SoftwareApplication), FAQ, Breadcrumb or Article. Each has crypto-specific fields built in: chain dropdowns, token standards, audit firms, authority sameAs URLs.
Fill the form fields
Required fields are flagged. Click Load sample to drop in production-grade examples (Aave token, Uniswap exchange, Phantom wallet, Aave Companies). Optional fields like audit firms, sameAs URLs and tokenomics data are where AI engines find authority signals.
Copy or download the output
Copy as pure JSON to drop into a backend or static site generator. Switch to Inline script for a ready-to-paste script tag. Download as .json. Validation warnings fire live so you fix issues before they ship.
7 schema types. All crypto-aware.
Each type maps to specific page types on a crypto site. Use them in combination on the same page when it makes sense.
FinancialProduct (Token)
For the page describing your token. Fields cover tickerSymbol, blockchain, token standard (ERC-20, ERC-721, BEP-20, SPL), contract address, total supply, launch date. Crypto-specific extensions go through additionalProperty entries. Audit firms map to auditedBy Organization entities. This is the schema the Token Schema audit module validates against.
CryptoExchange
For DEX or CEX homepages and product pages. Native schema.org type with exchangeType, foundingDate, areaServed, supported blockchains, sameAs to listings and authority pages. Use this instead of Organization for exchange domains, as schema.org provides this as a specialized type.
Organization
For project homepages, team pages and footer schema. Fields cover legalName, founders (multiple Person entities), founding date, employee count, address, sameAs URLs to Twitter, GitHub, LinkedIn, CoinGecko, Etherscan. Logo URL is the field that causes most rich result rejections when missing.
SoftwareApplication (dApp / Wallet)
For dApps, wallets, browser extensions and on-chain games. Application category (DeFi, NFT Marketplace, Wallet, GameFi, DEX, etc.), operating system (Web, iOS, Android, Chrome Extension), pricing model and optional aggregate rating. Used to qualify for app card rich results.
FAQPage
For any page with Q&A content. mainEntity is an array of Question entities with acceptedAnswer. AI engines (ChatGPT, Perplexity, Claude) heavily prefer FAQ-shaped content for citation. Build 5 to 12 entries per page, answers 1 to 4 sentences, named entities and concrete numbers wherever possible. This is the highest-leverage AEO win for most crypto projects.
BreadcrumbList
For every non-homepage page. itemListElement is an ordered array of ListItem entries with position, name and item (full URL). Helps both search engines and AI engines understand site structure. Auto-positions in the generator output. Required for the breadcrumb appearance in Google SERP.
Article
For blog posts, news and long-form content. Headline, description, author (Person sub-entity with name, URL, bio), datePublished, dateModified, image, publisher (Organization sub-entity with logo). mainEntityOfPage links back to the canonical URL. The crypto-aware version handles author E-E-A-T signals that Google and AI engines weight heavily.
Common questions about crypto schema markup
Patterns from crypto founder DMs, dev team questions and TG3 client audits.
Why does crypto need its own schema generator?
Generic schema generators do not know what blockchain a token is on, what token standard it follows, what audit firms validated the contract or what authority sources to link in sameAs (CoinGecko, CoinMarketCap, Etherscan). Crypto-specific fields like tickerSymbol, contractAddress, totalSupply, tokenStandard and audit firm citations need explicit handling. Schema.org technically allows all of this through additionalProperty extensions but no generic generator builds them by default.
Which schema types should I use for a crypto project?
The minimum trio for any crypto homepage is Organization plus FAQPage plus BreadcrumbList. Token projects add FinancialProduct on the token page. Exchanges use CryptoExchange instead of Organization. dApps and wallets use SoftwareApplication. Blog posts use Article. Most pages benefit from BreadcrumbList for navigation context. Validate everything you ship against the Token Schema Tester before going live.
Should I use FinancialProduct or CryptoCurrency for a token?
FinancialProduct is the schema.org type with broadest acceptance by Google and AI engines. There is no native CryptoCurrency or CryptoToken type in schema.org. We add crypto-specific data via additionalProperty fields (blockchain, tokenStandard, contractAddress, totalSupply, launchDate) attached to FinancialProduct. This pattern is what the Crawlux Token Schema audit module validates.
Where do I paste the generated JSON-LD?
Inside a script tag in the head of the relevant page: script type equals application slash ld plus json. The generator can output it pre-wrapped with the script tag, just toggle the Inline script output mode and copy. Each entity type usually goes on its corresponding page: Organization on the homepage, FinancialProduct on the token page, Article on each blog post, BreadcrumbList on every non-homepage page.
What is sameAs and why does it matter?
sameAs is the schema.org property that links your entity to its authoritative profiles elsewhere on the web. For crypto, that means your CoinGecko page, CoinMarketCap page, Etherscan contract page, official Twitter, GitHub, Discord and Telegram. AI engines use sameAs to verify an entity is real and authoritative. Missing sameAs is one of the top reasons crypto projects do not get cited by AI search engines. The AI Visibility audit module specifically scores this.
Do audit firms need to be in the schema?
Yes, on the token page schema. The auditedBy property accepts an array of Organization entities. Naming the audit firms (Trail of Bits, OpenZeppelin, Spearbit, Halborn, CertiK) by name in machine-readable schema gives AI engines a clean signal of security investment. The Crawlux Token Schema audit module specifically checks for this and surfaces missing audit firm citations as a critical gap.
How many FAQ items should I have on a page?
5 to 12 FAQ entries works best for AEO. Below 5 is too thin for AI engines to consider it a real FAQ section. Above 12 starts to feel padded. Each answer should be 1 to 4 sentences, with concrete numbers and named entities where possible. Reuse the FAQ schema across page types: homepage, product page, blog posts can each have their own contextual FAQ block.
Does Google still respect FAQPage schema for rich results?
Google reduced FAQPage rich result eligibility in 2023, but FAQPage schema still helps AI engines (ChatGPT, Perplexity, Claude) parse question-answer pairs and cite them. AEO benefit remains strong even where Google SERP benefit reduced. Build FAQPage schema for AI citation, not for blue-link snippet competition.
Schema markup, specifically for Web3
Schema.org is a generic vocabulary. When a search engine or AI engine processes structured data, it does not care whether the entity is a coffee shop, a SaaS product or a crypto protocol. It cares whether the data is machine-parseable, internally consistent and externally verifiable.
For crypto, the externally-verifiable part is what most projects miss. Generic schema generators build clean Organization or Product entities. They miss the data that actually proves your project is real: which chain you live on, what audit firms validated your contracts, which authority sources confirm your identity.
Where AI engines look for crypto entity verification
When ChatGPT or Perplexity decides whether to cite your project in an answer, they cross-reference multiple signals. Your sameAs URLs are checked against the actual authority pages. Your blockchain claim is checked against on-chain data through services like Etherscan and CoinGecko. Your audit firm citations are checked against the audit firms' published client lists. None of this is mysterious. It is mechanical entity verification.
Projects that surface this data in schema markup get cited. Projects that hide it in PDF whitepapers and image-based marketing pages do not. The AI Visibility audit module measures the citation frequency gap, which compounds month over month as more crypto users use AI engines as their primary research interface.
The trio every crypto homepage needs
Three schemas on the homepage cover most of the AEO benefit:
Organization with sameAs to Twitter, GitHub, CoinGecko, Etherscan, blog and Discord. Logo URL must be hosted on the same domain. Founders named explicitly via Person sub-entities. This is the entity AI engines look up.
FAQPage with 6 to 10 Q&A pairs covering the most common queries: what the project is, how it works, what makes it different, where to start. Each answer 1 to 4 sentences with concrete numbers. This is where AI engines pull direct quotes.
BreadcrumbList for navigation context. Almost trivially small but gives crawlers the site structure. Add this to every non-homepage page.
Token pages need their own treatment
The token page is where most schema markup oversights show up. FinancialProduct with full additionalProperty coverage (blockchain, tokenStandard, contractAddress, totalSupply, launchDate) plus auditedBy citing the actual firms by name plus sameAs to CoinGecko, Etherscan, CoinMarketCap and Twitter. Run the output through the Token Schema Tester before shipping. The Crawlux Token Schema audit module validates every check against your live domain in seconds.
FAQ schema is the underweighted AEO lever
Most crypto projects do not have FAQ sections at all. Of those that do, most do not mark them up as FAQPage schema. Of those that do mark them up, most have generic FAQs that read like a security blog from 2019. The leverage in 2026 is in writing 8 to 10 sharp FAQ entries with concrete data (audit firm names, token contract addresses, blockchain, TVL figures, founding dates) and marking them up as FAQPage schema on the homepage. Whitepapers with FAQ sections at the end get cited at materially higher rates than whitepapers without.
SoftwareApplication for dApps and wallets
For dApps and wallets, SoftwareApplication is the right type. applicationCategory should be specific (DeFi, Wallet, GameFi, NFT Marketplace, DEX, Lending, DAO Tooling) not generic. operatingSystem can be a comma-separated list including Web, iOS, Android, Chrome Extension. The aggregateRating field is high-leverage if you have real ratings from app stores or review sites, but should not be fabricated.
The validation step is mandatory
Schema markup that fails validation does worse than no schema at all. Use Google's Rich Results Test or schema.org's validator on every output before shipping. The Crawlux Token Schema audit module runs validation automatically against your live domain, plus the crypto-specific extensions Google's tools do not check (audit firm naming, sameAs to crypto authority sources, blockchain claim consistency).
Generate the schemas here. Test them with the Token Schema Tester. Then audit the live deployment with Crawlux. Three tools, one workflow, no excuses for missing entity verification in 2026.
Generate schema here. Audit your live domain with Crawlux.
Schema generated. Crawlux is our free audit tool that scans your full domain and gives you a complete report on whether the schema actually lifts your AI citation rate, plus 7 other audit areas. Takes about 4 minutes. No signup, no credit card.