![\"AMP](\"http:\/\/www.projectimmerse.com\/wp-content\/uploads\/2018\/07\/amp-for-wp-wordpress-plugin-1024x344.png\")
<\/p>\nI’m actually big fan of this wordpress plugin despite the bugs. The authors of this plugin I can tell have been working hard in fixing existing bugs and there are a lot of them, not an easy task. As a developer myself I know how wild code can get, so I give these guys mad respect and credit. <\/p>\n
<\/p>\n
Recently I was tasked with removing this plugin for a site. Disabling and removing the plugin was just the first step. The final step was to implement a redirect that would automatically redirect these amp urls to it’s respective non-amp url – leaving this as-is would be bad for SEO. And the client would not be happy to see their google rankings go down. So let’s take care of this. <\/p>\n
<\/p>\n
After playing around with some directives I was able to put together a working solution. Check it out below.<\/p>\n
\r\n# BEGIN WordPress\r\n<IfModule mod_rewrite.c>\r\nRewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\nRewriteCond %{REQUEST_FILENAME} !-f\r\nRewriteCond %{REQUEST_FILENAME} !-d\r\nRewriteRule . \/index.php [L]\r\n\r\n# Redirect AMP to non-AMP\r\nRewriteCond %{REQUEST_URI} (.+)\/amp(.*)$\r\nRewriteRule ^ %1\/ [R=301,L]\r\n\r\n<\/IfModule>\r\n<\/pre>\nWere basically saying that if a URL contains the amp string, redirect that URL to the original URL. I found that placing this directive near the top of the .htaccess file worked best. <\/p>\n","protected":false},"excerpt":{"rendered":"
I’m actually big fan of this wordpress plugin despite the bugs. The authors of this plugin I can tell have been working hard in fixing existing bugs and there are a lot of them, not an easy task. As a developer myself I know how wild code can get, so I give these guys mad … <\/p>\n