When Is a One-Page Website Enough, and How Do You Build One?

A one-page website is enough when everything you need to say serves a single purpose - a portfolio, a product launch, a link-in-bio, a simple business card site - and not enough the moment you need separate content to rank for separate topics. One page means one URL, one title tag, and one shot at ranking for whatever that page is about. That's a feature for a focused site and a real limit for anything broader. Here's what actually fits on one page, the SEO trade-off, and three ways to build one.

What actually fits on one page?

A one-page site works well when the whole point is a single message, viewed by someone who scrolls rather than navigates:

• A portfolio or personal site - who you are, selected work, contact info.
• A product or event launch page - one offer, one call to action.
• A link-in-bio page - a small hub of outbound links, often paired with a social profile.
• A simple business card site - hours, location, phone number, a few photos.
• A pre-launch or "coming soon" page - one message, one email capture form.

It stops fitting the moment you have genuinely separate topics that each deserve their own page - a blog with multiple posts, a product catalog, documentation, or anything where a visitor searches for one specific thing among several. Cramming a blog and a store and a portfolio onto a single scrolling page doesn't make the site simpler; it just means every one of those things is competing for the same URL.

What's the actual SEO trade-off?

The core trade-off is that one URL can really only be the primary answer for one topic. Google's own developer documentation on consolidating duplicate content explains why a single, clear URL per subject matters: choosing one representative page "helps search engines to be able to consolidate the signals they have for the individual URLs (such as links to them) into a single, preferred URL" (Google Search Central, "How to Specify a Canonical URL", checked September 2026). Spread the same authority-building signals - links, shares, on-page relevance - across several pages on separate topics, and each one benefits from being its own clear target.

Google's guidance on what makes content genuinely useful reinforces the same point from the content side. Its people-first content documentation asks site owners to check "Does your site have a primary purpose or focus?" and warns against a pattern where a site is "producing lots of content on many different topics in hopes that some of it might perform well in search results" (Google Search Central, "Creating helpful, reliable, people-first content", checked September 2026). A one-page site is the extreme, focused end of that spectrum - one topic, one page, nothing scattered. The trade-off is that you can't separately target more than one real search intent: a one-page portfolio site isn't also going to rank well for a dozen different blog-post topics, because it doesn't have a dozen different pages for Google to index and match against those searches.

In practice: if you have exactly one thing you want people to find you for, one page is a clean fit. If you have several distinct things people might search for separately, you need separate pages - or you're deliberately trading away the ability to rank for more than one of them.

What are my three routes to build one?

Route 1: A dedicated one-page tool

Carrd is built specifically around this constraint - it doesn't have a concept of adding a second page. Instead, it organizes content into named "sections" within one page, which Carrd's own documentation describes as regions 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). Its free tier is real and publishes a working site; a custom domain and working contact/signup forms require a paid plan. Our full guide to building a Carrd site covers the actual build steps, plan tiers, and what happens if you later need more than one page.

Route 2: A one-page site on a general builder

Most mainstream builders (Squarespace, Wix, Webflow, Framer) can build a single-page site just as easily as a multi-page one - you simply don't add a second page, and the whole site is one long scrolling design instead. This is a reasonable route if you might expand to a second or third page later, since the builder doesn't lock you into one page the way Carrd's model does. The trade-off is that these builders are heavier tools for a job Carrd is purpose-built for, and their entry paid plans typically cost more than Carrd's for the same one-page result.

Route 3: Design it in Figma, publish it with Figment

If you'd rather design the layout yourself before publishing, building the page in Figma and publishing it directly is a third route. Our guide to publishing a Figma design as a website covers the actual steps: preparing one top-level frame, adding link and hover behavior, and publishing it to a figment.so subdomain through the Figment plugin - free, with a badge, or on a paid plan for a custom domain and no badge. This fits a one-page site cleanly, since Figment's plugin publishes a single selected frame as the site - it isn't a multi-page CMS or blogging tool, so it's the wrong choice if what you actually need is several separately-ranking pages.

Which route should I actually pick?

• Pick Carrd if the site will realistically always be one page, and you want the smallest, cheapest tool built exactly for that job.
• Pick a general builder's one-page mode if there's a real chance you'll add a second or third page later, and you'd rather not migrate tools when that happens.
• Pick Figma plus Figment if you already design in Figma, want full visual control over the layout, and are comfortable with a design-first workflow rather than a drag-and-drop page editor.

What if I outgrow one page?

This is the most common way a one-page site stops being enough - you started with a single portfolio page and now need a blog, a second offer, or a dedicated page for a new topic. If you built on Carrd specifically, our dedicated guide to outgrowing Carrd covers the real options: linking multiple Carrd sites together, using path-style redirects, or moving to a multi-page builder, along with what actually carries over if you leave. The same underlying question applies regardless of tool: does the new content genuinely need its own URL to be found for its own topic, or does it still fit as another section on the same page? If it's the former, that's the signal to move to a real multi-page site rather than adding more sections to one that was never meant to hold them.

Bottom line: one page is the right choice when your site has exactly one job to do, and Google's own documentation is consistent with that - a clear, single-purpose page consolidates its ranking signal instead of splitting it. The moment you have more than one genuinely separate topic that people search for on its own, that's the signal to add real pages rather than more sections.