Essentials

Launch preparation and checklist

Adobe’s launch resources are designed to help you achieve a seamless and successful rollout of your Adobe Commerce storefront powered by Edge Delivery Services.

Adobe Commerce projects usually require much more than a simple content delivery network (CDN) switch to launch. You must ensure that the launch activities are well defined and planned. You should also prepare a rollback plan in case you encounter any issues during the launch.

Launch checklist

Completing all pre-work and tasks required to launch a new storefront can be overwhelming. This checklist helps ensure that you complete and track all necessary work before going live.

As you develop, carefully track all changes made in development or staging environments to ensure that they can be applied and deployed when you migrate to production.

SEO and indexing

Add a document title metadata for key pages (especially PDPs and PLPs). See the SEO metadata documentation for details.
Ensure that your PDPs have metadata and structured data (for example, LD-JSON data is configured).
Standardize URL formats for products (example: domain/product-name).
Redirect all vanity URLs to canonical URLs.
Add a robots.txt file to your project, which allows your site to be indexed by search engines. Ensure that your sitemaps are referenced and that you add rules to block indexing of any content that you do not want to be indexed (for example, the /drafts folder).
Add one or multiple redirect files to ensure that URLs that were changed as part of the migration still work (for example, when you remove the .html file extension).
Generate a sitemap for your site and catalog. To speed up the indexing process, Adobe recommends adding the sitemap to Google Search Console.

Enable pre-rendering

Add pre-rendering for key pages. See the pre-rendering documentation for details.
Verify that all URLs are in lower case to support pre-rendering without breaking any links.
Validate HTML source for metadata and enriched body content (to ensure pre-rendering is working).
Check availability of page translations for locales with different languages.

Performance and monitoring

(Optional) Configure Google Analytics and Google Tag Manager.
Validate your storefront events implementation and ensure that data is displayed in your Live Search and Product Recommendation dashboards in the Adobe Commerce Admin.
Ensure that the environment analytics config parameter is set appropriately in your Commerce configuration. It should be set to "Testing" when you are developing your storefront, and "Production" when you are ready to deploy your storefront. See the Instrumentation documentation for more information.
Ensure that the site’s Lighthouse score is green; targeting 100 on every page (taking into account previous considerations mentioned on this document).

Security and access

Verify that you have configured permissions for DA content and EDS sites. See DA.live permissions and authentication setup for authoring.
Ensure that the product visuals integration has been provisioned. See AEM Cloud Service access overview.
Verify/update password reset links. Match the Edge Delivery Services implementation in the Adobe Commerce Admin. See the FAQ for details.
Provide and configure production keys for integrations and payment providers.
Verify that the new domains/subdomains are allowlisted and potential backend webhooks are working.

CDN and caching

Update your CDN configuration with your production GraphQL endpoint yourproject.com/graphql. Make sure to also use this for all the Sidekick extensions and scripts (for example, sitemap generation, image importer).

When using Adobe Commerce Fastly, request a new CDN purge token for Commerce production environment. Update in Sharepoint in the .helix/config.xlsx file (authToken and serviceId).
Validate your CDN configuration and ensure that caching and cache invalidation work as expected.
For multi-store setups, add a store-specific cache buster (for example, a query parameter or proxy through CDN configuration) to Catalog Service and Live Search requests.

Catalog service

Switch to the Catalog Service production endpoint (https://catalog-service.adobe.io/graphql).
Ensure a production environment is configured in the Service Connector (will result in a new environmentId).
Sync the production catalog to the new production environment.
Create a new Commerce production API key-pair and use the public key as the x-api-key value.
Verify category IDs and ensure all category pages reference the correct category.
Update environmentId and x-api-key values in the config.json code file.
Notify the Catalog Service team about the new production environment and launch date.

Project management and updates

Notify Adobe early about your planned launch date to ensure that the Adobe Commerce team is available to support you during the launch.
Check for the latest boilerplate changes and update your project accordingly.

Documentation

For complete documentation on launching your storefront, visit the Launch section on the Adobe Experience Manager site or select the direct links below. You should also review the Commerce-specific launch checklist.

Go-Live Checklist: The go-live checklist is a summary of best practices to consider when launching a website.
Push Invalidation: Automatically purge content on your production CDN, whenever an author publishes content changes.
Cloudflare Worker Setup: Learn how to configure Cloudflare to deliver content.
Akamai Setup: Discover how to use the Akamai Property Manager to configure a property to deliver content.
Fastly Setup: This guide illustrates how to configure Fastly to deliver content.
CloudFront Setup: Set up Amazon Web Services Cloudfront to deliver your AEM site with push invalidation.
Bring your own DNS: A custom domain without having to set up a content delivery network.
Redirects: You can manage redirects as a spreadsheet from the redirects document in the root of your project folder.