Page alias export and import

Administrators can seamlessly import and export page aliases using a JSON file.

This feature lets you move page aliases across environments (for example, from development to production).

Using JSON files for Import and Export

To import and export aliases, administrators must follow specific steps:

1. Export the existing page aliases to a JSON file.

2. Import the JSON file into the desired environment.

This process allows for easy migration and backup of the page aliases, ensuring that editorial teams can quickly move across different environments and always revert to a stable version if needed.

Benefits of the Import and Export feature

• Streamlines the editorial process, reducing administrative workload when synchronizing the Page Builder across environments.

• Enables efficient backup and restoration of page aliases.

How does it work?

The capability to export and import the page aliases through JSON files allows moving aliases across environments quickly and without human errors.

Export

On the Site Structure page, at the root level:

• Select Export → Aliases to open the export window.
  

• In the export window, export all page aliases into a downloadable JSON file. You can select all languages or some to export.
  

• Then, download the JSON file.

Import

On the Site Structure page, at the root level:

• Select Import → Aliases to open the import window.
  

• Upload the JSON file containing the aliases to import.
  

• Once the JSON import file has been validated and uploaded, select Next to manage the import before executing it.
  

• The Compare Aliases page lists all pages with aliases either in the import JSON file or in the destination. Each page shows four columns:

  • Source: The import source, which is the import JSON file.

  • Destination: The name of the destination environment (e.g., integration, staging, or production).

  • Preview changes: How the import changes the page’s alias.

  • Action: Select to either apply or skip the import for that page. E.g., in case the import JSON file doesn’t include an alias that exists in the destination environment, it’s possible either to delete the alias — so, apply the import — or skip it.
    

• Select Import to run the import based on the selection you did on the Compare Aliases page. Check the result in the Import dashboard.