Vehicle Data Structure

Structured vehicle content, ready for templates, filters, leads and search

ADP Car Market Hub does more than import vehicles, it turns marketplace data into a clean, normalized WordPress data model that powers archives, detail pages, comparison, favourites, leads, analytics and schema-ready SEO output.

View Inventory Demo Explore Features

Data transformation

From raw import data to structured dealer content

Imported marketplace fields rarely match what a dealer website actually needs. ADP Car Market Hub normalizes incoming data into a stable structure so every vehicle becomes editable, queryable WordPress content, not a feed dump.

Transformation flow

Three controlled stages, one stable record

  1. Incoming source fields

    Raw marketplace attributes arrive with mixed naming, units and locale conventions, including loose categorical values.

  2. Normalized data model

    Fields are mapped to a typed schema with consistent units, currencies and taxonomy assignments, ready for queries and templates.

  3. Published WordPress vehicle

    Each record becomes a real WordPress vehicle post with grouped meta-boxes, taxonomies, media and schema, owned by the dealer site.

Data model

The vehicle data model, organized for real use

Every vehicle is described through four cooperating layers. Each layer stays independently useful, but together they make the same record available to templates, archive filters, comparison, leads, analytics and search.

Core attributes

Typed fields, ready to query

Make, model, mileage, price, year and power are stored as predictable fields with units and currency, so templates and queries can read them by name.

Taxonomies & filters

Faceted, archive-ready terms

Categorical attributes become real WordPress taxonomies, so dealers and visitors filter inventory by make, body type, fuel, transmission and condition without custom queries.

Metadata · SEO surface

Indexable, schema-ready metadata

Each vehicle exposes a stable slug, structured title, JSON-LD vehicle markup and OpenGraph fields, the SEO surface lives next to the data model, not bolted on.

Media & equipment

Gallery, equipment and labels

Vehicle media, equipment groups and labels are kept structured rather than flattened into a single text field, so detail pages and comparison can render them properly.

Backend product surfaces

How the data model looks inside WordPress

Editors meet the data model through real WordPress admin surfaces, not through abstract diagrams. Each card below illustrates one of the screens an inventory team uses every day.

Vehicles · Edit Edit screen

Grouped meta-boxes

Structured fields are surfaced in clear groups so editors can scan, override and publish without hunting through long flat forms.

  • Vehicle basics
  • Pricing & VAT
  • Technical details
  • Equipment groups
  • Media gallery
  • Publishing & visibility
Taxonomies Attribute panel

Taxonomy assignment

Make, body type, fuel, transmission and condition map to native WordPress taxonomies, so archive filters and search read directly from the same data.

  • MakeAudi
  • Body typeEstate
  • FuelDiesel
  • TransmissionS tronic
  • ConditionUsed
Import rules Field mapping

Source → normalized field

Each incoming attribute maps to a typed field with explicit units and a status, so dealers always know what is synced, derived or controlled.

  • make_name vehicle.make Synced
  • price_eur vehicle.price Synced
  • km_total vehicle.mileage Synced
  • image[] vehicle.media Queued
  • status vehicle.status Controlled
Equipment · Media Library panel

Equipment groups & labels

Equipment is structured into groups with consistent labels and shared across templates, comparison and search, never just a wall of free text.

Comfort Climate Heated seats Keyless
Safety Lane assist ACC Cameras
Media +15

Frontend impact

Structured data powers archive, filters and detail pages

Because the same structured fields back every public surface, dealers get faceted filters, comparable detail pages, favourites and leads that always reference the same vehicle truth.

/inventory/?make=audi&fuel=diesel
Audi A4 Avant 40 TDI 2024 · 12,480 km · Diesel
€ 38,900
Audi Q5 35 TDI quattro 2023 · 24,100 km · Diesel
€ 42,400
Audi A6 Avant 40 TDI 2024 · 8,720 km · Diesel
€ 44,950

SEO & schema surface

Schema-ready output, baked into the model

Because vehicle metadata is structured at the source, every detail page already carries an indexable URL, a clean H1, JSON-LD vehicle markup and OpenGraph fields, without bolt-on plugins to glue it together.

https://dealer.example.com/inventory/audi-a4-avant-2024 Detail page · indexable
Slug /inventory/audi-a4-avant-2024 Locale-aware, dealer-owned URL
H1 Audi A4 Avant 40 TDI quattro · 2024 Composed from structured fields
JSON-LD schema.org/Vehicle Make · model · price · mileage · fuel
OpenGraph og:title · og:image · og:price Linked sharing previews ready
Indexable HTML Stable URLs Vehicle schema No bolt-on plugin needed

Business value

Why a structured data model matters for dealers and agencies

A structured vehicle model is not a technical luxury, it changes how dealer teams manage inventory and how agencies build the dealer experience.

Dealer operations

Cleaner inventory management

Inventory teams work with grouped, predictable fields, pricing, technical and media, instead of long flat forms or external dashboards.

Agency · implementation

Reusable across templates

Archive, detail, comparison, favourites and lead modules all read the same fields, so agencies build once and reuse without bespoke glue code.

Marketing & SEO

Search & schema by default

Indexable URLs, structured titles and JSON-LD vehicle markup are part of the data model, not a separate SEO project on top of the inventory.

Long-term ownership

Stable foundation to extend

Future integrations, analytics and AI features plug into a stable structured model, so the inventory channel evolves without a rebuild.

Continue exploring

Where to go next in the showcase

This page describes the structured vehicle data model. The rest of the showcase demonstrates how that model is used in practice.

01 Platform foundation Core Platform See how the structured data model fits into the wider native WordPress platform behind every capability. 02 Archive & filters Inventory Archive See how the structured fields drive the faceted archive, search and filter experience. 03 Detail experience Vehicle Detail See the structured data model rendered as a complete native WordPress vehicle detail page. 04 See it live Inventory Preview Browse a real native vehicle inventory and see the data model running on a real WordPress site.

See the structure live

See structured vehicle data running on a real dealer site

Open the live inventory demo to see the structured data model in action, across archive, detail, comparison and lead surfaces, or jump back into the full features overview.

View Inventory Demo Explore Features Contact us