Skip to main content

Previewing and regenerating a landing page

How to review a landing page before publishing, and how to regenerate it with new instructions when the copy misses.

Written by Eddie Lavandera

The preview is the last stop before your landing page goes into a theme. It shows the finished page on desktop and mobile, and it is where you decide whether to publish, regenerate with different instructions, or start again. It is also the screen where the buttons matter most, so this walks through what each one does.

In this article:


Reaching the preview

The preview opens automatically when a landing page build finishes. It is titled Preview your advertorial or Preview your listicle.

You do not get back to this screen later. Once a page is published, you edit it through your pages list rather than through the preview.


What to check

Read the whole page rather than skimming it. In particular:

Check

Why

The opening

It decides whether anyone reads the rest

Every factual claim

Atlas writes plausible copy, and plausible is not the same as true

Testimonials and statistics

Generated social proof must be replaced with real proof or removed

The call to action

It should point at the product you chose

Prices and offers

They must match what your product page actually says

⚠️ You are responsible for what you publish. Generated testimonials, review counts and statistics are placeholders, not evidence. Replace them with real ones or remove them before publishing, particularly in regulated categories.


Desktop and mobile

Switch between Desktop preview and Mobile preview.

Check mobile carefully. Landing pages are long-form, most ad traffic is on a phone, and a paragraph that reads well on a wide screen can become an intimidating wall on a narrow one. Look for headings appearing often enough to break up the text, and calls to action that arrive before a reader would give up.


Regenerating with new context

If the copy is close but wrong in tone or emphasis, you do not have to start again. Select Edit AI context & regenerate.

  1. Write into Custom context what you want changed. The placeholder shows the kind of instruction that works: E.g., Use a confident tone, focus on benefits, keep paragraphs short, highlight the guarantee...

  2. Select Regenerate.

  3. Wait. Regenerating creates new content based on the updated context, and the preview updates when it finishes.

Write instructions rather than corrections. "Lead with the 30-day guarantee and cut the origin story" gives Atlas something to act on. "Make it better" does not.


What regenerating replaces

⚠️ Regenerating rewrites the entire page. It is not an edit: this replaces the current context and regenerates the entire content. Anything you liked about the current version may not survive.

If most of the page is right and only a section is wrong, it is usually better to publish and then edit that section in the Atlas editor, rather than regenerating and risking the parts that worked.

Two rules of thumb:

  • Wrong angle, wrong audience, wrong tone throughout: regenerate.

  • Right overall, one bad section or a few wrong facts: publish and edit.


Leaving the preview

Your page is saved. You can leave the preview and come back to it: the generated page is kept and appears in the Landing pages tab of your dashboard, where you can reopen it, preview it again and publish it whenever you are ready.

ℹ️ Atlas asks you to confirm before you leave. The page is saved either way, and nothing you do at this stage destroys the build.

Save as draft is an exit rather than an action. The page is already stored whether you press it or not.


Publishing

When you are happy, choose the theme under Theme to import into and select Import & edit in Shopify.

Watch for This theme isn't live — the page won't show on your store until this theme is published. That warning is information rather than an error, and publishing to a non-live theme is a good way to review before going live.


Next steps

Did this answer your question?