Happy to take a look, @carolakioka!
Can you please share one of your other stories which *is* okay in the AMP test, so we can reference?
Can you also please share your Site Health information privately via this form?
Thank you!
Thanks so much, @carolakioka! Interestingly enough, I ran your affected story through the Rich Results Tool earlier today and got “not a valid AMP page,” but now I’m seeing it as eligible for rich results with no issues.
Are the 3 issues that you noted showing up in Search Console, or did you see these in the testing tool?
Thanks!
I’ve tested here
The 3 issues appear when we edit the web story on the platform and click on the “preview” button. It appears those 3 issues on the “debug” tab.
Here’s a screenshot of it: https://drive.google.com/file/d/11vlulnnZ463oCxIZ05wWr903gjlWfu8D/view?usp=sharing
@carolakioka Very helpful, thank you!
It’s odd because it’s rare that we see only a single story on a site have issues like these, as opposed to *all* of your stories. Can you please try troubleshooting using the instructions below?
- Install and activate the Health Check & Troubleshooting plugin
- On your “Plugins” screen, click Troubleshoot to enable Troubleshooting Mode. This mode disables active plugins and switches to a default theme safely; this will not affect what your site visitors see, as it only changes the look and feel of your website for logged-in administrators.
- On the Troubleshooting Mode page, under Web Stories, click Enable while troubleshooting
- Go into the affected Web Story in the editor and see if the error warnings are still displaying
- If the warnings are still occurring, click Disable Troubleshooting Mode to exit Troubleshooting Mode
- If the warnings do not occur while in Troubleshooting Mode, re-enable your site’s plugins one-by-one by clicking Enable while Troubleshooting for each and then checking the Web Story in the editor again. This can help us pinpoint if a particular plugin or theme is causing the issue.
Please let me know what you find either way and we’ll go from there. Thanks!
@carolakioka I discussed this further with our team and wanted to note two things:
- One of the errors that you’re seeing is a known bug in Site Kit where excluding logged-in users from Analytics results in the invalid JSON error. There is a GitHub issue for this bug here and is planned to be released in v1.36.0 early next week.
- I see that you’re using the WP Super Cache plugin. Can you please try clearing your cache by going to Settings > WP Super Cache > Delete Cache and see if that resolves the remaining issues in your story?
Thank you!
Hello,
Thank you for your help.
We’ve tried the Troubleshooting step by step you’ve suggested.
When we disable both Sitekit and AMP plugins at the same time, the debug disappears, but the web story still doesn’t get a pass on the AMP test.
We also deleted the cache now, but the story still doesn’t get a pass in the AMP test 🙁
Maybe it’s better to just wait for the GitHub release next week?
Thanks!
@carolakioka Thanks for trying those steps!
When we disable both Sitekit and AMP plugins at the same time, the debug disappears, but the web story still doesn’t get a pass on the AMP test.
This makes sense – Troubleshooting Mode only makes changes to the admin side of your site, not the public site, so the errors would still appear in the external AMP test. The fact that they’re not appearing on the checklist in Web Stories when Site Kit and AMP are disabled indicates that that’s definitely where the issues are coming from.
So, this tells me that Site Kit is causing the Invalid JSON issue as noted in GitHub, but the other issues may also be caused by the Site Kit and/or AMP plugins. I’m going to do some testing on our side and will let you know as soon as I have an update.
Thank you again for providing all of this info to help us get to the bottom of this!
Okay, thank you so much for the help.
I’ll be looking forward to hearing from you 🙂
@carolakioka Thanks again for your patience here. Upon further testing and after discussing with our engineering team, we believe that all three of these errors are related to the Site Kit GitHub issue that I noted earlier, which a fix will be released for next week.
I’ll keep this issue open for now and let you know when the new release is available so that you can update and test again. Thanks!
@carolakioka Just wanted to follow up to let you know that Site Kit v1.36.0 was released and check if you are still experiencing issues with your story?
Please update the plugin, and update your story without making any changes. Clear any cache in WP Super Cache, or any other server side caching, and test your story in an incognito browser to see if the issue still persists.
Please let us know your results. Thanks!
Hello!
We’ve done the instructions you wrote, but the problem still persists.
The story doesn’t pass the amp test…
Thank you for your efforts!
Hi @carolakioka,
Thanks for following up. It looks like the JSON error is gone given the Site Kit update, but the other two errors remain.
I checked with our team, and the mandatory attribute ':zap:' is missing in tag 'html' error appears to be related to the AMP plugin. We’re investigating that and I’ll update you as soon as I have more info.
The other error message, DOMContentLoaded [...] AMP-WP, is referring to validation errors within the AMP plugin. Can you check to see if there are any validation errors showing there that you can address?
Thanks!
Hello!
I don’t know the specific reason, but we could validate amp in the story now.
I needed to delete one page (the 2nd one that explained what the term “queer” is), and it worked now…
The elements are pretty much the same as page 3 (currently page 2), so I’m not sure what happened.
Thank you so much for your efforts!
@carolakioka Very weird indeed, but glad you got it figured out!
I’ll mark this topic as resolved. Please do feel free to leave a review – we’d love to hear your feedback on the plugin!
