For SEO purposes and sharing on social media it’s common practice to include structured data and meta tags on your vehicle detail page. ILSA can help you with this by providing you with the necessary data.
To include structured data in Schema.org vocabulary, as used by Google and others, add all available structured_data.schema-fields to your details fieldset.
Then, on your vehicle detail page combine these fields into a separate JSON string (JSON.stringify(vehicle.structured_data.schema)) and add it to a <script type="application/ld+json"> tag.
The result should look something like this:
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Car","bodyType":"hatchback",...}</script>
Check with Schema.org’s validator if everything works as intended.
Google Vehicle Listings (and Google Products in general) use the same Schema.org tags so you should be all set by following the steps above. However, Google imposes additional requirements to the data. For example Google requires the VIN (structured_data.schema.vehicleIdentificationNumber) to be present, while Schema.org considers this field to be optional. This might result in both critical and non-critical issues in your Google Search Console. Critical issues (such as the VIN missing) will result in the vehicle listing to be ignored by Google. Non-critical issues are suggestions for improvement. These issues do not affect your page, just the structured data on your page. Have a look at common issues and solutions below.
Check with Google’s test tool or the Google Search Console for any issues.
| Issue | Cause | Possible solutions |
|---|---|---|
| Missing field "vehicleIdentificationNumber" | The advertiser did not supply VIN. |
|
| Missing field "vehicleModelDate" | The advertiser did not supply a model year. | |
| Invalid enum value in field "availability" | The vehicle is expected. | |
| Invalid enum value in field "itemCondition" | The vehicle is damaged. | |
| Missing field "description" (optional) | The advertiser did not supply a vehicle description. |
|
| Missing field "priceValidUntil" (optional) | It is not known how long the price is valid for. | |
| Missing field "shippingDetails" (optional) | The shipping policies are missing. | |
| Missing field "hasMerchantReturnPolicy" (optional) | There return policy of the advertiser is missing. | |
| Missing field "aggregateRating" (optional) | There is no product rating. | |
| Missing field "review" (optional) | There is no product review. | |
| Invalid string length in field "name" (optional) | The make, model and type consists of too many characters. |
|
If someone shares your vehicle detail page Facebook and other media will look for Open Graph tags. Add all available structured_data.opengraph-fields to your details fieldset and transform these into <meta property="og:{field}"> content="{value}" /> tags in the <head> section of your page.
The result should look something like this:
<meta property="og:title" content="MINI Cooper Hatchback" />
<meta property="og:type" content="product" />
<meta property="og:url" content="..." />
<meta property="og:image" content="https://images.ilsa.cloud/..." />
Check with Meta’s Sharing Debugger if everything works as intended.
To include an X or Twitter Card to your vehicle detail page add all available structured_data.xcard-fields to your details fieldset and transform these into <meta property="twitter:{field}"> content="{value}" /> tags in the <head> section of your page.
The result should look something like this:
<meta property="twitter:card" content="summary_large_image" />
<meta property="twitter:title" content="MINI Cooper Hatchback" />
<meta property="twitter:description" content="..." />
<meta property="twitter:image" content="https://images.ilsa.cloud/..." />
Check with X if everything works as intended.