Pascal Birchler

How are you viewing/displaying stories that people are able to swipe to the next story? Is this using the Web Stories block or is this on Google Discover.

Are you unmuting using your phone’s volume toggle, or by tapping on the mute icon in the story itself?

If you have a link to look at, that would be very helpful.

Depending on that information, you might want to open an issue at https://github.com/ampproject/amphtml instead, just as an FYI.

We can’t speak about third-party tools like that, but Search Console doesn’t report any issues for your web story you can probably ignore that message.

For further help with Screaming Frog you will need to reach out to their support to improve their tooling.

If you look at the?#meta-language-packs?channel, there was actually an issue with the import of 3.8.17. See https://wordpress.slack.com/archives/C0E7F4RND/p1727721503276069.

This was not because of a “This plugin is not properly prepared for localization. warning though, so that’s not relevant.

Either of you can ask in #polyglots or #meta for someone to re-trigger the import.

It sounds like some of your existing users don’t have the same capabilities as other users on your site. You can use a plugin like Members to view and modify capabilities for individual users and also user roles (they can belong to both).

There is currently no built-in way on the settings page to add Google Tag Manager to stories. It could be done via a plugin though I think.

What’s the use case, what do you want to achieve?

If it’s for Google Analytics, note that Google Tag Manager for AMP/Web Stories doesn’t support Google Analytics 4. You will need to specify the GA measurement ID manually on the settings page.

Hi there

For the untranslated strings, the generated PHP file contains entries such as:

This is a bug, and was fixed in version 2.6.1 of the wp i18n command. Please update WP-CLI to the latest version (2.11.0 at the time of writing). If you have installed wp-cli/i18n-command separately on top of WP-CLI, use wp package update to update it to the latest version. Then, delete the .l10n.php file and generate it again.

Again, I don’t see how Web Stories would possibly would possible cause this. But I’ll try to see if anything stands out from your Site Health data.

As for your theme and plugins, please use the Health Check plugin to use a different theme. It has a troubleshooting mode which changes the theme just for you and does not affect your visitors.

If this doesn’t help, there’s not really much we can do to help unfortunately, since this doesn’t appear to be a reproducible or widespread issue.

Hi there,

I don’t see how the Web Stories plugin would possibly cause additional lines to be added everywhere on your site…

Please try temporarily disabling all other plugins and using another theme to see if this still happens.

Please also share your Site Health info (Tools -> Site Health -> Info -> copy to clipboard)

Hi there

The critical error message in WordPress usually contains a link to documentation about debugging. Have you tried those steps?

In general:

1. Check your error logs to see if anything stands out. Ask your hosting provider for help if needed.
2. Temporarily disable all other plugins to see if this error still occurs

Note that recently the Gutenberg plugin had a bug that caused issues with Web Stories. Update Gutenberg to 19.3 to resolve that issue.

Our forum support focuses on using and troubleshooting issues with the Web Stories for WordPress plugin. Specific questions about traffic declines, ranking, crawling, and indexing are best answered by the experts at Google SEO and Analytics Help Communities.

Note that changes in Web Stories traffic are not unusual and can rely on many factors. For example, content featured on Google Discover regularly changes, and Google Search constantly improves its algorithms, which can affect ranking. Using the AMP validation tool and the Web Stories editor’s built-in pre-publish checklist for any newly published stories is a good practice to ensure your story is eligible to appear on Google services.

If you’re not sure whether a change in traffic is caused by a change to your site, we recommend using Search Console’s various tools to confirm that your content is properly crawled and indexed.

The archive page layout and what’s displayed on there is determined by your theme. We don’t control that.

However, you could create a custom stories archive page in the settings and then use the Web Stories block or the Query Loop to have more control over the appearance.

Just a quick update, Gutenberg 19.3 was released today that should resolve the critical error.

Unfortunately we can’t help with issues related to Discover here, our focus is the WordPress plugin, not the distribution. I recommend asking in the Google Search Central Help Community about that.

Hi there,

Are you using the Gutenberg plugin by chance? If so, that plugin contained a bug that caused this issue. It was fixed in version 19.3, which was just released today. So please update the Gutenberg plugin to resolve this.

I see that you are tracking Web Stories with the Google Analytics measurement IDs G-Y9PGYE48Z4 and G-1X1JZTTZM7. One is from Site Kit, one from the Web Stories settings.

Now those are just for Google Analytics, so it’s not related to Discover.

If no data is showing up in the Discover performance report in Search Console, consult the?Search Central Help Community?for further help.

Hi there

This appears to be a display issue with your theme, which shows both the interactive story player and the poster image on top of it, hence the “double display”.

You can remove the poster image using some custom CSS, which you could add in the Customizer under “Additional CSS”.

The following CSS should do the trick:

.post-type-archive-web-story .web-story.has-post-thumbnail .wp-post-image {
    display: none;
}