WordPress Architecture

A native WordPress architecture for vehicle inventory

Not an external embed and not a disconnected widget layer, ADP Car Market Hub installs as a WordPress plugin and runs natively inside the dealer site, with vehicles stored as real WordPress content, themable templates and admin control inside WP Admin.

View Inventory Demo View Core Platform

Architecture foundation

Native WordPress architecture, not an external embed

ADP Car Market Hub installs as a WordPress plugin on the dealer site. Imported inventory becomes real WordPress content, with stable URLs, structured fields and theme-owned rendering, instead of being rendered through a third-party iframe or feed widget.

Architecture flow

From external feed dependency to native WordPress ownership

From External feed dependency, third-party widget rendering inside someone else's frame.
To Native WordPress-owned architecture: dealer URLs, dealer templates, dealer control.

Architecture stack

The WordPress architecture, layer by layer

Read top to bottom: every layer maps to a familiar WordPress primitive, from the import source down through the WordPress data, taxonomy, render and admin layers, so the inventory channel stays grounded in standard WordPress concepts.

Source

Source & import layer

Validated inventory enters through the official AutoScout24 API on a scheduled cadence, observable inside WP Admin. This is the entry point for every layer below.

  1. Content

    WordPress data layer

    Each vehicle is stored as a real WordPress post in a dedicated public Vehicle custom post type with stable, locale-aware URLs.

  2. Structure

    Taxonomy & metadata layer

    Make, model, body and fuel are first-class WordPress taxonomies; structured fields like price, year and mileage live in predictable WordPress meta.

  3. Render

    Template & rendering layer

    Archive, single and taxonomy views follow the standard WordPress template hierarchy, so the dealer theme owns layout, components and brand.

  4. Workflow

    Admin, workflow & analytics layer

    Settings, imports, vehicle list tables, leads and content health live in WP Admin under standard WordPress roles, capabilities and hooks.

Content model

A structured content model the dealer site can build on

Vehicles, taxonomies, URLs and structured data are all expressed as standard WordPress concepts, so SEO, search, integrations and content workflows all work the way the rest of the site already works.

Vehicle URLs you can link to

Every vehicle gets a stable, locale-aware URL on the dealer domain, driven by WordPress rewrite rules, themable, indexable and shareable like any other native page.

Structured fields & SEO surface

Vehicle attributes are stored as predictable WordPress meta and exposed through indexable HTML and JSON-LD vehicle markup, discoverable by search the same way the rest of the dealer site is.

Taxonomies that power filters

Make, model, body type and fuel are first-class WordPress taxonomies, driving archive pages, faceted search and clean term URLs without bespoke filtering logic.

Hooks, REST & shortcodes

Action and filter hooks, REST endpoints and shortcodes/blocks let agencies extend vehicle output, integrate other systems and place inventory anywhere on the site.

Admin control

Control stays inside WordPress, where the team already works

Imports, content health, vehicles, taxonomies and lead workflows are managed inside WP Admin under standard WordPress roles and capabilities, no separate console, no second login.

  • WP Admin native.Vehicle list tables, edit screens and settings live in the standard WordPress admin UI.
  • Roles & capabilities.Access uses the existing WordPress role system, so dealer and agency teams keep one permission model.
  • Import & cron visibility.Scheduled imports, image processing and content jobs report status inside WordPress with structured logs.
  • Editorial overrides.Editors can augment, feature or annotate individual vehicles directly from the WordPress edit screen.

Theme & rendering

Layout and rendering belong to the dealer theme

When inventory is rendered through an external embed, layout and brand belong to the widget. With a native WordPress architecture, vehicle pages render through the dealer theme, the same templates, components, fonts and brand system as the rest of the site.

External embed / feed widget

Inventory rendered inside someone else's frame

  • Layout and presentation dictated by an external runtime
  • Vehicle URLs and content do not belong to the dealer site
  • Limited SEO and structured-data surface for individual vehicles
  • Theme styles and components stop at the widget boundary
  • Operational data and lead signals stay outside WordPress

Native WordPress architecture

Vehicles render through the dealer theme

  • Archive, single and taxonomy views follow the WordPress template hierarchy
  • Stable, locale-aware vehicle URLs on the dealer domain
  • Indexable HTML and JSON-LD structured data for every vehicle
  • Dealer theme owns layout, components, typography and brand
  • Imports, content and leads governed inside WordPress admin

Extension surfaces

Extends through standard WordPress mechanisms

Because vehicles live as native WordPress content, extending and integrating the platform uses the same primitives as the rest of WordPress, hooks, REST endpoints and scheduled jobs. Dealer teams keep their freedom to evolve the site over time.

Hooks & filters

Extend without forking

Standard WordPress action and filter hooks expose vehicle import, render and lead events so agencies can adjust behaviour from a child theme or companion plugin.

REST API

Vehicle data over REST

Vehicle content is reachable through WordPress REST endpoints, so external systems and headless surfaces can read structured inventory data without scraping HTML.

WP-Cron

Observable scheduled jobs

Imports, image processing and maintenance run through the standard WordPress cron system on a controlled cadence, observable inside WP Admin.

Architectural value

A foundation the dealer site can grow on

A native WordPress architecture is more than a delivery choice, it shapes how the inventory channel evolves, integrates and stays maintainable over time.

Owned foundation

WordPress-native by design, sustainable by default

Vehicle content, URLs, templates and operations all live inside the dealer's WordPress installation. Every primitive is a familiar WordPress concept, so the inventory channel can evolve with the rest of the site instead of being bound to an external runtime.

  • Vehicle content stored as native WordPress entities
  • Stable URLs and structured data persist as the site evolves
  • Hooks, REST and cron keep extension on standard WordPress paths

Continue exploring

Where to go next in the showcase

This page describes the WordPress architecture foundation. The rest of the showcase demonstrates what it looks like in practice.

01 Platform foundation Core Platform See how the WordPress architecture comes together as a complete native platform, the foundation behind every other feature. 02 Structured fields Vehicle Data Structure How vehicle attributes are normalised, stored as WordPress meta and exposed to templates, filters and integrations. 03 Visitor experience Frontend Experience How archive, vehicle detail, search and lead paths render through the dealer theme for visitors and customers. 04 Operational control WordPress Platform Control How platform control stays inside WordPress instead of an external console, and what that means for dealer teams.

Ready to see it

See native WordPress vehicle pages running on a real dealer site

Open the live inventory demo to experience native WordPress vehicle pages, or jump into the full features overview for the complete capability map.

View Inventory Demo Explore Features Contact us