Video Schema Generator — Free Online Tool

Video schema is structured data that describes a video asset using Schema.org type VideoObject, almost always published as JSON-LD in your HTML. It tells search systems the canonical title, a human-readable description, when the video was published, how long it runs, where the poster image lives, and—critically—where users can watch the file or embedded player. That machine-readable layer complements the visible player, transcript, and surrounding article copy; it does not replace honest editorial context, but it helps Google and other engines interpret your video page as a first-class video experience rather than a mystery iframe. When implemented accurately, VideoObject markup supports video rich results: enhanced listings that can surface thumbnails, duration, upload metadata, and in some contexts key moments derived from clip markup. YouTubers, video marketers, media publishers, and course creators all benefit when their landing pages clearly declare what a video is, who published it, and how long it lasts. Google may show video previews in standard search, in video mode, and in surfaces such as Discover when videos are eligible and the page meets quality expectations. Structured data is not a ranking guarantee, and rich results depend on policies, site quality, and query intent—but omitting Video JSON-LD on pages that prominently feature unique video is a missed opportunity for clarity. This SynthQuery Video Schema Generator runs entirely in your browser. You fill required fields (name, description, thumbnailUrl, uploadDate), recommended fields (duration via an ISO 8601 duration picker, contentUrl, embedUrl, view counts, expiry), and optional publisher, author, language, family-friendly flag, keywords, and transcript text. Add Clip rows for key moments, toggle live BroadcastEvent publication metadata, and optionally emit SeekToAction for deep links. Paste a YouTube URL to auto-fill from YouTube oEmbed (with a noembed.com fallback): title, a starter description, max-resolution thumbnail URL pattern, embed URL, and watch URL—then complete uploadDate and duration from YouTube Studio or your CMS because public oEmbed does not expose them. Validate against Google-oriented checks, copy or download JSON-LD, and test in Rich Results. Explore more utilities on the /free-tools hub or the full catalog at https://synthquery.com/tools.

The form maps directly to VideoObject and closely related patterns Google documents for video search features. The emitted graph always includes @context https://schema.org and @type VideoObject. Required properties for typical video rich result eligibility—name, description, thumbnailUrl, and uploadDate—have dedicated inputs with validation that flags empty values and malformed URLs. thumbnailUrl must be absolute http(s); prefer stable CDN URLs that match the poster users actually see beside your player. The duration picker converts hours, minutes, and seconds into ISO 8601 duration strings such as PT1H2M30S, which is the shape Google expects rather than a raw second count. contentUrl is appropriate when you host a direct media file users or crawlers can address; embedUrl is appropriate for iframe players including YouTube embed addresses. Supplying at least one of the two is strongly recommended—validation warns when both are blank. interactionStatistic maps to InteractionCounter with interactionType WatchAction and userInteractionCount for public view counts you are willing to disclose. Optional publisher nests Organization with name and logo ImageObject URL when both make sense for your brand. author emits Person with name for presenters or creators. inLanguage accepts a simple language tag (for example en). isFamilyFriendly can be explicitly true or false or left unset so the property is omitted. keywords accepts comma- or newline-separated tokens and serializes to a string or array depending on count. transcript carries plain text when you publish a full or partial transcript on the page. Clip sections build hasPart arrays of Clip entities, each with name, startOffset, endOffset in ISO 8601 duration form, and optional url deep links—ideal for chapter-style key moments. Live streaming uses publication typed as BroadcastEvent with isLiveBroadcast true plus optional startDate and endDate from datetime pickers. SeekToAction emits potentialAction with a target URL template containing the literal {seek_to_second_number} token when you want jump links aligned with Google’s key moments documentation. Templates for a hosted lesson and a live webinar plus clips help teams see realistic shapes before replacing example.com URLs.

VideoObject sits in the Schema.org hierarchy as a CreativeWork describing audiovisual content. Google consumes it to understand eligible videos for rich results, video mode, and related surfaces when pages meet quality thresholds. The minimum viable graph emphasizes honest alignment between JSON-LD and visible player metadata; mismatched titles, thumbnails, or durations erode trust and can trigger manual review patterns. Clip markup models key moments using hasPart and nested Clip entities with ISO 8601 startOffset and endOffset durations measured from the beginning of the parent video. SeekToAction adds potentialAction with a templated target URL so search experiences can deep link into seconds inside the player when supported. These patterns relate to how Google surfaces segmented previews but do not guarantee display for every query. YouTube hosts billions of videos, yet your site still benefits from VideoObject when you add unique editorial framing, transcripts, or structured chapters—Google’s documentation discusses both third-party platforms and self-hosted files. contentUrl should point at the actual media file when you control delivery; embedUrl should point at a player endpoint when you rely on iframes. Many legitimate implementations include both when policies allow. Indexing ultimately depends on crawlability, page quality, and consistent URLs. Refresh structured data after CDN changes, player migrations, or rebrands, and revalidate whenever you adjust clip timestamps to match edited masters.

YouTube video landing pages on your own domain: many creators syndicate embeds on articles or hub pages. VideoObject JSON-LD on those URLs clarifies the relationship between your written context and the YouTube player, especially when you add unique descriptions, transcripts, or clip metadata that do not exist on youtube.com alone. Pair with Meta Checker and Open Graph tuning so social snippets align with structured data. Course and cohort landing pages: module videos behind marketing pages benefit from duration, transcript, and publisher Organization markup tied to your training brand. Clip rows map cleanly to lesson agendas, exercises, and recap segments—helpful when students scan search results for specific chapters. Combine with FAQ schema on the same URL when you answer pricing, certification, or pacing questions. Podcast episode pages that publish video editions: describe the episode with VideoObject, link embedUrl to YouTube or Spotify embeds, and mark inLanguage for international audiences. When episodes are time-sensitive, expires can communicate takedown windows for licensed clips. News and media video articles: attach VideoObject to the article’s video hub with accurate uploadDate and high-resolution thumbnails that match visible posters. interactionStatistic may reflect public view counters already displayed in the hero module. Coordinate with Person schema for correspondents and Organization schema for the outlet. Product marketing and demo reels: highlight feature walkthroughs with Clip entities for each capability, contentUrl when you self-host MP4s for crisp loading, and publisher logo for brand recognition in rich previews. Product schema belongs on SKU pages; VideoObject belongs on the narrative demo URL—use both where the user journey splits across page types.

1) Start from a template or blank form. Templates illustrate a self-hosted lesson with contentUrl and a webinar with clips, BroadcastEvent, and SeekToAction—swap every placeholder URL, title, and statistic with authentic values tied to visible page content. 2) Optionally paste a YouTube watch, embed, Shorts, or youtu.be link and click Fetch from YouTube. The tool calls YouTube oEmbed first, then falls back to noembed.com if needed. Review the auto-filled title, description stub, thumbnail, embedUrl, and contentUrl. Immediately set uploadDate (and duration if it was not inferred from a timestamp pattern in the title) using YouTube Studio or your CMS, because public oEmbed feeds do not include first-publish timestamps or runtime. 3) Complete Required: write a concise name matching the on-page headline, a description that reflects the spoken or displayed summary, an absolute thumbnailUrl that matches your poster frame, and uploadDate in ISO form (the date input outputs YYYY-MM-DD; extend to full date-time in JSON if your workflow requires it). 4) Fill Recommended: use the duration picker for ISO 8601 output, add contentUrl for direct files and/or embedUrl for players, enter a public view count only if accurate and already shown elsewhere, and set expires if the video is time-limited (licensing, promos, or event replays). 5) Add Optional brand and creator context: publisher name plus logo URL together, author presenter name, inLanguage, family-friendly flag, comma-separated keywords, and transcript text that mirrors what users can read on the page. 6) Build key moments: click Add clip for each chapter. Give each clip a short name, set start and end offsets with the same hour/minute/second pickers used for main duration, and paste an optional deep link URL. Remove unused clips so you do not ship empty shells. 7) For live or simulcast replays, enable isLiveBroadcast and provide startDate and endDate when known. For SeekToAction, supply a target template that includes {seek_to_second_number} exactly as Google’s examples illustrate. 8) Watch the live JSON-LD preview update as you type. Click Validate, resolve errors, skim warnings, then Copy JSON-LD or Download. Embed a single script tag with type application/ld+json on the canonical video landing URL; avoid conflicting duplicate VideoObject blocks. 9) Open Test in Rich Results, paste your JSON in the Code tab, and monitor Search Console after launch. Refresh markup when titles, thumbnails, or URLs change.

Structured data must reflect what users see on the live page. Do not fabricate durations, view counts, upload dates, or transcripts to chase rich results—misrepresentation violates spam policies and can erode trust with both users and platforms. Only include interactionStatistic when the number is accurate and already public elsewhere. Thumbnails must be representative frames, not clickbait stills unrelated to the video. Embed Video JSON-LD on the canonical URL where the primary player lives; avoid duplicating conflicting VideoObject graphs across parameter-heavy duplicates. Coordinate with your CMS so plugins do not emit a second incompatible block. Continue investing in page speed, accessible players, captions, and internal linking—schema supports discovery but does not replace production quality. Pair this utility with the How-To Schema Generator for procedural articles, Product schema for SKU pages, FAQ schema for supporting Q&A, Meta Checker and OG Tag Generator for snippet alignment, and the full directory at https://synthquery.com/tools when you need AI detection, readability, or plagiarism workflows beyond markup.