Page can’t be unpublished in AEMaaCS
A page in Adobe Experience Manager as a Cloud Service (AEMaaCS) remains accessible even after being unpublished or deleted due to a vanity URL or alias pointing to another page. To fix this, check for vanity URL or alias configurations, verify the actual content path being served, and remove or update the conflicting settings in the repository.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites
Issue/Symptoms
In AEMaaCS, a page stays accessible through its public URL even after you unpublish or delete it. The page doesn’t appear in the repository or query results. Republishing a new page at the same path works temporarily, but unpublishing it again shows the old content. Logs indicate that requests are reaching AEM, but delivering ghost pages—content that should no longer exist.
The error log shows:
ERROR [ x.x.x.x [ 1741174619579] GET /example/page/ HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=test-aem/components/breadcrumb, superType=null, path=/content/another/example/page/jcr:content/root/breadcrumb
This means AEMaaCS is redirecting the request to another page due to a vanity URL or alias, and it can’t render the content correctly.
Resolution resolution
To resolve the issue where a page in AEMaaCS remains accessible after being unpublished:
- Add
?1=1to the end of the page URL, such as/example/page/?1=1, to bypass the dispatcher and identify the actual content path being served, such as/content/another/example/page. - Check the properties of
/content/another/example/pagefor a vanity URL or alias set to/example/page. - Remove or update the vanity URL or alias to stop the redirection.
- Republish the updated page and clear the dispatcher cache.
- Verify that
/example/pagenow returns a 404 error or the correct response.