DocumentationExperience Cloud KCS

Published pages return 404 errors in Adobe Experience Manager

Last update: October 16, 2026

In Adobe Experience Manager (AEM), pages fail to publish from the Author environment to the Publish environment. As a result, published content isn’t available on the public site and returns 404 Not Found errors. To fix this issue, configure and verify the required replication agent between the Author and Publish environments.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

  • Pages fail to publish from the Author environment to the Publish environment.
  • Published pages aren’t available on the public website.
  • Accessing published pages returns a 404 Not Found error.
  • Duplicate or broken pages in the content tree result in HTTP 500 server errors.

Resolution resolution

  1. Log in to your AEM Author instance.

  2. Navigate to Tools > Deployment > Replication > Agents on Author.

  3. Check whether a replication agent is configured for the target Publish environment.

  4. If no replication agent exists or you do not have access to create or configure one:

    • For on-premises or AMS deployments: Contact your AEM administrator or Managed Services provider and request the creation and configuration of a replication agent for the production Publish environment. Provide the necessary details for the target Publish instance.
    • For AEM as a Cloud Service (AEMaaCS): Replication agents are managed by Adobe and can’t be configured by customers. If publishing issues occur, contact Adobe Support for assistance.

  5. After a replication agent is available and configured, locate the page that you want to publish in AEM Author.

  6. Select the page and use Quick Publish or the Manage Publication workflow to publish it to the Publish environment.

  7. Verify that the page is accessible on the intended public URL.

  8. If the page is published but isn’t accessible at the intended public URL, review your dispatcher rewrite rules and confirm that the content path matches the routing configuration. If necessary, request a dispatcher configuration update from your administrator or provider.

  9. Remove any duplicate or broken pages from the content tree to prevent server errors and confusion.

recommendation-more-help
experience-cloud-kcs-help-kbarticles