AMP end of line

Reminder to folks it’s time to fully retire use of AMP as another failed abandoned Google attempt to take over the web when it was pointless and stupid for many sites where a print ready page would have worked just as well for mobile. It was a money grab to track folks usage by loading your content on their server. Ugh.

At this point, more than a year after AMP was retired as “end of life,” it’s time to move on.

Requires three things
a) setup proper 301 redirects to keep links if you had lots of inbound traffic, but frankly Google recommends simple 404 so they stop caching the /amp or ?amp URL — keep in mind normal htaccess redirect of /amp –> not /amp is tricky in case you have a post url slug of mycontent/amplify-your-cake — would kill that URL.

You need to try something like this in your root htaccess file, then *test* a amp url to make sure it redirects

e.g.,
RewriteEngine On

# Removes "amp" (or "amp/") from the end of the URL-path
RewriteRule (.*)amp/?$ /$1 [R=301,L]

this code also shared quite a bit online
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$
RewriteRule ^ %1/ [R=301,L]

2) deactivate any ‘AMP’ plugins in WordPress – which will remove the rel= link in your post headers; to remove a loop

3) clear AMP cache with Google: https://developers.google.com/amp/cache/update-cache

// I don’t work here, just started to do this last year, and catching up on final nail in the AMP coffin for our other sites this month //

if using redirection plugin

REGEX

Redirect AMP pages
http://site.com/article/amp/ ⇒ http://site.com/article/
Source
^/(.*?)/amp/$
Target
/$1/
Redirect ?amp pages
http://site.com/article/?amp=12 ⇒ http://site.com/article/
Source
^/(.*?)/\?amp=.*
Target
/$1/

Hello simchris

I hate google
I don’t know, in this time people are allowed to say, “I hate.”
It seems that we are living in a slave-like time, with new ideologies now dominating our collective culture and controlling our thoughts.
The strange thing is that despite the presence of many technology companies and browsers, no one acts as a god like Google, It seems that the gods Google, make a lot of mistakes
Although I like the simple design style in amp
The idea was good and practical
However, Google failed to build the infrastructure for this project, and it did not seem serious or convincing, and this is what is strange about the matter.

• This reply was modified 2 years by waleed9.

We started building websites March of 1995; so have seen a lot come and go. AMP was a good idea if you had a busy site someplace with slow server, etc., but when Google basically ‘forced’ people to be on AMP for mobile search results (much like G+ was *required* for a local business listing), their “do no evil” mantra was dead and buried. So, they keep abandoning things (RIP, Feedburner), that I won’t invest in any of their tech unless no other choice. We were so happy to see AMP go the way of another bad idea, as far as I was concerned. The idea of having to waste huge amounts of time building second version of content was dumb when stuff like ‘print friendly’ pages have been around for 25+ years. Anyway… good riddance, I say 🙂

Hello
finish for me too
Since 1 week

Sorry, forgot to mention, Google has made it harder to do the ‘clear amp cache’ thing. SHould have been a button in the official wordpress for amp plugin, but nooooooo.
If you serve 404s for the AMP endpoints, or do optional 301 redirects, that should suffice. There are no penalties or anything with removing AMP forever. Do it! 🙂
(I don’t work here, just loooooong time user.)
__ Chris S.

Hi @simchris

My site is hosted at namecheap that uses Nginx so there is no .htaccess file. In that case what to do?

I read 1 tutorial where someone told to do this:
regex

^/(.*?)/amp/$

In Source URL

/$1/

In Target URL

IS IT OK?

Hi, see my earlier post in thread on how to do the regex setting in the ‘redirection’ plugin, which I recommend. It can also monitor how many /amp redirects happen, which is kinda wild. 🙂

REGEX using ‘redirection’ plugin

Redirect AMP pages
http://site.com/article/amp/ ⇒ http://site.com/article/
Source
^/(.*?)/amp/$
Target
/$1/

Redirect ?amp pages
http://site.com/article/?amp=12 ⇒ http://site.com/article/
Source
^/(.*?)/\?amp=.*
Target
/$1/

Thank you so so much. I am not tech savvy. Now I realized the code I shared and part of your one is same. Thanks again

🙂
yes! I was including examples of which version to use depending on how you had been using the /amp endpoint.