The script tag contains invalid JSON that cannot be parsed.

I similarly see no validation error for https://www.techrbun.com/setup-cloudflare-cdn-for-blogger/?amp

Results: https://validator.amp.dev/#url=https%3A%2F%2Fwww.techrbun.com%2Fsetup-cloudflare-cdn-for-blogger%2F%3Famp

For the above URLs, I’m not seeing JSON parse errors when looking at the Structured Data Testing Tool:

https://search.google.com/structured-data/testing-tool#url=https%3A%2F%2Fwww.techrbun.com%2Fsetup-cloudflare-cdn-for-blogger%2F%3Famp

Same for the other URL:

https://search.google.com/structured-data/testing-tool#url=https%3A%2F%2Fwww.ccdiscovery.com%2Fkarachi-kings-complete-squad-players-list-schedule-of-psl-2020%3Famp

*Raises hands, does the time out thing*

If you need support and you are not the person who started this topic then per the forum guidelines please start your own topic.

https://www.ads-software.com/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

You can do so here.

https://www.ads-software.com/support/plugin/amp/#new-post

Pile on topics do not work here and I have archived the replies from everyone else who jumped onto this topic. Please start your own topic, that is how volunteer support works here.

I also found the issue reporter on Twitter for someone who isn’t even using WordPress: https://twitter.com/Chrischaos/status/1230518953421803523

So I don’t think there is a bug with the AMP plugin. I’m inquiring at the Google side.

Hi, please note that search console is not saying that it’s an “ERROR” it is showing it in the “VALID WITH WARNINGS” option, because the AMP page itself is valid, but contains some JSON snippet that cannot be parsed. And this is happening since the last update. Kindly give your opinion on that.

PS. I repeat, It’s not about the validity of the AMP page, as I myself have seen that the amp validation tool gives positive result. But the problem is that it cannot be parsed entirely and that’s what search console is reporting.

Note: the AMP plugin is not currently validating the JSON that is being added to the page. This may be why the error is showing up in Google Search Console. We try to prevent situations like that from happening, so I’ve opened an issue to fix: https://github.com/ampproject/amp-wp/issues/4320

This doesn’t address the underlying problem, however, that some theme or plugin apparently generated invalid JSON on the page. However, I cannot see any such invalid JSON (causing a parse error).

My issue fix after previous version installation AMP

@youthvocal which AMP version please?

Yes, you are absolutely correct. I am too rolling back to the old version. It is working perfectly. The new version has some bug. The team should take a note of this and fix the bug.

@heyanirban which of the old version fixed the error because I have tried both versions 1.4.2 and 1.4.3 but the problem still persist.

Please share which previous version you should used

Avital Andrews, heyanirban :

Please, Can you share which previous version is current working well, (because I was updated latest version and do not remember, which version I was used but that was working very well, So Help us) I need to rollback due to above described warning issues in my website.

@heyanirban @youthvocal @pankaj977 @stanleychukwumezie2015 @vikkymmk I have developed an extension plugin which works around this issue: https://gist.github.com/westonruter/d9df78faed75297f9ca6b6be36d37ab2

Installation instructions: https://gist.github.com/westonruter/d9df78faed75297f9ca6b6be36d37ab2#gistcomment-3184905

The underlying issue appears to be a bug with the AMP validator, so this workaround plugin should not be needed for long.

@pankaj977 @vikkymmk @stanleychukwumezie2015

I had simply rolled back to the previous version of the plugin using the UPDRAFTPLUS BACKUP PLUGIN.

@westonruter thank you! This plugin has fixed the problem. Also, I have understood that there’s actually nothing wrong with the AMP plugin, the AMP validator of Google is at fault as it is treating the /n (new line) as a non parseable character.

The fix is now live. I’m not able to reproduce the issue anymore. Feel free to re-add line breaks to your JSON. My workaround plugin can now be uninstalled.