Skip to main content

Clone a Page

Cloning helps you create a new page from an existing page or external design instead of starting from scratch.

Atomicat supports different clone-related workflows depending on where you start and what access your account has.

Clone options in Atomicat​

OptionWhat it does
Duplicate pageCopies an existing Atomicat page into a new unpublished page.
Create variantCreates a variant connected to the original page for testing.
Duplicate as mainConverts a variant-style copy into a standalone main page.
AtomicMCP cloneOpens AtomicMCP for assisted page cloning workflows.
JSON importCreates a page from compatible Elementor JSON.

Duplicate an existing Atomicat page​

Use duplicate when you want a safe copy of a page before making changes.

  1. Open the page list.
  2. Find the page you want to copy.
  3. Open the actions menu.
  4. Select the duplicate option.
  5. Atomicat creates a new page copy.
  6. Rename the copied page.
  7. Edit it before publishing.

Duplicated pages are created as unpublished copies. The copied page should not keep the original live domain, slug, synced paths, or published status.

Create a page variant​

Use variants when you want to test a different version of the same page.

  1. Open the page list.
  2. Find the main page.
  3. Open the actions menu.
  4. Select Create Variant.
  5. Edit the new variant in the builder.

Variants are useful for testing headlines, hero sections, offers, layouts, or calls to action while keeping the test related to the original page.

Clone from the new page flow​

From the page creation area, Atomicat may offer a clone option.

Depending on your setup, the clone workflow can:

  • Open AtomicMCP for a guided cloning process
  • Allow compatible JSON import
  • Create a page from converted sections
  • Import supported image assets
  • Assign the page to the selected project when a project is active

Clone from JSON​

Some accounts can import compatible Elementor JSON.

Atomicat validates the JSON, converts supported content into builder sections, imports supported images, and creates a new page. If the file is not compatible, Atomicat can show an error and guide the user toward AtomicMCP.

Access requirements​

Some clone actions require paid access, feature access, or specific account permissions.

If you cannot clone a page, possible reasons include:

  • The account does not have clone access.
  • The page is a synced page.
  • The page is a producer page.
  • The page is deleted.
  • The clone source is not compatible.
  • The imported JSON is invalid.

What to check after cloning​

Always review cloned pages carefully.

Check:

  • Page name
  • Images and backgrounds
  • Button links
  • Form fields
  • Mobile layout
  • Tracking scripts
  • Products and offers
  • Domain and slug
  • Thank-you pages or redirects
  • Any imported custom styling

Best practices​

  • Duplicate a page before making risky changes to a live campaign.
  • Rename clones immediately so they are easy to identify.
  • Do not publish cloned pages until all private links, scripts, and forms are reviewed.
  • Use variants for controlled testing instead of unrelated copies.
  • Use AtomicMCP when the source page or JSON import is not compatible.

Frequently asked questions​

Does duplicating a page copy the live URL?

No. Atomicat creates the duplicate as a separate unpublished page so it does not overwrite the original live URL.

Can free accounts clone pages?

Some clone actions may require paid or feature-specific access.

Can I clone Elementor pages?

Atomicat supports compatible JSON workflows and AtomicMCP-assisted cloning. Compatibility depends on the source file and page structure.

Why did my cloned page look different?

External pages and JSON files may include unsupported scripts, styles, widgets, or assets. Always review and adjust the cloned result before publishing.