Video Schema Generator

Build video markup locally and validate the resulting structure before publishing; live crawlability/media access still matters.

Video name

Upload date

Description

Thumbnail URL

Content URL

Embed URL

Duration (ISO 8601)

ReadyOutput is generated locally in your browser.

Structured data is not a rich-result guaranteeUse markup only for content that is visible and true on the page. Google eligibility also depends on feature-specific rules, content policies, crawlability, and validation after deployment.

Video Schema Generator: JSON-LD Audit & Rich Result Fields

Build VideoObject JSON-LD and audit name, description, thumbnail, upload date, duration, content/embed URLs and recommended fields.

Audit profile

Require content/embed URL

Use the tool above, then refresh this verification workspace.

VideoObject enrichment

Add publisher, interaction and availability evidence before publishing

This layer starts from the exact VideoObject fields above, reuses the existing schema engine, then adds optional truthful metadata. The generated JSON-LD is written back to the existing output for one-copy workflow.

Publisher namePublisher logo URLView countContent languageRegions allowedExpires Requires subscription

0/4Core fields

0Media URLs

0Optional enrichments

ReviewLocal preflight

Generate after reviewing the fields above. Local structure checks do not guarantee crawler access or a rich result.

Search-engine boundaries

Local markup checks cannot know what a crawler fetched, rendered, indexed or selected as canonical. Search engines may rewrite title links/snippets, choose different canonicals, ignore invalid or ineligible structured data, and apply live HTTP/robots conditions that are not present in pasted text. Treat these tools as pre-publish QA, then verify live behavior with the relevant search-engine tools.

Publication preflight, not an SEO score

Generated or pasted SEO data is checked for concrete structural conflicts, malformed values and handoff risks. The tool does not predict rankings, indexing certainty or rich-result eligibility.

Practical guide and verification

Describe the video that is actually present

VideoObject markup should correspond to a video users can access on the page. The v12.77 enrichment adds publisher, interaction, language, region and availability metadata, but adding fields cannot compensate for a missing, inaccessible or misleadingly described video.

Keep media URLs and the page relationship clear

contentUrl identifies the media file and embedUrl identifies a player location. Use real absolute URLs when those properties are available and verify the published resources are crawlable under the site policy. A locally valid JSON object cannot test the live HTTP response.

Use interaction counts as sourced observations

A view count can be represented as an InteractionCounter with WatchAction, but it should come from a defensible source and update policy. Do not invent a count merely to fill structured data, and remember that interaction statistics are descriptive metadata rather than a ranking guarantee.

Treat publisher and availability metadata as optional enrichment

Publisher identity, language, region availability, subscription status and expiry can make the object more explicit when they are true for the media. Omit unknown fields instead of manufacturing defaults that do not match the page or distribution rights.

Validate the deployed result separately

The generator can check JSON structure, core-field presence and simple URL or duration formatting locally. Search-engine eligibility depends on the live page, supported properties, content policies and crawler access, so use the relevant live structured-data tools after publishing and do not interpret a local readiness score as a promise of a rich result.