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

# Landing Pages

> Create hosted signup and launch pages that feed subscribers into Sequenzy

# Landing Pages

Landing Pages let you build hosted pages for waitlists, lead magnets, launches,
webinars, newsletters, demo requests, offers, and feature announcements without
leaving Sequenzy.

Each page can include a native signup form, route new subscribers into lists and
tags, and publish on a Sequenzy URL or your own verified landing-page domain.

## What You Can Build

Start from a blank page or one of the built-in templates:

* Coming soon waitlist
* Guide download
* Product launch
* Consultation booking
* Live workshop
* Creator newsletter
* Product Hunt launch
* Black Friday sale
* Agency consultation
* Feature spotlight

Templates use your workspace brand colors and email theme as a starting point,
then you can adjust the page theme directly in the builder.

## Create a Page

1. Open **Landing Pages** from the dashboard sidebar.
2. Click **New page**.
3. Choose a template and enter a page name.
4. Edit copy, sections, images, theme, form settings, and SEO metadata.
5. Click **Publish** when the page is ready.

Draft pages are not publicly available. Published pages receive a public URL and
can be copied or opened from the page list or editor toolbar.

## Editor

The landing-page editor has three main side panels:

* **Elements**: add individual blocks such as headings, text, images, buttons,
  feature grids, stats, testimonials, logo clouds, FAQs, pricing, forms,
  spacers, and dividers.
* **Sections**: add larger prebuilt sections such as heroes, resource previews,
  product offers, agendas, testimonials, logo clouds, FAQs, CTAs, pricing
  sections, and galleries.
* **Style**: adjust colors, font pairing, density, accent style, surface style,
  border radius, and workspace design defaults.

Use **Edit** mode for inline editing and drag-and-drop changes. Use **Preview**
mode to check the published experience without editor controls. The desktop and
mobile toggles help check responsive layout before publishing.

## Forms

A landing page can include one signup form. Form submissions create or update a
subscriber in the same workspace as the page.

Form settings control:

* Email, first name, last name, and phone fields
* Required first name, last name, or phone fields
* Custom fields stored as subscriber attributes: text, phone, number,
  textarea, select, radio, checkbox, consent, and hidden inputs
* Field placeholders and button text
* Form card width (narrow, medium, or wide) for content-heavy forms
* Success message
* Optional redirect URL after successful submission
* List routing: default lists, no lists, or specific lists
* Signup tags to apply after subscription

When you apply a saved form to a landing page, every form field carries over:
email, first name, last name, and phone map onto the native subscriber
fields, and all other fields become custom fields on the page's form.

Landing-page forms follow the workspace double opt-in setting. When double
opt-in is enabled, selected lists and tags are applied only after the subscriber
confirms their email address.

<Card title="Double Opt-In" icon="mail" href="/concepts/double-opt-in">
  Learn how confirmation emails, pending subscribers, lists, and signup tags
  work.
</Card>

## Form Endpoint

Published pages post to a page-specific endpoint:

```text theme={null}
POST /api/landing-pages/{pageId}/submit
```

The endpoint is served from the same app or custom-domain host as the published
page.

The hosted form sends `application/x-www-form-urlencoded` data, and the endpoint
also accepts JSON.

```bash theme={null}
curl -X POST "https://www.sequenzy.com/api/landing-pages/page_123/submit" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "reader@example.com",
    "firstName": "Ada",
    "lastName": "Lovelace"
  }'
```

Successful responses return the configured success message and, when configured,
a redirect URL:

```json theme={null}
{
  "success": true,
  "message": "You're on the list.",
  "redirectUrl": "https://example.com/thanks"
}
```

The endpoint also includes a hidden `website` honeypot field for spam
protection and rate-limits repeated submissions.

## Publishing URLs

Published pages are available at a Sequenzy-hosted URL:

```text theme={null}
https://www.sequenzy.com/lp/{companyId}/{slug}
```

When a custom landing-page domain is verified, the preferred public URL becomes:

```text theme={null}
https://pages.example.com/{slug}
```

Changing the page slug updates the public URL. Slugs are normalized and made
unique inside the workspace.

## Custom Domains

Use a custom landing-page domain when you want pages and their native forms to
live under your brand.

1. Open **Landing Pages**.
2. Open **Connect domain** from a published page or the page actions.
3. Enter a subdomain such as `pages.example.com`.
4. Add a CNAME record pointing to `pages.sequenzydns.com`.
5. Click **Verify**.

If your workspace has a compatible Cloudflare DNS provider connected for the
same root domain, Sequenzy can add the CNAME record automatically with **Add
DNS**.

Published pages keep using Sequenzy URLs until the custom domain is verified.
After verification, page URLs use the custom domain automatically.

## API, CLI, And MCP

Landing pages can be managed from the dashboard, public API, CLI, and MCP tools.
Use these when an AI agent, script, or backend needs to create and manage pages
without clicking through the dashboard.

### API

```bash theme={null}
curl -X POST "https://api.sequenzy.com/api/v1/landing-pages" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Product Waitlist","template":"waitlist"}'
```

Available API actions include list, get, create, update, publish, unpublish,
delete, connect domain, update domain settings, and verify domain status.

### CLI

```bash theme={null}
sequenzy landing-pages create "Product Waitlist" --template waitlist
sequenzy landing-pages publish lp_abc123
sequenzy landing-pages connect-domain pages.example.com
```

### MCP

Use MCP tools such as `create_landing_page`, `update_landing_page`,
`publish_landing_page`, `unpublish_landing_page`,
`connect_landing_page_domain`, and `update_landing_page_domain_settings` when
Claude, Codex, Cursor, or another agent should manage landing pages for you.

<CardGroup cols={3}>
  <Card title="Landing Pages API" icon="code" href="/api-reference/landing-pages/create">
    Create, publish, and manage pages from REST clients.
  </Card>

  <Card title="CLI" icon="terminal" href="/concepts/cli">
    Use `sequenzy landing-pages` commands in terminals and scripts.
  </Card>

  <Card title="MCP" icon="plug" href="/concepts/mcp">
    Let AI agents operate landing pages with MCP tools.
  </Card>
</CardGroup>

## SEO And Social Metadata

Open **Page settings** in the editor toolbar to edit:

* Page name
* Public slug
* SEO title
* Search and social description

If no SEO title or description is set, Sequenzy falls back to the page's primary
heading and body copy. The first image block is used as the social preview image
when one is available.

## Metrics

The landing-pages list shows:

* Status: draft or published
* Views
* Leads
* Last updated date

Views increase when a published page is loaded. Leads increase when a new
subscriber is created from the page form.

## Good To Know

* A landing page can contain at most one form block.
* Every landing page must keep one footer block.
* CTA, pricing, footer, and redirect URLs must be safe `http` or `https` URLs.
* Draft pages do not return public content.
* Custom domains serve pages by slug, so `https://pages.example.com/waitlist`
  works after the domain is verified.

<CardGroup cols={2}>
  <Card title="Signup Form Widget" icon="mail" href="/widgets/signup-form">
    Use embeddable forms when the page lives outside Sequenzy.
  </Card>

  <Card title="Subscribers" icon="users" href="/concepts/subscribers">
    Learn how form submissions create and update subscriber records.
  </Card>
</CardGroup>
