Does optimizing Web Stories really require specific SEO practices or just the basics?

Why does Google emphasize 'standard SEO' for Web Stories?

Pascal Birchler's statement cuts through a debate that has lingered since the launch of Web Stories: Should exotic rules be applied or should we simply transpose what already works? Google puts an end to the speculation. Meta descriptions remain relevant, and schema.org markup functions just like anywhere else.

What changes is the AMP layer. The poster image and publisher logo are not mere cosmetic 'bonuses' — they determine the validity of AMP itself. Without AMP validity, there's no indexing as a Story. It’s binary.

What does 'standard SEO practices' really mean in this context?

We are talking about title, meta description, and Open Graph markup if you’re aiming for social sharing. Canonical tags have not disappeared. The XML sitemap specific to Web Stories remains recommended — Google doesn’t state it here, but it’s implied in 'standard practices'.

On the schema.org side, you need to include standard metadata: headline, datePublished, author, publisher. Nothing new under the sun, except that the absence of just one field can tip your Story out of the carousel. AMP validation errors become blocking, not just 'non-optimal'.

What are the absolutely mandatory specific AMP elements?

Two elements stand out: the poster image (which serves as a thumbnail in carousels) and the publisher logo (which identifies the source). Without these two visuals, your Story is rejected by the AMP validator. This is explicit in the AMP Story spec.

The poster image must meet a specific ratio (3:4 or 4:3 depending on the case), weigh less than 8 MB, and display a minimum resolution of 640x853 pixels. The publisher logo, on the other hand, requires a square (1:1), typically 96x96 minimum. Too many sites overlook these constraints and end up with invisible Stories in Discover.

• Meta description: remains relevant, limit of 160 characters like elsewhere
• Schema.org: headline, datePublished, author, publisher obligatory
• AMP poster image: ratio 3:4, resolution 640x853 minimum, less than 8 MB
• Publisher logo AMP: ratio 1:1, 96x96 pixels minimum, identifies the source
• AMP validity: test via the official AMP tool, any critical error blocks indexing

Is this statement consistent with on-the-ground observations?

Yes, but it overlooks a crucial point: Google does not say that all classic SEO practices can be seamlessly transposed. For instance, internal linking within a Web Story is nearly non-existent — you don’t have a sidebar, menu, or footer with contextual links. The outgoing link at the end of the Story is often the only PageRank vector.

Another blind spot: perceived performance. Web Stories load via AMP, so Core Web Vitals are theoretically optimized by default. However, if your image server is slow or you use overly heavy videos, the user experience degrades, and Google may deprioritize your Stories in Discover. This isn’t stated here — [To be verified] through your own speed tests.

What nuances should be added regarding schema.org markup?

Google does not specify which schema.org variant to prioritize. Most publishers use NewsArticle or Article, but some sectors (e-commerce, recipes) should rather choose Product or Recipe. The devil is in the details: a missing field like image or publisher.logo can cost you eligibility for rich snippets.

Moreover, the publisher.logo in schema.org is not strictly the same as the AMP publisher logo. The former is a URL in the JSON-LD, while the latter is a tag <amp-story-page-attachment> or <amp-img> depending on the implementation. Confusing the two leads to subtle validation errors — I’ve seen sites valid on the schema.org side but rejected on the AMP side.

In what cases does this 'standard SEO' approach fall short?

If you’re aiming for the Google Discover carousel, standard SEO does not guarantee anything. Discover prioritizes engagement signals (CTR, time spent, interactions), not just technical compliance. You can have a technically perfect Story and remain invisible if your audience doesn’t click.

Another edge case: Web Stories on young domains. Google gives less weight to Stories from sites without an authority history. Even with impeccable markup, you will struggle to break through in Discover against established publishers. This is not mentioned in the statement, but it is observable in the SERPs.

What concrete steps should be taken to optimize a Web Story?

First, validate your Story with the official AMP tool. Paste your URL, fix all critical errors (in red). Warnings (in yellow) can be tolerated, but blocking errors exclude you from indexing. No negotiation possible.

Next, ensure your poster image complies with the specs: ratio 3:4, resolution 640x853 minimum, less than 8 MB, JPG or PNG format. Test the display in the mobile carousel — a blurry or poorly cropped image kills your CTR even before the user reads the title.

What mistakes should be avoided when implementing the markup?

The most frequent mistake: confusing the AMP publisher logo and the publisher.logo schema.org. The former must be declared in the <amp-story> tag with the publisher-logo-src attribute. The latter resides in the JSON-LD, often placed in the <head>. Both must point to valid URLs, but they are not the same technical fields.

A second trap: forgetting the meta description. Google states it’s 'standard SEO', so some publishers skip it thinking the title is enough. Mistake. The description appears in classic SERPs if your Story ranks outside Discover. Without it, Google generates a random snippet — often poor.

How to check if my site meets Google’s requirements?

Use Google Search Console: section 'Enhancements', sub-section 'Web Stories'. You will see blocking errors (invalid Stories) and warnings (recommended optimizations). Prioritize critical errors — only they exclude you from the index.

Follow up with a test in the Rich Results Test tool. Paste your URL, check that schema.org markup is detected. If Google doesn’t see your headline or publisher, it means your JSON-LD is incorrectly placed or syntactically incorrect.

• Validate each Story with the official AMP tool, fix all critical errors
• Check that the poster image complies with a ratio of 3:4, resolution of 640x853 min, weight < 8 MB
• Ensure the publisher logo is declared in the publisher-logo-src attribute of <amp-story>
• Implement complete schema.org markup: headline, datePublished, author, publisher, image
• Write a unique meta description for each Story (160 characters max)
• Monitor Google Search Console, Web Stories section, to detect indexing errors