Most advice on landing page vs website stops at "a landing page has one goal, a website has many." That's true, but it doesn't tell you which one your business needs. A landing page and a website aren't two different products. They're one publishing spectrum. What decides where you sit on it isn't a design preference, it's the actual scope of the business behind the page.
The five questions that actually decide it
Answer these honestly and count which column you land in more.
| Question | Landing page fits when... | Website fits when... |
|---|---|---|
| How many distinct offers do you sell? | One offer, or one offer at a time | Two or more offers a buyer might compare |
| Where does traffic come from? | One channel, one campaign, one link you're sharing | Several channels bringing people in with different questions |
| Does a buyer need proof before they trust you? | The pitch itself carries enough proof | You need dedicated space for case studies, credentials, or a portfolio |
| Is there content that changes or accumulates? | No, the page says the same thing for months | Yes, a blog, a growing portfolio, a changing service list |
| Who maintains it, and how often? | You, rarely, for one campaign | You or someone else, on an ongoing basis |
If most of your answers land in the left column, build a landing page. If most land in the right, you're describing a website, even if it only has three pages today.
What each looks like once you decide
What is a landing page?
A landing page is a single web page built to get a visitor to take one specific action: buy, book, sign up, or leave an email. It has no navigation menu, because there is nowhere else you want the visitor to go. Everything on it, from the headline to the last button, argues for that one action.
In practice that means a hero, some proof, the offer, and a call to action, repeated in different words if the page runs long. Any links on it either point at the action or open a form. A landing page can be four screens or forty, and it's still one URL making one argument.
When that one action is handing over contact details rather than buying, a lead-gen page is the version worth building, and where its submissions land decides whether the page earns anything. If the thing you are selling does not exist yet and the only action left is leaving an email, that is a coming-soon page, which is a smaller job again.
If you want to see how far one page can stretch, we reviewed five commercial one-page websites against the same rubric. The useful part is watching where each page decides to stop.
What is a website?
A website is a set of connected pages under one domain, each answering a different question a visitor might bring: what you do, what it costs, who you have done it for, how to reach you. A shared navigation ties the pages together, and the homepage's job is to route people, not to close the sale.
It doesn't need to be big. Three pages with a menu is a website. Forty sections on a single URL is still a landing page. The test is whether a visitor with a specific question gets sent to a page that exists to answer it.
Both are structures, not styles. Website layouts goes through five of them, with a prompt your agent can build from for each. If you would rather assemble the one-page version by hand, Carrd is built for exactly that; how it compares with having your agent build it is mostly a question of who maintains the page later.
The mistake that costs the most
Building a five-page site around one offer is the common one. Extra pages just dilute the single argument a landing page needs to make, and most of them sit unread. The reverse mistake happens too: staying on one page after a second offer or a second audience shows up, and cramming both into a page that was only ever built to make one argument.
Both mistakes come from the same place: picking the structure a "real business" is supposed to have, instead of the one the business you actually run needs this quarter.
What the choice costs, and what it does to search
None of this is in the table, because it isn't a question about your business. It's a consequence of the answer, and it's the part that decides whether you regret the choice in six months.
The cost side
A landing page is cheaper to build for a simple reason: there's one argument to write and one page to design. A website multiplies that. Every page needs its own reason to exist, its own copy, and a place in the navigation, and the pages have to agree with each other.
If an agent is doing the building, the gap in build time shrinks a lot. Asking for five pages is not five times the prompting. The gap in upkeep does not shrink.
Upkeep is where the real difference lives. A landing page goes stale as a unit: the offer changes, you rewrite the page, done. A website goes stale page by page. The pricing page is out of date, the portfolio stops at last year's work, the about page still mentions a partner who left. Each is small, and each is a separate thing somebody has to notice and fix.
Then there's the redesign. Redesigning a landing page is an afternoon with your agent. Redesigning a website means touching the navigation, the shared header and footer, and every page that depends on them. That's the cost nobody counts when they build five pages "just in case."
Hosting is the one line where the choice makes no difference, at least on Birta. Plans are limited by the number of projects and the weight of each one, not by page count. As checked on September 4, 2026, the free plan allows 50 projects at 25 MB each, and the Solo plan is $12 a month. If a project ever hits that ceiling, it will be images, not a fourth page.
If you're building this for a client rather than for yourself, the cost question turns into a pricing question, and that's its own article.
The SEO side
Search treats a page as the answer to a question, roughly one question per URL. That fact decides most of the SEO consequences here.
A landing page has one URL, so it can rank for one cluster of closely related searches: your name, your offer, maybe the offer's category plus your city. It will not rank for the questions your buyers ask before they know your offer exists, because there's no page answering them. That's fine if your traffic comes from ads, a newsletter, a social profile, or a link you send by hand, which is exactly the "one channel" answer in the table.
A website can rank each page for a different question, and the pages support each other. The services page ranks for what you sell, the case studies page for proof-seeking searches, the about page for your name. That coverage compounds in a way a single page can't. If your row-two answer was "several channels bringing people in with different questions," organic search is probably one of them, and only a website can serve it.
One warning in the other direction. Splitting one offer across five thin pages doesn't buy you five rankings. It buys you five pages that each say too little to rank for anything. One thorough page about one offer usually beats the same content chopped into a site, so don't build a website for SEO unless you genuinely have several distinct questions to answer.
Growing from one into the other
Here's the part that usually worries people, and it doesn't need to. There's no migration between "landing page" and "website" on Birta, because there's nothing to migrate. Publishing a project means publishing whatever files describe it right now. Adding a second page later is the same action as publishing the first one: ask your agent to build it, then publish. Nothing about the address, the account, or the plan changes because the project grew from one page to five.
The trigger for growing is almost always one row of the table flipping. A second offer shows up. A second channel starts sending people with different questions. The portfolio you meant to cap at six pieces is at fourteen. When that happens, add the page that row is asking for, and only that page.
Start with exactly as much site as you need today
One page or five, the publishing step is the same. Add pages when the business actually needs them, not before.