Design One Page In Your Page Builder. Cleo Builds The Rest.

A copy of a page you have already built, set aside as the starting point for future pages.

You build a page in Elementor to your own design. Presstack copies it, and that copy becomes the blueprint. The original stays live and untouched. Editing the original later has no effect on pages already stamped from it, and no effect on the blueprint itself.

When you ask for a new page, she fills the blueprint's structure with copy drawn from your instruction and the Knowledgebase. The result is your layout, not ours.

No. You see the before and after before anything goes live.

This matters most for bulk page work, because some page changes do not reverse cleanly once written. The safeguard is the preview, not an undo. Look before, not after.

Four checks run before she considers a page finished, overall quality, whether the page makes a case rather than just a description, whether the next step is clear to a reader, and whether the page is too close to one already on the site. If it fails the last one, she does not offer to publish it at all.

Writing copy uses credits. She shows you the cost before you confirm.

For a single page that is shown before the page is written. For a batch, the total is shown before the run starts, so twelve pages is not a surprise at the end. Viewing blueprints, running the duplicate check, and seeing the before-and-after preview are all included in the subscription and do not draw on credits.

Cleo compares what you offer against what you have published, and lists the gaps.

She reads the services and areas in your Knowledgebase, then checks those against the pages on the site. A plumber with eight service areas and six services might have forty-eight logical pages. If thirty exist and eighteen do not, she lists the eighteen. You decide which ones are worth building.

She does not decide priority for you. She makes the gap visible, because gaps you cannot see do not get filled.

Each site has its own blueprints, its own Knowledgebase, and its own page list.

An agency licence covers multiple client sites under one login. When you stamp a new page for a client, it draws on that client's Knowledgebase, so the copy reflects their services and areas rather than a generic fill. The duplicate check runs against that site's existing pages, not across all sites.

There is more on running Presstack across a portfolio on the agencies page.

Nothing. Pages already stamped from a blueprint are not affected by changes to it.

Each stamped page is its own published page from that point forward. You can edit the blueprint and those pages independently. If you want to bring an older page in line with a revised blueprint, the 'bring a page up to date' option handles that without rebuilding from scratch.

Yes. Any existing page can be set as a blueprint or repurposed directly.

If you have a service page that is already performing well, Presstack can copy it as a blueprint and stamp new location variants from that structure. Alternatively, the repurpose option rewrites the copy on a page without changing the layout, useful when a page exists but the words are no longer right.

Either way, you see the before-and-after before anything is written to the live page.

No. Everything on this page is in both versions.

Presstack Core is a plugin. It goes on the site as it stands and leaves the theme and page builder alone. Presstack Theme is the other version, becoming the website itself, with its own design system and template control for every page type. The blueprint system, the missing pages list, the duplicate check, and the before-and-after preview are all in both.

It shows you the current page and the proposed version side by side, before anything is written to the database.

For bulk page work this is the main safeguard. Some page changes do not reverse cleanly once applied, so the preview is more reliable than an undo. Read the proposed copy, check the structure looks right, then confirm. Nothing happens until you do.

Yes. The bulk change tool lets you apply the same instruction across as many pages as you select.

You write the instruction once, pick which pages it applies to, and she proposes the change for each one. You see a before-and-after for the batch before anything is confirmed. This is useful for updating a service name, changing a call to action, or removing copy that is no longer accurate across a set of location pages.

The missing pages list runs per site, so each client's gaps are separate.

Open the All Pages screen for a site and the list shows what has been built and what has not, based on the services and areas in that client's Knowledgebase. A client with ten services and six areas has sixty potential pages. If forty-two exist, you see the eighteen that do not. Showing a client that list tends to make the next conversation straightforward.

There is more on running Presstack across a portfolio on the agencies page.

Every page she has written or repurposed stays exactly as it is. The copy is in ordinary WordPress fields, on your site, under your control.

What pauses is her doing new ones. Your existing pages keep working. Cleo pauses.