Title: AMP Forced Redirection doesn’t work
Last modified: February 13, 2021

---

# AMP Forced Redirection doesn’t work

 *  Resolved [subitoweb](https://wordpress.org/support/users/subitoweb/)
 * (@subitoweb)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/amp-forced-redirection-doesnt-work/)
 * We need to get all mobile traffic in AMP version. We forced from the module, 
   clearly browsing from my devices it works, but from what analytics detects no.
   AMP traffic reported by analytics (I’ve also used other analytics scripts) report
   mobile AMP traffic only up to 15% of and 75% mobile.
    So the plugin doesn’t fully
   deliver traffic in AMP? How can we solve this. Thank you
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Famp-forced-redirection-doesnt-work%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/)
 * (@westonruter)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/amp-forced-redirection-doesnt-work/#post-14048798)
 * I believe this is the same issue that was previously reported: [https://wordpress.org/support/topic/google-analytics-amp-direct-view/](https://wordpress.org/support/topic/google-analytics-amp-direct-view/)
 * The issue is that client-side redirection drops the original `Referer` header.
 * One solution is to switch from client-side redirection (the default) to server
   server-side redirection. This can be done with the following mini plugin: [https://gist.github.com/westonruter/e5032d805625f0f743237708c43d3783](https://gist.github.com/westonruter/e5032d805625f0f743237708c43d3783)
 * Client-side redirection is the default because it is the most compatible across
   WP installs. If you have a page caching plugin you may need to adjust it when
   using server-side redirection.
 * I have opened a pull request ([https://github.com/ampproject/amp-wp/pull/5776](https://github.com/ampproject/amp-wp/pull/5776))
   to start to explore how we might pass along the `Referer` even when using server-
   side redirection, but it hasn’t been completed yet.
 *  Plugin Support [Milind More](https://wordpress.org/support/users/milindmore22/)
 * (@milindmore22)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/amp-forced-redirection-doesnt-work/#post-14116417)
 * As we didn’t receive a response I’ll mark this as resolved. Feel free to open
   a [new support topic](https://wordpress.org/support/plugin/amp/#new-post) if 
   you require any further assistance.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘AMP Forced Redirection doesn’t work’ is closed to new replies.

 * ![](https://ps.w.org/amp/assets/icon.svg?rev=2527602)
 * [AMP](https://wordpress.org/plugins/amp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/amp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/amp/)
 * [Active Topics](https://wordpress.org/support/plugin/amp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/amp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/amp/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [Milind More](https://wordpress.org/support/users/milindmore22/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/amp-forced-redirection-doesnt-work/#post-14116417)
 * Status: resolved