Universal Editor cannot open AEM Cloud page

[mpmuradov]

Hi here!

I tried to use Universal Editor with a page hosted in AEM Cloud (not locally). But UE cannot open the page.

Accorded to this doc https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev... I instrumented WKND page component. I put this

<script src="https://universal-editor-service.adobe.io/cors.js" async></script>
<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">

to `customheaderlibs.html` and I see in preview mode it was applied.

But UE doesn't recognize the page. I went here https://experience.adobe.com/#/@smartlingexchange/home opened `Experience Manager` -> `Universal Editor`, put link to the page https://author-p15353-e35406.adobeaemcloud.com/content/wknd/language-masters/en/test-editor.html?wcm... and launched the editor. It shows `Ooops` page

Did I missed something?

Any help is appreciated.

Thank you!

[SantoshSai]

Hi @mpmuradov,

Can you make sure:

• This is injected into the final rendered page.

• Open the page (test-editor.html) in the browser, do View Source, and verify both tags are visible there (not stripped by a proxy or CDN).

• This must be done only on the author instance – not on publish.

1. CORS Support

AEM must allow the Universal Editor service (https://universal-editor-service.adobe.io) through its CORS policy. You need to verify the AEM Cloud's

1. CORS configuration:

• In AEM Cloud, the dispatcher/CDN rules may block cors.js or not include the correct Access-Control-Allow-Origin headers.

• Check whether CORS is set up in the cdn.yaml or dispatcher config to allow this origin:

  - origin: https://universal-editor-service.adobe.io
    methods: [GET]
    headers: ["*"]

2. Document Type & Model Configuration

UE only works with structured content pages that are backed by a document type / content fragment model. If your page (test-editor.html) doesn’t use a model declared in UE config, it won't open.

• Has your page been registered in the UE via the appropriate JSON model or fragment model?

• Check if your page has structured content using a content model that is UE-enabled.

3. Universal Editor Configuration in Admin Console

Check if your AEM environment is correctly mapped in UE:

• Go to Adobe Admin Console > Product Configurations > Universal Editor.

• Verify that the mapping for your domain author-p15353-e35406.adobeaemcloud.com exists.

• You might need Adobe support to ensure your environment is UE-enabled.

If you're testing with the WKND site, try using this known working path:

https://author-<your-env>.adobeaemcloud.com/content/wknd/language-masters/en/magazine.html

That page is component-backed and already has structure.

Hope that helps!

[AmitVishwakarma]

Hi @mpmuradov ,

Follow all the steps below. These ensure your page is structurally editable, CORS-compliant, and correctly configured for Universal Editor.

1. Verify Page Is Structured and Supported by UE
Universal Editor only works with structured content, such as:
  - Editable templates using core components.
  - Pages bound to Content Fragment Models.
Check:
  - You are using a WKND or similar page with structure (like magazine.html).
  - Page includes data-aue-resource and data-aue-type attributes (UE markers).
      - Open browser dev tools => Inspect => Confirm those markers exist.

2. Validate Script and Meta Tag Placement
You said you added this to customheaderlibs.html:

<script src="https://universal-editor-service.adobe.io/cors.js" async></script>
<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">
​

Check:
  - Open the test-editor.html directly in browser (not in UE).
  - Right-click => View Page Source.
  - Ensure the script and meta tag are present in the rendered HTML (not stripped or blocked).

3. Configure CORS to Allow Universal Editor

You must allow https://universal-editor-service.adobe.io in CORS config (dispatcher or CDN).

Add to cdn.yaml or dispatcher.yaml:

cors:
  - origin: "https://universal-editor-service.adobe.io"
    methods: ["GET"]
    headers: ["*"]
    max-age: 86400

Check:

  - CORS config is deployed.

  - Use browser’s dev tools (Network tab) to confirm:

        - cors.js is not blocked.

        - Response header contains:

Access-Control-Allow-Origin: https://universal-editor-service.adobe.io

4. Enable and Map Environment in Universal Editor Admin Settings

Steps:

  - Go to Admin Console > Products > AEM/Universal Editor.

  - Check if author-p15353-e35406.adobeaemcloud.com is registered.

  - If not:

         - You may need Adobe support to map the environment or activate UE support for your org.

5. Try with Known Working Page
Before debugging your page, try with WKND's structured page:

https://author-p15353-e35406.adobeaemcloud.com/content/wknd/language-masters/en/magazine.html
​

If this works, the issue is likely:

  - Your test-editor.html page is not properly structured, or

  - The component or model mapping is missing.

6. UE Markers and Editable Configuration

Your page's components need to render data-aue-resource and data-aue-type. For that:

  - Components must extend from core components (or be UE-enabled manually).

  - Example marker:

<div data-aue-resource="urn:aemconnection:/content/wknd/language-masters/en/test-editor/jcr:content/root/responsivegrid/text"
     data-aue-type="text"
     data-aue-behavior="component">
</div>

Regards,
Amit

[arunpatidar]

Hi @mpmuradov 

The issue could be that UE is not able to communicate with AEM due to 3rd party cookie restriction.

Try in Chrome, normal window(not incognito) and check if error is gone or having other error. 

[muskaanchandwani]

Hello @mpmuradov 

Could you please try to remove the trailing slash from the instance URL in the meta tag?

<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">

to

<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com">

[Supriya_Savre]

Hi @mpmuradov,

Did the shared solution help you out? If yes, kindly consider marking the most suitable answer as ‘correct’.

If you’re still facing any challenges, please feel free to continue the conversation here. We’re happy to support further.