Migrating to Adobe Experience Manager: 4 Site Structure Considerations via @TaylorDanRW
0Reported today on Search Engine Journal
For the full article visit: http://tracking.feedpress.it/link/13962/13295234
Migrating to Adobe Experience Manager: 4 Site Structure Considerations
In 2019, Adobe Experience Manager (AEM) saw a substantial increase in platform uptake, with BuiltWith now estimating there are around 18,700 websites using the platform globally.
One can assume this number is only set to increase, given Adobe's purchase of the Magento platform.
More recently, Adobe also moved the Experience Manager to be a cloud-native SaaS application – making the CMS "more scalable and secure for content management across organizations".
With uptake increasing and typical AEM implementations ranging from a few hundred thousand dollars for the license to $2 million-plus for the complete implementation, transitioning to this platform naturally inherits a lot of attention from C-suite and the wider business.
This often comes with the expectation that such a substantial investment will yield improved results.
It, therefore, leaves two clear areas of risk that require management and mitigation:
A successful SEO migration in itself requires planning to make sure your multi-million dollar AEM implementation doesn't hit the rocks post-migration.
Additionally, making sure it's technically sound and that SEO is considered throughout the build process can impact organic search performance in the medium and long-term.
If you're currently planning on transitioning to AEM, or currently going through the implementation build, the below considerations may be useful in helping gear your AEM platform for better long-term performance.
Adobe does have comprehensive online documentation and support for Experience Manager.
I'll be primarily referencing documentation for AEM 6.5 (which may vary from 6.4 and 6.3 that are available via the support center).
It's also worth noting that not all of these consi