NPM JavaScript Module & Node Package Schema (JSON-LD Blueprint)
Structured data for NPM modules, TypeScript libraries, and Node.js packages with install commands, peer dependencies, and license badges.
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": "SoftwareApplication",
"name": "@omniseo/core",
"applicationCategory": "DeveloperApplication",
"operatingSystem": "Node.js 18+, Bun, Deno, Modern Browsers",
"softwareVersion": "3.4.1",
"downloadUrl": "https://www.npmjs.com/package/@omniseo/core",
"license": "https://opensource.org/licenses/MIT",
"requirements": "Node.js >= 18.0.0",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
},
"description": "Ultra-fast TypeScript library for schema linting, Open Graph image dimension checking, and Core Web Vitals physics calculations."
}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 |
|---|---|---|---|
| downloadUrl | URL | Required | Direct canonical link to NPM registry page. e.g. https://www.npmjs.com/package/@omniseo/core |
| softwareVersion | Text | Required | Latest NPM published release version. e.g. 3.4.1 |
| operatingSystem | Text | Required | Supported JS runtimes (Node.js, Deno, Bun, Browser). e.g. Node.js 18+, Bun, Deno |
| license | URL | Required | Package open-source license URI. e.g. https://opensource.org/licenses/MIT |
| requirements | Text | Recommended | Node engine versions and peer dependencies. e.g. Node.js >= 18.0.0 |
| applicationCategory | Text | Required | Must be 'DeveloperApplication'. e.g. DeveloperApplication |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying SoftwareApplication schema.
Missing Scoped Package Name in Schema
Listing plain 'core' instead of full scoped '@omniseo/core' package identifier.
Use exact published name '@scope/pkg'.
Missing Runtime Platform Specifications
Omitting runtime environments (Node, Deno, Bun) leaves compatibility ambiguous.
Enumerate runtimes in operatingSystem.
Mismatched softwareVersion vs package.json
Publishing v3.4.1 but hardcoding v1.0.0 in static schema snippet.
Automate schema version synchronization with package.json.
Recommended Implementation Scenarios
Related Schema Blueprints
Explore complementary structured data blueprints across the Technical SEO cluster.
Python Package (PyPI) & Wheel Distribution Schema (JSON-LD)
SoftwareSourceCode & Git Repository Schema (JSON-LD Blueprint)
DeveloperSDK & Client Library Toolkit Schema (JSON-LD)
OpenSourceProject & Community Hub Schema (JSON-LD Blueprint)
Displayed below main page header or above the tool container. • Zero CLS Container