Free · without registration
Checking video sites for technical SEO hurdles
Examine a video page for recognizable embeds, VideoObject information, and accessible resources. The checker separates HTML findings from questions that can only be answered in the browser or Search Console.
Check video page or stored HTML
Result and next steps
An accessible page is not yet an indexed video
A video can be embedded on a working page and still remain hard for Google to find. Therefore, check both the page and player, thumbnail and video markup. The checker recognizes video elements, assignable player iframes and VideoObject in JSON-LD and Microdata. Any card or form iframe is not automatically counted as a video.
What the findings mean
The evaluation shows, among others, name, thumbnailUrl and uploadDate. A missing image address requires a different correction than an HTTP-404 of the existing preview image. When resource checking is activated, up to eight targets are retrieved in a limited manner. A successful response confirms their HTTP accessibility, not playback or sharing for each search engine bot.
Example: Video after a CMS move
The player works, but thumbnailUrl still points to an old media path. Update the image address in the markup and then check the new resource. If a player only appears after consent or JavaScript execution, it must also be checked in the browser which content is available without interaction.
What you should additionally check manually
Is the video the main content of its own playback page? Is it immediately visible and playable? Do the title, thumbnail and description match the video? These questions cannot be answered conclusively by a static HTML check. The basis for classification are Googles Video SEO recommendations. For the XML file, the video sitemap generator is available separately.
Frequent questions
Does an error-free result guarantee video indexing?
No. Embedding, content, Google’s retrieval and other requirements play together. The tool checks selected technical signals.
Are YouTube and Vimeo Embeddings Recognized?
Known player iframes and embeddeds referenced in the VideoObject are taken into account. Players created purely by JavaScript may not be visible in the original HTML.
Are video files downloaded?
The resource verification first uses HEAD. Only with unsupported HEAD is a GET with a small read limit; full videos are not downloaded.
Does the tool check robots.txt?
In URL mode, the robots.txt of the page origin is taken into account. Resources on other hosts and additional bot locks must be checked separately.