When a one-page site is enough

A one page website for startup teams is enough while you have one offer and one audience. The page can explain the product, show a little proof, and ask for a conversation. Split it when people arrive with different jobs. Hiring, buying, and reading docs are different jobs. One scroll cannot do all three well.

The rule is about the visitor's purpose, not about how modern a single page looks. Google's people-first guidance asks whether a site has a primary purpose and an audience that would find the content useful if they came to you directly. One page can have that focus. A page that tries to recruit an engineer, close a customer, and document an API has several purposes, and each of them gets a thinner answer. Nielsen Norman Group's visit research adds a practical limit. People often leave within 10 to 20 seconds and read only about a quarter of the text on the pages they open. A long single page still has to make sense in the first screen. Length does not buy attention.

When one page is the right shape

Stay on one page when a stranger can describe the company in a sentence, and every visitor you care about wants the same next step.

A founder selling one service to one kind of buyer fits. A new product with a single workflow fits. A studio or a shop that wants an intro, a visit, or an order fits, as long as the order path is obvious. The page can have a hero, a short explanation, proof, and a way to start.

One page is also the right shape when you do not yet have the material for more. Empty inner pages make a young company look unfinished. A single careful page looks decided. You can add URLs later, when a second audience shows up in real messages, not when a template offers you a blog and a careers slot on day one.

Use the page to answer the objections you already hear. How it works. Who it is for. What it costs, or why the price is a conversation. Where the work or the product can be seen. Keep each answer short. The promise of one page is that a busy person can reach the end.

When to split

Split when a second job appears and starts to distort the first screen.

Candidates arrive and cannot find how you work or how to write to you, so someone adds a hiring paragraph under the product explanation. Buyers then have to scroll through benefits and values to find the price. Developers arrive for docs and land in a brand story. Each group is reasonable. The page has become a compromise none of them asked for.

These are the usual splits.

• A product or service page, when the homepage can no longer carry the explanation.
• A proof page, when the work needs more than a single image.
• A short about page, when people ask who is behind the work.
• A way to start a conversation, if the form or the calendar deserves a calm URL of its own.
• Docs, a help center, or a login, when existing users and buyers are sharing one front door.
• A jobs page, when you are actually hiring and have something true to say.

You do not need all of these on the day you split. Add the page that matches the job people are already trying to do. Leave the others until the same pressure shows up again.

A one-page site can link out to a calendar, a deck, or a doc without becoming a multi-page marketing site. The split that matters is a second marketing purpose with its own audience. A PDF proposal is not a second homepage. A careers page is.

What the single page still has to do

Choosing one page does not relax the opening. The first screen still has to say what this is and how to talk to a person. Anchor links to "About" and "Process" do not count as that answer. They are navigation. The sentence above them does the work.

Keep one action. If the page is for buyers, the action is the buyer conversation. A footer link for press or jobs can exist. A second button in the hero means you have already split the audience and have not yet split the site.

Make the order obvious. Offer, then how it works, then proof, then the action again. A single page becomes hard to finish when the order follows the company's org chart: story, team, features, press, and only then the thing you sell. Put the thing you sell first.

Check the page on a phone before you defend it. One page is often designed as a desktop scroll with large type, then stacked into a long walk. If the explanation sits three swipes down, mobile visitors never get the benefit of the format. Move the explanation up. Cut a decorative band before you add a new one.

What you give up, on purpose

A single page is a weak fit for search once people look for specific answers. Someone searching for your pricing, your docs, or a single project has nowhere precise to land. That is an acceptable cost while the audience is one group and you can win the visit from a direct introduction, a talk, or a short list of outbound notes.

It is a poor cost once those specific visits are real. Give the pricing question, the project, or the doc its own URL when you can see people asking. Distinct pages can have distinct titles. A single page with ten anchor sections still has one title, and it has to describe everything at once.

You also give up a quiet place to send a particular person. A founder who wants to share "how we work" with a candidate should not have to say "scroll until you see the gray band." A URL is a kinder handoff. Create it when the handoff becomes common, not in advance for a handoff you have not made.

How to tell that the page is full

Read the last month of conversations. If people keep asking a question the page already answers, the page is unclear, and you should rewrite before you add URLs. If people arrive wanting something the page refuses to mention, because mentioning it would shove the primary offer aside, you are ready to split.

A practical test: imagine sending the page to a buyer, a candidate, and a current customer. If you would write a different preface each time, apologizing for the irrelevant parts, the site wants another page. If the same note works for the people you care about, stay on one page and spend the effort on the sentence at the top.

When you do split, keep the set small. The next piece explains the pages a seed-stage site actually needs, including what to postpone so the site stays believable.

If you want help deciding whether this launch is one page or a short set, look at Hanabi's design and development services. The useful outcome is a site that matches the jobs people already bring to it.