Back to Community
Home / Community / Plugin → Amp

Resolving Common AMP and Elementor Compatibility Issues

14 threads Sep 10, 2025 Plugin → Amp

Content

Many WordPress users who rely on the Elementor page builder encounter problems when implementing the AMP plugin. This article explains the root cause of these conflicts and outlines the most common solutions to try.

The Core Problem: JavaScript and AMP Standards

The fundamental issue is that Elementor heavily depends on custom JavaScript to render its layouts and interactive features. The AMP framework, by its very nature, imposes strict limitations on the use of custom JavaScript to ensure fast loading times on mobile devices. When the AMP plugin activates, it strips out Elementor's JavaScript, which often results in:

  • Broken or misaligned layouts
  • Greyed-out or incorrectly styled pages
  • Non-functional interactive elements (e.g., hamburger menus, sliders, forms)
  • A mobile view that appears "jumbled" or incomplete

It's important to understand that this is a compatibility issue between the two technologies, not necessarily a bug in either plugin. The official 'AMP' team has stated that Elementor is not fully AMP compatible at this time.

Common Solutions to Try

1. Use a Transitional or Reader Mode Template

The AMP plugin offers different modes. If you are using Standard mode, try switching to Transitional or Reader mode. These modes serve the AMP version of a post on a separate URL (e.g., yoursite.com/post/?amp=1) or use a simplified, AMP-compatible template for your content. This can sometimes isolate the incompatibility, allowing your main site to function normally with Elementor while providing a valid AMP page for search engines.

2. Investigate the AMP Enhancer Plugin

A frequently suggested third-party solution is the AMP Enhancer plugin. This plugin is designed to add a layer of compatibility for popular page builders and plugins, including Elementor. It works by helping to convert some non-AMP components into AMP-friendly equivalents. User reports indicate it can resolve some, but not all, layout and functionality issues.

3. Check for Conflicting Plugins

As seen in the support threads, issues are often compounded by other plugins. Common conflicts arise with:

  • Schema plugins (e.g., All In One Schema Rich Snippets)
  • Marketing plugins (e.g., HubSpot)
  • Google Analytics plugins
  • Table plugins (e.g., Table Press)

Perform basic troubleshooting by temporarily disabling other plugins to see if the AMP page renders correctly. If it does, reactivate them one by one to identify the specific conflict.

4. Monitor Official Development

Since full compatibility relies on changes from both the 'AMP' and Elementor teams, it is advisable to follow the official GitHub issue tracking this problem. This is the best way to get notified when a native solution is developed and released.

When All Else Fails: Alternative Approaches

If the above solutions do not yield acceptable results for your website, you have a couple of other options:

  • Use a Different AMP-Compatible Page Builder: For new pages or posts that require AMP, consider using the native Gutenberg editor or another builder known for better AMP compatibility.
  • Selective AMP Disabling: You may choose to disable AMP entirely or disable it on specific pages that rely heavily on Elementor's functionality to preserve your design and user experience.

Ultimately, resolving AMP and Elementor issues requires a strategic approach, balancing the desire for AMP's speed benefits with the need for a fully functional website. The solutions outlined here provide a starting point for finding that balance.

Related Support Threads Support