What mandatory metadata must you configure to ensure your Web Stories are indexed by Google?

Why does Google require specific metadata for Web Stories?<\/h3>

Web Stories are not standard HTML pages — they are a visual format similar to Instagram Stories, designed for quick mobile consumption. Google cannot simply analyze the textual content like it would for a traditional web page: it needs structured markers to understand the subject, the author, and the editorial quality.<\/p>

Unlike a standard page where the crawler can infer certain information from the DOM, Web Stories require explicitly formatted metadata following a specific schema. Without these tags, Google cannot properly display the story in rich results or guarantee it will be indexed. It's a strict validation logic — no valid metadata, no visibility.<\/p>

What exactly are the mandatory metadata?

Two elements are absolutely required according to the official documentation: a poster image (the cover thumbnail) and an editor logo. The poster image must meet specific technical constraints: a ratio of 3:4 (or 9:16 depending on the display context), a minimum resolution of 640x853 pixels, in JPEG or PNG format.<\/p>

The editor logo must be square, in PNG or SVG, with a resolution between 96x96 and 300x300 pixels. This logo identifies the source of the content and strengthens the editorial dimension — Google wants to know who is publishing, not just display anonymous content. These metadata must be declared via Schema.org type "NewsArticle" or "Article" with properties specific to Web Stories.<\/p>

How does Google validate this metadata?

Validation occurs at two levels. First, at the time of crawling: Googlebot checks for the presence and compliance of the Schema.org tags. If mandatory properties are missing or do not meet the expected format, the story may be indexed as a regular page (without enrichment) or simply ignored.<\/p>

Next, through the Search Console and the specific report for Web Stories. This report highlights metadata errors — affected URLs, missing properties, image format issues. It's the primary diagnostic tool for identifying stories that do not pass validation. Concretely, a story without a valid poster image will never appear in Google's dedicated carousel of Discover or mobile search.<\/p>

• Mandatory poster image: ratio 3:4 or 9:16, minimum 640x853 pixels, JPEG or PNG
• Mandatory editor logo: square, 96x96 to 300x300 pixels, PNG or SVG
• Schema.org validation: type NewsArticle or Article with specific Web Stories properties
• Search Console control: dedicated report for Web Stories highlighting metadata errors
• No automatic fallback: without valid metadata, there will be no enriched display or guaranteed visibility

Is this requirement for strict metadata consistent with current SEO practices?

Yes, but with an unusual level of severity. Google has imposed structured metadata for rich results (recipes, events, products) for years, but generally allows for some tolerance — a missing property diminishes display without blocking indexing. Here, it's all or nothing: no poster or logo, no Web Stories visibility.<\/p>

This rigor reflects the editorial logic that Google wants to impose on the format. Web Stories are designed for a "content stream" environment (Discover, Google app), where visual quality and source credibility are as important as content. By requiring a logo and a cover image, Google effectively filters out whimsical publications and favors structured publishers. [To be verified]: we still lack field data on the actual indexing rate of stories with partial metadata — Google does not publicly document the exact crawler behavior in these edge cases.<\/p>

What are the concrete risks if the metadata is incorrect or missing?

The first risk is pure invisibility. A Web Story without a valid poster will never be displayed in the dedicated carousel of mobile search or Discover — it remains technically indexable like a regular page but loses all the interest of the format (visual visibility, tactile engagement, premium placement).<\/p>

The second risk, less documented but observed in the field, concerns the crawl budget. Poorly configured Web Stories generate repeated errors in Search Console, which may lead Googlebot to reduce the crawl frequency across the entire domain if the volume of errors becomes significant. For a site publishing several dozen stories per week, failing metadata creates a negative quality signal at the site scale. There are no direct algorithmic penalties, but a friction effect on crawling.<\/p>

In what cases can we do without Web Stories?

Let's be honest: Web Stories are only relevant for certain types of content. If your audience is primarily desktop, if you publish long-form or technical content, or if you lack the resources to produce quality visuals, the ROI is low. Google promotes the format, but actual engagement data remains mixed outside of media and e-commerce.<\/p>

Basically, before diving into Web Story production, check three things: (1) your organic mobile traffic accounts for at least 60% of the total, (2) your content lends itself to short visual storytelling (recipes, fashion, DIY, news), (3) you have the resources to produce optimized visuals — if not, focus on the classic optimization of your pages. The mandatory metadata are a clear signal: Google wants editorialized content, not whimsical testing.<\/p>