Free tools Windows power users keep installed
One-click scans. No signup required.
To disable Google AMP safely, first identify what is generating AMP, then turn it off at the appropriate scope, remove rel="amphtml" discovery links, and redirect every former AMP URL to its matching canonical page. Google Search Central specifies a 301 or 302 redirect when the non-AMP page remains available. Deleting a plugin without handling those URLs leaves indexed, cached, bookmarked, or linked AMP addresses unresolved.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What changes when you disable AMP?
AMP (Accelerated Mobile Pages) is an alternative rendering path for WordPress content. Depending on the implementation, it may create separate addresses such as /amp/, append a query parameter, or generate AMP output from the same permalink. A WordPress AMP installation can also alter templates, supported post types, and mobile-device behavior.
As an Amazon Associate I earn from qualifying purchases.
Turning off AMP stops new AMP output, but it does not instantly remove URLs that Google has already discovered. Search results, browser caches, XML sitemaps, external links, and users’ bookmarks can continue to request those addresses. A complete shutdown therefore has four parts:
- Inventory the AMP implementation and its URL patterns.
- Disable all or selected AMP generation.
- Remove AMP discovery markup from canonical pages.
- Redirect legacy AMP URLs to the corresponding non-AMP pages and monitor recrawling.
If the underlying article has been permanently deleted, a 404 (or an intentional 410 where your site uses it) is more appropriate than redirecting to an unrelated page. When the article still exists, preserve its path and slug in the redirect.
#1 Best Overall
1. Inventory the current AMP setup
Do not deactivate anything until you know which component serves AMP and which URLs it affects. Log in to WordPress and inspect the following.
Plugins and integrations
Open Plugins and note the AMP plugin, extensions, theme integrations, caching layers, and redirect tools. Some hosts or themes can add AMP support independently of the main plugin. Record the active version and export or screenshot its settings so you can diagnose an unexpected result or roll back.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesAMP settings and template mode
In the AMP settings screen, identify the template mode:
- Standard: AMP markup is the primary output, so disabling it can affect the main rendering path rather than only a secondary URL.
- Transitional: the site can serve both a regular and an AMP experience, often with shared theme behavior.
- Reader: AMP uses a separate, simplified template and commonly has distinct AMP URLs.
Also record which post types and templates are supported. Posts, pages, custom post types, archives, and taxonomies may not all behave the same way.
Mobile redirection and URL forms
Check whether the configuration redirects mobile visitors to AMP automatically. Test representative URLs while logged out on a desktop and a phone, and inspect the address bar after loading. Look for:
- A trailing
/amp/path segment. - An
?ampor similar query variant. - A separate host or subdomain.
- Automatic redirection based on the user agent.
Write down one AMP URL for every pattern and content type. You will use this inventory to build and test redirect mappings.
2. Choose between a full and selective shutdown
| Approach | Use it when | What changes | Main risk |
|---|---|---|---|
| Full-site removal | You no longer want AMP templates or URLs anywhere. | AMP generation is disabled globally, then all legacy patterns are redirected. | Missed URL variants can return errors or create redirect gaps. |
| Selective removal | Some post types, sections, or individual pages still need AMP. | AMP remains enabled for approved content and is disabled elsewhere. | Rules must distinguish retained and retired URLs precisely. |
| Content retirement | The original non-AMP content has also been permanently removed. | The old AMP URL returns a deliberate not-found response. | Redirecting unrelated content can confuse users and search engines. |
For a small site with one predictable pattern, a full shutdown is usually a one-time change. A large site with several templates, custom post types, or years of indexed AMP pages should use a staged rollout and monitor crawl reports between batches.
3. Disable AMP across the whole site
- Capture the existing configuration. Save the plugin settings, supported content types, template mode, mobile-redirection state, and any custom code. Keep a list of AMP URL examples.
- Disable the generator. In Plugins, deactivate the AMP plugin or the component that actually produces AMP. If the plugin has its own settings switch, turn that off first so the change is explicit.
- Uninstall only after checking dependencies. If the site no longer needs the plugin, uninstall it after deactivation. Removing files before recording settings makes troubleshooting harder. Check that your theme, cache, SEO, analytics, and structured-data integrations do not depend on its hooks.
- Clear generated and cached output. Purge the WordPress page cache, host or CDN cache, and any plugin-generated AMP files. Test in a private browser window so an old cached response does not look like active AMP.
- Confirm the regular page works. Load canonical URLs on desktop and mobile while logged out. They should return a normal 200 response and should not automatically switch to an AMP address.
Deactivation alone is not the migration. Continue with discovery-link removal and URL redirects before considering the work complete.
4. Disable AMP only on selected content
Per-post or per-page controls
The official AMP plugin supports disabling AMP on individual posts and pages. Edit the item, locate its AMP status control, disable AMP, save, and test both the canonical and former AMP addresses. Repeat for each item or use the plugin’s supported content-type settings when an entire section should be excluded.
The amp_is_enabled filter
When the plugin is network activated or when editorial rules need code-based control, the amp_is_enabled filter determines whether AMP functionality runs. Add a narrowly scoped callback in a child theme or a site-specific functionality plugin, not in a parent theme that will be overwritten during updates. For example:
add_filter( 'amp_is_enabled', function ( $enabled ) {
if ( is_page( array( 123, 456 ) ) ) {
return false;
}
return $enabled;
} );Replace the example page IDs with your own conditions and test every affected template. A coding error can disable AMP more broadly than intended, so keep a rollback copy and verify the result while logged out. The filter controls whether AMP runs; it does not by itself remove old URLs from Google’s index or create redirects.
5. Remove AMP discovery links from canonical pages
Open the source HTML of a regular, non-AMP page after disabling AMP. Search for an AMP discovery element such as:
<link rel="amphtml" href="https://example.com/article/amp/">Google Search Central’s explicit instruction is to remove the rel="amphtml" link from the canonical non-AMP page’s source code. The link tells crawlers that an AMP counterpart exists; leaving it in place can prolong discovery of a page you intended to retire.
Check rendered source rather than only the visual page. Cached HTML, theme headers, SEO integrations, or a server-side template may still emit the element after the plugin is disabled. Purge caches and recheck several content types. Do not remove the canonical URL element that points to the regular page itself; only the AMP discovery reference should disappear.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match6. Redirect every former AMP URL to its canonical counterpart
Build a complete mapping
Use the inventory from step one, server logs, Search Console examples, XML sitemaps, and a crawl of your own links to identify every legacy form. Map each AMP address to the same article, page, or custom post type without the AMP suffix or parameter. For example, an address ending in /news/game-update/amp/ should go to /news/game-update/, not to the home page.
Rank #4
Preserve the path, slug, language prefix, and meaningful query parameters needed by the canonical page. Avoid a blanket rule that sends every missing AMP URL to one generic destination; that creates poor user experiences and can be treated as a soft error.
Select the status code
- 301 Moved Permanently: use when AMP is retired and the canonical page is the lasting destination.
- 302 Found: Google documents 301 or 302 for removed AMP pages when the canonical non-AMP page remains live. A temporary 302 can be useful during a controlled transition, but change it to a permanent redirect when the decision is final.
- 404 Not Found: use when the AMP URL’s underlying content has genuinely been removed and there is no relevant replacement.
Do not chain redirects. The first request should reach the final canonical URL in one hop, and that URL should return 200 if the content remains published.
Choose where to implement the rules
| Control layer | Advantages | Checks before deployment |
|---|---|---|
| WordPress redirect plugin | Convenient interface, logging, and per-URL rules; useful when editors need to maintain mappings. | Confirm it runs before page caching where necessary, does not create loops, and can handle query-based AMP variants. |
| Web server or CDN | Redirects occur before WordPress loads, reducing overhead and avoiding plugin dependency. | Have the host or server administrator review syntax, rule order, cache behavior, and exclusions for retained AMP content. |
WordPress support guidance recognizes both a redirect plugin and hosting/server configuration as valid approaches. Whichever layer you choose, keep a written map of patterns and exceptions. If selective AMP remains enabled, make sure the redirect rule excludes the URLs you intentionally retain.
Recommended Free Tools
7. Test the migration before expanding it
Run these checks in a private session, while logged out, and from both desktop and mobile networks where possible:
- Request a representative old AMP URL for every pattern, post type, language, and directory.
- Confirm the response is a single 301 or 302 to the matching canonical URL, or a deliberate 404 for permanently deleted content.
- Follow the destination and verify it returns 200, loads the intended article, and does not redirect back to AMP.
- Inspect the canonical page source for the absence of
rel="amphtml". - Check that canonical, hreflang, structured-data, sitemap, and internal-link references now point to regular URLs.
- Test URLs with existing tracking parameters and encoded characters so a redirect does not drop required information or loop.
- Review server and redirect-plugin logs for repeated hits, chains, loops, and unexpected 404s.
For a large site, deploy a small batch first. Compare status codes and crawl errors, correct the mapping, then expand to additional directories or content types.
8. Monitor Google while it recrawls
Google does not remove AMP discoveries instantly. Google Search Central notes that discovery of deleted AMP pages is delayed, so old AMP addresses may remain in reports or produce temporary errors while Googlebot revisits them. There is no universal number of days to quote because recrawl timing varies by site and URL.
In Search Console:
- Inspect sample AMP URLs and confirm Google sees the intended redirect or not-found response.
- Watch indexing and page-experience reports for declining AMP impressions and new redirect or server errors.
- Review crawl statistics and your server logs for unexpected surges or URL patterns you missed.
- Keep the redirects in place; do not remove them merely because one report still lists an old AMP URL.
Continue publishing and maintaining the canonical pages normally. As Google recrawls, AMP URLs should disappear from active discovery in favor of the regular pages, while legitimate external links continue to reach the content through the redirect.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Common failure modes and fixes
The plugin is gone, but AMP URLs return 404
This means generation was disabled without a legacy-URL migration. Restore redirects from each old pattern to its matching canonical page. If the article itself no longer exists, leave a deliberate 404 rather than redirecting to an unrelated story.
AMP pages still appear in Google
Check that rel="amphtml" is absent from canonical source HTML, then verify the old URL returns the intended 301 or 302. Clear caches and allow time for Googlebot to recrawl. A remaining search result does not prove that AMP is still being generated.
Some sections redirect and others do not
Compare the failing URLs with your inventory. Custom post types, language folders, trailing-slash conventions, query variants, or a second AMP integration often use a different pattern. Add an explicit mapping and retest that content type.
A redirect loop appears
Inspect rule order and canonicalization. A server rule may send the AMP URL to a canonical address that WordPress or a cache layer transforms back into AMP. Temporarily disable overlapping rules, establish one owner for the redirect, purge caches, and retest one URL at a time.
Mobile visitors still see AMP
Check mobile-redirection settings, CDN edge rules, and cached responses. Test while logged out with a fresh cache. If only some devices are redirected, a user-agent rule may remain outside WordPress.
Quick Recap
Practical decision checklist
- Have you identified every AMP plugin, integration, mode, supported template, and mobile-redirection setting?
- Did you record the URL patterns before deactivation?
- Are you removing AMP globally or only from specified posts, pages, or content types?
- Is
rel="amphtml"gone from canonical source HTML? - Does every retained article’s former AMP URL reach its own canonical URL with one 301 or 302?
- Do permanently deleted articles return an intentional 404 instead of an irrelevant redirect?
- Have you tested logged-out desktop and mobile requests, caches, query variants, and custom post types?
- Are Search Console and server logs being monitored while Google recrawls?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
