302 redirect in AMP 1.0 from old /amp/ pages to the new ones /?amp

The reason is that if you switch back to Classic mode then the URL would again be /amp/. In any case, the use of 302 redirect shouldn’t be a problem for SEO because the canonical URL does not change. The canonical URL has the amphtml link that the AMP consumers would be looking for primarily.

Hello Weston,
I think there should be an option to return 301. We noticed a drop from several referrers eg- pinterest not sending any traffic since we implemented paired mode couple of days ago. Is there a way to change this ?

I’m not familiar with there being any difference in the Referer between 301 and 302 redirects. Have you found a 301 redirect preserves Referer where 302 does not?

Hi thanks, for the reply. I meant that it appears that referrer simply “does not like” 302 and it does not send traffic. Actually traffic from google search to amp pages has dropped as well. Also, if there were any links to amp pages 301 would be better. I did find the line in class-amp-theme-support and changed 302 to 301. Should work until another update I guess. Let me know what you think.

@fredmr So you are seeing that the change from 302 to 301 is fixing the issue? Would you open a PR to the plugin with that fix?

If you do, please branch your pull request off of the 1.0 branch.

I would like to give it one more day just to be sure. Never opened pull requests before. Will have a look tomorrow.

It could also just be that the AMP consumers have been switching over to the new amphtml link on the canonical URLs, so it may not actually be that the change in redirect is causing the desired change.

I agree, just I think 301 will push AMP consumers to make this switch faster.
Today – 0 traffic to new or old amp links, substantial drop, need more time for crawl and re-indexing. This plugin is fine if one goes for native mode, paired in my experience is a problem because of new permalink structure.

We could also skip redirecting entirely because there really isn’t a need to do so for the paired mode, since the paired URLs aren’t canonical anyway.

Also, I don’t understand why they would be a drop in traffic to the AMP pages.

@fredmr Please share the URL to an example AMP URL on your site.

Here is a sample post:
https://www.lushome.com/warm-metal-accents-bringing-luxurious-glow-modern-kitchen-design/196345?amp

Analytics graph shows about 2500-3000 visits to amp pages before plugin, and today – only around 200. Would appreciate any insights.

Where are you getting this analytics data from? I don’t see any analytics in the page itself.

Thanks for the response @westonruter

All works perfect ??

google analytics, I can attach the graph, where can I post the jpg ?

@fredmr So it’s Google Analytics _via_ Google Tag Manager. Is that right?

On https://www.lushome.com/warm-metal-accents-bringing-luxurious-glow-modern-kitchen-design/196345 I see:

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-P9CDW4V"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

But I’m not seeing any script-based alternative for this.

On the AMP version I’m not seeing any reference to GTM.

Have you configured analytics for AMP and non-AMP alike?