Comment on Amp Page

@westonruter

That may provide some benefit, but it would be very difficult to reliably parse JS code to try to detect class names as well as any other changes that JS may make to a page, like toggling attributes, creating elements, and so on.

Well, I think you’re right, but it seems so easy for the first sight.

I’m glad you’ve come to this conclusion. We’ve concluded the same and that’s why we’re so invested in the AMP plugin as a way to democratize performance and help publishers succeed on the web.

It’s pity that seems Google doesn’t affect this parameter on search results (it’s working the same way with Google My Business, when all have keywords in company name), that’s why old and unoptimized websites are on top, but I hope it will take effect soon.

I know this thread has been marked as resolved, but I’m wondering if this issue is back:
– I’ve recently switched to the wordpress default theme (Twenty Twenty) with no customisations at all;
– I had Jetpack comments enabled by default for all posts;
– Every post that I convert to blocks (or if I start a new one in block edit mode) returns an AMP error (pointing to the jetpack comment block);
– If I disable commenting for the post, AMP works just fine.

I had other issues also with the Cookies & Consent Banner (also for Jetpack) that also breaks in AMP. Any updates on the AMP compatibility with Jetpack?

@designative Please open a new support topic. Thanks.