The Landing Page Editor: Drag, Drop & Publish

Build your homepage and campaign pages by assembling ready-made sections on a live canvas, preview across devices, and publish when you're ready.

The Landing Page Editor is where you build your storefront's homepage — and any additional campaign page — by stacking ready-made sections on a canvas. There's no code involved: you add a section, fill in its content, and arrange it wherever you want on the page.

Screen: Online Store → Pages, then open the "pages you build" card. Inside the editor, the Landing Page ▾ control in the command bar opens a page switcher — see Switching between your store's pages below for what it does today.

The left rail: Add, Scenes, Brand

The left edge of the editor is a narrow, always-visible icon rail with three buttons — it starts collapsed on every fresh visit to the editor (it's a session-only choice, not something the editor remembers from last time):

• + (Add) — opens the section library immediately, without expanding the rail. See The Section Library for the full catalogue.
• ☰ (Scenes) — expands the rail into the full section list, renamed Scenes. Page name, SEO, and theme settings live in their own drawers (below) — this panel's only job is the section stack.
• Brand — opens the Brand drawer on the right (colours, fonts, spacing, and Brand Kit) without touching the rail at all. See Theme presets.

Once expanded, each section in the list can be:

• Selected — tap the row to jump to and select that section on the canvas.
• Reordered — the ↑ / ↓ arrows on the row move it up or down the stack (the preview rebuilds in real time); you can still drag a row to a new position too.
• Hidden — the eye icon toggles a section off without deleting it, useful for seasonal content you'll want back later. All three controls — jump, reorder, hide — are visible on the row at all times; you don't need to hover to find them.
• Duplicated — clone a section with its content and style intact, then tweak the copy, from the row's own menu.
• Deleted — with a confirmation prompt before it's gone, also from the row's menu.

Switching between your store's pages

Click Landing Page ▾ in the command bar to open Every page of your store — a single modal listing every page type BillionBiz can edit, grouped into seven categories (Home, Browse, Buy, Complete, Account, Content, Chrome), 24 page types in total: everything from your homepage and product/category pages through cart, checkout, account screens, About/Contact, and site chrome (header, footer, cookie/consent banner, toast notifications). Each type shows as a rounded pill; the page you're currently editing shows filled, the rest are quiet. Click any pill to jump straight into that page type's editor.

When you switch to Browse → Product, the Product page's right-side Design lens includes a Preview product section. Search for a real catalogue product, select it, and—when it has more than one variant—try a variant against the live canvas. The same tool also exists in the existing page-layout editor's left-sidebar Design tab. See Preview a real product and variant for the complete workflow, product-page-only behavior, and troubleshooting.

Cookie consent banner

Open Landing Page ▾, then under Chrome click the Cookie / Consent pill to edit the banner that asks your visitors about cookies. It is one of the store-wide "Chrome" pages, next to Header, Footer and Toast notifications.

The slim bar: what new stores get

A store that has never saved a consent layout (its saved variant is empty, the placeholder default, or not one of the known layouts) gets the slim bar:

• One line, floating at the bottom. A single sentence (default: "We use cookies to improve your experience.") plus a Privacy Policy link, and three buttons: Manage preferences, Reject all and Accept all (the button labels are the defaults; your saved wording wins).
• Manage preferences opens a small dialog. It lists Strictly necessary (always on, locked), Analytics, Marketing and Functional as switches, with Cancel and Save preferences. Pressing Escape, clicking the dimmed area, or Cancel closes it without saving. Save preferences stores the visitor's choice and hides the bar; it records "granted" if Analytics is switched on and "declined" otherwise.
• The page reserves only the bar's height. While the bar is showing, the storefront adds bottom space equal to the bar's real height, capped at 35% of the window height, so the bar never hides your footer or last row of content. The space disappears when the visitor answers.
• On a phone (640px wide or less) the sentence and the buttons stack on separate rows and the three buttons share the row equally.
• A button only appears if the layout's capabilities include it (Accept all, Reject all, Manage). The bar always keeps Accept all if it would otherwise have no way to be dismissed.

Which layout can you pick?

There is no control in the editor that selects the slim bar. The Cookie / Consent template gallery offers ready-made presets such as Minimal Banner, Boutique Modal, Glass Drawer, Editorial Corner Pill and Bastion Takeover; each is bound to one of the older layouts (banner, modal, drawer, corner pill, fullscreen), and none of them is the slim bar. So:

• If you have never applied a consent preset, you get the slim bar automatically.
• If you apply a preset, that preset's layout replaces the slim bar for your store.
• A store that had already saved one of those layouts keeps it exactly as before; stores are not switched to the slim bar behind your back.
• If a store has no cookie-banner configuration at all, the storefront falls back to its built-in classic banner rather than the slim bar.

Selecting and editing a section

Move your mouse over a section on the canvas and a thin dashed outline appears around it with its name in a small tag, both faded to about half strength — this is a hover hint, not a selection, so it can never be mistaken for one. Click any section directly on the canvas (not in the section list — right on the live preview) to select it: the outline switches to a solid line with a soft glow and the name tag becomes fully opaque — with several similar-looking sections on a page, this is how you confirm you've actually selected the one you meant to. A floating toolbar docks next to the selected section at the same time.

The toolbar's buttons are specific to what that section type actually supports — you won't see a button for something the section can't do:

• Words — for sections with plain-text fields (headline, eyebrow, subheading, button label), opens a small popover next to the section focused on those fields.
• Looks — for sections with more than one layout, opens a popover with the layout thumbnails.
• Photos — for sections with an image field, opens a popover to swap it.
• ↑ / ↓ — move the section up or down the stack.
• Hide / Show — toggle visibility, same as the eye icon in Scenes.
• Copy — duplicate the section, same as the row's own menu.
• All settings — opens the full per-section editor (below).

A section with none of Words, Looks, or Photos (a purely structural section, for example) simply doesn't show those chips — use All settings for anything it needs. There's no Delete button on this toolbar itself, and no keyboard shortcut for it yet either — delete a section from its Scenes row's own ••• menu.

Click All settings (on the toolbar) to open the full per-section editor — a floating card docked to one side of the canvas, titled with the section's human name (same name as its Scenes row) and a sub-line reading "Follows your brand kit · N changes", where N is how many fields you've actually changed away from their defaults.

Below the header sits a segmented control with three lenses — Content, Design, Behaviour — pick one to filter which control groups show underneath. There's no fourth "All" tab: an earlier version had one, but it made every panel open front-load every tab's controls at once, so it was dropped — searching (below) is now how you reach something outside the active lens. A lens with nothing to show for this section type (for example, a section with no A/B test support) is disabled with a tooltip explaining why, rather than switching to something else silently.

Under the active lens, a "Your changes — everything else follows the brand" callout lists exactly the fields you've changed for that lens. It reads "Nothing yet. Change anything below and it appears here, revertable forever." until you change something; once you have, it shows a collapsed "N changed in this lens" row — click it to expand the list. Each changed field shows its label in bold, its current value underneath, and a ⟲ (revert to default) button on the right that snaps just that one field back to the brand default.

Below the header sits a search field — "Search this section's controls…" — that filters the group list live as you type, matching a group's category name, its label, or the text of any control inside it. A matching group opens automatically as you type (search auto-expands hits, it doesn't just narrow the list) and stays scoped to whichever lens tab you're on; controls inside a matching group that don't themselves match the search text are dimmed rather than hidden, so you can still see them in context. Clearing the box (or switching tabs) brings back the full list.

Below that is a stack of control groups, each its own card — human names, not field jargon — with a count of the controls inside it shown at the right of its header row: Words, Media, Sale badge, Container, Backdrop & overlay, Typography, Buttons, Shadow & motion, Visibility, A/B test, and more, depending on what the section supports. If any control inside a group has been changed from the brand default, that group's title also picks up an accent-coloured "· N changed" suffix right next to its name — a group you haven't touched stays plain. When two or more groups belong to the same category and land next to each other, only the first one carries a small uppercase category label above it — the rest of that run reads as belonging to the same category without repeating the label. Click a group's card to expand it and edit its controls; not every section has every group, and a section with a layout choice (grid vs. list vs. carousel, and similar) has its variant picker rendered as a row of pictogram thumbnail cards above the group list, not a dropdown.

Inside a group, the controls themselves are picked to match what they're choosing, not a generic dropdown for everything:

• A small, fixed set of choices (Section Padding is the one you'll see most — None, Small, Medium, Large) renders as a row of equal-width pills in one rounded track, each with a small sublabel underneath its name (Section Padding's pills show 0px / ~32px / ~64px / ~96px) so you can see roughly what you're picking before you click it. The selected pill fills solid in your accent colour.
• A continuous number (spacing, sizing, and similar) renders as a slider with a number field next to it — drag the slider or type an exact number, and the current value (with its unit, where one applies) is shown live next to the control's label as you move it, not just once you let go.
• Store content renders as an entity picker. Choose its Choose product, Choose category, Choose collection, Choose review, or Choose product video action, then use Search… to find records in the current store. A multi-select picker keeps the chosen rows in storefront order: use Move up or Move down to reorder them, or Remove to take one out of the section without deleting its source record. Where a picker supports snapshots, each row also has a Live / Pinned control labelled Live or pinned. Pinned freezes only the display fields listed in the Live or Pinned table; the remaining product, availability, and eligibility data stays live.
• A colour opens a picker with a row of preset swatches — the swatch matching your current colour shows a thicker, accent-coloured border around it so you can spot which preset (if any) you're already on; picking a different swatch, or typing a hex value above the row, moves that border to the new one.

Header and Footer inspector task groups

When the page switcher is on Chrome → Header or Chrome → Footer, the right inspector uses the same Content, Design, and Behaviour lenses, but its groups are named for the merchant task rather than the underlying data field:

The selection matters: the whole Header/Footer, a row, and a child block expose different subsets. Open one group at a time; the panel remembers which group was open for that subject and lens during the current editor session. The old internal headings “Axes” and “Capabilities”, the standalone “Appearance” group, and nested labels such as “Slot layout” are no longer the navigation terms.

Use Search this block's controls with an outcome such as “background”, “font”, “sticky”, “cart”, or “mobile”; group synonyms participate in the search. Use the N changed filter to show only edited controls in the active lens. If a result is missing, clear both filters, confirm the correct Header/Footer row or block is selected, and try the task's other lens.

Click Done at the bottom of the card (or press Esc) to close it. Done only closes the card — it doesn't save anything itself, and no confirmation toast appears when you click it. Every edit you make is already written to your draft the moment you type it, the same way canvas edits are; saving to the server still runs on its own schedule (autosave) or when you click the header Save/Publish button, same as everywhere else in the editor.

Choosing referenced store content

Screen: Online Store → Store Editor → open the page → select a section → open the inspector group that contains the reference field. The group and field label depend on the section. For example, product-backed video sections use Video source → Product videos or Which videos to show → Product videos; Testimonial Rich Carousel uses Review source → Review filters → Product (optional).

Choose the field's Choose product, Choose category, Choose collection, Choose review, or Choose product video action. Search results come from the current store; select a result to save it. Every Feature Gaps field backed by the v3 entity picker saves the selected record's ID. A Live row saves no display copy, so the storefront uses the current source record when it renders. A Pinned row also saves a limited display snapshot. See Per-item Live or Pinned snapshots for what is preserved, what always stays live, and how to refresh or remove a snapshot.

In that selected list you can:

• use Move up or Move down to change the storefront order when the field accepts multiple records; and
• use the remove control to stop referencing an item without deleting the source record.

Opening a picker, searching, or closing it without choosing anything does not change the section. A failed search also leaves the saved selection unchanged. Product, category, and collection references attempt to resolve saved IDs to readable names; if a saved ID cannot be resolved, the picker keeps it visible instead of silently clearing it. Review and product-video pickers also preserve their saved IDs. Replace or remove a stale selection deliberately.

Published reference-backed sections resolve their selected products, categories, collections, reviews, offers, product videos, and other supported records at runtime. Each data family loads independently: if one source is unavailable, sections backed by other sources can still render. This is why a review section can be empty while a product section on the same page remains healthy. Check the affected source record and that section's filters before republishing unrelated content.

The Layout group, and why Width sometimes isn't there

Most sections carry a Layout group under the Design lens, holding controls like Width (Narrow / Standard / Wide / Full, with an edge-to-edge hint that also needs Padding set to 0 on all sides), Alignment, columns, and spacing. Not every section shows every one of these — a control only appears when it actually does something for that section's layout, so a section with no concept of "columns" simply has no Columns control, rather than showing one that silently does nothing.

Image Gallery is a concrete example of this: its Layout group's Card size control only shows for the Masonry, Grid, Fixed Rows, Auto Rows, and Infinite Scroll layouts — the ones whose renderer actually reads a card-size value. Switch the gallery's own layout picker to the absorbed Collage Mosaic, Image Collage, or Customer Photo Wall look and both Card size and Alignment disappear from the Layout group entirely, because those looks arrange their tiles with their own fixed layout logic that ignores both fields.

The Image Shape control (aspect ratio / crop for a section's photos) lives under the Design lens too, inside its own group, not under Content where the image itself is picked.

Set the gap between cards and the section padding

Seven sections have a spacing control in their Layout group that now changes what shoppers see: Shop by Category, Why Us, Best Selling, New Arrivals, Flash Sale, Category Circles and UGC Gallery. Before the fix a few of these edits saved but did not move anything on the page.

One "View all link" control

Featured Collection, Best Selling, New Arrivals, Flash Sale, Recently Viewed, Shop by Category and Trending Now each have a single View all link group under Content: Show view all link, Link URL and Link text. The older separate show/text/link controls that used to sit beside it are gone, so there is one place to set it. A section saved before this change keeps showing its existing view-all link, and the group opens with those old values filled in; your first edit there carries them over.

Keep section shadows and hero transitions separate

Screen: Online Store → Landing Page Editor → select a section → All settings → Design → Shadow → Shadow. Choose None, Soft, Medium or Bold to change the saved section shadow. These are outer shadows around the section's painted area. On a boxed section, the shadow follows that box along with its saved background and border. It does not add an inset wash over the content or change shadows belonging to a product card or image. For those, use the section's specific card or media controls instead.

Preview the section against the neighboring background before publishing. If an image still has its own shadow after the section Shadow is None, check that image's controls. If the section looks narrower than expected, inspect Design → Layout → Width and its padding; changing Shadow does not make a boxed section full width.

New hero and section transitions use the current background-band treatment without automatically adding the previous wave. An existing page with its previous transition explicitly preserved can retain that wave; preservation is specific to that page. Before publishing changes to an established page, compare the hero's lower edge and the next section in desktop and mobile preview. If you expected its previous wave and the preview differs, contact support before publishing.

A featured product is visible in the editor but missing on the storefront

Screen: Online Store → Landing Page Editor → select Featured Product → All settings → Content → Product → Product to feature. Choose a real product, then Save and Publish. On the standard Featured Product presentation, Pick a product is editor guidance when the source cannot resolve; it is not a storefront product. A deleted product must be replaced in the picker.

For Featured Collection, check Content → Products shown → Products to show or Collection, and each tab's collection when applicable. An empty Sale/New filter or one empty tab can still leave navigation available when other real products exist. Return to All or a populated tab before concluding that the source is missing. See Restore a missing source for precedence, empty-source behavior and published-page checks.

Scheduling a section's visibility

A section's Visibility group includes a start/end schedule — show a section only between two dates/times. Both times are in your store's own timezone (Settings → Store settings), not your browser's local timezone: type a wall-clock time and it goes live/hides at that moment in the store's configured zone, the same way a customer visiting the store experiences it.

Screen: Online Store → Landing Page Editor → select a section → All settings → Behaviour → Schedule. Set Visible from and Visible until to define the visibility window. A start in the past, an end earlier than the start, or an end in the past produces a validation message. Check these values and the displayed Store time before publishing.

The input stays disabled while the store timezone loads. A hung settings request falls back after 5 seconds to Asia/Kolkata; an invalid or failed response can trigger the fallback sooner. The warning says Store time could not be loaded. Using Asia/Kolkata; check the time before saving. Confirm the intended store timezone before entering a deadline. If valid settings arrive later, the displayed timezone updates without changing the saved instant. Clearing a date clears that boundary. These same safeguards apply to the family-member End time controls in the Section library.

Add section on a long page, and family-member names

Screen: Online Store → Landing Page Editor → left rail section list → Add section.

Choosing a component look

Some sections let you restyle one recurring piece of the section (its heading, its cards, its announcement message, its video) by picking a curated look instead of adjusting every control by hand. This is the component look picker.

Screen: Online Store → Landing Page Editor → select a section → All settings → Design.

The group titles include Heading look, Carousel controls, Media look, Call to action look, Tab navigation look, Form input look, Announcement bar, Price look, Card text look, Meta stack look, and a card group named for its family, such as Product card look. Price applies to product cards; card-specific Meta stack groups apply to product and category cards. Content groups can change name, such as Media content options; the media Behaviour group is Video playback.

What is inside a group

• In Design, each curated tile shows its name and description. Custom appears when your settings do not match a tile. Manual settings stay intact when you switch looks.
• Individual dropdowns offer Default and show Use component default when unset; on/off settings use switches. More than six visible controls puts the remainder under Advanced.
• Reset look in Design clears the controls the look manages, including any you changed by hand, and also clears the look selection itself. Reset design clears its appearance controls and the look selection. These actions are draft edits.

With no look chosen, or the default look, all eligible controls are available in their respective lenses. A non-default look shows the controls it uses plus those you already changed manually. Video-only controls are hidden while the resolved media settings are for an image. The Announcement bar and Free shipping banner retain their specialised editors described below.

Card display toggles. Every card group has five on/off switches that decide which pieces of the card are drawn: Show badge, Show tagline, Show rating, Show compare-at price and Show discount percent. They sit in the Content lens (not Design), inside the card group for the section, for example Product card look. They are shown whatever look you pick, including looks that do not set them.

What each switch does: Show badge shows or hides the card's badge (the badge label, or the discount badge). Show tagline shows or hides the card's subtitle line. Show rating shows or hides the star rating together with its review count (there is no separate count switch). Show compare-at price shows or hides the struck-through original price. Show discount percent shows or hides the percent-off chip, independently of the struck price.

A switch you have flipped is a saved override, so it keeps its value even if you later pick a different look, and flipping it back to the look's value still leaves it saved as your own choice (it does not return to following the look). To hand the switches back to the look, use Reset look in the Design lens of the same group: it clears every control that the look manages, including these five switches and any other hand-changed control in the group, and also clears the look selection itself, so you pick a look again afterwards. There is no per-switch reset.

A switch the selected look does not set shows the standard card default (On), without a From look caption. In the item groups of Category Circles and Shop by Category, an item with its own card override shows the same switches and an unset one shows On.

Carousel chrome. Once a section uses a carousel look (you picked a tile or changed a control in the Carousel chrome group), its arrows, dots, progress bar and autoplay control are drawn by the component look. The arrows and dots stay visible even when every item already fits on screen: there is no editor control that hides them automatically, so a section with few items can still show arrows that have nothing to scroll. Items shown at once come from the section's items-per-view settings (1 on mobile, 3 on tablet, 4 on desktop when unset). The breakpoints are phone up to 767 px, tablet 768 to 1023 px, desktop 1024 px and up. Hero Carousel always shows one slide at a time. Sections that have never had a carousel look picked are unchanged and keep their original arrows and dots.

Which value wins. For each component the editor picks the first of these that exists, from the narrowest to the widest:

1. The item's own look, for one item in a repeating section (see below).
2. The look set for that kind of item across the section.
3. The section-wide look for that component.
4. The section's original settings, and finally the plain default.

Values are chosen as a whole set per step, not control by control, and a look tile you pick doesn't erase controls you already changed: hand-changed controls stay while you switch tiles. If a hand-changed control seems to override the look tile you picked, use Reset look, then select the desired tile again. Reset look also clears the current look selection.

Looks for individual items. Sections made of repeating items show a group per item. In composite sections the group is titled Item 1 · Product, Item 2 · Category, and so on (kinds: Product, Category, Brand, Media, Testimonial, Before and after, Offer, Custom). In Category Circles and Shop by Category the groups are just Item 1, Item 2. The caption says either that the item overrides the section card look, or that it inherits the section card look until you choose one.

• The first change you make to an item copies the section value onto the item, so from then on the item is independent of later section-level changes.
• Use section default removes the item's override and the item follows the section again. Picking the default card look on an item does the same.
• Which panels an item gets depends on its kind: product items get Card, Price and Meta stack; category and brand items get Card and Meta stack; offer items get Card; media items get Media (plus Hotspots when the item has hotspots); testimonial items get Testimonial and Quote; before/after items get one Before and after panel. A custom item shows the note that it inherits section defaults because no restricted look family is declared for that kind.
• On Category Circles and Shop by Category each item shows a badge, Item override or Section default, with Edit item card look to start an override and Use section card look to remove it (disabled while the item has none).

Composite sections. Composite carousel, grid, marquee, split, stack and tabs sections add a section-level editor above the item groups. Choose a preset from the thumbnail tiles in Design; edit the items, Eyebrow, Title, and Subtitle in Content. Layout controls live in Design, and each item has Item kind, Card design, Tab label (tabs layout only) and Revert item overrides. Card design offers Standard (default), Featured commerce, Category circle, Editorial tile, Overlay tile and Promo overlay. The Surface material choice (Flat or Glass) is not in this editor: open the item's own card picker and use the Inspector’s Design lens. For sample-content reminders and the tabs Image shape control, follow Composite presets and sample content.

Announcement bar. The Announcement bar section has its own editor. It shows five look tiles (Single Message, Single Message + CTA, Message + Countdown, Marquee, Slide Messages) with Reset look in the Inspector's Design lens. Use the same Inspector's Content, Design, and Behaviour lenses; there is no second set of tabs inside this group. Each look shows only the fields it needs. In Content use Add announcement to add a message; each message can be duplicated, moved up or down, or removed. The Behaviour tab covers Remember dismissal, Hide on scroll, Pause on hover, Rotation interval, and what happens when a countdown ends (When countdown ends, Replacement message).

Free shipping banner. The Free shipping banner section shows its own look tiles (Current Banner, Progress to Threshold, Coupon Copy, Limited-Time Countdown, Dark Premium) without tabs. Below them are the content fields the chosen look uses (some of Message, Threshold amount, Preview cart amount, Currency symbol, Coupon code, Coupon label, Countdown end). Use current section look is disabled until you have chosen a look.

Card looks: what each card family offers. Product card looks are Default, Editorial Quiet, Minimal, Bold and Featured commerce. Category card looks are Default, Category circle, Editorial tile, Overlay tile and Promo overlay. Offer card looks are Offer Badge Grid, Premium Offer Cards, Ribbon Style, Festive Badge Style, Minimal Discount Tiles, Spotlight Offers, Flash Deal Strip and Category Offer Tiles.

Card looks need universal cards. Card looks, designs and materials only change the storefront for sections that use universal cards. A section uses classic (Legacy) cards until its Card system is set to Universal (unset means classic). The editor keeps the card tiles disabled until you explicitly switch. This applies to Best Selling Products, Trending Now, Recently Viewed, New Arrivals, Flash Sale, Featured Collection, Tabbed Products, Category Circles, Shop by Category and Promo Tiles. On a Legacy section the card group shows the notice Card looks apply to universal cards. This section uses classic cards. above the tiles. That group's look tiles and controls are dimmed and disabled, and a Switch to universal cards button appears. Click it to turn the section's Card system to Universal, then pick a look. Switching is an ordinary draft edit: you can undo it, it autosaves, and the storefront only changes after you Publish. Other component groups and the Inspector's tabs remain usable; this notice does not disable the whole section. Choosing a card tile does not switch card systems for you.

Shade Finder behaves differently. It shows no notice: its layout, hover, price and meta stack controls apply under either card system, and it has no design or material controls. Promo Tiles uses the same explicit switch as the other classic-card sections; after switching, choose an offer look and save the draft.

Saving. Choosing a look or changing a control updates your working draft. Use the top-bar Save control and check the save status. Publish saves the current draft before publishing; if that save fails, publishing stops. Nothing reaches your live store until publishing succeeds.

Troubleshooting

• "Why don't customers see my card look?" Check three things in order. First, the section must use universal cards: a section on classic (Legacy) cards ignores card looks, designs and materials, and shows the notice above until you click Switch to universal cards. Second, you must Publish: the switch and the look are draft edits until then. Third, an item may carry its own override that beats the section look (use Use section default).
• "Why don't I see a look picker on this section?" Only sections whose look catalog has options and a supported component host get a group in the Design lens. Call to action look is available on supported sections, including Newsletter CTA and Hero Banner; other sections may not contain a component that has a look picker. The Section library lists the sections that do. Also make sure you are on the Design lens, not Content or Behaviour.
• "I picked a look but a field I customised didn't change." A control you set by hand stays while you switch looks. Open the group and use Reset look, then select the desired tile again. Reset design in the Design lens also clears the look selection along with its appearance overrides. For a single item, use Use section default.
• "The item I edited ignores my section look." The item has its own override (its badge or caption says so). Use Use section default or Use section card look on that item.
• "Why doesn't my badge (or tagline, rating, compare-at price, discount percent) show?" Check in order. First, the section must use universal cards, because classic (Legacy) cards ignore these switches. Second, open the card group in the Content lens and check the switch: a look such as Minimal turns all five Off, and a switch you flipped Off earlier stays Off when you change looks, so if there is no From look caption it is your own saved choice. Third, Publish: switch changes are draft edits until then.
• "Why don't I see arrows or dots?" Check that the section has more than one item and that its own arrow and dot switches (for example Show scroll arrows on Trending Now) are on. The component look does not hide arrows or dots automatically when every item fits, so a missing control is a setting or an item-count issue, not a fit rule. On a section with no carousel look picked, the original arrows and dots are unchanged.
• "A control I expected is missing." After you pick a non-default look only that look's controls are listed, along with controls you changed manually. Choose the default look and check the appropriate Inspector lens. Clear Search this section's controls… if you have filtered it.
• Trending Now layout. The Layout setting (Horizontal scroll or Grid) on Trending Now changes the storefront only for carousel chrome: the carousel look's arrows, dots and autoplay are drawn only when Layout is Horizontal scroll. With Grid, those carousel controls do not appear.

Dropdown settings, empty lists and popup triggers

A few section settings that used to be missing or free text are now proper controls in All settings. Screen: Online Store → Landing Page Editor → select a section → All settings.

Settings with a fixed set of choices are dropdowns. If a section setting only accepts a closed set of values (for example a gap, a section padding, a height preset or a light/dark text colour), the inspector draws it from the section's own list of allowed values rather than a text box. These controls appear in the Fields group of the Content lens, for sections that do not already have a purpose-built control for that setting. The label is the setting's name in sentence case.

• A setting with four or fewer choices is a segmented strip of buttons; a setting with more than four choices is a dropdown. Both write the same saved value.
• If the section already holds a value that is not one of the allowed choices (for example from an older version or an imported template), that value is added to the end of the list and stays selected, so nothing is silently dropped. Pick an allowed choice to replace it.
• Settings grouped inside a block, such as an image's description or a trigger's kind, appear as their own rows named after the setting.

Add an item to any list. Lists of repeated items (cards, slides, rows) are drawn as a group named after the list, with an Add button. Add now works on every such list, including one saved with no items at all: it appends a blank item that already has the fields the section needs, so the new item is valid straight away. A list that only holds a plain reference (such as a list of product ids) is not drawn here, because those need a product or collection picker.

Popup trigger (Newsletter popup and Announcement popup). Screen: Online Store → Landing Page Editor → select the popup section → All settings → Behaviour → Playback & countdown → Popup trigger.

Switching between When the page opens and After a delay converts the saved number so the wait stays the same: 5000 milliseconds becomes 5 seconds, and 5 seconds becomes 5000 milliseconds. Switching to or from the other two options leaves the number as it is.

Loyalty program benefits are edited as a list of lines. Under Content → Content details, Benefits has one text row per benefit; use Add to append a line. An empty line is not added.

Troubleshooting

• "My popup doesn't show." Check the section is not hidden, then check Popup trigger. With After scrolling down, the page must be long enough to scroll to the depth you set. With When the visitor is about to leave it will not appear just from opening the page, so test it with the option that matches what you set. Changes are draft edits until you Publish.
• "My delay is a thousand times too long or short." Delay is seconds for After a delay and milliseconds for When the page opens. Re-pick the option so the number converts, or type the value in the unit shown on the field label.
• "I can't find a setting as a dropdown." Sections with a purpose-built control for that setting keep it in their own group (for example under Design) instead of Fields. Clear Search this section's controls… if you have filtered the list.
• "There is no Add button." The list is probably a list of plain references (products or collections), which are chosen with a picker instead.

Style media without replacing your content

Screen: Online Store → Landing Page Editor → select a media section → All settings → Design → Media look. For example, select Hero Video, or choose the Image + Text Slideshow family member to style its existing slide images.

Controls follow the selected look and source settings: some appear only after you choose an applicable tile, and video-only controls are hidden for image settings. Image-focused members such as 3D / AR Viewer style the fallback still image; a media look does not replace its model or interactive scene. If you also use a carousel look, its navigation remains a separate component.

Put a media item's button, overlay text or badge on the image. In a composite section (Carousel, Grid, Marquee, Split, Stack or Tabs), each media item has four optional text fields. Without the settings below, the button sits in the text block under the image and the overlay fields show nothing.

Edge cases: a button only exists when Button label is filled in, so with no label nothing shows on the image or below it. The overlay fields appear only when the matching switch is on (the switches are off by default), and an empty field shows nothing even with its switch on. Turning a switch on never creates the text, badge or destination. With CTA on media off, or never set, the button stays in the text block below the image.

Troubleshooting. "I turned on CTA on media and see no button": Button label is empty on that media item. "My overlay text or badge does not show": check that the field is filled on the item and that Overlay text or Overlay badge is on under Content → Media content options; the Clean look turns both off, and Reel has no badge while Product video card has no overlay text. "The button is still below the image": CTA on media is off for that section; a look tile you chose afterwards can reset it, but only if the value came from the previous look (a switch you set by hand stays), so reselect your look first and then check Content → Media content options → CTA on media.

Give buttons a shared look

Screen: Online Store → Landing Page Editor → select Newsletter CTA → All settings → Design → Call to action look. Hero Banner also offers this group for its supported action links. Availability follows the section's supported components; a look changes an existing action's presentation.

Manual controls and section button styling can take precedence over the look. Reset look clears the look selection and its managed overrides; select the tile again to apply its recipe. Reset design clears its appearance overrides and the look selection. Some media-led sections acquire coordinated button styling when a non-original component look is active; your explicit CTA choices still take precedence over those defaults. Size Guide CTA's shared button styling belongs to its active crafted presentation, so check the chosen presentation as well as the button look rather than assuming every original layout changes.

Content, Design and Behaviour tabs: where a control lives

In the current Store Editor (v3; live on UAT, the legacy editor on production keeps its own tabs), a selected section's inspector is split into Content, Design and Behaviour tabs. Content holds what the section says, Design holds how it looks, and Behaviour holds how it acts. The last group on the Behaviour tab is a collapsed Advanced group, and a section with slides lists the slides first.

Fifteen groups changed tabs in the current editor. Each one leaves a pointer on its old tab (see step 1) that switches to the new tab, focuses the group and opens it. Every other group stays where it was.

• Collapsible Content: Dividers moved from Behaviour to Design.
• Content Slider: Navigation & loop moved from Design to Behaviour.
• Divider: Divider size & style moved from Content to Design.
• FAQ, including FAQ Rich's inspector: Dividers moved from Content to Design.
• Hero Carousel: Height & image darkening and Section width moved from Content to Design; Dots & arrows moved from Content to Behaviour.
• Hero Banner: Position & width moved from Content to Design.
• Hero Split: Position & width moved from Content to Design.
• Hero Video: Content position moved from Content to Design.
• Shop By Room: Label position moved from Content to Design.
• Slideshow: Layout moved from Content to Design; Transition & navigation moved from Content to Behaviour.
• Video Hero Overlay: Entrance motion moved from Design to Behaviour.
• Video Section: Video layout moved from Behaviour to Design.

Heading weight, heading size, hero background, composite font and CTA look: settings that now take effect

These settings used to save without changing some sections on the storefront. They now apply. In every case the change only happens once you have set the control: a section where you never touched it renders exactly as before.

Custom CSS: declarations only

Screen: Store Editor v3 → select a section → Behaviour → Advanced → Custom CSS. Only store Owners and Admins can edit this field; others see "Only store Owners and Admins can edit Custom CSS."

Write plain declarations, one per line or separated by semicolons, for example color: #111; padding: 24px;. Do not write a selector or braces: the editor wraps what you type as the body of one rule scoped to this section, so a rule such as .title followed by braces is rejected. The empty box shows the placeholder "e.g. color: #111; padding: 24px;". Beneath it, the helper text reads "Declarations only (property: value;), applied to this section. Selectors and @-rules are not supported." and lists a red message for each problem while you type.

These are rejected: any curly brace, @import, url(...), expression(...), behavior:, javascript: and a closing style tag. At render time the check runs again, and if any one problem is present the whole Custom CSS for that section is dropped, not just the offending line.

Spotlight, the Header crumb and the first-run tour

• Spotlight. When the canvas Spotlight toggle is on and you select something (a section or a Header/Footer part), everything else on the canvas is dimmed and only your selection stays lit. Clicking the dimmed area exits the spotlight (it selects the page again) and shows a short hint that lasts about three seconds: "Editing (what you had selected) - select the page to edit outside this area". Pressing Escape (when you are not typing in a field or a dialog) also clears the selection.
• Getting back to the header. While you are editing one part of the header, the Header crumb in the breadcrumb at the top of the right-hand panel takes you back to the header's own settings.
• The first-run tour is a small card fixed to the bottom-right corner, not a full-screen overlay, so it never blocks the editor. It has four steps (Outline, Add a section, drag handle, Publish) with Back, Next, Skip and Done. Clicking anywhere outside the card closes it and the click still happens (an outline row or canvas section you click is selected as normal); Escape also closes it. Reopen it any time from the top bar overflow menu, Take the tour.

Editing text right on the canvas

For a curated set of section types, you don't have to open All settings just to fix a typo. A single click — not a double-click — directly on a plain-text field (a headline, eyebrow, subheading, or a button's label) in the live preview opens an input exactly over that text, matched to its font, size, and colour, so it reads as the text itself becoming editable rather than a box landing on top of it.

Desktop, tablet & mobile preview

A viewport switcher at the right end of the status strip (below the header) toggles between desktop, tablet, and mobile views. Each viewport renders your page at a fixed width — 1100px for desktop, 768px for tablet, 375px for mobile — the same numbers a real browser at those widths would use, so your page's own responsive breakpoints fire honestly instead of an approximation. The rendered card is then scaled down (never up) to fit whatever space your browser window actually gives the canvas, sitting on a light warm-gray surround so the page reads as a bright card floating on a calm field — widen your browser and the card gets visually larger up to its real size, it never stretches past it.

Switching between desktop, tablet, and mobile only resizes the preview card in place — it does not reload the page, so any section you're actively editing stays exactly where it was and your undo history is untouched.

A part of the preview shows "This section could not be displayed"

Screen: Online Store → Store Editor → open the page, then look at the live preview canvas.

The preview draws your page in separate regions: the header, the footer, the mobile bottom navigation bar, and the page content in between. If one region cannot be drawn, only that region is replaced by a small dashed-outline tile that reads "This section could not be displayed. It will refresh on your next edit." The other regions keep working, and you can keep editing. The tile does not name the region, so go by where it sits: at the top it is the header, at the bottom the footer.

What it means. The preview hit a problem drawing that one region with its current settings. It is a preview-only message: the published store is not affected, and customers never see this tile.

What to do

1. Make your next edit. The tile clears by itself the next time the editor sends a change to the preview, and the region is drawn again with the new settings. If the edit fixed the cause, the region comes back; if not, the tile stays.
2. If the tile stays, undo the last change you made to that region (header, footer, or the section in the page content): press the undo shortcut (see Undo, redo & keyboard shortcuts) and watch whether the tile clears.
3. Still there? Reload the editor page in your browser. Your saved draft is kept, and the preview is rebuilt from it.
4. If it persists after that, report it to support with the page you were editing (for example Home, Cart or Header) and the last change you made before the tile appeared.

Undo, redo & keyboard shortcuts

Every change is tracked in an undo/redo history for the current session. On Windows/Linux the modifier is Ctrl; on Mac it's ⌘.

Shortcuts are disabled while you're typing in a text field (except Esc, which still closes open dialogs), so they never interfere with writing copy. The digit keys switch the inspector lens (Content/Design/Behaviour) on whichever section is selected — they don't switch the device preview; there's no keyboard shortcut for that yet, use the device trio in the top bar. Reordering a section and hiding/showing it also have no keyboard shortcut yet — use the Outline row's own drag handle, ↑/↓ buttons, and eye icon.

Press Ctrl/⌘ + K to open the command palette — a searchable list of every action available in the editor (save, publish, add a section, jump to a control, and more), grouped by category, each with its shortcut shown next to it. While your store's plan is still loading, the palette shows only the commands available on every plan; commands gated to a higher tier appear once the plan finishes loading, never before (so you're never shown, then denied, an action you don't have).

The palette also searches the names of real controls, not only pages and general actions. Type a control name such as Logo size or Sticky mode, then select the result or press Enter. The editor opens that control's owning panel, switches to the correct Content, Design, or Behaviour lens, scrolls the control into view, and places keyboard focus on its input.

A full shortcut list, along with everything else, is available from the Help menu (the ? icon in the header): Keyboard shortcuts (the same list shown above, also opened directly by pressing ?), Help center, and Contact support. Take the tour (a short guided walkthrough of the Outline panel, adding a section, the drag handle, and the Publish button — it also opens automatically the first time you use the editor) is in the top bar overflow menu, not the Help menu; see Spotlight, the Header crumb and the first-run tour.

Auto-save, drafts & version history

Your work is auto-saved as a draft continuously while you edit, and again if you close the tab with unsaved changes — so closing the browser never loses your progress. A separate local backup is kept every 5 seconds while you're actively editing (and dirty), and BillionBiz offers to restore it if your session ends unexpectedly.

If an autosave fails — a network hiccup, a server error — a red banner appears at the bottom of the canvas: "Your last save failed. Your edits are safe in this browser tab but haven't reached the server yet — retry, or keep editing and we'll try again automatically." It carries two buttons, Retry save and Dismiss. Your edits are never lost or reverted while this banner is showing — the editor used to silently discard the failed edit and mark the page as saved anyway; it now keeps what you typed and keeps telling you it hasn't reached the server. Click Retry save to try again immediately, or Dismiss to keep editing and let the normal autosave loop retry on its own; either way, the banner reappears if a later save also fails, and disappears on its own the moment a save succeeds.

Saving in the current Store Editor

The newer Store Editor used for journey pages and Chrome → Header/Footer has one status action in the top bar instead of the Landing Page Editor banner above. After an edit it reads Save; select it (or press Ctrl/⌘ + S) and it changes to Saving…. A successful request returns to the saved/publish status.

If the request fails, the action reads Retry and the error toast also offers Retry. Server, timeout, network, and unknown failures all keep the current draft in the editor rather than rolling it back. Select either Retry action after the connection or server recovers. Updating preview… on the canvas only means the storefront frame is catching up with the local draft—it does not replace Save or prove that the server accepted it.

Click History in the editor header to open the version browser. From there you can:

• Search or filter through your recent saved versions.
• Preview any earlier version before deciding whether to use it.
• Restore an earlier version — you'll be asked to confirm, since this replaces your current draft.

Each entry in the list — including Current Editor Version at the top — shows a change-count summary against your current draft: +N sections added, -N sections removed, N modified, and a Styles changed chip when the page's global styles differ. These counts reflect only real content/style differences: a version whose sections were saved in a different internal order, or that went through an old-format migration with no actual field change, still reports zero added, zero removed, and zero modified. Current Editor Version always shows +0 / -0 / 0 modified with no Styles changed chip, since it's being compared against itself.

Restoring a local backup

If BillionBiz finds a local backup newer than the last version saved on the server (for example, after your browser or laptop crashed mid-edit), it offers to restore it. Clicking Restore first compares timestamps:

• If the backup is actually older than or the same age as the server's last save — meaning the server already has everything the backup does, or more — BillionBiz discards the backup on the spot and tells you so, rather than rolling your page backward.
• Otherwise, you'll see a confirmation dialog naming both times explicitly ("This local backup is from [backup time]. The page was last saved on the server at [server time]. Restoring will replace your current draft with the backup's content — you can still Undo afterward."). Confirm to load the backup into your draft, or cancel to leave your current draft untouched.

The backup banner itself also self-dismisses without any click from you if the server's saved version catches up to (or passes) the backup while you still have it open unread — for instance, if another tab or a colleague saves newer content first. You'll only ever be offered a backup that's genuinely ahead of what's already saved.

Audit log

Click the audit-log icon next to History in the header to open a feed of who changed what and when — every section add, delete, duplicate, reorder, and content/style edit, plus theme changes, is logged with the editor's name and a relative timestamp ("2 hours ago"). Filter the feed by what happened or by a date range, and click Refresh to pull in the latest entries without closing the drawer. Use this alongside History when you need to know who made a change, not just what the page looked like before it.

Check whether your draft was saved

Screen: Online Store → Landing Page Editor → top-bar save status. Save stores your working draft; Saving… means the save is still in progress. Retry lets you retry a failed save. A conflict status means someone else edited the draft; resolve that conflict before publishing.

After saving, Live — draft differs means customers still receive the previously published page. Never published means there is no published version of this page yet. Live — draft matches means the saved draft and published version agree. Opening a clean draft can show No changes yet rather than a new save timestamp.

After a successful publish the pill refreshes on its own: it re-reads the live page when the publish finishes, so it no longer stays on Live — draft differs after you publish. If it still says Live — draft differs right after a publish with no edits since, the publish did not complete; check the page status and publish again.

If customers see old content, confirm the intended page, wait for saving to finish, and publish. Publishing first saves any unsaved edits as the draft, and if that save fails the publish does not go ahead. If Retry or a conflict remains, address it before checking the customer page again.

When saving is stopped because someone else saved first

Screen: Online Store → Store Editor → open the page. If the page's draft was changed from somewhere else (a teammate, or the same page open in another browser tab) after you opened it, your next save is refused instead of overwriting their work. Nothing is merged automatically, and your edits stay on the canvas so you can see what you were doing.

A warning banner appears at the bottom of the editor with the text: "Someone else saved changes to this page after you opened it, so your changes were not saved. Reload the latest version to continue." It has one button, Reload latest. Unlike the publish banner below, there is no Dismiss button: the banner stays until you reload.

If you select Publish while this banner is showing, the publish does not go ahead: publishing first saves your edits, that save is refused for the same reason, and the banner stays on screen rather than the click silently doing nothing.

Troubleshooting. "Why can't I publish?": if the banner is up, the draft on the server is newer than your copy; select Reload latest, re-apply your edits, then publish. "My edits disappeared after Reload latest": that is what reloading does; the other person's version replaced your unsaved copy. To avoid this, keep one person (and one tab) editing a page at a time.

When publishing is stopped because someone else published first

If the live page was published from somewhere else (a teammate, or another browser tab) after you opened it, BillionBiz refuses your publish rather than overwrite theirs. Nothing on your live store changes. What you see depends on the editor you are in:

• Store Editor, template pages. A banner appears at the bottom of the editor: "This page was published from somewhere else after you opened it, so your publish was stopped. Reload the latest version to continue." It has two buttons, Reload latest and Dismiss.
• Store Editor, page designs. A snackbar reads "This page changed while you were editing. Reload the latest draft, then publish again." with a Reload latest button on it.

Troubleshooting. "Publish keeps getting stopped": someone else is publishing this page in parallel, or you chose Dismiss and published from the old copy again; reload first, then publish. "My edits vanished after Reload latest": reload deliberately swaps in the other publish's draft, so unsaved edits are gone; re-apply them and publish again.

Publishing & the preview link

Publishing is a separate step from saving. Click Publish in the editor header (or press Ctrl/⌘ + P) to start the publish pipeline:

If validation finds a problem, the Publish button shows a small badge with the number of errors instead of publishing. Click it to open a popover listing every error — which section, which field, and what's wrong — each with a Jump to section button that selects and scrolls to the offending section so you can fix it without hunting for it yourself.

If your draft would remove sections that are currently live — especially if it would publish a page with zero sections — BillionBiz shows you exactly what's being removed and asks you to confirm before publishing. This protects you from accidentally wiping your live homepage with an in-progress draft.

A status strip below the header keeps you posted on the outcome: it shows draft, published, or unsaved changes, with a pulsing dot for at-a-glance state. Hover it for the exact detail — a progress bar while a publish is in flight, an error message if the last publish failed, or the date and editor name of your last successful publish once it's done.

Sharing a preview link

To let someone see your unpublished draft exactly as it looks right now — a client, a colleague, anyone without a BillionBiz login — without publishing it, open the ⋯ menu in the editor header and choose Share preview. (This only appears while you're editing the landing page itself; other page types don't have a share view yet, so the menu item is hidden rather than disabled on those.)

A page can have at most 20 active share links at once; trying to create a 21st is refused with "This page already has 20 active share links. Turn one off before creating another." — turn an existing one off first. If your store has no storefront domain configured yet, creating a link fails with "No storefront address is configured for this store."

Template gallery

If you're starting from a blank page, or you want to swap your current layout for a different look, open the template gallery: Online Store → Pages, then open the "pages you build" card and click Start from a template — or, if you're already inside the editor, click the section library's + icon in the left rail and switch to the Start from template tab. Both paths land you on the same gallery.

The gallery itself lives at its own page, /landing-page-editor/templates, so the URL is shareable and bookmarkable — anything you type into search or pick in the industry filter updates the URL (?industry=, ?q=) so a link you send a teammate reopens the same filtered view.

Every card has two actions:

• Preview — opens the template in a new browser tab at its own preview URL (/landing-template-preview/<template-slug>), rendering every one of its real sections with sample products and content so you can judge the actual layout, not a screenshot. A Preview mode banner across the top makes clear this isn't your live page. Use the desktop/mobile toggle in the top bar to check both layouts, and click Use this template from inside the preview to apply it directly — you don't have to go back to the gallery tab first.
• Use this template (or Upgrade to use on a locked card) — applies the template to your page immediately.

Plan gating: free vs. every paid plan

Template access is now all-or-nothing by plan tier, not per-template. If your store is on the Free plan, every one of the 18 templates shows a lock badge ("Upgrade to unlock") over its cover image and its button reads Upgrade to use instead of Use this template — clicking it shows a toast telling you to upgrade rather than applying anything. The moment your store is on any paid plan, all 18 templates unlock at once — there's no per-template "requires Growth" or "requires Max" tier to work around anymore.

Browsing from inside the editor

The section library's Start from template tab (the + icon in the left rail, then the tab next to All sections and My snippets) shows the same 18 cards in a more compact layout — same cover art, industry tag, name, and section count, without the description text. It's meant for a quick swap without leaving the editor. A Browse full gallery link in the top-right corner of that tab opens the full standalone gallery page in a new tab if you want the filter rail and search. Picking Use this template from the compact tab shows the same replace-confirmation dialog described above before it touches your draft.

Guided first-time setup

If you'd rather answer a short set of questions than build a page section by section, BillionBiz offers a seven-step guided studio that builds a complete homepage for you.

If your store has no published page yet, you don't need to go looking for it — open Online Store → Pages and click into the "pages you build" card as you normally would (or open /landing-page-editor directly), and BillionBiz takes you straight into the seven-step wizard automatically. You'll land on Step 1: Your brand immediately, no extra click required.

This auto-entry has a few edge cases:

• Click "Use the classic editor instead" (or otherwise back out of the wizard) once, and BillionBiz remembers — the next time you open the editor for that store, you land in the regular section-by-section editor (or the template gallery, if that's where you'd have landed anyway) instead of being sent back into the wizard. This is remembered per store, not per browser session, so it sticks across logins and devices for anyone editing that store.
• Asking for the template gallery explicitly — clicking Start from a template, or opening /landing-page-editor/templates directly — always wins over auto-entry, even on a brand-new store with no published page.
• The maintenance page is never auto-routed into the wizard. The guided studio only understands a normal storefront homepage; if you're editing your maintenance/coming-soon page, opening it always goes straight to the classic editor.
• The persistent Set up my page button in the editor header (see below) still works normally even after you've backed out once — dismissing auto-entry only stops it from happening automatically on open, it doesn't hide the manual entry point.

Once your store has a published page, auto-entry no longer applies — opening the editor takes you straight to your page, as normal. To run the guided flow again, click Set up my page in the editor header (the icon button next to AI Assist, tooltipped "Guided page setup"). Since you already have a live page, this takes you to the Improve my page checklist instead of the seven-step wizard (see Improve my page: the returning-merchant checklist below) — whether you see the wizard or the checklist is decided by whether your store actually has a published page with sections right now, not by which button or link you used to get there.

The seven steps

You can jump to any step at any time using the numbered list on the left, and every step is skippable — the wizard never blocks you from moving on. A step you skip isn't left empty; it contributes whatever default is described above (a generic story sentence, the 10% discount, and so on), so review each step before publishing rather than assuming "skipped" means "left out."

Improve my page: the returning-merchant checklist

Once your store has a published page, the same Set up my page header button opens a read-only Improve my page checklist instead of the wizard — a "here's how your page is doing" summary across six categories: Your brand, Your welcome, Your products, Your story, What customers say, and A welcome offer. Each is marked Set or Not set yet by checking your page's real, current sections (and, for Your brand, whether Brand Kit is actually turned on) — it's a live read of your existing page, not a re-run of your wizard answers.

Every item's Edit button, and the Open the full editor button at the bottom, both take you to the classic section-by-section editor — the checklist never re-runs the wizard on a page that already has content, since the wizard would silently replace your real sections with its own handful rather than merge with them.

Images, illustrations & stock photos

Click the image icon in the header to open the Content library — the same dialog opens whenever a section's Content tab asks you to pick an image. It has four tabs:

• My Images — every image you've uploaded to this store, searchable, with a grid or list view. The very first tile in the grid is an inline "Drop files or browse" tile — drag a file onto it or click it to upload without switching to the Upload New tab. Right-click an image for Replace, Copy URL, Download, or Delete, and use Load More to page through a large library.
• Illustrations — a built-in set of royalty-free illustrations, browsable by category or by search.
• Stock Photos — search Unsplash or Pexels for free stock photography, if your store has a stock-photo API key configured; each result carries the required photographer attribution.
• Upload New — drag and drop files or click to select. JPG, PNG, GIF, and WebP are supported, up to 10MB per file, and you can select several files at once.

When you're placing an image on a section that uses cover-crop (the image fills its container), click anywhere on the preview to set a focal point — the point that stays visible no matter how the image gets cropped on different screen sizes.

This full-preview treatment is specific to the My Images tab. When you upload a photo, or click an existing image on My Images, the library scrolls the picked image into view (upload only) and shows a full, uncropped preview of it above the Select Image button — this is what will be placed if you confirm, not a cropped thumbnail. If the section supports a focal point, the focal-point picker sits next to that preview. On the Illustrations and Stock Photos tabs, clicking a tile doesn't open a separate preview or focal-point picker — it just marks that tile with a check-mark and an accent border, and confirming placement still needs Select Illustration / Use Photo in the footer. Nothing is actually placed on your section until you click one of those footer buttons.

Some section content fields use a simpler, inline picker instead of the full Content library (its own Upload / URL / Brand Assets tabs, right there in the Content tab). Either way, dropping or selecting a file shows an "Uploading…" state on the preview while the file is sent to BillionBiz's storage; the field only saves a permanent image URL once that upload finishes. If an upload fails, you'll see an error message under the field and the section keeps showing whichever image it had before you tried — it never silently saves a broken temporary link that would work in this tab but stop loading everywhere else once you close it.

SEO, social sharing & integrations

Click the SEO score badge in the editor header (a number out of 100, in the status strip below the header) to open the Page settings drawer on the right — everything about how this page is found, shared, protected, and connected to outside tools lives here now, as six accordion groups you expand one at a time. SEO is expanded by default; the page's live preview URL is shown as a static line at the top of the drawer, above the groups.

SEO — set the Page title (up to 70 characters before the field warns you it's getting long) and Meta description (up to 160 characters, same warning behaviour) that appear in search results, plus the page's URL slug. The score breakdown lists every check BillionBiz runs (title length, meta description, image alt text, and similar), which ones are passing, and a hint for fixing the ones that aren't.

Social share — set an Open Graph image, OG title, and OG description (each falls back to your SEO title/description if left blank), then check the Facebook and Twitter/X tabs of the live preview card to see exactly how the page will look when someone shares its link, including per-platform character counts.

Privacy — two switches: Allow search engine indexing (on by default; turn it off to keep this specific page out of search results without unpublishing it) and Password protect, which reveals a Password field once turned on — visitors must enter it before the page renders.

Search engine visibility — Include in sitemap.xml (a separate switch from indexing — you can allow indexing but still leave a page out of the generated sitemap), a Canonical URL override for when this content is duplicated elsewhere, and an Hreflang editor: add one row per alternate-language version of this page (a language code and its URL) so search engines know they're the same content in different languages.

Structured data (JSON-LD) — paste a JSON-LD schema object (for example a WebPage or BreadcrumbList type) into a monospace text box; it's injected as a <script type="application/ld+json"> in the page's <head> when published. Invalid JSON shows an inline error instead of silently failing to publish something broken.

Integrations — connect this page to outside tools:

• Google Analytics 4 — turn on GA4 event tracking and enter your Measurement ID.
• Tracking pixels — Meta Pixel, Google Ads conversion ID/label, LinkedIn Insight Tag, and TikTok Pixel IDs, for ad platforms that need to see which visitors reached this page.
• Lead capture — choose where new leads from this page's forms go: your store's Newsletter list, a Mailchimp audience (by audience ID), or a Webhook URL. You can also ping a Slack channel on every new lead and customise the thank-you message shown after someone submits their details.
• Webhooks — add one or more webhook URLs that fire on publish, theme change, or section change (toggle which events each webhook cares about). Each webhook can be enabled or disabled, and its recent deliveries are viewable inline — each with a status, latency, and timestamp, with a Retry button on any failed delivery.

Page health

Next to the SEO badge, a health score badge (also out of 100) gives you a single number for the page's overall quality. Click it to open the health drawer, which groups issues into four categories — SEO, Accessibility, Performance, and Content — each flagged as an error, warning, or tip, with a Fix button that jumps straight to the section that needs attention where one applies. Below the issues, a Smart suggestions panel surfaces lower-priority improvements you can act on directly from the drawer.

The health checks also cover colour contrast. Where text and its background fall below 4.5:1, the page drawer reports a warning such as "Section (name) text contrast is N:1", and Check store reports the header ("Header text contrast is N:1") and each footer row ("Footer row (name) text contrast is N:1" or "link contrast is N:1"). Each names the colour to change in the inspector. The store-level footer check runs on the Footer page and tests each row's text and link colour against that row's background.

The accessibility check also looks at every image in a section for a description (alt text). Most sections are flagged "Image is missing alt text (field: ...)" when no alt-text field is filled in for that image, so open the section and fill that image's Alt text field. Three sections have an Image description field instead, because the storefront falls back to another field of the same item when the description is blank. A description that is only spaces counts as blank.

The Hero banner Image description is not shown for the Numbered index, Kinetic marquee, Stacked deck and Offer strip layouts, because those layouts draw the image with no description or no image at all. Flagged hero images read "Image has no description (field: slides[1].desktopImageUrl)" for a carousel slide or the matching image field for a banner. In Image only mode a slide's headline is hidden but is still used as the description.

These errors do not block publishing: if the page has any error-level issue, Publish first shows a "Review errors before publishing" prompt with Keep editing and Publish anyway.

Section ID: the link anchor for a section

Every section has an optional Section ID in the Advanced group of its inspector (see the tabs section above for where the Advanced group sits). It is the anchor that makes a link such as /#our-story scroll to that section, and it is what a Pill Anchor Nav pill points at.

• Duplicates get their own ID. When you Duplicate a section, paste one, or add the same section type to the page twice, the copy cannot keep an ID that is already used on the page. The editor appends -2 (then -3, and so on) to the copy's Section ID, so our-story becomes our-story-2. A blank Section ID stays blank. A popup's dismiss key is suffixed the same way when another section already uses it. Update any link that should point at the copy.
• It only sets the anchor. The Section ID does not control how the section looks. The section's styles and its device-visibility settings are tied to the section itself, so setting, changing or clearing a Section ID never detaches a section from its styling.

Reusable snippets

Save any section's exact content and style as a named snippet so you can reuse it without rebuilding it from scratch. From a section's ⋯ menu, choose Save as snippet, give it a name and (optionally) a folder to keep them organised. From then on:

• Open + Add Section and switch to the My Snippets tab to insert a saved snippet as a new section.
• Use Apply preset from any existing section's ⋯ menu to overwrite that section's content and style with a saved snippet's.
• Open the snippet manager (also reachable from the section library) to rename, delete, or reorganise your saved snippets into folders.

Copying and pasting sections as code

From a section's Scenes row ••• menu, Copy as code puts a JSON representation of that section on your clipboard (toast: "Section copied as code"); Paste section (from the same menu, on any section) reads a copied section back and inserts it. This is how you move a section between pages, or keep a personal backup outside the snippet manager.

A few things are deliberately stripped before anything is copied, so pasting a section never carries things that only made sense on the page you copied it from:

• A/B tests and personalisation — a copied section never carries its running A/B test or any personalisation rules; paste it and it starts as a single, un-tested version.
• Custom CSS and custom HTML in the section's Advanced settings are removed at any nesting depth.
• Any link field pointing at an unsafe URL scheme is blanked — only http(s), mailto:, tel:, and relative links survive the copy.
• Any field that stores raw HTML (Custom HTML, Founder Story, and the rich Featured Product description) is sanitised on the way out, so pasted HTML can't carry an embedded script.

A/B testing a section

Select a section that supports it, switch to the Behaviour lens, and open the A/B test group. Sections whose type doesn't support testing show this group greyed out with a reason rather than hiding it, and if you don't have permission to manage tests you'll see the same controls locked with a reason instead of nothing at all — either way, you always know the option exists even when you can't use it right now.

Setting up a test creates two variants — a Control and a second variant — starting at a 50/50 traffic split, running against a page views goal by default. You can add more variants, retarget the goal to clicks, form submissions, or a custom event, and edit each variant's content independently; a Preview action lets you see any variant rendered on the canvas without it actually being served to a real visitor (variant preview is editor-only and is never saved).

Custom HTML and booking embeds

Booking-scheduler embeds (Calendly, Cal.com, Square, Acuity, and similar) and any section with raw Custom HTML always render inside a sandboxed iframe on your storefront — scripts, forms, and popups from the embedded page are allowed to run, but the embed can never navigate your storefront tab away or read data from the rest of your store.

For a booking section, the Booking link field needs an https:// URL. If you paste an http:// (non-secure) link, the field shows an inline warning — "Booking links must start with https://" — but you can still save it; the warning doesn't block you. On the live storefront, though, only an absolute https:// link ever loads: anything else (http, a relative path, or an empty field) shows the section's own placeholder ("Add your booking link to preview") instead of a broken or blank embed.

Next steps