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

# Domains and Publishing in LanderLab: Overview

> Learn how publishing works in LanderLab: connecting a domain through Cloudflare or manual DNS, publishing and republishing pages, and domain-level settings.

LanderLab hosts your pages for you. There is no server to configure, no deployment step, and no hosting bill separate from your plan. You bring a domain, connect it once, and every page you publish afterwards goes live on it.

## Connecting a domain

Two paths, and the right one depends on where your DNS is managed.

<Columns cols={2}>
  <Column>
    <Card title="Cloudflare integration" icon="cloud" href="/features/domain/cloudflare/connect-domain">
      Connect your Cloudflare account and LanderLab configures DNS automatically. Fastest option and the one to use unless you have a reason not to.
    </Card>
  </Column>

  <Column>
    <Card title="Manual DNS" icon="server" href="/features/domain/manual-connection">
      Add CNAME and TXT records at your registrar yourself. Use this when DNS lives somewhere other than Cloudflare.
    </Card>
  </Column>
</Columns>

If you are using Cloudflare, [add your account first](/features/domain/cloudflare/add-account). That gives LanderLab permission to manage records, which is what removes the manual step later.

<Note>
  When you add a domain through Cloudflare, a nameserver popup appears immediately. If you close it before copying the values, reopen it from the **Pending** status label next to the domain in your Domains list.
</Note>

One domain can host many pages on different paths, so you do not need a separate domain per campaign. Most teams run one domain per brand or vertical and organize the rest with paths.

## Publishing a page

<Steps>
  <Step title="Set your SEO details">
    Fill in the page title, meta description, and favicon under [SEO settings](/features/landing-pages/settings/seo) and [general settings](/features/landing-pages/settings/general) before going live, not after.
  </Step>

  <Step title="Publish">
    Choose your domain and the path the page should live on, then publish. See [publish a landing page](/features/landing-pages/operations/publish).
  </Step>

  <Step title="Republish after every change">
    Edits, new integrations, and new pixels all stay in preview until you [republish](/features/landing-pages/operations/republish).
  </Step>
</Steps>

<Warning>
  This is the single most common support question. If a change is not showing on the live URL, or a pixel is not firing, republish before troubleshooting anything else.
</Warning>

To take a page offline without losing it, [unpublish](/features/landing-pages/operations/unpublish) it. The page and all its content stay in your workspace and can be republished at any time.

## Domain-level settings

Some things are better configured once per domain than repeated on every page.

* [Global scripts](/features/domain/settings/global-scripts) inject tracking pixels, analytics, or custom CSS across every page published on the domain. If you are pasting the same snippet into ten pages, put it here instead.
* [404 page](/features/domain/settings/404) controls what visitors see at a URL that does not exist. Use the default or point it at your own page.
* [Disable indexing](/features/domain/settings/disable-indexing) stops search engines from indexing anything on the domain. Standard practice for paid traffic domains, where organic indexing of ad landing pages is usually unwanted.

<Tip>
  Turning off indexing on ad domains keeps test pages, variants, and expired offers out of search results, and prevents your landing pages from competing with your main site.
</Tip>

## Exporting a page

Pages are not locked in. [Download a landing page as a ZIP](/features/landing-pages/operations/download) with all assets included, to back it up, hand it to a client, or host it elsewhere.

## Organizing many pages

Once you are running more than a handful of campaigns, structure starts to matter.

<Columns cols={2}>
  <Column>
    <Card title="Folders" icon="folder" href="/features/landing-pages/folders/create">
      Group pages by campaign, funnel, or client inside a workspace.
    </Card>
  </Column>

  <Column>
    <Card title="Workspaces" icon="user-group" href="/overview/team">
      Separate clients or brands entirely, with their own domains and access control.
    </Card>
  </Column>
</Columns>