15 November 2026

How to Use Structured Data for Media-Rich Pages

Presented by @mediadiscovery

What Matters Most for Media-Rich Pages

For pages built around images, video, or audio, the structured data types that matter most are those that describe the media itself and how it relates to the rest of the page. Schema.org provides types like ImageObject, VideoObject, and AudioObject, plus container types like Article that hold them. Using these correctly helps search engines understand what the media is, who created it, when it was published, and what it shows. That understanding can lead to rich results such as video carousels, image previews, or breadcrumbs that make your content stand out in search results.

Why Media Needs Its Own Structured Data

A page with a video embedded in a blog post has two distinct pieces of content: the article and the video. If you only mark up the article, search engines may not see the video as a separate, indexable asset. By adding VideoObject markup, you tell Google and other engines exactly what the video contains, its duration, its thumbnail URL, and more. The same logic applies to images and audio files. Without this markup, the media remains invisible as a search entity.

This is where media structured data becomes a practical tool rather than an abstract concept. When you mark up media correctly, you give search engines the context they need to surface your content in visual search, video results, and AI-driven overviews. For a site focused on turning media assets into acquisition channels, this distinction is critical.

The Foundation: Schema.org Types

Article, ImageObject, VideoObject

The most common pattern for media-rich pages is an Article that contains one or more media objects. Article is the container; it holds the headline, author, publish date, and body text. Inside that, you nest an ImageObject for the featured image and a VideoObject for any embedded video. Each object has its own set of properties. For ImageObject, you might include caption, contentUrl, and license. For VideoObject, you add duration, transcript, and embedUrl.

BreadcrumbList is another type that matters for media-rich pages, especially if you have a hierarchy of categories or playlists. BreadcrumbList tells search engines the page's place in your site structure, which can help users navigate to related media. In a video library, for example, a breadcrumb might show Home > Tutorials > Video Editing > Clip 5.

Entity Relationships

Schema.org lets you express relationships between entities. A VideoObject can have a subjectOf relationship to an Article, or a composer relationship to a Person. These connections help search engines build a richer graph of your content. For a page that reviews a film, for instance, you could link the VideoObject to the Movie type and the Movie to the Director. Each link adds context that may improve how your media appears in knowledge panels and rich results.

How to Implement Without Overcomplicating

JSON-LD is the preferred format for most implementations. You embed a script block in the page head or body, and within it you describe all the entities on that page. The key is to keep the markup clean and avoid duplication. If a video appears on multiple pages, each page should describe that video with its own VideoObject block, but you can reference a common identifier like a URL or a property value to show they are the same asset.

A common mistake is marking up the media as a generic Thing or using only the Article type. That leaves media properties unused. Another mistake is mismatching URLs: the contentUrl in your VideoObject must point to the actual video file, not the embed page. If you use a video hosting service, check whether it provides a direct file URL or an embed URL. Use the file URL for contentUrl and the embed URL for embedUrl.

For images, the ImageObject type works well for hero images, product photos, and infographics. If you have a gallery of images, you can use a CollectionPage or ImageGallery type. Each image gets its own ImageObject with its own caption and URL. That way, search engines can index each image separately, which can help them appear in image search results.

Practical Considerations

When you start marking up media, test your markup with the Rich Results Test tool. It will show you which properties are recognized and which are missing. Pay attention to required properties: for VideoObject, you need name, description, thumbnailUrl, and uploadDate. Without these, the markup may be ignored.

How to Use Structured Data for Media-Rich Pages

Media structured data also matters for accessibility, though that is a secondary benefit. When you provide a caption for an image or a transcript for a video, you help users who rely on screen readers. But the primary goal is search visibility. A well-marked-up video can appear in a video carousel, which drives more clicks than a plain text snippet.

One trade-off is the maintenance overhead. Every time you add a new video or image, you need to update the JSON-LD block. For large sites, this often requires a content management system that generates the markup automatically. If you are doing it manually, focus on the pages that get the most traffic or the media that has the highest conversion potential.

What to Watch Out For

Do not confuse structured data with metadata. Metadata lives in the head of the page and is meant for browsers and social platforms. Structured data lives in JSON-LD or inline and is meant for search engines. Both can coexist, but they serve different purposes. For media, the structured data should describe the media itself, not just the page it sits on.

Another pitfall is marking up media that is not actually present on the page. If you have a video on page A but mark it up on page B, search engines may treat that as spam. Always put the markup on the same page where the media appears.

The entity relationship aspect can get complex quickly. For a simple blog post with one video, you only need Article and VideoObject. For a product page with multiple images and a demo video, you might need Product, ImageObject, and VideoObject. Keep the graph simple until you have a clear reason to add more types. Overcomplicating the markup can lead to errors that cause the entire block to be ignored.

Final Piece of Advice

Think of media structured data as a way to give search engines a catalog of your media assets. Each asset gets its own entry with its own properties. The page is just the container. When you treat media this way, you make it possible for search engines to surface your videos in video search, your images in image search, and your articles in news or blog search. That separation is what turns a single page into multiple entry points for users.

The second use of media structured data should be in a middle paragraph, and here it is: If you manage a site with a large media library, media structured data helps you keep track of what you have and how it performs. That data can inform decisions about which videos to promote, which images to update, and which pages need new media to stay competitive.

In the end, the types that matter are the ones that match your content. If you have a podcast, AudioObject is essential. If you have a tutorial site, VideoObject and ImageObject are your main tools. Article and BreadcrumbList are supporting players that give context. By focusing on these types and their relationships, you can make your media-rich pages work harder for search visibility without adding unnecessary complexity.