Adobe Commerce integration
No native Adobe Commerce connector, here is what does work.
Create and update CMS pages and blocks in Adobe Commerce over REST, with inactive state as the review gate.
How it works
SearchHandled connects to Adobe Commerce (Magento) through the REST API with an OAuth 1.0a integration or an admin token, and writes content as CMS pages and CMS blocks via the /V1/cmsPage and /V1/cmsBlock endpoints. That means guides, landing pages, and support content with titles, URL keys, content heaps, and meta fields, created directly in the store's own CMS system. Adobe Commerce has no native blog, and we do not pretend otherwise: third-party blog extensions each have their own APIs, and we handle those case by case.
There is no draft or scheduled state on CMS pages through the API; the only state is is_active. So our review gate uses what actually exists: content is created with is_active set to false, it is invisible to shoppers while your team reviews it in the admin, and approval flips it active. Content staging exists only on Commerce Enterprise, so we never claim scheduling we cannot deliver on your edition.
Best forMerchants on Adobe Commerce who want buying guides and support pages created as CMS content, with honest expectations about the platform's limits.
Setup, step by step
- In the Commerce admin, create an integration (System, then Integrations) with access to Content resources, or generate an admin token.
- Connect the store URL and credentials in SearchHandled.
- Run the connection check, which creates and removes an inactive test page to verify write access.
- Choose where content lands (CMS pages, blocks, or both), the store views it applies to, and your URL key conventions.
- Deliver a test page inactive, review it in the admin, and flip it active to confirm the full flow.
Best practices
Decide the page hierarchy before volume arrives
CMS pages live wherever their URL keys put them. Settle a convention such as guides/topic-name early, because reorganizing URL keys after pages are indexed costs you redirects.
Use blocks for reusable fragments, pages for destinations
CMS blocks slot into layouts and category pages; CMS pages are standalone URLs. We can deliver both, and using each for what it is keeps your content architecture sane.
Keep the review step in the admin
Since inactive is the only holding state, make reviewing inactive pages part of your team's routine. Preview them in the admin before flipping active; there is no separate draft preview system to lean on.
Tell us if you run a blog extension
If your store uses a third-party blog extension, its API is specific to that extension. We evaluate support case by case, and until then CMS pages are the reliable path.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
No native blog on the platform
Adobe Commerce simply has no built-in blog, and the third-party blog extensions that fill the gap each expose different APIs, so there is no single blog integration to build against.
How we handle itWe target CMS pages and blocks, which are native and stable, and we say so plainly rather than advertising blog support the platform does not have. Extension support is evaluated case by case.
developer.adobe.com
No draft or scheduled state via the API
CMS pages have only is_active; there is no draft state and no API scheduling, since content staging is exclusive to Commerce Enterprise.
How we handle itWe create every page inactive and flip it active on your approval, using the one holding state that exists, and we never claim scheduling on editions where it cannot be delivered.
developer.adobe.com
Questions teams ask
- Can SearchHandled run a blog on my Magento store?
Not natively, because the platform has no blog. We deliver guides and support content as CMS pages, which works well for evergreen content. If you run a blog extension, we can look at its specific API, but we will not promise it sight unseen.
- How does review work without a draft state?
Through the inactive flag, which is what the platform provides. Pages arrive with is_active false, invisible to shoppers, and your approval flips them live. It is a real gate, just a binary one.
- Can content be scheduled to go live at a set time?
Not through the standard API; scheduled content staging exists only on Commerce Enterprise. On other editions, we can time the activation call for you on our side, but we are explicit that this is us flipping the flag at a time, not platform-native scheduling.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Adobe Commerce matters moves it up the rollout.