DocumentationExperience Cloud KCS

AEM email templates do not show AMP support or generate valid AMP output

Last update: July 10, 2026

Adobe Experience Manager (AEM) email templates do not display AMP configuration options in Page Policies, or AMP output fails validation when rendering AMP pages. Update the page component to inherit from the AMP-enabled Core Components page and configure AMP mode in the template policy to restore AMP functionality and generate valid AMP output. To resolve the issue, update component inheritance and validate AMP output.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Adobe Experience Manager 6.5 Managed Services
  • AEM Core Components with AMP extension
  • Email templates that use editable templates and Page Policies

Issue/Symptoms

  • AMP configuration options do not appear in the Page Policy interface.
  • AMP Mode options remain unavailable for editable templates.
  • The page.amp.html selector loads, but AMP validation fails.
  • Generated AMP pages do not meet Google AMP validation requirements.

Cause

The project’s page component does not inherit from the AMP-enabled Core Components page. Although Adobe Experience Manager(AEM) includes the AMP extension by default, AEM does not enable AMP support automatically. When the sling:resourceSuperType property does not point to core/wcm/extensions/amp/components/page/v1/page, AEM does not display AMP Mode options in Page Policies and does not generate valid AMP HTML output. As a result, AMP configuration remains unavailable and AMP pages fail validation.

Resolution resolution

Follow these steps to resolve the issue

  1. Verify that the Core Components AMP extension exists in the repository installation path and confirm that Adobe Experience Manager (AEM) loads the extension correctly.
  2. Append.amp.html to a page URL and verify that AEM renders an AMP version of the page.
  3. Open the site’s page component in CRXDE and review the current sling:resourceSuperType value.
  4. Update the component’ssling:resourceSuperType property to the AMP-enabled Core Components page: core/wcm/extensions/amp/components/page/v1/page.
  5. Save the component configuration and confirm that the updated inheritance value persists.
  6. Open the template’s Page Policy and verify that the AMP Mode options appear.
  7. Select the required AMP Mode setting, save the policy, and confirm that AEM applies the configuration to pages that use the template.
  8. Validate the generated page.amp.html output by using Google’s AMP Validator and confirm that no validation errors remain.
recommendation-more-help
experience-cloud-kcs-help-kbarticles