Home

Removing AMP Content

Removing AMP Pages from Google Search: A Comprehensive Guide

This document provides a detailed guide for web developers on how to remove Accelerated Mobile Pages (AMP) from Google Search. It includes explanations, illustrative examples, and code snippets to help you through the process.

Understanding the Terminology:

  • Canonical Page: The definitive version of a webpage. It can be either an AMP page or a non-AMP page.

  • AMP Page: A lightweight version of a webpage optimized for fast mobile loading.

  • Non-AMP Page: The standard version of a webpage, not specifically optimized for mobile speed.

Page Setup Scenarios:

  1. Canonical AMP: Only one version (the AMP page) exists, serving as the canonical version.

  2. Canonical Non-AMP: Two versions exist: an AMP page and a canonical non-AMP page.

Removal Options:

We will explore three primary methods for removing AMP content:

  1. Removing All Versions: Delete both the AMP and canonical non-AMP pages.

  2. Removing Only the AMP Page: Keep the canonical non-AMP page while removing its AMP counterpart.

  3. CMS-Based Removal: Leverage your Content Management System (CMS) to remove either all versions or only the AMP version.

Option 1: Removing All Versions of AMP Content

This method is the fastest way to remove your AMP content from Google Search. However, it might temporarily display error messages to users until Google fully processes the removal.

Step-by-Step Guide:

  1. Deletion: Delete both the AMP and non-AMP versions of the page from your server or CMS.

    # Example: Deleting files from a server using SSH
rm /path/to/your/amp-page.html
rm /path/to/your/non-amp-page.html

Note: A delay occurs between deleting your AMP page and Googlebot recognizing the removal. During this time, users might encounter error messages.

Option 2: Removing Only AMP Pages (Preserving Canonical Non-AMP Pages)

This method allows you to remove only the AMP version while keeping the canonical non-AMP page accessible.

Step-by-Step Guide:

  1. Remove AMP Link: Delete the rel="amphtml" link from the <head> section of your canonical non-AMP page.

    <!-- Before Removal -->
<link rel="amphtml" href="https://www.example.com/page.amp.html"> 

<!-- After Removal -->

  2. Server Configuration: Configure your server to return either a 301 Moved Permanently or 302 Found redirect for the removed AMP page, pointing to the canonical non-AMP page.

    # Example Nginx Configuration
location /page.amp.html {
  return 301 https://www.example.com/page.html;
}

  3. Additional Steps for Non-Google Platforms:

    • HTTP 404: To remove the AMP page from platforms other than Google, configure your server to return a 404 Not Found response for the removed AMP page. This prevents the Google AMP Cache from serving outdated content.

    • Cache Update: Update the Google AMP Cache to reflect the removal.

  4. Verification: Similar to Option 1, verify the removal through Google Search and the AMP status report in Google Search Console.

  5. Optional Permalink Preservation: To keep permalinks active, configure a 301 Redirect from the removed AMP page to the canonical non-AMP page.

Option 3: Removing AMP and Non-AMP Pages Using a CMS

Many CMS platforms offer integrated options for managing and removing AMP content.

Deleting a Single Page:

  1. Access your CMS interface and locate the page you want to delete.

  2. Use the CMS's "unpublish" or "delete" functionality to remove both the AMP and non-AMP versions.

  3. Consult your CMS provider's documentation for specific instructions (e.g., WordPress, Drupal, Squarespace).

Disabling AMP Site-Wide:

  1. Check your CMS provider's documentation or contact their support for instructions on disabling AMP.

  2. Warning: This action removes all AMP pages from your site.

  3. Ensure your CMS redirects users to the canonical non-AMP pages after AMP is disabled.

Conclusion

By following these detailed instructions, you can effectively remove your AMP pages from Google Search while minimizing disruption to your users. Always remember to test thoroughly after implementing any changes and consult your specific CMS documentation for tailored guidance.

PreviousValidating AMP ContentNextJavaScript

Last updated