October 14, 2019 at 10:59 pm
Most of my Amp pages are indexed fine but I got a message from Google that I have a warning for a few blog posts where I used buttons.
I have not updated these in some time. I thought at first it was because they were still in classic layout using button shortcode. So I sat down and went through one of these posts and updated it to the new format using the “advanced button” item in layout. When I tested that URL again, Google gave me the same warning. I thought perhaps it was a cache problem. I cleared Cache at Cloudfront and turned off WP Rocket. Still got the warning. When I look at the Source code for HTML, I can see the code it’s complaining about so I don’t think it’s a cache problem or at least not obvious to me that it is. It’s likewise not obvious to me what the problem is.
This is one of the URLs that Google says has an issue.
*Login to see link
_amp_mustache_117d86f99c60bc901db7074ecf62afbd@media (max-width: 767px) {.kt-btns_544672-af .kt-btn-wrap-0 .kt-button {_amp_mustache_117d86f99c60bc901db7074ecf62afbd.kt-button {
I also have something else weird going on with this Amp page now that I’ve recreated the wheel using the new style button. I gather buttons display as text instead of buttons? The first one has an orange background the way my buttons do on the regular post. The rest of the text “buttons” on AMP are displaying without the orange background. I really don’t have a preference other than I’d like them to all display the same. I’m wondering if this is because I duplicated that block each time after creating it once and just updated the link for each one? I wanted to keep them all the same style without having to re-click the colors over and over. Just a guess that may be what caused the first one to display with a color and all the rest to not. Maybe it’s something else altogether.
On a similar note, in the regular layout I used a spacer after each button so that there would be room before the next paragraph. I see that didn’t go into the AMP style version at all. Is it possible it could at least insert a line feed or something in place of spacers?
Sorry for piling on multiple concerns. Since it’s not currently eligible for AMP indexing, that’s obviously the priority problem! Ha!
If there’s any detail you need, etc. to figure this one out, just let me know!
Thank you,
Mark