PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

Build a page with Avada Builder and choose it as Base Layout to Clone. PageForge copies its content into each generated page and fills in placeholders.

Updated November 18, 20262 min read

Avada Builder saves a page’s containers, columns and elements in the page content. When you choose an Avada page as the base layout, PageForge copies that content into every generated page and replaces the placeholders with each row’s values.

Set it up

  1. Build a regular page with Avada Builder. Put placeholders in title, text and button elements, for example {Service} in {City}.
  2. Save it. It can stay a draft.
  3. Go to PageForge > Templates, edit your template and choose the page under Base Layout to Clone. If it is not in the list, enter its ID in Base Page/Template ID.
  4. Set the Title Pattern and Slug Pattern and save.
  5. Run Check and preview, then generate a few rows as drafts.

What gets copied

From the base pageResult on each generated page
Page content with Avada Builder elementsCopied, placeholders replaced
Page templateCopied
Featured imageUsed when the row provides no other image
Other Avada page options stored outside the contentNot copied

A text element in the saved content can look like this:

[fusion_text]<p>Fast {Service} in {City}. Call {Phone} for a free quote.</p>[/fusion_text]

For the row Window Cleaning, Melbourne, 03 5550 1234, the generated page shows “Fast Window Cleaning in Melbourne” with that phone number.

Where placeholders are replaced

  • At generation, in the copied page content.
  • At display. If a placeholder remains in the content, PageForge replaces it when the generated page is shown, along with the page title your theme prints.
  • Shortcode. For element fields that do not accept braces, use [pageforge var="City"].

Limits

PageForge supports Avada where the required builder data is saved in the page content.

  • Per-page Avada options that are stored separately from the content, such as page-level overrides, are not copied. Set them at theme level, or check and adjust them on the generated pages.
  • Avada layouts that apply site-wide, such as global headers and footers, belong to the whole site and are not copied into each page.
  • Use a regular page as the base. Avada library items are not listed in Base Layout to Clone, so test carefully if you enter one by ID.

Tip Generate three rows as drafts, then open one in Avada Builder and one on the front end. Compare them with the base page, including the mobile view, before you run the full CSV.

Next: Create a template and Placeholders show on the page.

Was this page helpful?

↑↓ to move↵ to open