Most dealer sites that invest in vehicle walkaround videos stop at embedding a YouTube player on the VDP and calling it done. That gets you the engagement benefit, but it leaves the actual search-visibility opportunity on the table — showing up in Google’s dedicated video results — because that depends on structured data the embed alone doesn’t provide.
Why embedding alone isn’t enough
Hosting your walkaround videos on YouTube and embedding them is still the right baseline move — it avoids hosting large video files yourself, which keeps page weight down, and YouTube handles encoding and adaptive streaming for you. But Google’s video search results (the dedicated “video” tab, and video rich results in standard search) are driven by structured data, not by the presence of an embedded player. Without VideoObject schema on the page, Google has to infer what the video is about from surrounding page text — unreliable at best on a VDP where the text is mostly spec tables.
What VideoObject schema actually requires
The required and recommended properties for a VideoObject that Google can use for rich results include:
- name — a clear, descriptive title, not just the vehicle’s VIN or stock number.
- description — what the video actually shows, written for humans and crawlers alike.
- thumbnailUrl — a high-resolution still frame, since this is what displays in search results before a user clicks.
- uploadDate — in ISO 8601 format.
- duration — also ISO 8601 (e.g., PT3M42S for three minutes forty-two seconds).
- contentUrl or embedUrl — pointing to the actual playable video, which for a YouTube embed is the embed URL.
Without these properties present, Google’s own documentation is direct about the consequence: no video rich result gets generated, regardless of how well the embed itself performs for human visitors.
Captions and transcripts matter for indexing too
Several current guides recommend adding captions and transcripts to walkaround videos specifically for indexing benefit, not just accessibility. A transcript gives Google crawlable text describing exactly what’s shown and said in the video — trim levels mentioned, features called out, condition notes — content that would otherwise exist only inside video frames crawlers can’t read.
Implementing it on a WordPress dealer site
If your VDP template is built with a page builder or custom theme template rather than relying entirely on a vehicle-feed plugin’s default markup, you have two practical paths:
- Many SEO plugins (Rank Math and others) support custom schema types including VideoObject through their schema generator — check whether your plugin’s schema builder already covers this before writing manual markup.
- Where the SEO plugin’s generator doesn’t reach VDP template fields, a JSON-LD block added directly to the VDP template, populated from the same fields driving your vehicle feed (year, make, model, stock number) plus the video’s own metadata, is a reliable fallback.
What not to expect
Be skeptical of specific ranking-impact statistics circulating in dealer marketing content — one frequently repeated claim that video pages are “53x more likely to rank on page 1” traces back to a Forrester reference that multiple current sources couldn’t independently verify. The honest case for VideoObject schema isn’t a guaranteed ranking multiplier — it’s the difference between being eligible for Google’s video-specific search surfaces and not being eligible at all. For a VDP, that’s still worth the structured data work.
What to Actually Film
- Exterior walkaround — condition, any notable wear, angles a stock photo never shows
- Start-up and sound — buyers want to hear the engine, not just see a photo of it
- Infotainment and key features — a 10-second demo of the screen or a standout feature
- One real-world moment — cargo space, back-seat legroom, whatever this specific vehicle’s buyer actually cares about
Where the Video Goes on the Page
| Element | Why it matters |
|---|---|
| Video near the top of the VDP | Captures attention before a shopper decides to bounce |
| Vertical / mobile-first format | Matches how most shoppers are actually viewing the page |
| Click-to-call and click-to-text near the video | Converts a shopper who just got convinced, while they’re still convinced |
| Video hosted efficiently (not a giant unoptimized file) | A slow-loading video costs more in page speed than it gains in engagement |
Don’t Let Video Undo Your Page Speed
The engagement gains are real, but only if the video doesn’t tank your load time — a heavy, unoptimized video file working against Core Web Vitals can cost you more in bounce rate than the video gains in engagement. Host it through a proper video platform or compressed format rather than embedding a raw, oversized file. If you haven’t reviewed your VDP against the broader engagement checklist, see Vehicle Detail Page Best Practices for Car Dealers. If you want your VDP template reviewed for where video and click-to-call should sit, get in touch.