Frontend Experience

A native vehicle browsing experience on the dealer website

ADP Car Market Hub turns your inventory into a searchable, themeable and lead-ready browsing experience on the dealer website, including archive pages, vehicle cards, filter and sort controls, vehicle detail pages and customer journeys that stay on the dealer site. Add vehicles in the backend or import them optionally via the AutoScout24 API.

View Inventory Demo Explore Features

More than a vehicle list

A dealer website should guide the browsing experience, not just display vehicles

A native vehicle browsing experience supports searching, filtering and browsing your inventory, reuses vehicles across the site, and turns vehicle interest into clearer next steps for the visitor.

  • Native archive pages. Real inventory pages on the dealer domain — not an embedded frame.
  • Search and filter logic. Filtering, sorting and keyword search live on the dealer site.
  • Vehicle cards as components. Reusable website modules, not just rows in a list.
  • Clear paths to detail. Each vehicle has its own detail page on the dealer domain.
  • Lead-ready journeys. Compare, favorites and contact stay inside the dealer site.

On the dealer website

What the visitor actually uses

The frontend experience is made of real, native components that the visitor interacts with directly on the dealer website — not inside a third-party widget.

Search

Filter and search

Make, model, price, fuel and more — visitors narrow inventory directly on the dealer site.

Archive

Vehicle archive

A native results page with paginated inventory, all hosted on the dealer domain.

Controls

Sort and browse controls

Sort by price or date, switch between grid and list, and adjust results per page.

Component

Vehicle cards

Photo, title, price and key specs — themeable cards that match the dealer site.

Detail page

Vehicle detail pages

Each vehicle gets a native page with full specifications, gallery and contact options.

Lead

Compare, favorites & lead entry

Save vehicles, compare side by side and send enquiries — all from the dealer site.

Customer journey

From browse to enquiry on the dealer website

Visitors move from the inventory archive into a vehicle detail page, take an action that signals intent, and submit an enquiry, all without leaving the dealer site.

  1. Archive view Browse archive Visitor lands on the inventory archive and uses filters and sort to narrow the result set. Discovery
  2. Vehicle detail Open vehicle detail A native vehicle page presents gallery, specifications and pricing on the dealer domain. Engagement
  3. Customer intent Compare, save, continue Visitor saves favorites or adds vehicles to the comparison view — all on the dealer site. Intent signal
  4. Lead captured on site Contact dealer The enquiry is submitted from the vehicle detail page and stays inside the dealer website. Lead

Directional journey — exact steps follow the visitor, but every step lives on the dealer website.

Reusable components

Vehicle cards become reusable website components

Once inventory is native WordPress content, vehicle cards and inventory snippets can be reused across landing pages, promotions, highlight sections, related vehicles and campaign pages — instead of being rebuilt every time.

  • Themeable cards that follow the dealer brand.
  • Drop-in modules for landing pages and editorial pages.
  • Consistent presentation across the whole site.

Component library

Reusable inventory modules

  • Featured vehicle card Hero placement on the home page or a campaign page Block
  • Similar vehicles Related inventory shown next to the current vehicle Block
  • Campaign spotlight Curated vehicles for a seasonal or promotional moment Page
  • Recently added vehicles Auto-updating list of the newest inventory Shortcode
  • Model promotion strip Highlight a specific make or model across the site Block
Inventory becomes a reusable design system — not a single page.

Practical benefits

Practical benefits of a stronger vehicle browsing experience

A real, native browsing experience supports clearer vehicle discovery, a dealer-owned customer journey and reusable website value, without forcing the visitor into an external frame.

BrowsingClearer UX

Better browsing clarity

Native filters, sort controls and vehicle cards make it easier for visitors to find what they actually want.

OwnershipOn-site

Dealer-owned customer journey

Browse, compare, save and contact — the whole journey stays inside the dealer website.

LeadsLead-ready

Clearer lead paths

Contact, favorites and comparison sit on the vehicle page — making it easier to capture interest.

ComponentsReusable

Reusable website components

Vehicle cards and inventory blocks can power campaigns, landing pages and editorial sections.

DesignOn-brand

Themeable presentation

Inventory follows the dealer theme and brand — not a third-party widget style.

SEOIndexable

SEO-friendly vehicle pages

Each vehicle has its own native page with stable URLs — discoverable on the dealer domain.

Two visitor experiences

Two ways the visitor can experience your inventory

An embedded feed shows vehicles inside an external frame on the dealer page. A native frontend experience makes the vehicles part of the dealer website itself.

Embedded feed

External frame on the dealer page

  • Browsing surface Isolated experience Limited
  • Design control Bound to the widget Limited
  • Component reuse Hard to reuse elsewhere Weak
  • Customer journey Hard to shape end to end Review
  • Lead route Often leaves the site Review

Native dealer website

ADP Car Market Hub frontend experience

  • Browsing surface Real archive pages Native
  • Design control Themeable layout Themeable
  • Component reuse Reusable vehicle components Reusable
  • Customer journey Owned by the dealer Owned
  • Lead route On the vehicle page Connected

Directional comparison — exact behavior depends on each embed solution and each WordPress site setup. See the full feed vs platform comparison

Operational summary

The dealer website becomes the center of the inventory experience

Archive browsing, search, vehicle detail pages, lead routes and reusable inventory modules all live on the dealer site — making the dealer website the operational center of the visitor experience.

The agency or implementation partner builds on top of the same WordPress, instead of integrating around an external embed.

Frontend operations

What lives on the dealer site

  • Vehicle archive Native results page On site
  • Search & filter Filter and sort logic On site
  • Vehicle detail Native vehicle page Indexable
  • Lead routes Contact, favorites, compare Connected
  • Reusable modules Blocks & shortcodes Reusable
  • Dealer-owned value Domain, content, journey Owned
A frontend layer the dealer actually owns and can build on.

Continue exploring

Where to go next in the showcase

This page focused on the visitor-facing frontend experience. The rest of the showcase covers the platform itself, the business case and how it compares to an embedded vehicle feed.

01 Platform Platform Overview How the WordPress plugin turns AutoScout24 inventory into owned content. 02 Architecture Native WordPress Platform Why the inventory layer is a native WordPress plugin instead of an external embed. 03 See it live Inventory Demo Browse native vehicle pages exactly as a visitor would on a dealer website. 04 Capability map Features overview The complete capability map of the WordPress plugin behind the frontend.

Ready to see it

See the vehicle browsing experience on a real dealer site

Open the inventory demo to see how native WordPress vehicle archive pages and vehicle details work in practice — or jump into the full features overview for the complete capability map.

View Inventory Demo Explore Features