Removing AMP is not just about disabling a feature. First decide whether to keep canonical non-AMP pages, then address old URLs, page markup, and search results. To keep the corresponding regular web pages, Google’s guidance calls for removing rel=”amphtml” from the canonical pages and setting up 301 or 302 redirects from AMP URLs to those pages. Do not simply empty the AMP files. After making these changes, check that the old URLs redirect correctly and whether search results still offer AMP versions.
Are you removing a version or deleting the entire article?
AMP is not necessarily an additional version. Google’s guidance distinguishes between two configurations: an AMP-only page that is itself canonical, or an AMP page paired with a canonical non-AMP page. Before proceeding, identify which configuration your site uses. Do not assume that a regular web page will remain available after you delete AMP.
- Keep the article and remove only AMP: If a corresponding canonical non-AMP page already exists, update the page markup and set up redirects.
- Remove the article as well: If both AMP and non-AMP versions exist, delete both. Google’s guidance also describes a method for quickly removing all versions, but only for situations requiring prompt removal, and warns that users may see error messages.
Old AMP URLs need a destination, not just a blank page
When keeping only the non-AMP version, check the following in order:
- Has rel=”amphtml” been removed from the source code of the canonical non-AMP page?
- Does the old AMP URL use a 301 or 302 redirect to the corresponding canonical non-AMP page?
- If you want permalinks to remain functional, have you used 301 redirects as instructed?
Emptying the files is no substitute for these changes. Google’s guidance states that blank documents without markup are considered invalid, and search results may continue to show the oldest valid version that is still available. If you also want to prevent non-Google platforms from accessing AMP, the guidance separately describes removing the pages and returning 404 responses. This is a different goal from keeping old links functional, so clarify what you need first.
If you use a CMS, check which pages will be removed and whether redirects are supported
A CMS (content management system) generally publishes both AMP and non-AMP pages. Unpublishing or deleting an individual article may remove both versions of that article, while disabling AMP removes AMP pages across the entire site. The two actions affect different sets of pages.
For sites hosted on a CMS domain, Google’s guidance states that the CMS can redirect users to canonical non-AMP pages after AMP is disabled. This does not mean every site will redirect automatically. Check that the redirects work, and contact your provider for help if there are problems.
After removal, check URLs and search results separately
Having redirects in place does not mean search results will update immediately. Googlebot may take time to discover that pages have been deleted, and users may encounter errors in the meantime. In addition to checking the responses from old URLs and the pages they lead to, search for the original content to confirm whether AMP results have been removed. The first check shows what visitors see when they open an old URL; the second shows whether search results reflect the changes.
Removing AMP: perspectives from across the web
What else should you check after deleting a WordPress AMP plugin?
A 2022 WordPress tutorial warns that old URLs may return 404 errors after you deactivate and delete an AMP plugin, and recommends setting up 301 redirects for URLs containing “/amp.” This advice concerns plugin removal; in practice, you should still verify the AMP URL format your site uses and whether corresponding non-AMP pages exist as redirect destinations.
How can you monitor indexing changes after removing a large number of AMP pages?
Search for the original content to see whether AMP versions still appear in the results. Google's guidance also recommends watching for a decline in the number of indexed AMP pages in the Search Console AMP status report to track overall changes across large numbers of pages. However, the available material does not confirm whether that report is still accessible, so the current interface cannot be assumed to offer the same functionality.
When an entire piece of content needs to be removed quickly, which URLs should the removal requests cover?
The removal requests should cover the URLs of both the AMP and non-AMP versions. Google's guidance gives these steps: delete both versions, submit removal requests for their URLs, and check the status of the requests. This approach applies only when all versions genuinely need to be removed as quickly as possible. Search systems may take time to detect the deletion, and users may see error messages in the meantime. The available material also does not confirm how the listed tools should be used today.
References
- 如何從 Google 搜尋中移除您的 AMP 網頁 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can you monitor indexing changes after removing a large number of AMP pages?; When an entire piece of content needs to be removed quickly, which URLs should the removal requests cover?
- AMP是什麼?AMP和SEO的關聯?Google AMP網頁優缺點解析welly.tw · 2022-01-24T02:01:01.579Z — Discusses: What else should you check after deleting a WordPress AMP plugin?
