> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluid.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract.
> Authenticate with the header Authorization: Bearer <token>; public storefront read endpoints require no auth.
> To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible.
> After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch.
> Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null.
> When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination.
> Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile.
> The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country).
> api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract).
> Successful responses wrap the resource payload alongside a top-level integer status and a meta object.
> Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other.
> For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces.
> Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings.
> Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties.
> Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables.
> A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation.
> The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations.
> Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check.
> Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times.

# Pages

> Create and manage your storefront's custom pages: content, status and scheduling, SEO, country availability, theme template and translations.

Use the **Pages** screen to create your storefront's custom pages and manage their content, status, SEO and availability. To change a page's layout, you open it in the visual editor from here.

## Where to find it

In the admin sidebar, under **Storefront**, select **Pages**.

<Note>
  To open this screen, your role needs **View only** or **Full access** for **Pages**. To create, edit or delete pages, it needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Pages** is in the **Content & Website** card. Open the card and set access from the **Pages** area's menu, not the card's.
</Note>

## What's on the screen

**Create Page** and **Open Editor** are at the top of the screen. **Open Editor** opens your theme's default home page template in the [Page Editor](/help/admin/page-editor).

A banner above the list offers a new version of the pages table. Click **Try it** to switch to it and **Switch back** to return. Your choice is remembered in this browser. This page describes the standard table.

* The **All**, **Published**, **Scheduled** and **Draft** tabs filter the list by status.
* Use the search box to find pages.
* The filters panel has **Status** and **Country Availability**. Choose values, then click **Apply Filters**.

The list has these columns:

* **Image**: the page's image, or an empty frame if it has none.
* **Title**: click it to open the page. A page with no title shows **Untitled**. You can sort by this column.
* **Status**: **Published**, **Draft**, or **Scheduled** with its publish date and time.
* **Countries**: flags for the countries the page is available in, with **+** and a number when there are more than two. **All** means the page has no country restriction and is available everywhere you sell.

Each row's actions menu has **Edit** and **Delete**. Select several rows to delete them together; the menu then reads, for example, **Delete 3 rows**.

## Create a page

<Steps>
  <Step title="Start a new page">
    On the **Pages** screen, click **Create Page**. The **Create Page** screen opens.
  </Step>

  <Step title="Fill in the page details">
    In the **Page Details** card, enter a **Title**. It's required. Add a **Description** in the text editor if you want one. Under **Media**, click **Select Image** to choose the page's image: JPG, PNG, GIF, WebP, BMP or SVG, up to 10MB.
  </Step>

  <Step title="Choose the status">
    In the **Status** card, a new page starts as **Published**, which makes it live when you create it. To keep it hidden while you work on it, choose **Draft**. To publish it later, see [Schedule a page](#schedule-a-page).
  </Step>

  <Step title="Check the template and countries">
    In the **Theme Template** card, your active theme's default page template is selected for you. Choose another if you need to. In the **Countries** card, leave the field empty to make the page available everywhere you sell, or choose specific countries.
  </Step>

  <Step title="Set SEO, if needed">
    In the **SEO And Link Sharing** card, click **Edit**. See [Set SEO and the page URL](#set-seo-and-the-page-url).
  </Step>

  <Step title="Create the page">
    Click **Create Page**. The button is grayed out until the page has a title. A confirmation message appears and the page's detail screen opens.
  </Step>
</Steps>

## Edit a page

<Steps>
  <Step title="Open the page">
    In the list, click the page's title, or choose **Edit** from its actions menu. The **Page Details** screen opens with the page's title and status badge at the top.
  </Step>

  <Step title="Make your changes">
    Change the fields in the **Page Details** card and the cards on the right.
  </Step>

  <Step title="Save">
    Click **Save**. A confirmation message appears and you stay on the page.
  </Step>
</Steps>

The top of a saved page also has:

* **Actions**: a menu with **Publish Now** (shown when the page isn't published), **Reset Cache** and **Delete Page**. **Publish Now** saves all your changes and publishes the page in one step.
* **Open Visual Editor**: opens the page's theme template in the [Page Editor](/help/admin/page-editor), where you change its layout. It's grayed out until the page has a saved theme template. If you change **Theme Template**, click **Save** before you open the editor.
* **Translations**: see [Translate a page](#translate-a-page).
* **Preview**: opens the page on your storefront in a new tab.

The **Metafields** card below **Page Details** shows the metafields defined for pages. **Manage Definitions** takes you to [Metadata Definitions](/help/admin/settings/metadata-definitions) in Settings.

## Schedule a page

<Steps>
  <Step title="Choose Scheduled">
    On the page, in the **Status** card, choose **Scheduled**. A date and time picker opens below it.
  </Step>

  <Step title="Pick the date">
    Choose a date and time in the future, then click **Schedule Activation**. The card shows **Scheduled for activation** with the date and time.
  </Step>

  <Step title="Save">
    Click **Save**, or **Create Page** for a new page.
  </Step>
</Steps>

If you save a scheduled page with no date or a date in the past, an error message appears and nothing is saved.

<Warning>
  Scheduling isn't a privacy setting. The date controls when the page appears in listings and can be indexed by search engines, but anyone with the direct link can open it before then. To keep a page hidden, use **Draft**.
</Warning>

## Set SEO and the page URL

<Steps>
  <Step title="Open the SEO panel">
    In the **SEO And Link Sharing** card, click **Edit**.
  </Step>

  <Step title="Edit the search listing">
    Enter a **Title Tag** of at least 3 characters (10 to 70 is recommended) and a **Meta Description** of at least 5 characters (140 to 160 is recommended, 160 at most). Use **Preview** to see how the page looks as a **Google Search Result**, in a **Text Message** or on **X (formerly Twitter)**.
  </Step>

  <Step title="Set the URL and visibility">
    The page's URL is generated from its title. To set your own, turn on **Use custom slug** and enter the **URL Slug**. Turn off **Search engine visibility** to keep the page off Google and other search engines.
  </Step>

  <Step title="Apply and save">
    Click **Done**, then click **Save** on the page.
  </Step>
</Steps>

If you don't set an SEO image, the page's image from **Media** is used.

## Translate a page

<Steps>
  <Step title="Open translations">
    On a saved page, click **Translations**. The button appears on wider screens.
  </Step>

  <Step title="Enter translations">
    Edit the **Title**, **Description** and **Page Image** for each of your company's active languages.
  </Step>

  <Step title="Save the translations">
    Click **Save** in the translations panel. Translations are saved there, separately from the page's **Save** button.
  </Step>
</Steps>

## Delete a page

<Steps>
  <Step title="Choose Delete">
    In the list, choose **Delete** from the page's actions menu. To delete several pages, select their rows and choose **Delete** from the table header's menu. On a page, choose **Delete Page** from the **Actions** menu.
  </Step>

  <Step title="Confirm">
    In the confirmation dialog, click **Delete** (or **Delete Page**). From a page, you return to the list.
  </Step>
</Steps>

<Warning>
  Deleting a page can't be undone.
</Warning>

## Analytics

Once a page is saved, the **Analytics** card on the right shows **Page Views**, **Shares**, **Page Speed** and **Content Compliance**. Click a metric for details. **Page Speed** and **Content Compliance** each have a **Run Scan** button; results can take a few minutes to appear.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="What should I check before publishing a page?" id="check-before-publishing">
    Keep the page in **Draft** while you work on it. Before you publish:

    * Click **Preview** to check the page on your storefront.
    * Check the **Title Tag** and **Meta Description** in **SEO And Link Sharing**.
    * Confirm the **Countries** the page should be available in.
    * Run **Page Speed** and **Content Compliance** scans from the **Analytics** card.

    Then choose **Publish Now** from the **Actions** menu.
  </Accordion>

  <Accordion title="Why is my new page already live?" id="new-page-live">
    New pages start with the status **Published**. To create a page without publishing it, choose **Draft** in the **Status** card before you click **Create Page**. To unpublish a saved page, change its status to **Draft** and click **Save**.
  </Accordion>

  <Accordion title="Why is Open Visual Editor grayed out?" id="visual-editor-disabled">
    The page has no saved theme template yet. Choose a template in the **Theme Template** card and click **Save**. If the card says **No active theme. Set one to create templates.**, set an active theme first.
  </Accordion>

  <Accordion title="Why don't I see Create Page or Save?" id="no-create-or-save">
    Your role can view pages but doesn't have **Full access** for **Pages**. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles).
  </Accordion>
</AccordionGroup>

## Related pages

* [Storefront](/help/admin/storefront)
* [Page Editor](/help/admin/page-editor)
* [Media](/help/admin/media)
* [Create a page (developer guide)](/setup/create-a-page)
* [SEO](/storefront/seo)
* [Slugs and URLs](/storefront/slugs-and-urls)
* [Country availability](/storefront/country-availability)
* [Translations](/storefront/translations)
* [Metafields](/storefront/metafields)
* [Roles](/help/admin/settings/roles)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.