Audit VideoObject markup
Inspect raw HTML for VideoObject properties and the core metadata supplied for an embedded or hosted video.
Video SEO Checker
Free, no signup. Check raw-HTML VideoObject, thumbnails, key moments, embed loading, and a limited main-content signal without pretending to render or play the video.
Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Sample report Deterministic detector example
Raw HTML containing one VideoObject, an HTTPS thumbnailUrl, SeekToAction, and a lazy-loaded YouTube iframe returns:
VideoObject markup: 1 VideoObject block found.
Video thumbnail: A video thumbnail URL appears in raw HTML.
Key moments: Clip or SeekToAction key-moment markup found.
Embed hygiene: Video iframe uses lazy loading or a facade.
Video as main content: depends on the raw visible-word threshold.
How to use it
- Enter the public watch or article page that embeds the video.
- Select Audit and review all five rows.
- Verify missing signals in rendered HTML when the player or schema is injected by JavaScript.
- Validate the complete VideoObject and test playback, thumbnails, and moments independently.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
What the results mean
- VideoObject markup — counts matching JSON-LD type strings.
- Video thumbnail — finds an HTTP(S) thumbnailUrl pattern.
- Key moments — finds Clip or SeekToAction strings.
- Embed hygiene — checks YouTube/Vimeo iframes for lazy loading or facade classes.
- Video as main content — a raw-HTML word-count heuristic, not a rendered verdict.
How it works
The protected endpoint returns public raw HTML. Deterministic detectors inspect serialized markup and iframe attributes, count matching VideoObject strings, and use a 250-word body-text threshold for the limited main-content clue. Findings have a warning ceiling; unavailable document evidence remains not evaluated.
Features
- Five independent video findings.
- Multiple VideoObject block count.
- Clip and SeekToAction recognition.
- Lazy-load/facade signal for common hosted-video embeds.
Limitations
The audit does not render JavaScript, play media, validate schema properties, fetch the thumbnail/content URL, confirm indexability, or test key-moment timestamps. It recognizes YouTube/Vimeo iframe URLs but not every player. Word count cannot establish visual prominence. Transcript quality, captions, watch-page eligibility, live streams, video sitemaps, and search appearance are outside scope.
Frequently asked questions
What video SEO signals does this tool inspect?
It checks for VideoObjectVideoObject schema (schema.org/VideoObject) marks up video content for Google's video rich results — thumbnail, duration, and key moments — surfacing on main search, the Video tab, Google Images, and Google Discover. It also covers the related Clip (key moments) and BroadcastEvent (LIVE badge) types on the same guide. JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., a thumbnail URL, Clip or SeekToAction markup, YouTube/Vimeo iframe loading signals, and a limited raw-HTML clue that video may be the main content.
Does it play or render the video?
No. It parses fetched raw HTML and does not execute JavaScriptTurning HTML, CSS, and JavaScript into the final visual page and DOM., load the player, verify playback, or inspect frames.
What does video as main content mean here?
It is a narrow heuristic: a page with a detected video and fewer than 250 visible raw-HTML words may pass. This does not reproduce Google rendering or classification.
Are key moments required?
No. Their absence is informational. Clip and SeekToAction markup can help describe moments when implemented accurately, but not every video needs them.
Feature requests for Video Seo Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Verify thumbnail signals
Check whether the declared thumbnail URL and related image fields are present and usable in the fetched source.
Review key-moment markup
Inspect supported clip or seek-action signals without claiming downstream search eligibility.
Preflight a video-page template
Test a representative page before rolling an embed or structured-data change across the library.
Watch the full workflow
Video SEO Checker walkthrough
Read the transcript
Video SEO Checker
Video search visibility depends on more than an embedded player. This checker inspects five bounded raw-H-T-M-L signals: VideoObject markup, a thumbnail, key moments, embed loading, and a limited main-content clue. I’ll show the workflow, a clearly fictional report, how to interpret each row, what the audit cannot see, and the validation steps to take next.
Step 1
Use this checker on a public watch page or article containing a video. It is especially useful before launch, after template changes, or when expected video search features do not appear.
Step 2
Enter the complete public page U-R-L, not the YouTube or Vimeo watch U-R-L unless that is the page you own and want to inspect. The protected endpoint fetches one public document.
Step 3
This walkthrough enters a fictional example dot com page and does not make a live audit request. In normal use, select Audit and review all five findings instead of treating one passing row as an overall verdict.
Step 4
This illustrative report shows the expected result shape. Each row represents separate evidence, so one missing signal does not erase another observed positive and one pass does not prove broad video eligibility.
Step 5
VideoObject markup reports matching type strings found in serialized H-T-M-L. It does not validate required or recommended properties, compare multiple objects, or prove the schema describes the visible video.
Step 6
The thumbnail row detects an H-T-T-P or H-T-T-P-S thumbnail U-R-L pattern. It does not fetch the image, inspect its dimensions, confirm stable access, or prove the selected frame is representative.
Step 7
Key moments reports Clip or SeekToAction strings. Their absence is informational, and their presence does not validate timestamps, labels, deep links, or whether the moments match actual playback.
Step 8
For recognized YouTube or Vimeo iframes, the tool looks for lazy loading or a facade signal. It cannot cover every player, measure performance, execute consent flows, or confirm that playback initializes.
Step 9
The main-content clue combines detected video markup with fewer than two hundred fifty visible raw-H-T-M-L words. That threshold cannot establish rendered size, placement, prominence, or Google classification.
Step 10
If acquisition is truncated, observed positives may remain useful, but absence and complete-page clean claims become not evaluated. Inspect the page directly instead of interpreting missing captured evidence as a failure.
Step 11
The audit does not render JavaScript, play media, inspect frames, validate complete schema, test transcript or captions, fetch media assets, confirm indexability, or observe search appearance. JavaScript-injected evidence may require rendered inspection.
Step 12
After fixing supported warnings, inspect rendered H-T-M-L, validate the full VideoObject, test the thumbnail and player, confirm key-moment links, review crawl and canonical signals, and monitor real indexing and search appearance over time.
Use the report as a focused inspection—not an eligibility verdict.
Start with the public watch or article U-R-L, resolve each supported finding, and then validate the rendered page and complete VideoObject with dedicated testing. Confirm playback, thumbnail access, key-moment accuracy, crawlability, canonicals, and indexability independently. Search appearance remains an observed outcome, not something this raw-H-T-M-L audit can guarantee.
Common issues & how to fix them
- Warning VideoObject markup is missing Fix: Add VideoObject JSON-LD for the primary video with matching name, description, thumbnailUrl, uploadDate, and contentUrl or embedUrl.
- Warning Video thumbnail URL is missing Fix: Provide a stable, crawlable thumbnailUrl in VideoObject markup that matches the visible video thumbnail.
- Information Key-moment markup is missing Fix: Add Clip markup or SeekToAction only when the player supports stable timestamps and the segments accurately match the video.
- Information Video iframe lacks lazy loading or a facade Fix: Lazy-load the offscreen iframe or replace it with a click-to-load facade so the player does not block the initial page load.
- Information Video cannot be established as main content Fix: Place the video prominently as the page’s main content with supporting text and complete VideoObject markup.