Close
Menu

RTCXpression

AMP Revisited – I Still Can’t Make Forms and Other Things Work Right


August 12, 2017

The first time I tried to work with accelerated mobile pages (AMP) was about a year ago. I tried again about seven months ago and I had the same problems.

I just spent most of the last two days trying to work with them again. I’m still having issues and I’m not a novice. I’m sure a novice would be completely lost.

I don’t like the way the AMP coders implemented form support. I don’t like the way they implemented iframe support. There’s a lot of things I don’t like about AMP.

AMP is an Unfortunate Necessity

To say that Google is pushing AMP is an understatement. I’ve tracked my metrics for months. My top pages have continuously dropped in the search engine results pages (SERPS). My web traffic is less than half of what it was in January.

If I change some or even all of my pages to comply with Google’s desires, would things get better? Probably. Is it something I want to do? Not really. Unfortunately, to get back into Google’s good graces, I’ll have to obey my evil overlords.

Issues with AdSense Ads

The AdSense ads, including the matched content units, work correctly on all device sizes as is. When I tested changes, the AMP ads for AdSense only worked right on mobile (cell phones).

If I want AdSense to work everywhere, I’ll have to supply two versions of every page where I display AdSense ads. I can do that, even if it isn’t the way I want to do it.


Getting the Right Things to Work

I can’t get forms to work the way I want them to, so I won’t bother. The desktop version of each article page will continue to offer commenting but the AMP mobile version won’t. The current mobile display will work as always – some search engines won’t favor AMP.

I’m going to focus my efforts on my articles. They’re the pages you’ll find when you search with Google anyway. I’ll have instructions on each page, telling you how to post a comment, if that’s something you want to do.

I tried to create an “AMP only” version of this website. It looked almost the same as it does now. That approach isn’t going to work.

By the way, I could use the amp-lightbox component for the hidden sidebar but not the amp-sidebar component. It seems the coders aren’t interested in making that component work right – clicking on a hyperlink closes the sidebar. They’re ignoring tons of open issues at Github.

No Fanfare

Once I get everything working the best way I can get it to work, I’ll just do it. I won’t make any announcements or anything like that. It will take days or weeks for the AMP mobile versions of each page to get indexed.

It may make no difference to you. Depending on how you search and how you use the web, these special pages could be invisible as far as you’re concerned.

I’m irritated and it’s because I shouldn’t have to have two versions of any page. Isn’t that the reason CSS media conditions were invented?

Please go to this alternate page if you would like read or post comments.

Share:

Categories: Technology

Tags: , , ,

Previous and Next Articles (if any):

« »

More

Please read some of my more important pages if you have the time:

Comments Policy           Privacy Policy

RTCXpression established Feb 28, 2011
Copyright © 2013-2017 RT Cunningham
Hosted at Digital Ocean