Support » Plugin: AMP » ampwp-af808503-69e7-5666-af39-5019f9f1705e

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @juanjueves,

    I have checked your website; the loose mode will apply AMP components only when they are compatible and full AMP only when doesn’t have any issues. How is so far your experience with the sandboxing feature?

    Thread Starter juanjueves

    (@juanjueves)

    I have tried on several occasions to be able to add any more options to my site. This time it seems that I don’t get errors in Google Search Console of the AMP type…

    Hi @juanjueves

    Which errors are you getting on Google Search Console? Because errors related to structure data can be

    I don’t see so many plugins installed; for example, the Fast Velocity Minify, the AMP plugin already does CSS minification, and tree shaking. Could be this is not needed on the Standard mode.

    And the “WP Content Copy Protection & No Right Click” can create some errors but doesn’t protect 100% of users to copy the content.

    Thread Starter juanjueves

    (@juanjueves)

    Thanks mate. In the end I have put the standard mode again. Searchs in Google take much longer and there are so many coverage errors as well as amps in Console that scare me. Also, I don’t know why, when I put loose mode I end up having less Adsense income, verified in the days that I have proceeded like this.

    Hi @juanjueves,

    Have you used other modes before? There are errors and warnings; they can look scary if you errors they need attention. If they are warnings, depends on how they affect the page, it can be “good to fix.” If you describe the errors, we can try to help with them.

    About the loose mode, it is an experimental feature; the more stable scenario is using standard mode or reader mode with a compatible theme if you are having trouble with errors.

    Thread Starter juanjueves

    (@juanjueves)

    Thanks!
    Yes, actually I have used other amp modes before. But the plugin itself recommends the standard to me.
    There are so many errors and so different that I don’t know how to proceed and I always return to the standard mode so as not to worry.
    Server 500, 404, pages determined not to be amp, coverage errors…
    Anyway, I’m currently reading that the amp option may be deprecated.
    And even from Google Analytics it is warned that in 2023 the traditional mode will cease to be operational to only have the G4 version.
    Perhaps it is necessary to start thinking about dispensing with amp for the sites…`

    • This reply was modified 8 months, 2 weeks ago by juanjueves.
    • This reply was modified 8 months, 2 weeks ago by juanjueves.

    Hi @juanjueves,

    Thanks for getting back,

    There are so many errors and so different that I don’t know how to proceed, and I always return to the standard mode so as not to worry.

    If you be more specific, I can help you with that. I have checked some of the main pages, and they are valid AMP pages.

    https://search.google.com/test/amp/result?id=Y_pLTztov5ITt2lnZpqfoA
    https://search.google.com/test/amp/result?id=ZxCMIXbHyJe185xYnKDfgw

    also, rich results check:

    https://search.google.com/test/rich-results/result?id=XwoT0fj3q18MQnGo18uL2w

    Server 500, 404, pages determined not to be amp, coverage errors…

    Error 500 can be related to the application in general. And error 404 is for not found content. The plugin itself doesn’t generate 404 errors; you should check if your application has any redirection applied, and if you remove any page or change the structure should review the new routes for that.

    Anyway, I’m currently reading that the amp option may be deprecated.
    And even from Google Analytics it is warned that in 2023 the traditional mode will cease to be operational to only have the G4 version.

    I think you get confused between Universal Analytics and AMP, there are two different things Universal Analytics is a tool to track users, and AMP is a component library. G4 will replace Universal Analytics; you can read more here: https://support.google.com/analytics/answer/11583528

    AMP still evolving the sandboxing that you were testing is part of the bento project some of the initiatives around AMP, you can read more about that here https://bentojs.dev/

    An extra thing you can check some of the content about fixing errors on search console:

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ampwp-af808503-69e7-5666-af39-5019f9f1705e’ is closed to new replies.