# My Carrd Site Needs More Pages: What Are My Options?

Canonical: https://figment.so/blog/outgrow-carrd-next-steps

Carrd has one page with sections, not multiple pages. Before you leave, you can use Pro Plus path-style redirects or link several Carrd sites on subdomains. A blog, store or truly multi-page site needs another platform.

**Carrd does not have multiple pages. It has one page divided into sections that act like pages, and that is the limit you are running into.** Carrd's docs describe two ways to stretch it before you leave: path-style redirects that make a section feel like its own URL, and several linked Carrd sites on subdomains. Past that, the right next platform depends on whether you need a blog, a store, or a multi-page design.

## Why does my Carrd site only have one page?

A Carrd site is one HTML page with linked regions, not a set of pages with their own URLs and metadata. Carrd describes itself as "Simple, free, fully responsive one-page sites for pretty much anything" ([Carrd](https://carrd.com/)). Its documentation says sections "allow you to divide a site into named regions ('sections') that can be linked to and switched between to **simulate** the effect of having multiple pages on a one-page site" ([Carrd Docs, "Using Sections"](https://carrd.com/docs/building/using-sections)).

If your content needs distinct pages, such as a blog with post URLs, a multi-step store, or a documentation site, sections cannot hold it on any plan.

## What can I do inside Carrd before I leave?

Two documented features go further than most people expect.

**Path-style redirects (Pro Plus).** You can point a "slash" URL at a section, an external destination, or the site itself: "you can optionally create redirects that point 'slash' URLs (like `/about`) to either a specific section of the site, an external URL, or simply back to the site" ([Carrd Docs, "Setting up Redirects"](https://carrd.com/docs/sites/setting-up-redirects)). The syntax is one `/request=destination` pair per line, with wildcards:

- `/contact=#contact` redirects `/contact` to the section `#contact`
- `/blog=https://medium.com/untitled` redirects `/blog` to an external URL
- `/products/*=#products` redirects anything under `/products/` to a section

(All examples are from the same page.) Carrd handles every redirect as a 301 ([Carrd Docs](https://carrd.com/docs/sites/setting-up-redirects)). The destination is still an anchor on the same page, so the section gets no page title or meta description of its own.

**Multiple linked Carrd sites (Pro Standard and up for custom subdomains).** Every Carrd plan grants a fixed number of "site slots," which are separate sites you can build and publish from one account. **Basic** (free) and **Pro Lite** each include 3 site slots, **Pro Standard** includes 10, and **Pro Plus** includes 25. Paid add-ons scale one account up to 1,000 slots on either tier ([Carrd Docs, "Understanding Site Slots"](https://carrd.com/docs/account/understanding-site-slots)).

Custom subdomains, a Pro Standard-and-up feature, publish a site to `subdomain.domain.ext` ([Carrd Docs, "Using a Custom Subdomain"](https://carrd.com/docs/sites/using-a-custom-subdomain)). Together, that gives you a main site at the root domain, a second Carrd site at `blog.yourdomain.com`, and a third at `shop.yourdomain.com`, cross-linked in each navigation. Each is still a one-page site internally, but they have separate URLs and separate SEO metadata.

## What does Carrd export if I leave?

On Pro Plus or higher, you can download static source, but forms stop working and you cannot upload it back. Carrd says "the unminified HTML, CSS, and JS source code for any of the sites on your account can be downloaded," but "elements requiring the Carrd platform to operate (most notably form elements) will, while visibly present, **not** be functional in this download," and "the downloaded version of a site **cannot** be uploaded back to the Carrd platform" ([Carrd Docs, "Downloading a Site"](https://carrd.com/docs/sites/downloading)).

You get a static snapshot you could host anywhere, without working forms. It is a one-way export, useful as a backup or as a starting point for a hand-coded rebuild, not a live migration path. There is no CMS to export, because a Carrd site has no content layer separate from its page design.

## What should I move to?

It depends on which limit you hit:

| What you need | Why Carrd cannot do it | A reasonable next step |
| --- | --- | --- |
| A blog with individual post URLs, tags, and an archive | No CMS, no post-level pages, only sections on one page | A publishing platform with a real content model. Carrd's docs list no CMS or post feature to compare against |
| An online store with a catalog, cart, and checkout | Carrd's "Widgets" only embed third-party checkout buttons (Stripe, PayPal, Gumroad). There is no product catalog or cart | A commerce platform where product data is exportable (see the [export matrix](/blog/export-your-website-from-a-website-builder) for what each one releases) |
| A multi-page marketing site (About, Pricing, Case Studies, Careers), each page with its own URL and metadata | Sections simulate pages on one page. Redirects can mask the URL but cannot give each "page" its own crawlable document | A multi-page site. If the design lives in Figma, the [Figment plugin](https://www.figma.com/community/plugin/1003000718170427134/Figment.so) publishes page frames as a hosted website (see [Figma to website: how to publish your design](/blog/how-to-create-website-figma)). It has no CMS |
| One more section-like "page" on your existing one-pager | Nothing is broken yet | Add a section, and consider a Pro Plus redirect for a clean URL |

Carrd is a good one-page builder, and site slots plus subdomains stretch it further than "one page" suggests. The signal that you have outgrown it is not a page count. It is needing a content type Carrd does not model: individual posts, a product catalog, or pages that need their own crawlable identity.

## How do I move a Carrd site if I leave?

1. Save the current text, images, downloads, form destinations, domain settings, and analytics settings. Take desktop and mobile screenshots of the complete page.
2. List every section link and path-style redirect that people use. Decide which new page receives each old path.
3. Build the replacement as real pages when the content needs separate URLs. Keep desktop and mobile layouts for each page.
4. Test navigation, forms, analytics, metadata, and every planned redirect on the replacement address.
5. Keep the Carrd site live until the replacement passes those checks. Change the domain only after the new pages work, and keep the saved Carrd copy during the rollback window.

If the Carrd site is still a good one-page fit, do not move it just to use a heavier tool. Migrate when you need a content model, a commerce system, or independent pages that Carrd does not provide.

## What if a change goes wrong?

Carrd changes are easy to undo. A redirect is one line you can delete, and a second linked site on a subdomain can be unpublished without touching the main one. Before you move anything off Carrd, keep the live site published until the replacement is checked on desktop and mobile. On Pro Plus, download a static copy first as a backup.
