{"id":25544,"date":"2026-09-05T02:45:27","date_gmt":"2026-09-04T23:45:27","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/best-practices-for-creating-web-stories\/"},"modified":"2026-09-06T00:52:08","modified_gmt":"2026-09-05T21:52:08","slug":"best-practices-for-creating-web-stories","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/best-practices-for-creating-web-stories\/","title":{"rendered":"Best practices for creating Web Stories"},"content":{"rendered":"

\n To keep your readers engaged, follow our best practices for creating
\n Web Stories<\/a>. We recommend
\n focusing on the critical tasks first. If you have more time, follow the recommended best
\n practices too.\n <\/p>\n

\n Storytelling
\n <\/h2>\n\n\n
Critical storytelling best practices<\/b><\/th>\n
\n Video first\n <\/td>\n\n Video is more engaging than text or images. Use as much video as possible, and supplement with
\n images and text.\n <\/td>\n<\/tr>\n<\/table>\n

More storytelling best practices<\/h3>\n\n\n\n
Recommended storytelling best practices<\/b><\/th>\n
\n Bring your perspective\n <\/td>\n\n Go beyond the facts. Share your opinions. Be the protagonist of your own story. Make it relatable.\n <\/td>\n<\/tr>\n
\n Have a narrative arc\n <\/td>\n\n Create suspense in your story from one page to another. Bring the user along in the journey
\n by providing context and narrative. Deliver payoff for sticking with you to the end.\n <\/td>\n<\/tr>\n<\/table>\n

\n Design
\n <\/h2>\n\n\n\n\n\n
Critical design best practices<\/b><\/th>\n
\n Reduce your character count\n <\/td>\n\n Avoid including multiple pages with walls of text. Consider reducing text to
\n approximately 280 characters per page (the length of a tweet).\n <\/td>\n<\/tr>\n
\n Don’t block text\n <\/td>\n\n Make sure text is not blocked by other content on the page. Avoid burned in text; by
\n not using burned in text, you prevent text from being blocked when it gets resized to fit
\n various device sizes.\n <\/td>\n<\/tr>\n
\n Keep text within bounds\n <\/td>\n\n Ensure that all text in your Web Story is visible to the reader. Avoid burned in text; by
\n not using burned in text, you prevent text from overflowing when it gets resized to fit
\n various device sizes.\n <\/td>\n<\/tr>\n
\n Use animations mindfully\n <\/td>\n\n Bring your stories to life with animations. Avoid distracting or repetitive animations which
\n can cause fatigue.\n <\/td>\n<\/tr>\n<\/table>\n

More design best practices<\/h3>\n\n\n\n\n\n\n\n\n
Recommended design best practices<\/b><\/th>\n
\n Use Web Stories-specific call to action\n <\/td>\n\n When re-creating stories that were originally created for a social platform like Instagram,
\n Snapchat or YouTube, be sure to remove any reader call-to-action specific to a
\n certain platform. Make sure that users are able to follow any actions suggested in your
\n Web Story.\n <\/td>\n<\/tr>\n
\n Use full bleed videos and images\n <\/td>\n\n Include full bleed assets in your stories to create a more immersive experience for readers.\n <\/td>\n<\/tr>\n
\n Avoid low resolution or distorted images and videos\n <\/td>\n\n Use high-quality images, and take care when resizing images to portrait.\n <\/td>\n<\/tr>\n
\n Add a logo to your cover page\n <\/td>\n\n Include a high-resolution logo that represents your brand.\n <\/td>\n<\/tr>\n
\n Shorten video length\n <\/td>\n\n We recommend videos that are less than 15 seconds per page, or 60 seconds maximum.\n <\/td>\n<\/tr>\n
\n Include audio\n <\/td>\n\n Use high-quality audio clips that are at least 5 seconds long with balanced volume, and ensure
\nspeech is audible.\n <\/td>\n<\/tr>\n
\n Consider auto advance for video-only stories\n <\/td>\n\n Auto-advanced experience for video-based Web Stories could work well for a laid back experience.\n <\/td>\n<\/tr>\n<\/table>\n

\n SEO
\n <\/h2>\n