If you run a WordPress site you have probably contemplated already at some point whether or not you should implement the hot new Google AMP for mobile. We had the same dilemma here at Kinsta and ended up testing it for a while. In the end, we didn’t see good results and it ended up hurting our conversion rate on mobile devices.
So today we are going to dive into how to disable Google AMP on your blog, and how to safely do it without 404 errors or harming your SEO. Simply deactivating the AMP plugin alone could end up really harming your site, so be careful. The good news is that both methods mentioned below don’t require a WordPress developer and can be done in a few minutes!
Google AMP
Google AMP (Accelerated Mobile Pages Project) was originally launched back in October 2015. The project relies on AMP HTML, a new open framework built entirely out of existing web technologies, which allows websites to build light-weight web pages. To put it simply, it offers a way to serve up a stripped down version of your current web page. You can read more about it in our in-depth post on Google AMP, as well as compare all the pros and cons.
Why Google AMP Didn’t Work For Us
Due to all the hype around Google AMP, we decided to give it a try on our Kinsta site. You never really know what will happen until you test something. So we let it run for two months and here are the conclusions we came to. Note: This could vary in almost every industry, so we highly recommend testing it on your own site before drawing conclusions. A couple of ways to test this include:
- Looking at data in Google Search Console before and after.
- Comparing data from Google Analytics on your /amp/ URLs vs original URLs from organic traffic before and after.
Here is some data from during the time AMP was enabled on our site.
Google AMP Positions
As you can see, after enabling Google AMP and allowing them time to index we definitely saw a decrease in average positions in SERPs on mobile.
Google AMP CTR
After enabling Google AMP we saw a decrease in CTR on mobile.
Google AMP Impressions
After enabling Google AMP we did see a higher number of impressions.
Google AMP Clicks
After enabling Google AMP we saw a slight increase in total clicks.
So for us, there was good and bad in the data above. However, the most important part was looking at the data in Google Analytics for the time AMP was enabled:
- Our mobile leads dropped by 59.09%.
- Our newsletter email sign-ups from mobile dropped by 16.67%.
- Our account creations from mobile devices dropped 10.53%.
Because of this, we decided that Google AMP was not working for our business model. So why did we not see good results, when others do? Well, probably one of the biggest reasons is that our site is already pretty fast on mobile. So we didn’t see a huge increase in speed, as some other ad-heavy sites might have. According to Google, 70% of cellular network connections globally will occur at 3G or slower speeds through 2020. So while it is super important to optimize for mobile, those that already have a well-optimized site probably won’t notice huge differences.
Another reason is that we don’t publish news. A lot of big publications are using AMP and taking advantage of the carousel in SERPs. A lot of big companies like The Washington Post, Gizmodo, and Wired all saw big improvements with Google AMP, but these are all news-oriented and ad-heavy content sites. We, of course, publish a lot of content, but our primary focus is still on generating leads and signing up customers.
Could we have done more conversion rate optimization to our AMP install? Probably yes. There are ways to add CTAs, newsletter signups, etc. We did optimize for some of this. But after seeing the conversion data above it wasn’t worth managing Google AMP separately, which can be a pain, just to have a slightly faster mobile site. Also, a lot of our traffic and audience to the Kinsta blog is not from mobile to begin with, so we decided to disable Google AMP.
Also, currently there are no SEO benefits from AMP yet unless you are a news site trying to score the carousel in SERPs. We analyzed our mobile rankings and after AMP was fully removed, our rankings actually went up. Again, this could just be from natural progress. But we saw no increases in SERPs from running AMP. If your site is slow to begin with though you might, so we always advise testing on your own site.
Other brands have also seen no harmful impact from removing AMP, and like us, actually saw improvements. Outside Magazine increased pageviews per visit 13 percent after ditching Google AMP.
How to Disable Google AMP
There are a couple of different ways you disable Google AMP. Google has their official documentation on how to remove AMP from Google Search. A big problem with this though is that it usually requires a developer and their instructions are not very WordPress friendly. Their very first step is to remove the rel=”amphtml” link from the canonical non-AMP page, while still leaving the AMP page in place. Thankfully though there are a few different ways to approach this without harming your SEO. You don’t want to simply disable the Google AMP plugin as this will result in 404 pages.
Option 1 – Search and Replace (Regex)
The first option involves using a search and replace plugin to remove the rel=”amphtml” code while no-indexing the AMP pages. We can thank Gulshan Kumar who originally posted this strategy. This assumes you are utilizing the free AMP for WP plugin.
Step 1
First, you will need to download and install the free WordPress Real-Time Find and Replace plugin. One of the great things about this plugin is that it doesn’t modify your WordPress database or site, so it is very safe to use on your site without worrying about breaking anything. Basically, it finds and replaces rules that are executed AFTER a page is generated by WordPress, but BEFORE it is sent to a user’s browser.
If you are a developer, you could, of course, do a normal search and replace. And we normally we would recommend doing changes in the database long-term, but in this scenario, it works great to temporarily remove the AMP code while things are re-indexing. It also means you can easily do this without a developer. Although we always recommend still taking a backup!
The plugin currently has over 90,000+ active installs with a 4.5 out of 5-star rating. You can download it from the WordPress repository or by searching for it within your WordPress dashboard under “Add New” plugins.
Step 2
Click on Real-Time Find and Replace under tools in your WordPress dashboard. Click on “Add” and add the following code into the Find: field:
<link rel="amphtml" href="(.+)" >Click on the box next to “RegEx” and then click on “Update Settings.” This will replace/remove that important AMP tag as Google recommends on your canonical non-AMP pages and or posts.
Step 3
The next step is to mark the AMP pages as no-index. Click into the AMP for WP options panel and on the “SEO” section. In the Additional tags for Head section input the following code and hit “Save Changes.”
<meta name="robots" content="noindex,follow"/>This will tell Google to no longer index your AMP pages in search and therefore it will start re-indexing your original URLs for mobile.
We recommend leaving the AMP plugin enabled until all of your AMP posts/pages have re-indexed over to the original URLs.
Step 4
We also recommend following the 301 redirects in option 2 below just to be safe!
Option 2 – Disable and Add Redirects
The second option is a little messier, but we’ve also seen this work fine. We recommend this option only if you have any issues implementing the method above. This involves simply disabling the AMP plugin and adding 301 redirects. Thanks to the AMP for WP for originally posting this.
Step 1
The first step is to simply add 301 redirects for everything that has an AMP URL. First, you will need to download and install the free WordPress Redirection plugin. You could use your own redirect solution or plugin, but the reason we recommend this one is because you will need one that supports regular expressions. You can always uninstall the plugin after everything has re-indexed.
The plugin currently has over 1 million active installs with a 4 out of 5-star rating. You can download it from the WordPress repository or by searching for it within your WordPress dashboard under “Add New” plugins.
Step 2
Click on Redirection under tools in your WordPress dashboard. Then add the following code into the Source URL field and ensure you check the “Regex” box:
/(.*)\/ampThen add the following to the Target URL field (updating the domain with your own):
https://yourdomain.com/$1Ensure Redirections is selected and click on “Add Redirect.”
After adding this we recommend browsing to a couple of your AMP blog posts or pages and test to make sure they are redirecting properly. Also, if you are a Kinsta customer, you can skip installing the above plugin and simply add the global redirect from the redirects tool in your MyKinsta dashboard. Our tool supports regular expressions.
Alternatively, if you are running Apache, you could also add the following to the top of your .htaccess file:
# Redirect from AMP to non-AMP path
RewriteEngine On
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$
RewriteRule ^ %1/ [R=301,L]Step 3
You can then deactivate and uninstall the AMP for WP plugin.
Make sure to check out our additional tips further below to monitor the re-indexing process.
Monitoring Reindexing
You can monitor the progress of removing Google AMP in Google Search Console under “Search Appearance > Accelerated Mobile Pages.” As you can see below, the moment we implemented the above strategy our AMP URLs started to de-index. You can also try resubmitting your sitemap file to speed up the process. Depending upon the number of AMP pages you have indexed this process could take anywhere from a couple of days to a couple of weeks.
We also recommend utilizing a keyword rank tracking tool. For example, we monitor our desktop and mobile keywords here at Kinsta using Accuranker. It allowed us to easily see the history of each keyword and that the /amp/ URLs on mobile were re-indexing over to the original URL. This can be a quick and easy way to verify that everything goes smoothly.
Summary
We all love faster mobile sites, and we applaud Google for trying to make the web a better place. But as we discussed above, perhaps you aren’t seeing the results you hoped for with Google AMP. We always recommend testing it as it could vary per industry. The amount of mobile traffic your site gets could also greatly impact your results.
We aren’t the only ones that have had issues with AMP. Rock Star Coders saw a 70% drop in their conversion rate after testing AMP on their sites.
Thankfully there are easy ways to disable Google AMP if you want to resort back to your original setup. Both of the options above don’t require a developer and will ensure your visitors don’t see nasty 404 errors, while retaining your rankings in SERPs.
Have any questions or have you encountered your own issues when trying to disable Google AMP? If so, we would love to hear about them below in the comments.
Brian has a huge passion for WordPress, has been using it for over a decade, and even develops a couple of premium plugins. Brian enjoys blogging, movies, and hiking. Connect with Brian on Twitter.
Thank you! This is helpful! I use the Redirection method.
Hello Brian,
Thank you so much for sharing the eye-opening case-study, and the safest ways for taking down the AMP pages. I am pretty sure; most users will find it helpful.
After implementing the Search & replace method, later after noindexing, a redirect can be setup from AMP to the non-AMP path to avoid possible 404 at old AMP permalinks. Below is a rule for it.
# Redirect from AMP to non-AMP path
RewriteEngine On
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$
RewriteRule ^ %1/ [R=301,L]
For little performance gain, getting hit by AMP is a loss for the business. In real, delivering the best user-experience at the mobile site should be the top priority to compete with AMP version pages. :)
Thanks & Regards,
Gulshan
Great thanks, I have updated the above post with the snippet :) Always good to have additional options.
Thanks for the info. I made a mistake of using the AMP plugin and then simply deactivating it, which created a lot of 404 errors. If I want to use one of the solutions, which you have wrote about, do I need to re-install the AMP plugin?
Solution #2 above doesn’t require the AMP plugin being installed.
Brian, thanks for sharing this. I think the key takeaway is that you don’t necessarily need to jump on the AMP bandwagon unless you’re a high frequency news publisher and already have a reasonably fast mobile optimized website.
You nailed it!
I’ve used AMP, but didn’t really like how it works on my business website. You are right, the conversion rate drops a lot.
I removed AMP and use the redirection method. This post has helped me. Thanks for this.
I totally respect your opinion. I’m just curious, Did you optimize your AMP for the conversion rates as you did for your blog?
Hey Ahmed, we did some optimization, but nowhere near what we could have done. It came down to the issue of, since there is no SEO benefit at this very moment, why maintain a separate AMP setup? For ad-heavy sites and news sites wanting that carousel, it might be a different story… but for us, it wasn’t worth the extra effort, compared to simply optimizing our main site for both. We are also launching a brand new site soon, so this also impacted our decision. Our new site has very well placed mobile CTAs, etc…
However, you can guarantee I will be keeping my eye on AMP. Because Google one day could give extra SEO ranking benefits… and if they do, well, that would definitely play into a big part of the equation for us as whether or not we should bother with AMP :)
I too have a confusion about the thing- my original website loads faster than the AMP version – The numbers are:
For Original
Load Speed – 1.2 Seconds
Page Size – 131KB
Number of request – 20
Pagespeed grade – 98%
Yslow grade – 82%
For AMP version
Load Speed – 1.9 seconds
Page Size – 509KB
Pagespeed grade – 100%
Yslow – 91%
My site is about Coffee maker reviews named Friedcoffee. Should I really use AMP or not?
Very informative. Thanks a ton.
¡Buen contenido!
Seems like a lot of stress just to remove it
I own a Health site not like the big guys but would you recommend i use it? i publish daily though
Hey Kingsley, it all depends on your site. Also, if you are a Google News site, the carousel in SERPs might be very important for you. However, we haven’t seen any increase in rankings in SERPs due to AMP. This might change in the future, but currently, there is no SEO advantage. Unless perhaps your mobile site is very slow.
Hey, I want to enable the amp version again, how do i reverse this process again?
Essentially yes. Option 2 would be very easy, as you can simply disable the redirect and enable AMP URLs again.
I pondered the AMP implementation of cookies control under new GDPR regulation. At this time there is no way to implement it correctly, meaning separate choice for separate purposes. AMP technology is much behind the times so we decided to remove it completely for compliance purposes.
I chosen option 1 and I found that because the caching plugin is minifing some of the HTML the amphtml tag was concatenated with an style tag like this:
In this situation the regex provided is not good. I had to use two regex rules:
1. link rel=”amphtml” href=”(.*?)”
2. just because the above rule is leaving in place instead of nothing (just replace < > with empty string)
Rule 1 had to deal with no greed option because the original regex is selecting up to the end of style tag. Using [^>] to forbid > inside the src attribute is not supported by the plugin even if the regex is correct.
I installed amp on my site.. now google search is throwing up errors and looks like Ill have to pay to get them fixed. My rankings have dropped a bit on one of my pages, but I dont know if thats because of a competitor comiong to makrte or amp errors having a negative seo effect? Anyone else had this? amp errors negatively effecting rankings?
Really thinking of just disabling it as detailed above
Hey Shaun,
If AMP is setup incorrectly or reporting errors it very well could lead to ranking issues due to the fact that Google might not be able to crawl your content. We do have a guide on how to set it up properly: https://kinsta.com/blog/google-amp/
The AMP errors should help you diagnose what you need to fix. If all else fails, you could hire a developer to fix the issue for you: https://kinsta.com/blog/hire-wordpress-developer/
Thanks Brian
Loved the way you have explained it. I am hosting my website on kinsta and believe me the support guy did it in 2 minutes. I have faced problem with amp
The bounced rate increased
Sessions decreased
People stopped commenting and what not.
Hey Ajay,
Yes Google AMP impacts every site in different ways. The best way to know if it will work for your site is to test it. Make sure to optimize after the fact as well. The AMP plugins typically have settings where you can add comments back in, CTAs, etc.
Hey Brian I was using AMP for my wordpress website, but in one month I got unsatisfactory results, so I simply deactivated and removed that AMP plugin from my website but after removal I got my traffic decreased in Google Analytics. The most surprising thing is that the past records of traffic, in Google Analytics, was also decreased, I don’t know why? can you tell me?
Hey Saurabh,
Did you follow all the instructions above? You can’t just remove the AMP plugin, you need to add 301 redirects. Otherwise, people will still hit your AMP URLs in Google’s index and then not arrive to your site at all. Make sure to follow all the steps above.
Thanks Brian, was fed up with getting errors using AMP, I don’t like it at all. As a site owner and a visitor to other websites. It strips things out and I cannot stand it, followed your tips for redirecting via Kinsta redirect option, works like a dream!
Thanks dude!
Great, glad to hear it Ben! Yes, why aren’t we improving our sites for mobile instead of porting them to another platform? AMP is great, but not fixing the original problem.
Helly Brian, this is a great tutorial about AMP configuration as I am searching around to fix the problem on AMP indexation. I am still not confident how this amp stuff would work as I am now facing my site index both version desktop and amp page.
We ran loads of speed tests with AMP installed on WP sites and there were no speed gains whatsoever, so dumped it…yes G is now reporting 404 errors about 3 months later…go figure why it’s taken so long.
I’m not sure G actually has the human power to deliver to its previous standard – results on competitive fields are very poor unless an authority site happens to have a good article…!
Hi Richard, I am not sure how you tested your AMP page speed but the standard speed testing tools such as GT Metrics cannot test the true speed of AMP since Google serves AMP pages that are clicked through their SERPS via their cache. You can find an interesting article about it here: https://www.ampproject.org/latest/blog/measuring-amp-performance/
When testing it correctly I found that my site speed dropped from 3.2s (GT Metrix) to 1.1s (GT Metrix with Google Cache URL)
AMP end up hurting our company’s website. Maybe Google is selfish…thanks for the deactivation guide.
I’m pleased to find this case study as it validates problems I have been having with one of my sites.
After putting a lot of effort into my pages and server to reduce load times till they were very fast indeed, I implemented AMP using the AMPforWP plugin.
Since then continuous improvements to the AMP and organic layouts have been needed, an increased amount of content per page required, subtle AMP validation issues to be understood and then conquered.
The reward has been a decline in rankings and lead conversions for every keyword where an AMP page has been indexed in Google. Specifically it appears that AMP pages rank poorly in the Local 3-Pack; this has been very difficult for my service-area client who dispatches emergency vehicles in a 30-mile radius from his garage – a continuous erosion of incoming calls!
I appreciate your honesty regarding Google’s latest fad, and, for the deactivation options.
So glad it was helpful Dennis! We try to be as transparent as possible.
I have a similar case study, After 9/24 algorithm update, I lost 30 percent of my blog traffic, mostly because more trusted sites, and gov site ranked higher than me, SO I decided to remove AMP, as I wanted to target featured snippet more than ranking first, and the AMP makes me lose a lot of the features we have on the page (design UX, UI).
After removing AMP, and making sure I don’t have issues with mobile speed on my blog post, after a month. now I got 40% more traffic from mobile. and posts are performing better, with new featured snippet gained :)
AMP is not always right for you! Case closed!
I tried following both of these steps and, as recommended, I checked to see if my pages were redirecting. They aren’t. I went to the plugin and its registering my views as hits but that’s it. Any advice?
Hey Elissa!
Sorry to hear the above steps aren’t working for you. Due to the fact that every site is different, and perhaps you have a conflict with another plugin, we would recommend reaching out to your hosting provider for help. They might be able to see why your redirects aren’t happening.
What tool are you using on the printscreen of your site ranking?
Hi Marcos, that tracking tool called Accuranker https://kinsta.com/blog/best-seo-plugins-for-wordpress/#accuranker
Hi, thanks for this article guide. This is what I’m looking for to disable AMP on my blog. I’m planning to use Option 2 – Disable and Add Redirects.
I’m using AMP url format like this; mydomain.com/amp/url-post. Should I use the same regex format to redirect my amp page?
Thank you!
Hey, Thanks for the amazing guide, But still I am confused!
because the way 1 of “Real-Time Find and Replace” is not working for me. As I do that steps by installing a plugin and then follow other steps. My website is not opening!
Then I leave the Way 1.
Now I am following Way 2 by redirecting and deleting AMP.
Is that okay and make sense?
I already faced losses from AMP. Search Console is showing the following errors:
1) Referenced AMP URL is not an AMP
2) CSS syntax error in tag ‘style amp-custom’.
_______________________________________________________
Thanks for your help in advance!
Regards
Talha
Just stumbled upon this article for removing AMP, and it looks pretty easy to follow.
I’m fed up of AMP and it’s perpetual error messages, so I’ll be removing it in the next few days.
One point here though – if Google really really wanted to improve site-speed by taking coding back into the 1960s and turning everything into sub-standard WAP sites, why don’t they just disable all of the bloated ads?
Even news-heavy websites would run perfectly without ads – oh, hang on – Google would lose money, so GoogleWap is purely for THEIR benefit!
Please help me. My amp pages is structured like this
https://www.site.com/amp/article-one
I would like to know what source url should I use.
Thank you.
Hi Brian, I am currently testing AMP too, to be honest I don’t have enough traffic to really test the impact on bottom end sign ups and leads, since my site is fairly new in a very competitive niche. So please keep this in mind when I say that I believe that AMP has got a bad name due to the lack of good WordPress Plugins that are trying to make AMP available at 1 click of a button or offering very limited and basic alternate sites.
Understanding the difference between AMP code and standard HTML code will quickly tell you that it is not possible for these plugins to truly convert HTML to amp by cleaning it up. I have tested all the AMP plugins on WordPress and I, as many of the people here have had tormenting times with errors. In the case of the Plugins that create an alternate site altogether, the layouts are really crap.
A couple of weeks ago I faced a decision. Move away from AMP completely or give it a proper try. I decided on the latter and went for a single AMP only site. I bought a theme that really supports AMP well and runs on the official AMP plugin – re-developed some parts such as the menu and star rating and some other custom ones and am now running an error free site that hasn’t lost much of it’s look and feel (apart from AJAX stuff) and loads up at 1.1s as opposed (when served through Google cache) to an already fast site that run on 3.2s – one can see some of the examples on the AMP site to see that it is possible to have a nice and well functioning site based entirely on AMP. If you want to test the true speed of AMP when served of Google Cache (which is done automatically by them), you can read more about it here: https://www.ampproject.org/latest/blog/measuring-amp-performance/
I launched this site last Thursday so I cannot really come here and tell you whether it is good or bad. I have seen a huge drop in ranking especially on mobile because my Keywords were ranking on the separate AMP pages and those have now moved to the original (canonical) url.
I am confident that with some patience, this will work out long term since I believe that in the near future Google will prioritize AMP more and more and at the moment, most people are simply facing the same issues that everyone faced in the dotM era. Today single sites that support both mobile and desktop have overcome those problems and I believe that the same will happen with AMP.
Anyways, I will stop blabbering, I would like to hear whether you agree with me or not. And I would also like to hear if you believe that the HUGE in rankings drop I am currently facing is temporary or whether you believe that it will not improve again.
Thanks so much for this, my theme broke support for AMP. Using the redirection in .htaccess.
Hey Brian, This was super helpful – thanks!
One question: is it okay to delete the *Real Time Find And Replace* plugin now that all of my AMP addresses are redirecting correctly?
Hi,
I was using amp with newspaper theme. This created pages with /?amp/ rather than /amp/ in my amp versions of posts. I am trying to use your redirection code in my htaccess file but it works only for /amp/ and not /?amp. I am stuck
Can you help me?
Did you use a pre-made AMP theme that looked different than the desktop theme or did you team design a custom one? We created a native AMP WP theme (which means both the desktop and mobile experiences are the same AMP theme) and have seen a 61% increase in organic traffic compared to last year.
Hey Joseph!
Yes, we customized our theme quite a bit. But that was a few years ago now. Probably time to give it another shot. 😉 A lot has changed with AMP now, even in terms of how Google shows your URL in SERPs, etc.
I saw reduced conversion rates on my AMP pages compared to responsive mobile pages. The user experience was largely the same on both pages, just a faster load on the AMP pages with so many less scripts running in the background. Doesn’t seem to make sense that virtually the same page layout, when loaded faster, would convert at a lower rate. Is there just something wrong with AMP?
I have done this, but noticed the AMP version is not just /amp but /?amp which was put in place by the theme I am using (Newspaper).
I have redirected as indicated but when I test the urls with /?amp it does redirect to the normal version but URL stays the same.
It’s from 2017?! I wish I’ve seen that post earlier! My site was on 1st page of Google SERP then I added AMP with AMPFORWP which makes beautiful AMP pages but my site completely DISAPPEARED 😣 FROM the Google SERP! Not even on 2nd page nor on 6th page, it just vanished! We’re in Nov 2019, how come Google didn’t improve since then?
Can you elaborate on why there was a drop in conversion? Was functionality lost because of restricted JS?
Option 1 does not seem to work as described for WordPress V5.3.2 with Divi V4.3.3 and AMPforWP V1.0.29. Can anyone offer a reason why?
AMP resulted in lost of conversion for me also and I took it down in 2018.
People were not taking paid services due to lack of appealing colors and other eye catching features.
Thanks for the article, I was again thinking to put AMP back but I won’t now.
I had an SEO who told me “I needed AMP to rank”…what a joke. It absolutely ruined my site. I am starting to think that self proclaimed SEO guys who charge thousands a month are just snake oil salesman that have been doing it so long they believe their own BS. I fired that guy and have been doing my own “SEO” which basically consist of me making my site faster, organizing my content better and keeping track of the trends in traffic etc. It is doing so much better than it ever has when an “SEO expert” was “working” on it. I cannot tell you how many crazy links to my site I found when I started monitoring my own stuff. I paid this guy thousands of dollars so he could pay someone in Asia 5 bucks to spam my URL on a bunch of garbage website. These “SEO” people are lower than trash scammers. So even though AMP destroyed my site, it opened my eyes to what was happening to me and in the end saved me thousands.
Thanks so much for this! We had tested AMP on our site because all the SEO journals were saying to use it. But the thing is, we’re a web design company and we build sites that are already fast, responsive, and mobile-friendly. So it made no sense to have AMP pages, which are a much lower quality experience and don’t include any of our branding. The AMP pages have always received lower engagement and I knew I wanted to ditch AMP, but I didn’t feel confident setting up a redirect catchall until I read this. I’ve added an annotation to Google Analytics that I disabled AMP today just in case, but I think it will be a positive move, especially for our blog posts. :)
Hi Brian, thanks for great post.
How to redirect urls with the suffix /?amp to normal pages?
Hello, if you’re hosting with Kinsta, you can use a wildcard redirect rule to strip out the ?amp query string. If you’re hosted elsewhere, there may be some plugins that could help you redirect – there would be performance overhead though.
OMG, thank you! Getting rid of AMP was harder than getting rid of scabies. I had no idea how to fix it and the redirect option seemed to work great. Thank you!!
Hi Brian Jackson and Kinsta team,
Thank you for giving me some solid reasons to remove AMP from my website, which I really wanted to do so.
I’ve removed the AMP from my website successfully without any errors or problems!
Here’s a #tip for others wanting to remove AMP easily:
1. Open the AMP’s Plugin Settings.
2. Switch to the Supported Templates tab.
3. Now, uncheck all the “Content types enabled for AMP” options.
3. Hit the save button.
What will happen then?
Unchecking to all will set up a permanent 301 redirect of AMP-enabled pages to Non-AMP pages, and that happens without any errors.
What do next?
Just wait for some days when you find your Search Console shows 0 AMP pages indexed.
Then disable the AMP plugin from your WordPress website.
And that’s all!
I hope this helps you!
very cool! I have used the RankMath redirection feature and used these 2 REGEX expressions and disabled the AMP for WP app:
(.*)/amp
(.*)/?amp
https://domain.com/$1
it works very well, now I am going to watch the rankings dropping maybe!
AMP is garbage, that’s my big takeaway.