§

November 15, 2026

Using Structured Data to Clarify Important Page and Media Details

By @searchlantern

❦

When search engines crawl a page, they see text, images, and video, but they do not always know what each element means or how it relates to the rest of the content. A product image, a how-to video, and a breadcrumb trail all need context. Structured data - specifically the vocabulary from Schema.org delivered via JSON-LD - gives machines that context. By adding the right markup, you tell a search engine that this image is a primary image for the article, that this video is a step-by-step tutorial, and that these links form a BreadcrumbList. The result is a richer search result and a clearer understanding of your media assets.

For a site that turns media assets into organic acquisition channels, getting this right matters. Video files, high-resolution images, and carefully written articles only earn their place if search engines can interpret them correctly. This is where search entity markup comes in. It connects each piece of media to the entity it represents - a person, a product, an organization - so that a search engine can treat it as a thing rather than a blob of bytes. Below is a practical, step-by-step approach to applying this markup to your pages and media.

Step 1: Identify the Primary Entity of the Page

Every page should have one main subject. An article about a recipe has the recipe as its primary entity. A product page has the product. A video page has the video. Before you write any markup, decide what that primary entity is. This decision guides every other piece of structured data you add.

Once you know the primary entity, you declare it using a Schema.org type. Common choices are Article, Product, VideoObject, ImageObject, or Organization. For a typical blog post, Article works well. For a product page, use Product. For a gallery of images, use ImageObject. The type you choose becomes the root of your JSON-LD block.

What to watch: Do not try to declare multiple primary entities on one page. A page that tries to be both an Article and a Product confuses search engines. If your page has a product description and a related article, nest the article inside the product as a property, or vice versa. Pick one anchor and build from there.

Step 2: Link Media to the Primary Entity

Images and videos are often left as disconnected markup. An image might have its own ImageObject block, and a video its own VideoObject block, but if neither is linked to the main entity of the page, the search engine does not know they belong together. To fix this, use the image and video properties on the primary entity.

For example, if your primary entity is an Article, you add an image property that points to an ImageObject, and a video property that points to a VideoObject. The ImageObject itself then includes the URL, the caption, and the license if applicable. The VideoObject includes the video URL, the duration, the description, and the thumbnail.

What to watch: Ensure that the media files you reference are accessible to crawlers. A blocked image or video will not be indexed, no matter how correct your markup is. Also, avoid pointing to the same media file from multiple unrelated entities on the same page; that can dilute the relationship.

Step 3: Add Entity Relationships for People, Products, and Organizations

Many pages mention people, products, or brands. A recipe page might mention a chef. A review page might mention the product being reviewed. An about page might mention the company. Structured data can express these relationships explicitly. For a person, use the author property on an Article, and nest a Person object inside it. For a product mentioned in the article, use the mentions property or nest a Product object directly if the article is about that product.

These relationships help search engines understand the context of your media. A video of a recipe becomes more meaningful when the search engine knows it was created by a specific chef. A product image becomes more useful when the search engine knows it shows a specific model.

What to watch: Only add relationships that are true and visible on the page. If a person is not clearly identified in the visible text, adding their name in markup can be seen as misleading. Keep the markup faithful to what a human reader sees.

Step 4: Use BreadcrumbList for Navigation Context

Breadcrumbs help users and search engines understand where a page sits in the site hierarchy. A BreadcrumbList item can be added to every page to show the path from the home page to the current page. This is especially helpful for sites with many nested categories or media galleries.

The markup for a BreadcrumbList is straightforward: a list of ListItem objects, each with a position, name, and URL. The last item in the list is the current page. When search engines see this, they can display the breadcrumb trail in search results, which improves click-through rates.

Using Structured Data to Clarify Important Page and Media Details

What to watch: Keep breadcrumbs consistent across the site. If a page appears in multiple categories, pick the primary path. Do not add every possible breadcrumb variation; that can confuse crawlers. Also, ensure the URLs in the breadcrumb are the canonical versions.

Step 5: Test and Validate Your Markup

Markup is only useful if it is correct. After adding the JSON-LD to your page, run it through Google's Rich Results Test or the Schema.org validator. These tools will flag missing required properties, incorrect types, and syntax errors. Pay special attention to the @context and @type fields; a typo there breaks the entire block.

Testing also shows you how the search engine interprets your entities. If the test output shows a different primary entity than you intended, go back and adjust the relationships. Sometimes a missing property like datePublished on an Article can cause the search engine to ignore the markup entirely.

What to watch: Do not rely on a single test. After making changes, re-test. Also, check the Google Search Console for any structured data errors or warnings. A warning about a missing field might be acceptable, but an error means the markup is not being parsed at all.

Step 6: Maintain Consistency Across Media Types

If you have a library of videos and images, apply the same markup pattern to each asset. Consistency reduces errors and helps search engines learn your site's structure. Create a template for your JSON-LD that covers the common properties: a VideoObject always has name, description, thumbnailUrl, contentUrl, and duration. An ImageObject always has name, contentUrl, and caption. Stick to these templates and only add extra properties when needed.

For a site that focuses on media assets, like animationandwhatnot.com, this consistency is especially important. When every video and image carries the same high-quality markup, search engines start to trust the site as a reliable source of media content. That trust can translate into better visibility in image and video search results.

What to watch: Do not overstuff the markup with unnecessary properties. Adding every possible Schema.org property to a VideoObject does not improve results and can slow down page rendering. Stick to the properties that matter for your content and your audience.

Step 7: Monitor Changes in Schema.org and Search Engine Guidelines

Structured data is not static. Schema.org adds new types and properties every year. Search engines update their guidelines on what they support and how they treat certain markup. A property that was optional last year might become required this year, or vice versa. Stay informed by following the Schema.org blog and the Google Search Central updates.

When a change affects your markup, update your templates and re-test all affected pages. A small change in the duration format for VideoObject, for example, could cause your video markup to stop being parsed. Regular audits - every few months - keep your structured data healthy.

What to watch: Do not chase every new type. If a new type does not fit your content, skip it. Adding irrelevant markup can confuse the entity relationships you have already built.

Structured data, when applied carefully, turns raw media files into connected entities that search engines can understand and display as rich results. The steps above give you a repeatable process: identify the primary entity, link your media, add real relationships, use breadcrumbs, test everything, keep it consistent, and stay current. For a site like animationandwhatnot.com, this approach helps ensure that every image, video, and article works together to create a clear picture for search engines - and for the people who find your content through them.

❧