how do i make a one-page website that still works?

web · 2026-09-17 · 3 min

a one-page site is a decision about scope, not a budget compromise. it works when one page can answer the whole question: who you are, what you do, proof, and how to start. it fails when you have five different services and three audiences, because the page becomes a queue nobody reads to the end.

the structure that works is almost always the same: a first screen with the offer, a section of proof, the services in short blocks, a few questions, and a contact section. everything reachable from a menu that scrolls instead of loading.

when one page is enough

freelancers, consultants, a single restaurant, a single event, a product with one buyer. the test is simple: can a stranger describe what you do after ten seconds, and is there only one action worth taking?

if the answer is yes, a one-page site is faster to build, easier to keep current, and cheaper to host. it also forces the hard editing: every sentence has to earn its place. a landing page is the extreme version of this, and the logic is similar: do i need a landing page.

the anchors

each section gets an id, and the menu links to #servizi, #lavori, #contatti. keep the labels short and in the order a visitor would ask the questions. the browser handles the scroll; you do not need javascript for it.

two details make the difference. first, the sticky header should not cover the section title when it jumps — add scroll-margin-top in css. second, the url should update as you scroll if you want people to share a section, which takes a small script or a scrollspy library.

when to split

split when a page needs its own search intent. "restauro mobili a parma" and "consulenza arredi" are two pages, not two paragraphs, if people search them separately. split also when the page passes roughly ten screens on a phone and the contact form is buried.

the honest trade-off: one page ranks for fewer queries and accumulates less authority per topic. for a local business with one service, that is fine. for a studio with six, it is a ceiling.

faq

is a one-page site bad for seo?

not inherently, but it is limited: one url can target one main topic well. if you need to rank for several distinct services, separate pages do that better.

can i add pages later?

yes, and the menu is the only thing that has to change. build the anchors with names you can turn into urls later, and the migration is small.

how long should the page be?

long enough to answer the questions a customer asks before writing, short enough that the contact section is two thumb-scrolls away on a phone.