3D CAD Model & Game Engine Asset Schema Markup (JSON-LD)
Structured data for 3D digital models, game assets, CAD engineering blueprints, and AR/VR meshes, detailing polygon counts, PBR textures, file formats (FBX, OBJ, GLTF), and licenses.
Displayed below main page header or above the tool container. • Zero CLS Container
Production JSON-LD Code Block
Embed this structured data block directly into your HTML <head> or framework layout template.
{
"@context": "https://schema.org",
"@type": "3DModel",
"@id": "https://example.com/models/sci-fi-mech-walker#asset",
"name": "Sci-Fi Heavy Bipedal Mech Walker 3D Game Asset",
"description": "Production-ready rigged and animated sci-fi mech walker with 45,000 polygons, 4K PBR textures (Albedo, Normal, Roughness, Metallic), and ready for Unreal Engine 5 and Unity.",
"encodingFormat": "model/gltf-binary",
"license": "https://example.com/licenses/commercial-game-asset",
"offers": {
"@type": "Offer",
"price": "45.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"seller": {
"@type": "Organization",
"name": "PolyForge 3D Assets"
}
}
}Typed Properties Specification (6 Fields)
Key Schema.org properties and sub-objects required to qualify for rich snippet treatment in Google Search.
| Property | Expected Type | Status | Description & Example |
|---|---|---|---|
| name | Text | Required | Official title of the 3D model, mesh, or CAD component. e.g. Sci-Fi Heavy Bipedal Mech Walker 3D Game Asset |
| encodingFormat | Text | Required | Standard MIME format for 3D files (e.g. model/gltf-binary, model/obj). e.g. model/gltf-binary |
| license | URL | Required | Direct URL to game asset or commercial rendering license terms. e.g. https://example.com/licenses/commercial-game-asset |
| offers | Offer | Required | Download price, currency, availability, and vendor store. e.g. { "@type": "Offer", "price": "45.00", "priceCurrency": "USD" } |
| description | Text | Recommended | Technical specifications covering polygon count, UV mapping, rigging, and texture resolution. e.g. Production-ready rigged and animated sci-fi mech walker with 45,000 polygons... |
| inLanguage | Text | Recommended | Asset documentation language (e.g. 'en'). e.g. en |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying 3DModel schema.
Missing Standard MIME Type on encodingFormat
Using informal extensions like '.fbx' instead of standardized MIME types like 'model/gltf-binary' causes 3D viewer search parsers to fail.
Use standard MIME types (e.g. model/gltf+json, model/gltf-binary).
Omitting Polygon and Rigging Details in Description
Game developers filter strictly by polygon budget (low-poly vs high-poly); omitting poly counts reduces developer search relevance.
State exact polygon count and rigging status in description.
Missing Commercial Game Engine License URL
Developers require clear game distribution rights; omitting the license link slows purchase decision cycles.
Include absolute HTTPS link to commercial licensing terms.
Recommended Implementation Scenarios
Related Schema Blueprints
Explore complementary structured data blueprints across the Creative Work & Media cluster.
NFT & Digital Artwork Collectible Schema Markup (JSON-LD)
Audio Sample Pack & Royalty-Free Sound Library Schema Markup (JSON-LD)
Digital Software License & Activation Key Schema Markup (JSON-LD)
Commercial Digital Font & Typography Family Schema Markup (JSON-LD)
Displayed below main page header or above the tool container. • Zero CLS Container