The go-live checklist is a summary of best practices to consider when launching a website. These steps are generally good practices but have some aspects specific to Adobe Experience Manager.
Steps Before Go-Live
Content and Design QA
Make sure that your content and design conforms to the specifications and that you are happy with the website you see on your projects
.hlx.live domain. This may include checks for specific accessibility and SEO requirements of your project.
Every AEM project should produce a lighthouse score of 100 for mobile and desktop from Google Pagespeed insights on its respective
See the document Keeping it 100, Web Performance for more information.
Make sure that all your analytics setup and the rest of your martech stack is firing as expected and visitor data is visible in your reporting dashboards.
In most migrations there are legacy URLs that are retired. Make sure those are reflected in your redirects spreadsheet (
redirects.xlsx in sharepoint or
redirects in google), found in your project content folder.
See the document Redirects for more information.
Sitemap & Robots
For most websites with a significant number of pages, a sitemap is desirable. AEM automatically generates those from the query index.
If you have a sitemap that’s generated for your site make sure it is discoverable from your
robots.txt. Note that
robots.txt is (technically) case sensitive, and a good example is:
User-agent: * Allow: / Sitemap: https://<your-domain>/sitemap.xml
hlx.live are kept hidden from crawlers intentionally, to avoid duplicate content.
Adding a favicon to your site gives it a professional look in your visitor’s browsers.
See the document Favicon for more information.
One of the last steps in a go-live is usually to update your CDN configuration (e.g. Cloudflare, Fastly, Akamai, Cloudfront) to point to your
Ideally the CDN configuration is tested in a staging environment to make sure that everything works as expected.
Please see the following CDN setup documentation for more information.
Push Invalidation Setup
Make sure push invalidation is properly set up according to the document Configuring Push Invalidation for BYO Production CDN. Test the setup by publishing a small change and verifying that the change is visible on the production domain.
Update Production Host
After setting up your production CDN, add the
host property to the sidekick configuration in
/tools/sidekick/config.json in your github repo, to allow your authors to navigate directly from the production domain to edit directly from the sidekick.
See the document Sidekick Configuration for more information.
Post Go-Live Validation
Validate that the performance is still at a lighthouse score of 100 via pagespeed insights on the production environment. Introducing a CDN layer can have adverse performance effects that are usually visible on the protocol layer. Typical culprits are running HTTP/1.1 or ineffective origin caching as well as bot detection or other libraries injected by the CDN configuration.
Google Search Console
If you have an active Google Search Console with your sitemap uploaded, it may be valuable to get a coverage report and make sure that indexing works as expected. The Google Search Console should be monitored for the weeks after a go-live.
After a website has been migrated there is usually a set of 404 Not Founds, which should be monitored after the go-live and redirected to popular page URLs. This information can be pulled from your site analytics and the respective Slack bot report. Monitoring this for the weeks after a go-live is recommended.