According to the supplied Google developer documentation, Web Stories must be valid AMP pages and include the required metadata to be eligible to appear in Search and Discover. They must also be discoverable and indexable by Google and comply with applicable content policies. This article refers to Web Stories published on websites that readers navigate by tapping or swiping, not story posts on platforms in general. If you use a story editor, you still need to confirm that its output meets this format’s requirements.
Check the story format first, then indexing
Web Stories are still web pages, so general web page guidelines and search engine optimization practices also apply. After creating a story, use an AMP validation tool to check for and fix errors. Do not skip format validation simply because the story plays correctly.
- Link to the story from other pages on your website, or add its URL to a sitemap to help Google discover the content.
- Each story should specify its own URL as its canonical URL.
- Make sure robots.txt does not block Googlebot from accessing the story and that noindex does not prevent indexing.
- Use Search Console’s URL Inspection tool and relevant indexing reports to confirm whether the story has been indexed.
For example, if a story has been added to a sitemap but still has a noindex directive, submitting its URL alone does not mean its indexing setup is complete. If the same story is available in multiple languages, you should also make the localized versions available to Google.
Check preview metadata and image requirements
To display previews correctly, the documentation requires four fields: publisher-logo-src, poster-portrait-src, title, and publisher. Check that this information is complete before publishing.
- The poster image must be at least 640×853 pixels, with a display aspect ratio of 3:4.
- The publisher logo must be at least 96×96 pixels, with a display aspect ratio of 1:1.
- The title must not exceed 90 half-width characters. A descriptive title of fewer than 70 half-width characters is recommended.
Avoid embedding text in the poster image, as it may interfere with the title in the search preview. The documentation also recommends checking that the story preview displays correctly, rather than merely confirming that the fields are present.
Content completeness is also part of eligibility
According to the supplied policy text, stories must comply with Discover policies, Search Essentials, and general Search policies to appear as individual results in Search and Discover. To appear in richer formats in Search, they must also comply with Search feature policies and Web Stories content policies.
Stories should have a consistent theme and a complete narrative. They must not require readers to leave the story and visit another website or app to access important information. Media should not be excessively stretched or visibly pixelated.
There is also a limit on text: under the supplied policy, stories cannot be displayed as Web Stories if most of their pages contain more than 180 half-width characters of text. The documentation recommends using short videos of less than 60 seconds per page instead, wherever possible. This is a recommendation about presentation, not a requirement to include video on every page.
Web Stories visibility in Search and Discover: perspectives from across the web
Can Web Stories appear in desktop search results?
Yes, but they should support landscape displays. Google's creation documentation lists this as a practice for displaying Web Stories in desktop search results. When creating a story, you should therefore check not only its appearance on a phone in portrait orientation, but also how it looks on a landscape screen.
How does the display of Web Stories differ between Search and Discover?
According to the supplied Google documentation, Web Stories can appear as individual search results in Search and as individual cards in the Discover feed. The Search feature is available in regions and languages supported by Google Search; Discover cards are available in regions and languages where Discover is available. The documentation notes that these cards appear most often in the United States, India, and Brazil.
What are the consequences of serious content policy violations?
If a website seriously violates Web Stories content policies, it may permanently lose eligibility for richer presentations in Google Search, such as the carousel. This consequence concerns richer presentations in Search; it does not, by itself, mean that the website will necessarily be excluded from all search results or from Discover.
References
- 讓網路故事顯示在 Google 上 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How does the display of Web Stories differ between Search and Discover?
- Google 的網路故事內容政策 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: What are the consequences of serious content policy violations?
- 創作網路故事的最佳做法 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Can Web Stories appear in desktop search results?



