Can the Video Object Schema on AMP really boost your videos into Top Stories?

Why does Google associate Video Object Schema with AMP?

Google has long been seeking to promote fast and structured content in its premium carousels. AMP ensures speed, while the Video Object schema provides the semantic structure. By combining the two, you provide exactly what the algorithm expects for a spot in Top Stories.

This statement is not trivial: it confirms that video pages are not excluded from Top Stories, contrary to what some practitioners believed. Google does not reserve this placement solely for text articles. If your markup is clean and your images comply, you are playing in the same league as major media outlets.

What are the exact technical requirements for thumbnails?

Google imposes strict constraints on preview images. The thumbnail must be at least 1200 pixels wide, maintain a 16:9 or 4:3 aspect ratio, and be served over HTTPS. This is non-negotiable. An image that is too small or poorly formatted is enough to exclude you from the carousel, even if everything else is perfect.

The format also matters: JPEG, PNG, or WebP work, but avoid exotic formats. Google must be able to extract and display the thumbnail instantly. If crawling fails, or the image takes too long to load, you lose your entry ticket.

Is AMP really mandatory for video Top Stories?

Google's wording raises uncertainty. Officially, AMP is no longer an absolute requirement for Top Stories since 2021. However, this statement suggests that for videos, AMP remains a massive competitive advantage. Real-world tests show that AMP pages still capture 70-80% of carousel placements.

Practically speaking? If you're aiming for Top Stories with video, don't gamble on a standard page. The AMP investment remains worthwhile for this specific use case, even if other formats could theoretically be eligible.

• Video Object Schema + AMP = winning combo for premium carousels
• Thumbnails must be at least 1200px wide in HTTPS
• Accepted formats: JPEG, PNG, WebP with 16:9 or 4:3 aspect ratio
• AMP is no longer mandatory in theory, but remains dominant in practice for video
• One technical detail missed = exclusion from the carousel, even if the rest is perfect

Does this statement really reflect what we observe on the ground?

Yes and no. On pure news sites, the combo AMP + Video Object does indeed work for getting into Top Stories. But the algorithm remains fickle. I've seen technically perfect implementations that never ranked, while pages with minor errors passed without issue. [To check]: Google does not specify the actual weight of domain authority in this process.

The real issue? Google speaks about technical requirements as if they were binary, while eligibility also depends on editorial signals that they never document. Your content can be technically flawless and never appear if Google doesn't consider your site a "reliable news source".

What are the most common implementation pitfalls?

The first pitfall: confusing Video Object with VideoObject (no space). Both exist in schema.org, but Google expects "VideoObject" as one word. A misplaced capital letter and your markup is ignored. Always test with the rich results testing tool, don’t trust your IDE.

The second classic mistake: using the page URL as contentUrl instead of pointing to the actual video file. Google wants the .mp4, not the HTML page hosting it. I've seen dozens of sites spend months debugging this point while the documentation is explicit.

In which cases is this markup useless?

If your site is not recognized as a news source by Google News, you can implement this schema perfectly, and it probably won't bring you anything for Top Stories. This carousel is reserved for media players, plain and simple. Regular businesses, even with quality video content, have almost no chance.

Another case: if your videos are not recent news. Top Stories heavily favors content published in the last hours. An evergreen video, even perfectly tagged in AMP with Video Object, will never get that placement. Focus your efforts on hot content.

How to correctly implement the VideoObject schema on AMP?

Start by ensuring your AMP page is already indexed and error-free in the Search Console. There's no point in adding schema on a broken base. Then, inject the JSON-LD markup into the <head>, strictly following the mandatory properties: name, description, thumbnailUrl, uploadDate, duration, contentUrl.

For the thumbnail, generate a dedicated version at 1280x720 minimum (16:9) or 1600x1200 (4:3). Don't recycle a small image hoping Google will accept it "anyway". Serve it over HTTPS, test the loading time, and ensure it displays correctly on mobile. A poorly rendered carousel on smartphones ruins your chances.

What critical mistakes must be avoided at all costs?

Never declare a video duration in raw seconds: use ISO 8601 format (PT1M30S for 1 minute and 30 seconds). Google rejects plain numeric values. Another fatal error: pointing thumbnailUrl to an image that redirects or requires authentication. The URL must return a direct 200 code with the image in response.

Avoid duplicating the same schema on both AMP and non-AMP versions if both coexist. Google may interpret this as markup spam. Place the schema only on the canonical version you want to rank in Top Stories, typically the AMP version.

How can you verify that everything works from Google's side?

Use Google’s rich results testing tool, but don't stop there. Request a real-time URL inspection in the Search Console to see exactly what Googlebot extracts. If the visual rendering does not show your video, it means there is a problem with blocked resources or JS timeout.

Also, monitor the AMP coverage reports. A "Valid" status does not guarantee Top Stories eligibility: look specifically for errors related to video rich results. Google may validate your AMP page but reject the schema for reasons it does not always specify. In that case, compare with competitors who rank and track the differences.

• Validate the AMP page in the Search Console before adding the schema
• Use JSON-LD in the <head> with all mandatory properties
• Generate a dedicated thumbnail 1280x720 minimum, served over HTTPS
• Format duration in ISO 8601 (PT1M30S), never in raw seconds
• Point contentUrl to the .mp4 video file, not the HTML page
• Test with both the rich results tool AND real-time URL inspection