Skip to main content

Site settings & publishing

The Settings screen controls the site as a whole: its name, whether it's live, which renderer serves it, the draft-preview link, the age gate, analytics & custom code, and 301 redirects. It lives at /admin/sites/:siteId (the Settings rail item); saving any change needs the storefront.manage permission.

Who can use it​

  • Saving any Settings change needs the storefront.manage permission (Admins); viewing only requires signing in as a company user.
  • Avero Sites is gated by the Hosted Site add-on — see the billing path at the end of this guide, or Build your Avero site.

Site status​

The General card's Site status decides what the public sees on any domain connected to this site:

  • Draft — not live — "Not live. A connected domain keeps serving your legacy site until you publish." Your built pages and this site's redirects are not served.
  • Published — live — "Live. A connected domain serves this site."
  • Taken down — every page on a connected domain, the shop and checkout included, answers "This site is no longer available" until you set the status back to Published.

A new site starts as a Draft. Saving a change to Taken down asks you to confirm first — Take this site down? — with Take site down and Cancel.

This is the site's state, distinct from an individual page's publish status (a page is published from the editor — see Build your Avero site). Save changes confirms "Site updated".

Site settings — site status, the renderer switch, preview link, and age gate.

Settings — General (site status, renderer, preview link), the age gate, and Managed elsewhere.

Picture being updated

This picture shows an earlier version of this screen. The steps on this page are current.

The renderer switch​

Renderer decides what visitors see once the site is Published:

  • Legacy hosted site (current) — keeps rendering today's brand-configured website.
  • Avero Sites (page builder) — serves the pages you build here.

As the setting explains: "Legacy keeps rendering today’s brand-configured website. Switching to Avero Sites serves the pages you build here — falling back to the legacy renderer for any page you haven’t built yet." New sites start on Legacy; flip to Avero Sites when your built pages are ready. The switch has no effect on visitors while the site is a Draft. The dashboard's Site health panel flags a site still on the legacy renderer with a Switch shortcut here.

Preview link shares drafts without publishing — "Share drafts without publishing. Rotating revokes the old link." Rotate generates a tokenized share URL at /_preview?token=… and revokes the previous one: "Preview link rotated — old links revoked". This is the same rotating draft link the editor's Share draft button uses; anyone with the current link sees the unpublished draft with no login.

The per-site age gate​

The Age gate card shows visitors a one-tap age check before they can browse — "Show visitors a one-tap age check before they can browse. POS ID-scan & compliance rules are separate — see 'Managed elsewhere'."

  • Require age confirmation — the on/off switch. It shows a one-tap "Are you [21] or older?" screen on the first visit, before any page — "Recommended on for alcohol sites."
  • Minimum age — the age asserted ("Usually 21 in the US.").
  • Remember for (days) — how long before a returning visitor is asked again.
  • If underage, send them to — a redirect URL; "Leave blank to show a built-in 'come back when you're of age' screen instead."

Save age gate confirms "Age gate saved". This is the marketing site's own gate — it's separate from POS ID-scan and compliance, which live under Managed elsewhere.

Favicon & touch icon​

The Favicon & touch icon card — "The browser-tab and mobile home-screen icons for this site. Uploaded images serve from your media library; leave empty to use the Avero default." — sets the site's icons:

  • Favicon — "Square PNG/ICO/SVG. Shown in the browser tab. 32×32 or larger."
  • Apple touch icon — "Square PNG, 180×180. The mobile home-screen icon. Falls back to the favicon."

Pick or upload each from the media library (Choose / upload), then Save icons — Avero confirms "Icons updated". The published site serves them in its <head> automatically.

Custom code & analytics​

The Custom code & analytics card connects analytics and adds verification tags — "Connect Google Analytics or Plausible, add verification & preconnect tags to the page <head>, and optionally gate analytics behind a cookie-consent banner. Custom head markup is sanitized for safety — no scripts."

Analytics is structured: you enter a validated id — never a script — and Avero emits the official vendor snippet on the site itself.

  • Google Analytics 4 — your measurement id (G-XXXXXXXXXX) — "Measurement id. Loads gtag.js — never paste a raw script." A value that isn't a GA4 id is flagged: "Enter a valid GA4 measurement id (starts with G-)."
  • Plausible — the bare domain you registered with Plausible (e.g. shop.yourbrand.com) — "The data-domain you registered. Cookieless, privacy-friendly."

Custom <head> markup takes verification and preconnect tags only — as the field says, "For safety, everything except <meta> and <link> tags (with https URLs) is stripped on save — no <script>." The stripping happens server-side on save: <script>, <style>, and inline event handlers are removed along with their content, so a pasted analytics or chat-widget script simply vanishes rather than runs. The field is capped at 4,000 characters. For a script-based embed inside a page, use the editor's sandboxed Custom HTML block instead — see Build your Avero site.

Cookie-consent banner — "Show a consent banner and keep analytics off until visitors accept." When it's on, visitors see "We value your privacy — we use cookies to measure site traffic. Analytics stay off until you accept." with Accept / Decline buttons, and GA4/Plausible load only after Accept. Your custom <meta>/<link> tags carry no tracking, so they apply either way.

Save custom code confirms "Custom code updated".

Redirects​

The Redirects card sends old paths to new ones — "Send old paths to new ones with a permanent (301) redirect, so renamed or retired pages don't break inbound links. Honored before the page loads — good for SEO and bookmarks."

Add redirect adds a row with From (old path) (e.g. /old-page) and To (new path or URL) (/new-page or a full https://… URL); the trash button removes a row. Invalid values are flagged as you type — "Must be a path starting with “/”." / "Use a path or an http(s)/mailto/tel URL." — and dropped on save. Save redirects confirms "Redirects updated". Redirects are only honoured while the site's status is Published.

How matching works:

  • Sources are exact paths — no wildcards or patterns. /old and /old/ count as the same path.
  • Matching ignores the query string, and a visitor's query string (UTM tags, say) is carried over to an on-site target — unless the target already has its own.
  • Targets can be a path on this site or an http(s), mailto:, or tel: URL. A rule pointing a path at itself is dropped, each source can appear once (the first rule wins), and a site holds up to 100 rules.
  • Redirects fire on page visits only — never on files (images, robots.txt) or API routes — and return a real 301, visible to search crawlers, not just a hop inside the loaded site.

Managed elsewhere​

Site-level settings that actually live at the company level are gathered in the Managed elsewhere card — "Company-level — edit once, applies everywhere." Each row links out:

RowWhat it coversOpens
Company identityName, contact, social profiles/admin/company
Brand Kit & themeLogo, colors, fonts across all sites/admin/company
Domain DNS & ownershipBuy, verify, and route domains/admin/store?tab=domains
POS complianceAge & ID-scan rules, tax/admin/store
Catalogue & productsInventory, pricing, variants/admin/catalogue
Embed & wine clubReservation & club widgets/admin/store?tab=embed

The Brand Kit & theme row opens Company Settings on its first tab, Corporate. Click the Brands tab to reach the brand's logo, colors and fonts.

The add-on & billing path​

Avero Sites is a paid add-on gated by the Hosted Site entitlement. If it isn't enabled, /admin/sites shows the "Add a hosted website" upsell with View plans (/admin/billing) and Contact sales (sales@averoguest.com). Turn the add-on on for your account and the full Sites dashboard — including this Settings screen — becomes available.

Reference​

ControlWhereWhat it does
Site statusSettings → GeneralDraft — not live / Published — live / Taken down.
RendererSettings → GeneralLegacy vs Avero Sites page builder.
RotateSettings → Preview linkIssues a new draft link, revokes the old.
Require age confirmationSettings → Age gateTurns the marketing-site age gate on.
Save iconsSettings → FaviconSaves the favicon + Apple touch icon to the site.
Save custom codeSettings → Custom codeGA4/Plausible ids, sanitized head tags, consent.
Save redirectsSettings → RedirectsPer-site 301 rules — old path → new path or URL.
Managed elsewhereSettingsLinks to the company-level surfaces above.

Troubleshooting​

  • My built pages aren't showing to visitors — check both settings on the General card: Site status must be Published — live, and Renderer must be Avero Sites (page builder). Then Save changes.
  • Visitors see "This site is no longer available" — the site's status is Taken down. Set it back to Published — live.
  • A page I haven't built 404s under Avero Sites — it doesn't; Avero Sites falls back to the legacy renderer for any page you haven't built yet.
  • The old preview link stopped working — someone hit Rotate (or Reset link in the editor); share the current one.
  • My script disappeared from Custom <head> markup — that's the sanitizer working: only <meta> and <link> tags survive a save. Use the structured Google Analytics 4 / Plausible fields for analytics; for an in-page embed, use the Custom HTML block.
  • A redirect isn't firing — sources match exact paths only (no wildcards), and redirects never apply to files or API routes. Check the From value matches the retired URL's path exactly, and that the site's status is Published.
  • The age gate isn't POS ID-scan — right; the marketing-site age gate is separate. POS ID-scan and compliance are under Managed elsewhere → POS compliance.