Should you really redirect your outdated AMP pages?

Why does Google believe that an AMP redirect is unnecessary?

The logic is based on the already established canonical relationship between the AMP page and its standard version. When you set up AMP correctly, each AMP page contains a <link rel="canonical"> tag that points to the original mobile or desktop version.

This directive tells Google that the AMP page is just a technical variant, not a distinct page with its unique content. Therefore, removing AMP without a redirect amounts to taking away an alternative version when the main equivalent still exists.

What’s the difference between technical disappearance and user experience?

From a crawl and indexing perspective, Google understands the removal of an AMP page thanks to the pre-existing canonical signal. Search engines naturally transfer signals to the standard version without significant ranking loss.

But users, on the other hand, do not read canonical tags. If someone has bookmarked an AMP URL, or if an external link still points to it, a sudden removal generates a frustrating 404 error. This is where the redirect becomes relevant: it protects the human experience, not the indexing.

In what context does this statement truly apply?

Mueller speaks of a specific scenario: the complete deactivation of AMP architecture on a site transitioning to a traditional mobile-first approach or optimized Core Web Vitals. Many sites have abandoned AMP after Google removed the lightning badge from search results.

The recommendation aims to simplify this migration by avoiding thousands of unnecessary server-side redirects. But it assumes that your site has never attracted direct traffic or specific backlinks to AMP URLs, which is rarely the case in practice.

• The canonical tag AMP → standard enables Google to understand the removal without a 301 redirect
• Redirects remain recommended if user traffic persists on AMP URLs
• External backlinks to AMP pages justify a redirect to preserve PageRank
• Massive 404 errors undermine user trust even if Google technically tolerates them
• This approach mainly applies to sites with a purely technical AMP implementation, without promoting AMP URLs

Is this statement consistent with field observations?

Yes and no. In terms of pure indexing, I confirm that Google manages AMP removal without redirects correctly. Tests show that canonical pages maintain their positions and do not suffer a drastic drop.

However, from a analytics and user behavior standpoint, the reality is more nuanced. [To be verified] Google has never published data on the percentage of direct traffic to AMP URLs once they are indexed. My observations indicate that 5% to 15% of mobile traffic can still land on the AMP URL through bookmarks, social links, or third-party caches.

What risks does this minimalist approach entail?

Removing AMP without a redirect creates an invisible technical debt. Backlinks pointing to your old AMP pages lose their link equity if you do not redirect. Google can theoretically transfer these signals through the canonical tag, but in practice, a 301 redirect remains more reliable.

Monitoring tools like Search Console will show increasing 404 errors for months or even years as caches invalidate. Some scrapers and aggregators retain AMP URLs for a long time. Ignoring these errors clutters your reports and masks real problems.

In what cases does this rule absolutely not apply?

If you have actively promoted your AMP URLs (newsletters, paid campaigns, social shares), redirects are mandatory. The canonical signal does not protect the experience of visitors who arrive directly.

The same goes if your AMP pages have gained quality backlinks independent of the standard version. A news article specifically pointing to your AMP loses its SEO impact without a redirect.

What should you do concretely before removing AMP?

Start by auditing actual traffic to your AMP URLs in Google Analytics or your measurement tool. Filter sessions coming directly from the AMP URL (not via the canonical version). If this traffic exceeds 2-3%, the redirect is not optional.

Next, check your incoming backlinks using Ahrefs, Majestic, or Search Console. Export all links pointing to URLs containing /amp/, .amp, or ?amp=1 based on your implementation. If you have more than 50 backlinks from distinct domains, prepare a redirect plan.

How to implement a clean AMP migration?

The safest method: set up 301 redirects at the server level (Apache .htaccess or Nginx) that redirect each AMP URL to its standard equivalent. This operation is scriptable if your URL structure is consistent.

Simultaneously, remove the <link rel="amphtml"> tags from your standard pages and the <html ⚡> tags from your AMP templates. Keep the redirects active for at least 12 months to allow all caches (Google, Cloudflare, third-party CDN) to fully recycle.

What mistakes should be avoided at all costs?

Never remove AMP files from the server without checking access logs. Some bots and third-party services continue to request these URLs for years. A sudden removal generates spikes in server errors that can affect your crawl budget.

Also, avoid redirecting all your AMP URLs to the homepage for convenience. Google interprets these chained redirects as soft-404s. Each redirect should point to the exact thematic equivalent, not to a generic page.

• Analyze direct traffic to AMP URLs in Analytics (threshold: > 2%)
• Audit backlinks specifically pointing to AMP pages
• Set up individual 301 redirects, not a global redirect to the homepage
• Remove amphtml tags from standard pages before deletion
• Keep redirects active for at least 12 months
• Monitor 404 errors in Search Console after migration