Landing pages: generate and manage landing pages for your ads
Landing pages lists every landing page that Commander has written for your store, and starts new ones. Open it from Create > Landing pages. To edit, publish or archive one page, see Landing page editor.
Problem and intended user
The media buyer (the person who runs your paid ads) sends clicks to a page. If the page does not repeat the hook, the offer and the look of the ad, visitors leave. The ecommerce manager (the person who runs the store) needs a page for each product or angle, and each page needs a writer, a designer and a place in the theme. Ads then wait for pages, or they point at a generic product page.
Current workflow
Without Commander, the ecommerce manager or an agency builds each page in the Shopify theme editor, or in a page-builder app. Someone copies the headline and the image from the ad by hand. Someone checks that the page and the ad still match after each change.
Prerequisites
- The Shopify app is installed and your product catalog is synced.
- Commander knows your store's style: your fonts, colours and sections. The New landing page flow learns it for you when you create a page. After you publish a different theme, Commander learns the new theme's style by itself when you next open Landing pages or a place that starts a page. Every other place that starts a page keeps Generate off until Commander knows your style. See Learn your store's style under How Commander works.
- Credits. Generating a page uses credits. The dialog and the Billing page show the cost. See Credits and top-ups.
- Optional: Shopify's Theme Access app. With it, pages publish as full-width sections of your theme. Without it, they publish in the basic layout. See Theme Access (Settings > Theme Access).
- Optional: an ad. A page can start from an ad, from a product, or from the brand alone.
How Commander works
Commander reads your store's theme and keeps a record of its style. It learns again by itself when you publish a different theme or change your theme a lot. For each page, Commander reads the product and the ad, when you pick one. AI then writes the copy and builds the page from your store's own theme. A page is always a Draft first. There is no approval step: it goes live when you select Publish, or when you deploy an ad that the page was made for. A change to a page that is already live stays unpublished until you publish it. On a Full-width page, you can also edit the parts of the page in the Shopify theme editor, and Commander reads your changes back. See Landing page editor.
WARNING
Generating a page uses credits. Check the cost in the dialog or on the Billing page before you start.
Learn your store's style
The Store style chip sits beside New landing page. Select it to open the Your store's style window, which shows what Commander learned: fonts, colours, sections, store facts and voice. Once Commander has learned your style, Relearn in that window reads your theme again whenever you want. It is off while Commander checks your theme, and it is not there while an update runs.
What starts a learn depends on what changed:
- A new theme. After you publish a different theme, Commander learns its style by itself the next time you open Landing pages, the New landing page flow, or another place that starts a page. New pages wait until it finishes: a banner reads Learning your new theme's style, Generate stays off, and the New landing page flow holds your Create until the style is ready, then starts the page once. You can leave the page. Commander keeps learning in the background. If it takes longer than usual, the banner says so and Commander keeps going.
- A big change to your current theme. Commander checks your theme for changes when you open Landing pages or a place that starts a page. After a big change, such as a redesign, it updates the style in the background. The chip reads Updating style with a step count, and new pages keep using the current style until the update is saved. Nothing is switched off.
- Small edits. A copy change, a new product, or a change to a template other than your home or product page never changes your style, and nothing shows on the page.
The chip shows where Commander is:
- Learn your store's style replaces the chip when Commander has no record yet. Select it, then select Learn my store's style.
- Learning style with a step count shows on the chip while Commander reads a new theme, and Updating style while it updates the style of your current theme.
- Relearn suggested appears on the chip when Commander can learn more about your theme, or when your theme changed a lot and the automatic update did not start. Your pages keep working. Select the chip, then Relearn in the Your store's style window.
- Relearn needed appears when you published a different theme and Commander did not start learning it by itself. A banner above the list asks you to relearn. Select Relearn in the banner. Until the style is learned, Generate stays off and the New landing page flow cannot create a page.
- Taking longer than usual appears when a learn has stopped making progress. While Commander learns a new theme, select Try again in the banner. When Commander still has a usable style, select the chip, then Relearn in the Your store's style window. When Commander is learning your store for the first time, the chip has no button. In the New landing page flow, Create stops waiting and the step shows Try again. Select it to start the learn again.
- Couldn't learn style and Couldn't update style appear after a failed learn. See When learning fails below.
- Using previous style appears after you choose Use previous style. See the failure steps below.
While a new theme is learned, the places that start a page tell you why they wait, and switch on again by themselves:
| Place | What it says |
|---|---|
| The Generate landing page dialog | "Commander is learning your store's style. You can generate pages when it finishes." Generate is off. |
| Remodel on a page | "Remodel is available once Commander has learned your store's style." |
| Also generate a landing page in the Deploy N ads dialog | "Landing pages are available once Commander has learned your new theme's style" with the step. Your ads can still deploy now. |
| The landing page option when you place a creative | "Your ad is saved without a landing page. Commander is learning your store's style; add a landing page once it finishes." |
When Commander did not start learning a new theme by itself, these places show "You published a different theme. Relearn your store's style so new pages match it." and a Go to Landing pages link. Select Relearn there.
A page that was waiting when the theme changed does not get created. Its card reads "Your theme changed while this page waited. Create it again once Commander has learned the new style."
When learning fails
Commander shows the reason. The failure stays on screen until a learn works, or until Commander clears it after some days. It is still there after you reload the page, or open Commander on another screen. The banner reads We couldn't learn your store's style. Pressing Create in the New landing page flow shows "Your page wasn't started." with the same reason, and nothing is created.
| Reason | What to do |
|---|---|
| "We couldn't open your storefront. Check that it's online and open to visitors, then try again." | Open your storefront in a browser. When it loads, select Try again. |
| "Your storefront's bot protection (for example Cloudflare) blocked us from reading it. Allow it to be read, then try again." | Your storefront is online, but its bot protection stops automated reads. In your bot protection settings, allow your storefront to be read, then select Try again. |
| "We couldn't get past your storefront password. Check the password in Settings, then try again." | Select the Storefront password link in the message, or open Settings > Theme Access and go to the Storefront password page. Check the password, then select Try again. See Theme Access. |
| "Learning your store's style took too long. Try again in a few minutes." | Wait, then select Try again. |
| "Commander can't reach your store. Reopen the app from your Shopify admin, then try again." | Reopen Commander from your Shopify admin, then select Try again. |
After a failure, Commander does not start another automatic learn for the same theme for a while. Try again is always available, and it starts a learn right away.
If you cannot wait and you learned a style on an earlier theme, you can use that style for now. Use previous style appears beside Try again only when Commander has a style from an earlier theme.
WARNING
Use previous style makes new pages use your earlier theme's style, so they may not match your new theme. Relearn once the problem is fixed to switch back.
Select Use previous style. While it is on, the chip reads Using previous style and Relearn is in the Your store's style window. A successful learn turns it off, and it also ends by itself after a while. It applies to the theme you chose it on. If you switch to another theme, Commander learns that theme.
When a background update of your current theme fails, nothing is switched off. The chip reads Couldn't update style, and the Your store's style window says "We couldn't update your store's style." and "New pages keep using the style Commander learned before." Select Try again there.
Pages started from an ad use its fonts
When you start a page from an ad that Commander made, the page's headings and its button use that ad's fonts, so the page continues the ad a visitor just saw. Body text follows your store's style. If Commander cannot read the ad's fonts, the page keeps your store's fonts. On a Full-width page, the page's font settings in the Shopify theme editor list the ad's fonts first, so you can change them there. On other pages, the fonts stay as the ad set them.
A sticky button on long product pages
On a long product page where the Add to cart form sits far down, Commander can add a bar at the bottom of the screen that keeps the buy button in reach while the shopper scrolls. The bar always says the add-to-cart word of your page's language, such as Add to cart, and takes the shopper to the form. Commander adds it only when the page has few other ways to buy.
The bar is the last section of the page. In Sections it shows as Sticky button, and you can reword, hide or remove it there. A later remodel leaves it in place unless its note asks to change it; check the preview before you keep the remodel. Once you remove the bar from a page, Commander does not add it back to that page, whether you removed it in Sections or asked a remodel to remove it. See Landing page editor.
Create a page with the wizard
- Select New landing page.
- Under What should the page continue?, choose An ad (recommended: visitors land on the same headline and picture they clicked), A product or Your brand.
- Pick what it continues. For An ad, answer Which ad? by choosing a card from the grid. A hint above the grid reads "Choose an ad to build its page. The page continues its promise: same hook, same offer." Each card has a round selection mark, which shows a check on the chosen card. Each card shows the whole ad picture. To see it larger, point at the card, or select Preview, the magnifier in the picture's corner. For a carousel, the card shows one of its cards. Search ads looks through all your ads. It matches the headline, the ad's text, its name and its product. Beside the search box, Sort orders the grid: Recently synced, Most spend or Best ROAS. Under them, narrow the grid with the Status, Product, Ran in and ROAS menus. Status: Active shows only live ads. In Product, No product linked shows ads that sell no product, and Choose a product… opens your products so you can pick one. While Ran in or ROAS is on, the grid hides ads that Commander made, and a note says so. With Ran in on, each card's results cover that period. Clear filters turns the filters off and keeps your search and sort. While new results load, the search box shows Updating…. Load more shows the next ads. Under each ad, a line names its product. Whole store means the ad has no single product. It sends visitors to your home page, a collection or the cart, or Commander made it for your brand. Product not detected means Commander could not tell which product the ad sells. For an imported ad with no product, the wizard says "This ad is not linked to a product, so the page is about your store." It links to the ad's Linked tab, which opens in a new tab. Choose + Link product there and come back. The page uses that product, unless you already picked one. A card marked Different product is linked to another product. The page is about the product the ad is linked to. For A product, answer Which product? with Choose a product, then optionally start from one of its ads under Start from one of its ads?. The For this product chip lists only the ads linked to that product, with a line such as "{n} ads sell {product}.". Turn it off to see every ad, with the ads for other products marked. If you change the product, the ad you chose stays chosen when it sells the new product. Otherwise Commander drops it. If the ad is linked to a different product, Commander asks "Switch the page to {product}?": Switch to {product} moves the page to the ad's product, Keep {product} leaves the page about yours with a new headline and the product photo, or Choose another ad. Review and create stays off until you answer. For Your brand, optionally say what the page should achieve. Edit brand opens your brand settings in a new tab.
- Optional: open Customise. It shows what the page opens with. Choose the Headline: From the ad (marked recommended while it is the default) or New headline. With From the ad, the hint quotes the headline the page opens with, which Commander may shorten to fit the page. The ad shows under it, with View ad. When an imported ad has no headline, the page opens on the first line of its text. With New headline, Commander writes the headline when it creates the page. Choose the Picture at the top: Automatic (recommended), Product photo, No image, or The whole ad for an ad that Commander made. Automatic uses the ad's picture with the ad's words removed, or the product photo when the ad has no picture. Choose the Picture width: Full width or Contained. Without Theme Access, the page uses the basic layout, where your theme may keep the picture as wide as your content. Without an ad you can also say what the page should achieve. Customise also holds the Strong promises switch, which is off. With it off, the page uses careful wording and makes no health or body-effect claim. Turn it on to let the page make strong promises and quote reviews that describe health results. The page still states only what your store's pages, facts and reviews support. You are responsible for what your page claims. A brand page has Customise too, and there it holds this switch, so you can set it before you create the page. You cannot change the choice after the page is created, and pages made earlier have it off. The page keeps your choice when you regenerate it.
- Check the Your page summary and select Review and create. The price and your balance show beside the button, with "Charged only if the page is created." The Review and create dialog lists the product or brand, the ad and your settings, with your balance before and after. Select Create for N credits to start the page, or Back to edit to return to the form. The page is saved as a hidden draft in Shopify. Nothing goes live until you publish. To leave without a page, select Discard. If you changed something, Commander asks first: Keep editing or Discard. On a phone the bar has no Discard, so leave with the back arrow in the header. It does not ask first.
The ad picker shows ads that are not archived. Next to Review and create, a line says what is still missing, for example "Choose one of the ads above to continue.".
When the ad you chose is not running, a warning shows under the ad picker. It shows when the page starts from an ad, and when a product page uses the optional Start from one of its ads? picker. The same warning shows again in the Review and create dialog. Its heading names the state: "This ad is paused", "This ad is stopped", "This ad has finished", "This ad is archived", "This ad was rejected" or "This ad was not published". The text says the page gets no traffic from that ad until it runs again. For a paused ad it reads "until you switch the ad back on", for a rejected ad "until the ad is approved" and for an ad that was not published "until the ad is published". The warning does not stop you: you can still create the page. A draft ad, or an ad that is ready to publish, shows no warning, because you can build a page before its ad goes live.
Start a page from other places
The Create landing page button on a single ad's card or row, and the button on the ad's detail page, open the wizard above with that ad already chosen under An ad, so you land on the last two questions. If the ad is no longer available, for example because it was archived, the wizard opens on its first question and says "This ad is no longer available." When the ad already has a page, the button reads Open landing page instead. On your own ads, such as the rows of Ad performance, the … (More actions) menu then adds Create another landing page, which opens the wizard with that ad chosen. On the small ad tiles, such as the cards in Your Ad Creatives and the top-creative thumbnails on a Home dashboard, the same action sits in the … (More actions) menu instead of a button. On a Generated ad and in the Refresh queue on Lifecycle, the … (More actions) menu holds Duplicate in Lab.
The other places below, and the bulk Generate landing pages (N) button, open one dialog, Generate landing page. It lists the ads, with Skipped: already being generated or Skipped: unavailable beside any ad it leaves out. An ad that already has a page is not left out: it gets a second page, and its row reads "Has a page: «{page}». The ad keeps linking to it until you choose." When the page's name is not available, the row reads "This ad has a page. It keeps linking to it until you choose." When some of the chosen ads already have a page, a sentence above the button says how many, for example "2 of these ads already have a page. Each keeps its current page until you choose the new one." You choose the options, then select Generate.
WARNING
Each page uses credits, a second page for an ad included. When your store's plan uses credits, a line under the options counts the pages the run makes and shows their cost, and the button names the same count and cost.
| Place | Control |
|---|---|
| Create > Ads | The Create landing page button on the ad's card, which opens the wizard with the ad chosen, or Select ads and Generate landing pages (N) |
| Create > Creatives | The Create landing page button on a Creative Set's card, or Select sets and Generate landing pages (N) |
| The Studio editor | Create landing page in More actions |
| Ad detail | Create landing page in the header, and in the Landing page tab, for your own ads. It opens the wizard with the ad chosen. See Ad detail. |
| Bulk deploy | Also generate a landing page in the Deploy N ads dialog. It makes one page for the batch, from the first ad. |
| Option | Choices |
|---|---|
| Page focus | Follow the ad's message or Standalone product page |
| Picture at the top | Automatic (recommended), Product photo or No image |
| Picture width | Full width (the default) or Contained. It does not show with No image. |
An ad that has a page shows Open landing page or View landing page instead. On Ad performance, the … menu beside an ad's Open landing page button in the table also offers Create another landing page, which opens the wizard with the ad chosen. A run takes up to 20. The selection bar says so, and the dialog reads "Choose up to 20 ads per run." when you pick too many. After Generate, a message reads Landing page queued, or the number queued. The page then shows as a Generating card.
Follow a page while Commander writes it
After you confirm, the wizard shows the page's screen while Commander writes it. The header shows the page's name. For a page made from an ad, the name is the ad's name (its headline when it has one). Otherwise it reads "{product} page" for a product page, or "{store name} page" for a brand page. When the product or the store name is not known yet, it reads New landing page or Brand landing page. The Generating card in the list shows the same name. The header also shows the product, the ad it continues, and a Generating badge. The badge does not name the step: the progress list names it once. The trail above the header reads Create > Landing pages > the page's name while Commander writes it. The activity chip at the bottom of the app leaves the progress of this page to the screen, and still shows other pages that Commander is writing. The … (More actions) menu is off until the page is ready. For a page made from an ad, a strip reads "Continues the {platform} ad" with the ad's headline. Under it, a preview area with Desktop and Mobile holds Writing your page and the steps: Queued, Reading your store, Writing and building the page and Saving it to Shopify as a hidden draft. Four more steps show only while Commander runs them. Before the page is written, Learning what customers buy this for appears while Commander works out from your customers' reviews what they buy the product for, and Planning the page appears while it decides the page's main idea and its sections. After the page is written, Reviewing the page appears while Commander checks the page against what it knows about your product and your store, such as facts, prices and claims, and reads it as a shopper would. Fixing what the review found appears after it, only when the check found something to correct. Commander can skip a step, for example when it already did that work for an earlier page. A skipped step does not show. When Commander has to learn your store's style first, because the store has none yet or because you published a different theme, the list reads Learning your store's style first and has a Cancel button. Commander holds your page and starts it once, as soon as the style is ready. Cancel drops the held page, not the learning. The two halves differ on leaving. While your store's style is being learned, stay on the page: if you leave, the style keeps learning in the background, but the page is not created, so you press Create again once the style is ready. If learning fails, the form comes back with "Your page wasn't started." and the reason, as described under When learning fails. A big change to your current theme never holds a page: Commander starts it right away on the current style. Once Commander is writing the page, it is safe to leave: the page keeps being written and shows in Landing pages while it is. Page details opens the address ("Set when you publish"), the product, what it was made from and when it started. Stay and Commander opens the page when it is ready, or leave with the arrow, Back to Landing pages. A card marked Generating stays in the list until the page is ready.
Exact output
A list of pages, most recently updated first, with a card for each. Cards and List switch the view.
The header reads Your landing pages, with "Pages for your ads and products, written in your store's style. Nothing goes live until you publish." and the number of pages that are live, for example "1 live". When some pages need you, a button beside it says how many, for example "Show 3 that need attention": a page with an issue to fix, changes that are not live yet, or a change made in Shopify that you can bring in with Sync from Shopify. A page from the previous generator, or one that is Managed in Shopify, does not count for a change made in Shopify. The number follows your search and the other filters, so selecting it shows exactly that many pages. Select it to show only those pages; select it again, or remove the Needs attention chip, to show all of them. Needs attention is not a field under More filters; its chip is how you remove it. It does not combine with Pages: Archived, because an archived page never needs attention: turning one on turns the other off. The toolbar has a search box (Search landing pages, for headlines, products or ads), Products: which opens Filter by products, and More filters. More filters holds Pages (Saved or Archived), Status (All, Draft or Live), Made from (All, From an ad, From a product or Brand page), Active (Active only shows live pages) and, when your products have categories, Category. Archived pages show only under Pages: Archived. Each filter in force shows as a chip, and Clear all removes them. Select sits right after More filters. The toolbar also shows the number of pages, a sort menu (Last updated, Newest first, Oldest first, Headline A–Z, Status) and the Cards and List switch. A line reads "Showing X of Y pages", and Load more shows more.
The List view is a table with the columns Page, Status, Product, Address, Last updated and Actions. Select anywhere on a row to open the page. In selection mode, the checkbox and the actions are their own targets.
Each card shows:
| Part | What it shows |
|---|---|
| Picture | The page itself at desktop width, shrunk to fit inside a small browser frame. The bar shows your store's domain. The picture loads when the card nears the screen. Until then, a snapshot of the page. A page with neither reads No preview yet. On a live page the bar shows the page's address instead, with a small copy icon at its right end. Select the copy icon to copy the page's full address. The icon is hidden in selection mode. |
| Status | Draft, Live or Archived, with notes such as Unpublished changes, Edited in Shopify or Managed in Shopify |
| Title | The page's headline. A page with no headline, such as one from the previous generator, shows its search title instead, or its address when it has none. Selecting the title, or the card, opens the page. The ad line, the product line and, in selection mode, the checkbox are their own targets. |
| Remodelling… | An AI remodel is running on the page. It shows beside the status. |
| Previous generator | A page made by the earlier version of Commander. It shows beside the status. |
| Product | The product, or Whole store for a page with no product. A deleted product reads "Product no longer in your catalog". Select it to read the product in a window. |
| Where it began | From ad · {ad name}, From an ad with "Ad no longer available" when the ad is gone, From a product, Brand page or Collection. Select the ad to see it in a window. When the ad has more than one page, the page the ad's live link opens shows Ad's page, and the ad's page in Commander shows Ad's page (Commander) when the ad opens another page. |
| Address | View live page opens the page on your store in a new tab. A draft that Shopify holds reads Hidden draft in Shopify, and a page with no page in Shopify yet reads No page yet. An archived page that had been live reads Archived · address redirects. An archived page that was never live reads Archived. |
| Open page | On a Draft or Archived card. Opens a preview of the page in a new tab, with a note at the top that visitors cannot open the page. If your browser blocks the new tab, a message asks you to allow pop-ups. |
| Updated | The day the page last changed |
| Next step | One button for what to do with the page: View progress, Fix issues, Publish, Review changes, View page or Open |
| More actions | Duplicate as draft saves a copy as a hidden draft and opens it, with the message "Copy saved as a hidden draft." It is off on a page from the previous generator, and the menu says "A page from the previous generator can't be copied." Archive asks you to confirm, then takes the page down. The dialog says where the page's address goes, or that a page that was never published changes nothing for visitors. It is off on a page that is Managed in Shopify, and the menu says why. On an archived page, Restore asks you to confirm ("Restoring puts the page live at its address, so visitors can open it."), says whether the page comes back hidden from search or visible, then puts the page live. This menu has no search entry: open the page and use Show in search engines or Hide from search engines in its ⋯ menu. See Landing page editor. |
A Generating card shows the step and the day it was queued. It has no link and no checkbox.
When Theme Access is not connected, a note above the filters reads "Get full-width pages with live prices and your store's own Add to cart." Select Connect Theme Access (free), or dismiss it with the close button. Your browser remembers that you dismissed it.
What a generated page can carry
Commander chooses from a set of page patterns for each page and leaves out the ones that do not fit, so a page may carry any of these, and none is always there:
- A small label above a heading, with one phrase of the heading highlighted.
- A customer review placed next to the claim it supports. A review of one product has a caption that names the product. A review about the store as a whole has no product caption.
- A short story section about your store or its founder. Commander writes it in its own words from the text of your About or Contact page, and only when one of them has text about you. It states no figure that those pages do not state. Where it can, Commander removes a sentence with a figure that they do not state.
- A section of its own with the quotes that you already publish on your home, About or Contact page. The page shows each quote word for word, with no stars and no name. It stays apart from your customer reviews: Commander never counts these quotes as reviews, never puts them among the reviews, and never lets one back a rating.
- A card with a quote from a professional that you already publish, with their job title under it. The card shows the title and never the person's name. Commander places it in the section that gives the reasons to choose your product. Commander does not use a quote that makes a health claim, and it keeps a card whose words claim nothing, even when the person's title is in health care. If you create the page with Strong promises on, Commander may also use a quote that describes a health or body result, for your published quotes as for customer reviews. The privacy rules still apply, so a card never shows a name. A card is not a customer review, so it does not replace the reviews on the page.
- A section that opens on the problem your ad names. On a page made from your own ad, when the ad leads with a problem, the page can open on that problem in the visitor's own words, either in the main heading area or in an "Is this you?" section. It adds no fact or figure of its own.
- A short overview under the main heading with a tick before each point. It can include a rating line, only when enough of your reviews back it. Commander removes a rating line that does not match your reviews.
- A comparison table, built from the comparison table on your own product page. See Landing page comparison.
- A row of press, certification or partner logos that your own home or About page already shows. See Landing page logo row.
Commander reads your home, About and Contact pages for these. If it cannot reach them when it writes a page, the page is written without them. Commander removes a card that does not match what your pages publish.
Commander plans the sections of most pages before it writes them. The plan can include your story, expert cards, logos and the quotes you publish when your pages have them. A page that Commander writes without a plan can carry them too. In Demo Mode, the sample pages show them.
The buy box of a page can also show a price per day under a purchase choice, the same price once more outside the buy box, and a buy bar on phones. See Landing page buy box.
Read each page before you publish it, as for any generated page.
Bulk actions
Select Select in the toolbar to show a checkbox on each card and row. It changes to Done, which clears the selection and hides the checkboxes. A bar under the toolbar shows All (selects every page shown), "N selected", Publish, Archive, Delete and Clear. Each action shows in brackets how many of the selected pages it applies to, and stays off when none. When an action is off while pages are selected, the reason shows beside it, for example "Fix the product mismatch next to the ad first." When the selected pages are left out for different reasons, it reads "None of the selected pages can be published right now. Select one at a time to see why." (and the same for Archive). Each action opens a confirmation. The Publish confirmation counts how many of the pages stay hidden from search. Bulk publish changes nothing about search: each page keeps its state, and you change it on the page. Pages that cannot take the action are left out and listed with the reason, for example a page that is Managed in Shopify for Publish and Archive. Delete keeps a page that an ad still points to, and the failure card names the ad. On a page that is Managed in Shopify, Delete removes only the Commander copy. When Delete leaves a page in Shopify, the message names it: "Deleted from Commander. The page in Shopify was left in place." A page that cannot be deleted for now is listed with the reason, for example "Commander is busy with this page's ad. Try again in a minute." A failure card lists the pages that could not be done, and they stay selected so you can try again.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| A Draft card | Open it, review it and publish it. | ecommerce manager |
| A Live card | Send your ads to the page. This happens outside this page. | media buyer |
| A Generating card | Wait. The card turns into a page. | ecommerce manager |
| Fix issues | Open the page and fix what is wrong, for example a page that is about another product than its ad. Then publish it. A publish that is refused reads "Fix the page before publishing". | ecommerce manager |
| Unpublished changes and Review changes | Open the page, read the changes and select Publish changes, or discard them. See Landing page editor. | ecommerce manager |
| Edited in Shopify | Open the page and select Sync from Shopify to bring the change into Commander. | ecommerce manager |
| Managed in Shopify | Nothing to do. Commander no longer changes the page. Open it to go back to the Commander version. | ecommerce manager |
| Basic layout on a card | Connect Theme Access if you want full-width pages. | ecommerce manager |
| Relearn suggested | Select the chip, then Relearn in the Your store's style window. | ecommerce manager |
| Relearn needed or Couldn't learn style | Select Relearn or Try again in the banner. If it keeps failing, follow the reason, or select Use previous style. | ecommerce manager |
| Updating style | Keep working. New pages use the current style until the update is saved. | ecommerce manager |
| Taking longer than usual | While a new theme is learned, select Try again in the banner. With a usable style, select the chip, then Relearn in the Your store's style window. In the New landing page flow, select Try again in the step. | ecommerce manager |
| Couldn't update style | Select the chip, then Try again in the Your store's style window. New pages keep using the style Commander learned before. | ecommerce manager |
| Previous generator | Remodel the page in the editor before you publish it. | ecommerce manager |
| An Archived card (under More filters > Pages: Archived) | Restore it, or delete it. | ecommerce manager |
Expected value and measurement
A landing page that repeats the promise of the ad can help visitors see that they reached the right place.
To check, compare the ads that point at a Commander page with the ads that point elsewhere. Open Performance > Ad performance and read the spend and the revenue for each. See Ad performance. Use your own analytics for conversion. You cannot isolate the page from other changes, such as new creatives, audiences or offers, that ran at the same time.
Subscription and prepaid options
When your product sells subscription or prepaid plans in Shopify, the page's buy box offers them as your product page does: the same plans for each size, the same plan sent to the cart, and the amount charged. A plan that charges once for several deliveries shows what is charged. When your store or your product page states how many deliveries one charge covers, the page also shows the price of one delivery, the price without the plan and the saving. When the count is not stated anywhere, the page shows the plan's charge and name without those figures. Commander copies your product page's own plan names, perks and notes when it can read them.
Product options in the buy box
When your product has options, such as Size or Color, the page's buy box gives each option its own group of choices. An option with only one value shows no choice, because there is nothing to pick. When a shopper picks a value that does not combine with the other choices, the page moves those choices to an available one.
When Commander draws the preview itself, it shows the groups the live page shows. If Commander cannot read the product's options, it shows one list of every choice instead. It shows the page as it first appears, so choosing a value there does not update the rest of the buy box. To try the choices, select Open page in the landing page editor, or open the live page. See Landing page editor.
Limitations and exceptions
- AI writes each page and can be wrong. Review every page before you publish it.
- A remodel needs a note that says what to change. It does what the note asks. Before you keep it, it lists the code on the page, with where each part came from, and the parts to check, such as the Add to cart form, prices and testimonials. The list never blocks Publish remodel. See Landing page editor.
- A page that goes live through Commander is hidden from search engines and your store's search unless you show it. Anyone with the link can still open it. Search engines can take a few days to catch up when you change it. Links that point at a hidden page do not pass their weight to your product page, so point the links you build at the product page. A page that went live before this may be visible to search engines: open the page and check its ⋯ menu. See Landing page editor.
- A review card can show the reviewer's first name and last initial, or, when the name has no first name, a title and an initial ("Mrs W.") or two initials ("J. S."), with Verified buyer when the review app marks the review as verified. The name comes from Commander's stored copy of the review and is added when the page is previewed or published, so AI never reads or writes it. A published page shows a name that arrives later after you next publish changes to it or generate it again. Reviews that Commander held before names were stored show Verified buyer only, until the review app sends them again. A name that cannot be shortened safely to a first name and an initial, such as one written in Chinese, Japanese or Korean characters, a title with a family name only, a title alone, or a label such as "Verified buyer", is not shown. See Connect a review app or import reviews from CSV.
- Learning can fail. The banner reads We couldn't learn your store's style with the reason, and a failed Create reads "Your page wasn't started." Select Try again. Without a usable style, pages wait. A failed press that left no reason reads "Commander couldn't start learning your store's style. Try again in a few minutes." A background update that fails keeps your current style and shows Couldn't update style on the chip.
- Commander compares your theme only when you open Landing pages or a place that starts a page. Changes that do not affect how pages look, such as translations or a template other than your home or product page, never start a learn. A small change to a theme that is not big enough is not picked up until you select Relearn.
- Use previous style makes new pages use an earlier theme's style, so they may not match your new theme. It is offered only after a failed learn, and it covers only the theme you chose it on.
- Generation can stop at a limit. The dialog says "You have reached the hourly limit for landing pages." or "Too many requests. Try again in a few minutes." When a run asks for more than the hour allows, it can also say how many more pages you can generate this hour, and when you can try again. When a start fails, the dialog shows the reason, or "Could not start landing page generation. Nothing was charged."
- An ad can have several pages, from the wizard and from the Generate landing page dialog, for an imported ad and for an ad that Commander generated. Each page gets its own address, and each one uses credits. For an ad that already has a page, the wizard names it: "«{page}» is this ad's page. Create makes a second page. {ad} keeps linking to «{page}» until you choose the new one." Open «{page}» opens that page. While the page's name is not available, the wizard says "This ad already has a page. Create makes a second page. The ad keeps linking to it until you choose the new one." with Open it. The button reads Review and create second page, and the confirm button Create second page, with the cost.
- An ad sends people to one of its pages, the ad's page. Its first page becomes the ad's page by itself. A later page never does: the ad keeps its page until you choose another one. Choose it on the ad's Landing page tab, on the new page's own screen, or when you deploy the ad. See Landing page editor and Ad detail.
- When the ad's page is archived, the ad keeps linking to it, and the archived address redirects. The next page you create for that ad becomes the ad's page in Commander when the ad has no other page that is not archived. The ad's live link changes only when you change it in your ad platform. Make this the ad's page changes only Commander's pick, and How to point it here shows the steps for the link.
- In the New landing page wizard, Commander removes the words from an ad's picture before the page opens on it, so your headline is the only text on the picture. The whole ad keeps the ad's words.
- If Commander cannot remove them, the page opens on the product photo, or on the ad's picture as it is.
- The bulk Generate landing pages dialog does not remove the words from an imported ad's picture.
- The Product filter and a search by product only find ads that Commander linked to a product.
- A list that does not load reads "We couldn't load your landing pages. Reload to try again."
When the list is empty
With no pages, the list reads No landing pages yet, "Create one from an ad, a product or your brand. Pages made from an ad keep its headline and image.", and offers New landing page. If filters hide every page, it reads No landing pages match these filters and "Try another search, product or filter." Select Clear filters.
Demo Mode
In Demo Mode, the list shows sample pages. Creating a page and generating pages from ads are blocked and show a message. The bulk dialog says the action is simulated, and the pages stay as they are. The address bar on a card shows no copy icon. See Demo Mode.