Support » Plugin: AMP » A Little Help (Info) Needed

  • Resolved Stephen Ekpa

    (@droidafrica)


    Hi…
    My theme only support AMP in reader mode. But my site is heavily based on a plugin that generate a custom post type, but that plugin does not support AMP at all.

    But with few tweaking, Am able to get my theme, and this plugin to work with AMP in Transitional mode. And when I tested here and here, it showed pass and valid respectively.

    I set up horizontal menu on None AMP (Mobile), and it works same way in AMP as well. Google is caching the new AMP pages, but now;

    1. Do I need to worry about ranking even though both theme and custom post plugin does not support AMP, if given that all factors relating to good and rank-able content are in place?

    2. If indexed, AMP pages load very fast from Google cache, but when visiting AMP url hosted on my server, it loads very slowly. For example, visiting https://droidafrica.net/gadget/nokia-c10/?amp=1 loads far slower than visiting the none AMP version. Should I worry over this?

    3.I’ve kept some long but unnecessary content under what I’d describe as “click to expand” modal, just for the purpose of keeping the site layout clean and neat on mobile. This click to expand sections work well on mobile, but since there are javascript based, there aren’t working on AMP pages. When Google index my AMP pages, will those sections be indexed? Moreover, will Google penalize me for putting content in modals that works in none AMP, but not working in AMP?

    I know these are a lot of questions, so my heart felt appreciation goes to anyone who knows the answer and decided NOT to look away…Thanks!

    • This topic was modified 4 months, 3 weeks ago by Stephen Ekpa.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out, hopefully we can assist you with your queries.

    My theme only support AMP in reader mode. But my site is heavily based on a plugin that generate a custom post type, but that plugin does not support AMP at all.

    You could try an alternative custom post type plugin such as Custom Post Type UI. Custom Post Type creation doesn’t typically impact your sites front end so I would image most other similar plugins would work as expected.

    Great however that you did manage to work through the incompatibilities and make it work.

    1. Do I need to worry about ranking even though both theme and custom post plugin does not support AMP, if given that all factors relating to good and rank-able content are in place?

    I would review your custom post types and how they are generated. As long as you have the same content between your AMP and non AMP URLs I don’t think you need to worry about ranking. The product experts at the Search Console Help Center should be able to assist better than we can here when it comes to ranking and search queries.

    2. If indexed, AMP pages load very fast from Google cache, but when visiting AMP url hosted on my server, it loads very slowly. For example, visiting https://droidafrica.net/gadget/nokia-c10/?amp=1 loads far slower than visiting the none AMP version. Should I worry over this?

    I’ve performed some checks on your site and I find your AMP version loads much faster. Have you done some performance checks using servics such as web.dev or PageSpeed insights? (AMP | non AMP)

    3.I’ve kept some long but unnecessary content under what I’d describe as “click to expand” modal, just for the purpose of keeping the site layout clean and neat on mobile. This click to expand sections work well on mobile, but since there are javascript based, there aren’t working on AMP pages. When Google index my AMP pages, will those sections be indexed? Moreover, will Google penalize me for putting content in modals that works in none AMP, but not working in AMP?

    While this may also be better answered by the search experts in the Search Console Help Center ideally your content should match between both versions of your site. You can use AMP components such as amp-accordion or amp-selector for similar functionality to your expanding read more. You could also use AMP-bind to toggle classes with your existing plugin or follow this guide for similar AMP functionality.

    Let me know if you have any further questions on the above.

    Thread Starter Stephen Ekpa

    (@droidafrica)

    Wow…that was fast! Thank you so much @jamesosborne, your reply is highly appreciated. Currently going through the load more tutorial, and will revert back here if I need better hands.

    As for the other two question, I’ll just observe Google for a week or two and see how they handle it. I might also gather more ideas from ranking professionals over at Search Console Help Center, but that would depend on what happens within the coming days/weeks.

    As for the loading speed, tools actually says it load faster, but real time usage suggests otherwise…I think this should be a minor issue, since the pages are cached on Google, and from Google, it loads faster.

    Just one more thing, (I’m not even sure if the question belongs here). Anyways, I have used add_filter( 'amp_to_amp_linking_enabled', '__return_false' ); to disable AMP to AMP linking, such that visitor arrives at AMP pages from Google, then further clicks down the line heads over to none AMP. Could there be any negative impact associated with this configuration SEO wise?

    • This reply was modified 4 months, 3 weeks ago by Stephen Ekpa.
    Plugin Support James Osborne

    (@jamesosborne)

    No problem at all, happy to help. Feel free to revert after further testing. Correct also that AMP cache could being further performance benefits.

    Just one more thing, (I’m not even sure if the question belongs here). Anyways, I have used add_filter( ‘amp_to_amp_linking_enabled’, ‘__return_false’ ); to disable AMP to AMP linking, such that visitor arrives at AMP pages from Google, then further clicks down the line heads over to none AMP. Could there be any negative impact associated with this configuration SEO wise?

    I don’t think this will have any negative impact. Directing users from an AMP URL to the canonical version. I don’t see it being any different to having AMP disabled on some pages or posts. With a user who lands on an AMP URLs of yours from search I don’t see it any different to them clicking on an internal link without an AMP version available.

    Thread Starter Stephen Ekpa

    (@droidafrica)

    Thank you so very much sir for your help!

    Plugin Support James Osborne

    (@jamesosborne)

    No problem at all. If you have any further questions be sure to reach out. And once you get a chance to test out the plugin be sure to share your feedback.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.