The one-page website, and when it is the right shape

The strongest argument against one-page websites is the one people make with a straight face and real evidence: a single page cannot rank for many things at once. Search engines match queries to pages, and if you have one page, you have one shot. A five-page site can own five different searches. That is not a myth, and anyone who waves it away is selling you something.

It is also, for most individual sites, irrelevant. Not because SEO does not matter, but because the searches that bring people to a personal or single-service site are overwhelmingly for one thing: the name, or the one offering. Nobody arrives at a freelance copywriter's site through five distinct query clusters. They arrive because someone said the name, or because the link was in an email signature, or because they saw the work somewhere and wanted to know who made it. Splitting that into five pages does not create four new entrances. It creates four new places for a visitor to be, none of which is where you wanted them.

Which is the actual case for one page, and it has nothing to do with being simpler or faster to build. It is that most individual sites are one page pretending to be five. The About page is three paragraphs. The Services page is a list that would fit in a screen. The Contact page is an email address and a spinning globe. Nothing was gained by the division except the clicks required to reassemble it.

A page is not a smaller site, it has its own rules

The mistake that ruins one-page sites is treating them as a compressed version of a normal site — the same five sections, stacked, with a menu at the top that scrolls instead of navigates. That produces something worse than either shape: a page long enough to feel like a site, with none of a site's affordances for finding your way around.

A single page is a linear medium. It has an order, and the order is not a menu — it is the argument. The visitor starts at the top and either keeps going or leaves, and every section is a decision point where they might stop. On a multi-page site, a weak About page costs you that page. On a one-page site, a weak second section costs you everything below it.

That single property generates most of the practical rules. It is why section order is the main design decision rather than an afterthought, why there is one call to action rather than one per section, and why "we can put that further down" is almost never a solution to a disagreement about content. Further down is where things go to be unread. We work through the section-by-section version of this in how to structure a one-page site; what follows here is the shape-level decision that comes before it.

If a section can be scrolled past without loss, cut it

The most useful test we know for one-page content is uncomfortable to apply. Take each section and ask what a visitor loses by scrolling straight past it. Not what they gain by reading it — anything can be justified that way — but what is missing from their picture of you if they never see it.

Run this honestly and most pages lose a third of their length. The section listing technologies as a grid of logos: a visitor who skips it knows nothing less, because the same information was implicit in the work described above it. The paragraph about your philosophy of collaboration: unless it says something a competitor would not also claim, it is decoration. The testimonial with no name attached: it does not survive the test either, because an unattributable quote does not change anyone's belief.

What does survive is specific. A one-line statement of what you do and for whom, at the top, before anything else. Two or three pieces of proof with enough detail that a stranger could describe them to someone else. A short passage that gives the page a voice rather than a register — this is where a person is allowed to be a person. And the means of contact. That is four things, and four things is a complete page.

The test also catches the failure mode nobody admits to: sections that exist because the template had a slot. Every builder ships layouts with a "Team" block and a "Numbers" block and a strip of client logos, and a solo consultant with no team, no numbers worth publishing and two clients under NDA will fill all three rather than delete them. An empty slot feels like a gap. It is not. A page that stops when it has said what it has to say reads as confidence; the same page padded reads as someone who thought a website was supposed to be a certain length.

Order the sections by what a stranger needs next, and put contact last

The order that works follows a single question: what does someone who has just arrived need before they can use the next thing?

They need to know what they are looking at. That is the first section, and it should say what you do in language a person outside your field would use, not a tagline. Then they need a reason to believe it, which is the work — projects, clients, results, whatever your evidence actually is. Then, and only then, the human material: the background, the path, the things that make you a specific person rather than a category. It goes third because it is only interesting once someone has decided you are worth being interested in. Put it second and it reads as self-absorption; put it third and it reads as depth.

Contact goes last, and this is the part people fight about. The instinct is to put it in a nav bar at the top, permanently visible, because you do not want to lose anyone. But a one-page site has no nav bar in the normal sense — the top of the page is doing the job a homepage does, and a "Contact" link there is asking for commitment before you have given a reason. The scroll itself is the qualification. Someone who has read to the bottom is a different visitor from someone who just landed, and the bottom of the page is where they are most persuaded they have ever been.

The compromise that works, if the page is long, is anchor navigation: a small menu that jumps within the page. It is honest about what it does, it costs nothing, and it lets someone who came back a second time skip to the part they wanted. What it must not do is look like site navigation. If the labels read like page names, visitors expect page loads, and a jump that lands them halfway down a document they thought they had left is disorienting in a way that a plain scroll never is.

One call to action, repeated verbatim if it appears more than once. Two different asks — "book a call" here, "download the deck" there — split the visitor's attention at exactly the moment you have all of it.

Some tools are built for one page and some merely tolerate it

Nearly every builder can produce a single page. The difference is whether the tool's structure, pricing and defaults assume one page or assume a site with one page currently in it, and that difference shows up in what you fight against.

Carrd is the clearest example of a tool built for the shape. It exists for single-page profile, landing and link-in-bio pages, and the pricing reflects a product that never intends to grow: annual billing only, Free at $0 for three sites, Pro Lite at $9 per year, Pro Standard at $19 per year for ten sites, Pro Plus at $49 per year for twenty-five. The trap is the one Carrd's own docs name — Pro Lite is described as being for users who do not use custom domains, so the advertised $9 entry does not put a portfolio on your own name. That needs the $19 tier. The free tier carries a "Made with Carrd" footer, has an element limit, and has no forms, widgets or analytics. There is no AI generation anywhere in the product. You start from a template and you write everything.

Single-page templates inside general builders are the second route, and they work, with a caveat. Framer's Basic plan is $10 per month billed annually or $15 monthly, priced per site, and includes a custom domain and thirty pages — twenty-nine more than you need. You are paying for a page tree, a CMS and collaboration you will not touch. That is not irrational if you expect to grow into it, but be clear that the thing you are buying is optionality. Webflow's cheapest paid site plan, Basic at $15 per month billed annually or $25 monthly, gives you 300 static pages and no CMS at all — the CMS starts at Premium. For one page, that is a lot of platform standing behind a single scroll.

The third route is generation from something you already have. reach is the tool built specifically for the case where the page is about a person: you upload a CV and a photo, answer a short form and choose a look, and it composes the page rather than handing you a canvas. Generation runs in two phases: about two seconds of deterministic composition with no model call at all, followed by about eight seconds where a single model call refines the palette, the section order, the rhythm and the copy. The two numbers worth quoting are the ones that follow from that: the page is generated in about twenty seconds, and you can be live at a free subdomain in under two minutes. If the second phase fails, the first phase's page ships, so a run cannot end empty. The sections it can produce are fixed at eight types — hero, CV timeline, own projects, values, personality, interests, books, contact — with hero always first and contact always last, which is either a limitation or an opinion about section order, depending on whether you agree with the one above. Publishing to a yourname.joinreach.app subdomain is instant and free.

The limits are absolute and worth stating before the price. One project is exactly one index.html: there are no sub-pages, no navigation between pages, no site tree, and no path to one later. There is no CMS, no shop, and no contact form — the contact section is a mail link and profile links, not something that posts anywhere. There is no HTML export and no custom code field, so you cannot take the markup elsewhere and you cannot paste in your own CSS or scripts. You also cannot connect a domain you already own; the only route to a custom domain is buying one through reach, which for anyone whose name is already sitting at a registrar is a blocker with no workaround. The editor needs a desktop — below 820 pixels it becomes a read-only preview. Premium is $4.99 per month or $49 per year.

Route	Price	Billing	Custom domain
Carrd Pro Lite	$9	per year, annual only	no
Carrd Pro Standard	$19	per year, annual only	yes
reach subdomain	$0	included	no
reach Premium	$4.99 / $49	per month or per year	only domains bought through reach
Framer Basic	$10	per month, billed annually	yes
Webflow Basic (site plan)	$15	per month, billed annually	yes
Typedream Launch	$15	per month, billed annually, per site	yes

Prices checked August 2026.

Two things fall out of that table. The cheapest way to a one-page site on your own domain is still Carrd at $19 a year, and nothing in the AI-generation category comes close on price. And the general builders cost roughly six to ten times as much per year for a capability set you have already decided not to use. What you are choosing between is not really price. It is whether your obstacle is money, momentum or the blank page — and those three obstacles have different answers, which is the whole of the CV generator versus template comparison.

Three signals that you have outgrown the page

One page stops being right at identifiable moments, and none of them is "it feels small".

The first is when you start writing things that need to be dated. A post, an update, a case study you will add to monthly — anything with a chronology implies a list, and a list implies pages behind it. You can fake this on a single page for about three entries. At the fourth the page becomes an archive with the introduction stapled to the top, and the introduction stops being read.

The second is when two different visitors need two different first sections. A consultant who sells to enterprise buyers and also teaches a course has two audiences with almost no overlap in what they need to see first. On one page, one of them reads a section addressed to someone else before reaching theirs, and the linear order that made the page strong is now working against half the traffic. That is the point where separate entry points earn their clicks.

The third is transactional: the moment something has to be bought, booked against a calendar with real availability, or submitted through a form that routes somewhere. Not because a single page cannot host a checkout — some can — but because commerce brings its own required pages. Terms, returns, a receipt flow, a privacy statement that actually applies. The site tree arrives whether you planned it or not. We take the borderline cases apart in when one page is not enough, and the general trade-off in the one-page and multi-page comparison.

Absent those three, we would build one page and stop. For a person selling judgement, availability or a body of work — a freelancer, a consultant, a designer, a developer, a founder putting a face to a company — the page is the whole product, and the correct tool is whichever one removes the obstacle you actually have. If that obstacle is cost and you are happy to write, Carrd at $19 a year is the answer and has been for years. If it is the blank canvas and the content already exists in a CV, a generator that hands you a draft to edit is worth more than any template, provided you can live without sub-pages, exports and your existing domain. And if you can name which of the three signals above is six months away, skip both and start on a builder with a page tree, because migrating a page you like is more expensive than building a slightly overspecified one now.