Implementation

From your inventory to a live native WordPress dealer website

ADP Car Market Hub supports a structured WordPress implementation, from inventory setup to native WordPress vehicle pages, lead workflows, launch readiness and operational handover. Add vehicles in the backend or connect the AutoScout24 API optionally. The plugin gives dealer teams and agencies a repeatable rollout model instead of a custom rebuild every time.

View Inventory Demo Explore Features

What implementation actually means

A WordPress implementation is more than installing a plugin

A real implementation is the structured delivery of a native WordPress vehicle platform. ADP Car Market Hub helps move from your inventory to a live, owned, SEO-friendly dealer website with vehicle pages, lead workflows, reusable components, reporting visibility and a clean operational handover.

  • AutoScout24 inventory connection. A scheduled, structured AutoScout24 inventory workflow into WordPress.
  • Native vehicle pages. SEO-friendly vehicle pages with stable URLs on the dealer domain.
  • Lead workflows. Contact, favorites and comparison feeding structured queues inside WordPress.
  • Reusable components. Shortcodes and inventory blocks the team can reuse on campaign and landing pages.
  • Operational handover. Reporting visibility and a documented handover so the dealer team can run the site.

Implementation phases

A controlled WordPress rollout, phase by phase

Five structured phases turn your inventory into a live native WordPress dealer website. Each phase has a clear focus, a small set of concrete tasks and a defined output, so dealer teams, agencies and implementation partners always know where the project stands.

  1. 01 Discovery & requirements
    • Align scope, brand and target markets
    • Confirm AutoScout24 access and approvals
    • Map page priorities and lead surfaces
    Output Aligned implementation plan
  2. 02 Connection & data setup
    • Connect AutoScout24 API to WordPress
    • Validate inventory import and structure
    • Configure locale and URL structure
    Output Live AutoScout24 inventory in WordPress
  3. 03 Page & component build
    • Build vehicle detail and archive pages
    • Apply brand, theme and layout system
    • Wire lead surfaces and reusable blocks
    Output Branded native vehicle pages
  4. 04 QA & launch preparation
    • Review SEO structure and indexability
    • Test lead routing and tracking signals
    • Confirm launch readiness across teams
    Output Validated, launch-ready website
  5. 05 Handover & operation
    • Walk the dealer team through the admin
    • Document inventory and lead workflows
    • Confirm reporting and ownership
    Output Operational handover & ownership

Inputs vs outputs

What the client provides — what the implementation team delivers

A clear split of responsibilities makes the rollout easier to explain and easier to plan. The dealership or dealer group provides a small, well-defined set of inputs. The implementation team — internal or agency — turns those inputs into a structured WordPress vehicle inventory platform.

Client inputs

What the dealership provides

  • AutoScout24 access API credentials & approval Required
  • Brand assets Logo, colors, typography Provided
  • Page priorities Inventory, contact, locations Provided
  • Approval contacts Sales, marketing, ownership Required
  • Legal & regional rules Imprint, privacy, locales Required

Implementation outputs

What the implementation team delivers

  • Vehicle page structure Detail & archive pages Delivered
  • Templates & components Reusable inventory blocks Delivered
  • Lead surfaces Contact, favorites, compare Delivered
  • Launch setup SEO structure & routing Delivered
  • Tracking & reporting Inside the WordPress admin Delivered
  • Handover notes Operating model & ownership Delivered

Implementation output

A live native WordPress vehicle platform

At the end of an implementation, the dealership has a structured WordPress site driven by AutoScout24 inventory — with a defined deliverables list and a dashboard-style view of where each component stands.

Output board

Where the rollout stands

  • Pages ready On track
  • Components ready Wired
  • Lead routes Active
  • Handover In review
  • Vehicle pages built Ready
  • Components wired Ready
  • Lead routes connected Active
  • Launch readiness Review
  • Handover documentation In progress
Directional view — exact readiness depends on each project.

Project model options

Three WordPress implementation models, one repeatable platform

The same WordPress plugin supports a single dealer site, a multi-site dealer group rollout, or an agency-led implementation. The structure stays the same — only the focus and scale change.

Single dealership website

Best fit
Independent dealerships and garages running their own WordPress site.
Implementation focus
AutoScout24 inventory, native vehicle pages, lead workflows, launch.
Output
A live, owned, SEO-friendly dealer website.
Launch-ready site

Dealer group rollout

Best fit
Dealer groups with several brands, locations or country sites.
Implementation focus
Repeatable structure, shared components, locale-aware URLs.
Output
A consistent inventory experience across every site.
Scalable rollout

Agency-supported implementation

Best fit
WordPress agencies and implementation partners delivering for dealer clients.
Implementation focus
Reusable plugin capabilities, design control, clean integration points.
Output
A repeatable rollout model the agency can apply per client.
Repeatable model

Launch readiness & handover

How teams know the implementation is ready

A structured readiness view replaces guesswork with a clear, shared picture. The board on the right illustrates the categories an implementation typically covers — directional only, not a guaranteed launch claim.

What launch readiness covers

  • Inventory & pages AutoScout24 connection, vehicle pages and templates
  • Lead & SEO surfaces Contact routes, structure and indexability
  • Reporting & handover Visibility in WordPress and a clear team handover
Status Ready Review Planned
  • Inventory connection Ready
  • Vehicle pages Ready
  • Lead routes Ready
  • Design & templates Ready
  • SEO structure Review
  • Reporting visibility Review
  • Team handover In progress
Structured readiness — designed to make the launch decision easier to explain. Summary Structured readiness Reviewable launch state Handover visibility

Risks & how the structure helps

Common WordPress implementation risks and how the platform addresses them

Most rollout problems are not technical — they are structural. A repeatable WordPress plugin model helps reduce a small set of common risks, without removing the need for project ownership.

  • Risk Unclear feed ownership Inventory lives inside someone else's widget, with no clear control. Platform response Native AutoScout24 inventory Inventory lands as native WordPress content with structured ownership.
  • Risk Weak page structure No real SEO surface for individual vehicles, no stable URLs. Platform response SEO-friendly vehicle pages Stable URLs, structured data and locale-aware slugs by default.
  • Risk Fragmented lead routes Contact, compare and favorites scattered across disconnected tools. Platform response Lead workflows on vehicle pages Contact, favorites and comparison feed structured queues in WordPress.
  • Risk Manual campaign rebuilds Marketing pages re-built from scratch every campaign, every season. Platform response Reusable inventory blocks Shortcodes and components support repeatable campaign and landing pages.
  • Risk Unclear reporting No shared view of inventory, leads and engagement after launch. Platform response Reporting inside WordPress Engagement and lead signals surface in the same admin the team uses.
  • Risk Handover gaps After launch, the dealer team is unsure how to operate or extend the site. Platform response Documented operational handover A clear handover step closes the project and sets up day-to-day ownership.

Continue exploring

Where to go next in the showcase

This page describes how an implementation is structured. The rest of the showcase explains the platform itself, the business value, the dealer and agency perspectives, and what the result looks like in practice.

01 Platform Platform Overview How the native WordPress plugin turns AutoScout24 inventory into owned content. 02 Dealer view For Dealerships How dealerships, dealer groups and garages benefit from a native WordPress plugin. 03 Agency view For Agencies How WordPress agencies and implementation partners build with the plugin. 04 See it live Inventory Demo Browse native vehicle pages exactly as a visitor would on a dealer website.

Ready to see it

See the implementation result on a real WordPress dealer site

Open the live inventory demo to experience native vehicle pages on a real WordPress site, or jump into the full features overview for the complete capability map behind the implementation.

View Inventory Demo Explore Features