Should you really redirect your old AMP URLs to the new ones?

Why does Google handle AMP redirections differently?

The reason is purely technical. Google maintains a centralized AMP cache that serves pages from its own servers, not from your domain. This system allows for almost real-time content refreshing.

Unlike classic pages where a lost URL can remain 404 for weeks in the index, the AMP cache updates within a few days . Google actively crawls these versions to ensure their freshness. This architecture completely changes the game regarding the criticality of redirections.

What does this change for migration management?

For a classic site migration, every 301 counts. A broken link can mean a loss of PageRank and a negative signal for the user. The redirections are documented, tested, verified URL by URL.

With AMP, this absolute rigor is no longer as vital. Google automatically detects new URLs through cache crawling. If your canonical page points to the new AMP version, the system quickly adjusts without a complete reliance on 301s.

Does this flexibility apply to all AMP contexts?

Not necessarily. Mueller refers to the general context where Google is the primary traffic driver to AMP pages . If your AMP URLs are shared directly on social networks or in newsletters, redirections become important again.

Similarly, if external sites have created backlinks to your old AMP URLs (rare but possible), not redirecting effectively leads to cutting those links permanently . Google's flexibility does not compensate for the loss of external SEO juice.

• The AMP cache refreshes in a few days , much faster than traditional indexing
• AMP redirections are less critical than for normal pages, but not optional in all cases
• Automatic detection of new URLs by Google mainly works through the canonical link and active cache crawling
• Backlinks and direct traffic to AMP still justify clean redirections
• This rule does not exempt you from a rigorous migration strategy if your AMP traffic is significant

Is this statement consistent with observed practices in the field?

Yes, largely. It's indeed observed that AMP URL changes propagate faster in the SERPs than changes to classic pages. Google has always prioritized the freshness of AMP content to justify the format.

But be careful not to generalize. [To be verified] On sites with a significant AMP volume (media, news), some practitioners report temporary traffic losses during migrations without redirections. Mueller's 'a few days' can stretch to 1-2 weeks depending on your site's crawl frequency.

What nuances should be considered regarding this position?

Mueller mentions a 'less critical' concern, not an absolute absence of criticality. Overlooking AMP redirections remains a risk . If your AMP traffic constitutes 30% of your organic visits, this risk can be costly in visibility during the transition.

Second nuance: this flexibility pertains to URLs served via Google’s cache (google.com\/amp\/... ). If you use AMP standalone or third-party CDNs, the classical redirection rules fully apply. The shortcut only works within Google’s cache ecosystem.

In what cases does this rule not apply at all?

First case: e-commerce sites with AMP product pages . If users have bookmarked or shared product URLs, not redirecting creates a catastrophic experience and leads to lost sales. The speed of the cache doesn’t change anything.

Second case: environments where AMP is indexed as the main version , not as an alternative. Some sites publish only in AMP (a rare but existing choice). Here, redirections have exactly the same criticality as for a classic site.

What should you do concretely during an AMP URL migration?

Even if redirections are 'less critical', set them up by default . The technical cost of a 301 mapping is minimal compared to the risk of traffic loss, even temporarily. Use your usual redirection file and treat AMP URLs like the others.

Next, check that your canonical tags point to the new URLs . This link is what allows Google to automatically detect changes in the AMP cache. Without the correct canonical, even redirections won’t suffice for a clean transition.

How to check if the AMP transition is going smoothly?

Use Search Console, AMP tab , to monitor indexing errors. If Google detects broken or not found AMP pages, you will see alerts appear within a few days. This is your main alarm signal.

Simultaneously, track your AMP traffic in Google Analytics (segment on pages \/amp\/ or URL parameter according to your structure). A sharp decline that does not resolve within 7-10 days signals a problem with redirections or canonical tags. At that point, manually audit the problematic URLs.

What mistakes should you absolutely avoid?

Never say "AMP is secondary; we’ll deal with it later". On some news or viral content sites, AMP accounts for 40 to 60% of organic mobile traffic . Neglecting these URLs amounts to undermining your visibility.

Another mistake: implementing temporary 302 redirects "for now". Always use permanent 301s . 302s do not pass PageRank and can create confusion in Google’s cache, thus negating the speed advantage Mueller mentions.

• Map all old AMP URLs to new ones with 301 redirects, even if Google detects them quickly
• Verify that each page contains a canonical link pointing to the updated AMP version
• Monitor Search Console (AMP section) for 2-3 weeks post-migration to detect errors
• Segment AMP traffic in Analytics to identify any volume anomalies
• Manually test a sample of old URLs to confirm that the 301s are working well
• Avoid 302 redirects or redirect chains that slow down detection by Google