SEO & Optimization
Metadata can be attached to the Web Story from the Document tab in the sidebar, as well as directly before publishing. This includes the poster image, author, and an excerpt or description. Add these to ensure maximum compatibility with search engines and discovery features that take advantage of that metadata.
Tip: Consult the checklist to see which required metadata is missing before publishing your story.
Monetize your stories
Make money off your Web Stories by automatically inserting ads between pages. You can enable the following supported integrations in your plugin's settings:
If you use the Site Kit by Google WordPress plugin, you can set up Google AdSense there.
There are two ways to include analytics in your Web Stories:
- Add your Google Analytics tracking ID in the settings
- If you use the Site Kit by Google WordPress plugin, you can set up Google Analytics there.
What is the "improved analytics configuration"?
Up until version 1.12.0, Web Stories for WordPress used a custom analytics configuration with a custom set of events. Starting in version 1.13.0, we changed the default analytics configuration to a streamlined, recommended preset with fewer events. Existing users will continue to use the previous configuration unless opted-in by clicking the "Migrate" button. The specific changes are listed in the table below.
|Before v1.13||v1.13 and later||Description|
|N/A|| ||Fired once per story view. Parameters: the story title and number of pages.|
| || ||Fired when a story page becomes visible. Parameters: the story title and viewed page index.|
| || ||Fired when the last story page displays to the user (can be used to measure completion rate). Parameters: the story title.|
| ||(Removed)||Fired when clicking an element that opens a tooltip such as an |
| ||(Removed)||Fired when clicking on a tooltip.|
| ||(Removed)||Fired when opening a drawer or dialog inside a story, such as a page attachment.|
| ||(Removed)||Fired when closing a drawer or dialog inside a story, such as a page attachment.|
| ||(Removed)||Fired when the user initiates an interaction to mute the audio for the current story.|
| ||(Removed)||Fired when the user initiates an interaction to unmute the audio for the current story.|
| ||(Removed)||Fired when a user opens a page attachment.|
| ||(Removed)||Fired when a user closes a page attachment.|
| ||(Removed)||Fired when the story displays the bookend to the user, after the last page of the current story.|
| ||(Removed)||Fired when the user dismisses the bookend.|
When creating a web page, heading tags can be used to emphasize important text. The Web Stories editor does this for you by automatically choosing the right heading tags for your text elements depending on their size and position on the page. That means you do not have to worry about which heading tags are being used for your content.
However, in some cases you might want to override the default behavior. In the editor, you can achieve that in the Accessibility panel under the Style tab. There you can deliberately set a text element's heading level from 1-3 or mark it as a regular paragraph.