Hi there,

It would be best if you can provide us with your backend and FTP access for further check on this issues as it is required for you to changes those data on your related blog post to match AMP requirements.

Please advice.

Hi Warith,

We are a bit reluctant to give access to our back-end and FTP.

What if we export the blog articles with the AMP-errors - would you then be able to troubleshoot the problem?

Thank you


Kind regards
Rikke

Hi there,

Maybe you can provide us with your blog post links for us to check those issues and we might need to access your backend also, as most those error(on AMP) are might be caused by some of your plugin and might be your blog post structures are not follow what amp have set.

Please advice.

Hi Warith,

I hereby send you a list from google search console with the blog post links with the AMP-errors.

Kind regards
Rikke

Hi there,

It seems that there are no error shown when i tried to validate them as you can see here http://take.ms/GZKTT. I suspected that Goggle havent crawled your blog post latest changed yet and that why it kept showing you those error.

It would be best if you can wait for google to crawl them first or maybe go to this URL https://search.google.com/test/amp and copy your URL and see whether those blog post pass those rules or not.

Please advice.

Hi again,

Our web developer has send the attached document and writes the following:

These links can be scanned through other services to identify problems.
EasyBlog can view these pages without accesses to backend and tell you how to fix it. The problem is that 15 AMP-Tags are connected on the page, but only 4 are used. The remaining 11 has a warning.

Will you have a look at the new attached document?

Hi there,

Have you checked those links using given URL on above reply and did they shown any error in it? as currently everything is showing/working fine as you can see here http://take.ms/s8kCD

Please advice.