Overview
Writes a content fix straight back into the system that publishes it, so shipping a change is not an export, an edit and an import.
AI crawler tracking on a Adobe Experience Manager site
Counting AI crawler visits needs the server or CDN logs for the domain, which Adobe Experience Manager does not hand out and no vendor can read from a content API. That is a property of where the site is served, not of the CMS, so put the domain behind Cloudflare and the visits are counted while publishing keeps working here.
Set up CloudflareHow it works
Before you start: AEM as a Cloud Service with the OpenAPI-based APIs enabled on the environment. On-premise AEM is not covered.
- 1In Adobe Developer Console, create a project, add the AEM Sites (Content Fragments) API with OAuth Server-to-Server, and note the client id and client secret.
- 2In the Admin Console, put the technical account the project created into a product profile with rights on the author environment.
- 3In SKYA, choose Adobe Experience Manager under Connect your site: paste the author URL, the client id and secret, the Content Fragment model path and the parent folder.
- 4Publish to site creates an unpublished fragment; open the Content Fragments console, review it, and publish.
Where to find what Adobe Experience Manager asks you for
- OAuth Server-to-Server credential
- developer.adobe.com/console, your project, Credentials. Client id and client secret are on that page.
- Permission it needs: aem.fragments.management and aem.folders, which the console adds when the AEM API is selected.
- Model path and parent folder
- Tools, General, Content Fragment Models gives the model path (for example /conf/site/settings/dam/cfm/models/article); the parent folder is where the fragments live under /content/dam.
Key benefits
- Create unpublished Content Fragments in AEM as a Cloud Service from the action plan.
- Every piece lands as a draft in your own editor, so nothing goes live from SKYA and nothing needs pasting.
- The draft keeps its title, slug, excerpt and the reason it was written, so review takes a minute, not a rebuild.
You might also need
Page titles, meta descriptions and Open Graph written to your Webflow pages after you approve them, and drafts into your blog collection. For a store, products imported into AI Shopping, and a longer product description you approve saved as a staged change. SKYA never publishes your site.
Read your Contentful entries beside your AI visibility, with writing to follow.
Draft into a Sanity dataset from the action plan, with a write token you create in Manage.
Draft items into a Framer CMS collection through the Server API key from Site Settings.
See what AI says about you
Start free for 7 days. No card, and every number on the first screen says what it is built on.