2026 Structured Data Blueprint

The Ultimate EngineSpecification
Schema Generator

Information about the engine of the vehicle. A vehicle can have multiple engines represented by multiple engine specification entities.

Includes:additionalTypealternateNamedescriptiondisambiguatingDescriptionengineDisplacementenginePowerengineTypefuelType+10 more
Instant JSON-LD Generation

Magic Build

Paste your URL below and our AI will automatically fill the EngineSpecification fields for you.

Configuration

Live Generator

EngineSpecification Schema

Fill in the fields below to generate your JSON-LD. Required fields are marked with *.

Required Fields

The name of the item. (Expects: Text)

Recommended

An image of the item. This can be a [[URL]] or a fully described [[ImageObject]]. (Expects: ImageObject, URL)

URL of the item. (Expects: URL)

Why use EngineSpecification?

Structured data like EngineSpecification markup helps search engines identify the most important details about your content instantly, improving your chances of earning rich results.

Output Panel

Awaiting input...

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 Generator

What is EngineSpecification Schema?

Information about the engine of the vehicle. A vehicle can have multiple engines represented by multiple engine specification entities.

Why It Matters for SEO

Google uses EngineSpecification 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 EngineSpecification 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 EngineSpecification JSON-LD

1

Generate

Use the form above to fill in your details and generate valid EngineSpecification JSON-LD markup in seconds.

2

Copy

Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.

3

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

EngineSpecification 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.

PropertyDescriptionExpected TypeStatus
additionalTypeAn 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, URLOptional
alternateNameAn alias for the item.TextOptional
descriptionA description of the item.Text, TextObjectOptional
disambiguatingDescriptionA 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.TextOptional
engineDisplacementThe volume swept by all of the pistons inside the cylinders of an internal combustion engine in a single movement. \n\nTypical unit code(s): CMQ for cubic centimeter, LTR for liters, INQ for cubic inches\n* Note 1: You can link to information about how the given value has been determined using the valueReference property.\n* Note 2: You can use minValue and maxValue to indicate ranges.QuantitativeValueOptional
enginePowerThe power of the vehicle's engine. Typical unit code(s): KWT for kilowatt, BHP for brake horsepower, N12 for metric horsepower (PS, with 1 PS = 735,49875 W)\n\n* Note 1: There are many different ways of measuring an engine's power. For an overview, see [http://en.wikipedia.org/wiki/Horsepower#Engine\_power\_test\_codes](http://en.wikipedia.org/wiki/Horsepower#Engine_power_test_codes).\n* Note 2: You can link to information about how the given value has been determined using the valueReference property.\n* Note 3: You can use minValue and maxValue to indicate ranges.QuantitativeValueOptional
engineTypeThe type of engine or engines powering the vehicle.QualitativeValue, Text, URLOptional
fuelTypeThe type of fuel suitable for the engine or engines of the vehicle. If the vehicle has only one engine, this property can be attached directly to the vehicle.QualitativeValue, Text, URLOptional
identifierThe 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, URLOptional
imageAn image of the item. This can be a URL or a fully described ImageObject.ImageObject, URLRecommended
mainEntityOfPageIndicates 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, URLOptional
nameThe name of the item.TextRequired
ownerA person or organization who owns this Thing.Organization, PersonOptional
potentialActionIndicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.ActionOptional
sameAsURL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.URLOptional
subjectOfA CreativeWork or Event about this Thing.CreativeWork, EventOptional
torqueThe torque (turning force) of the vehicle's engine.\n\nTypical unit code(s): NU for newton metre (N m), F17 for pound-force per foot, or F48 for pound-force per inch\n\n* Note 1: You can link to information about how the given value has been determined (e.g. reference RPM) using the valueReference property.\n* Note 2: You can use minValue and maxValue to indicate ranges.QuantitativeValueOptional
urlURL of the item.URLRecommended

Example EngineSpecification JSON-LD

Here's what valid EngineSpecification structured data looks like with sample values filled in. Use the generator above to replace these with your own data.

Example Output
{
  "@context": "https://schema.org",
  "@type": "EngineSpecification",
  "name": "Example EngineSpecification",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "description": "A sample description for this EngineSpecification.",
  "disambiguatingDescription": "Example disambiguatingDescription",
  "engineDisplacement": {
    "@type": "QuantitativeValue",
    "name": "Example QuantitativeValue",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  }
}

Validate Your EngineSpecification 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.

Free Schema Audit Tool →

Check your EngineSpecification schema for errors and Rich Result eligibility