My Carrd Site Needs More Pages: What Are My Options?
Carrd doesn't have multiple pages — it has one page divided into sections that act like pages, and that's the limit you're actually running into. Carrd's own docs describe two real ways to stretch that before you leave: path-style redirects that make a section feel like its own URL, and linking several Carrd sites together under one account. Past that point, which platform fits next depends on what you actually need — a blog, a store, or a genuinely multi-page design — not on a single "upgrade from Carrd" answer.
Why does my Carrd site only have one page?
Carrd describes itself plainly: "Simple, free, fully responsive one-page sites for pretty much anything" (Carrd). Its documentation is direct about what a section actually is: 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", checked September 2026). That word "simulate" is the whole story — a Carrd site is one HTML page with anchor-linked regions, not a set of separate pages with their own URLs, own metadata, or their own load. If your content genuinely needs distinct pages — a blog with individual post URLs, a multi-step store, a documentation site — sections were never going to hold it, no matter which plan you're on.
What can I actually do inside Carrd before I leave?
Two documented features get you further than most people realize:
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", checked September 2026). The syntax is a /request=destination pair per line, and it supports wildcards:
/contact=#contact— redirects/contactto the section#contact/blog=https://medium.com/untitled— redirects/blogto an external URL/products/*=#products— wildcard-redirects anything under/products/to a section
(All examples from the same page.) This is the honest way to make a Carrd section look like its own page in a shared link or a browser address bar — Carrd handles every redirect as a 301 (Carrd Docs), but the destination is still an anchor on the same page, so the section doesn't get its own page title or meta description.
Multiple linked Carrd sites (Pro Standard and up for custom subdomains). Every Carrd plan grants a fixed number of "site slots" — separate sites you can build and publish from one account: Basic (free) and Pro Lite both include 3 site slots, Pro Standard includes 10, and Pro Plus includes 25, with paid add-ons scaling a single account up to 1,000 slots on either tier (Carrd Docs, "Understanding Site Slots", checked September 2026). Combined with custom subdomains — a Pro Standard-and-up feature for publishing a site to subdomain.domain.ext (Carrd Docs, "Using a Custom Subdomain", checked September 2026) — this means a real multi-part web presence is possible without leaving Carrd: your main site at the root domain, a second Carrd site at blog.yourdomain.com, a third at shop.yourdomain.com, cross-linked in each one's navigation. Each one is still a one-page site internally, but together they behave like separate sections of a larger site with real, separate URLs and separate SEO metadata.
What does Carrd actually export if I leave?
Only on Pro Plus or higher, and with a real limitation: "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", checked September 2026). Practically: you get a static snapshot you could host anywhere, minus working forms, and it's a one-way door — useful as a backup or a starting point for a hand-coded rebuild, not a live migration path. There's no CMS to export either, because there's no CMS: a Carrd site has no separate content layer distinct from its page design.
What should I actually move to?
This depends entirely on which limit you hit, not on a single "next platform after Carrd":
| What you actually need | Why Carrd can't do it | A reasonable next step |
|---|---|---|
| A real blog with individual post URLs, tags, and an archive | No CMS, no post-level pages — only sections on one page | A dedicated publishing platform with a real content model — Carrd's own docs list no CMS or post feature to compare it against |
| An online store with a real catalog, cart, and checkout | Carrd's "Widgets" only embed third-party checkout buttons (Stripe, PayPal, Gumroad) — there's no product catalog or cart of Carrd's own | A platform built around commerce, where product data is a first-class, exportable thing (see the export matrix for what each one actually releases) |
| A genuinely multi-page marketing site — About, Pricing, Case Studies, Careers — each with its own URL and metadata | Sections simulate this on one page; redirects can mask the URL but not give each "page" its own crawlable document | A real multi-page site. If your design already lives in (or belongs in) Figma, publish it directly with the Figment plugin — see Figma to website: how to publish your design for the walkthrough |
| Just one more section-like "page" on your existing one-pager | Nothing's actually broken yet | Add another section, and consider a Pro Plus redirect so it has a clean-looking URL |
Carrd is not a bad tool for what it does — it's a genuinely good one-page site builder, and its multi-site-slots-plus-subdomains combination is a legitimate way to stretch it further than "one page" suggests. The honest signal that you've outgrown it isn't a page count; it's needing a content type Carrd doesn't model at all — individual posts, a product catalog, or pages that need their own crawlable identity rather than an anchor link dressed up with a redirect.
What if a change goes wrong?
Carrd changes are low-risk 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, and, if you're on Pro Plus, download a copy of the site first as a static backup.
Bottom line: Before assuming you need a different platform, check whether a Pro Plus redirect or a second linked Carrd site on a subdomain actually solves your problem — both are real, documented features, not workarounds Carrd is trying to hide. If what you need is a true CMS, a real store, or pages with their own crawlable metadata, that's a different kind of tool than Carrd was built to be, and no plan upgrade changes that.
