Websites and stores
When does a one-page website make sense?
A one-page website can suit one offer and one main customer decision, such as registering for a workshop or enquiring about a specific service. Different audiences and information needs may call for separate pages. This guide covers selection scenarios, content, illustration, navigation and measurement.
One proposition and one route
The important question is whether the offer follows one coherent route. Visitors should be able to move from the service description to an example and then to contact without reading material intended for a different audience.
Write the proposition in one sentence, then list questions people ask before contacting you. If the answers form a simple sequence, one page may be enough. If each audience needs a different starting point, consider separate pages.
One-page sites, landing pages and apps are different things
One-page describes structure: the main offer fits into one document, and navigation may lead to sections within it. Landing page describes a role: the destination for a particular campaign or action. It can be one document inside a much larger website. A single-page application, or SPA, describes an implementation approach and does not automatically mean a website with one offer. Separate these terms when discussing the project so you commission an appropriate result rather than accidentally choose a technology.
For example, a workshop organiser might need a programme, practical information and registration on one page. Terms and privacy information can still have their own addresses. A one-page format does not require squeezing every document into the same scrolling screen. Decide what belongs in the main explanation and what supports further checks. Simplifying the structure should not remove important conditions, organiser details or the opportunity to ask a question before registration. The visitor’s decision remains the organising principle.
Use customer scenarios to choose the format
Consider a specialist offering one clearly defined service in a specific area. Customers need the scope, information about the provider, evidence of the work and a contact route. A one-page site can connect these elements coherently. Now consider a company serving investors, partners and private customers with separate services. Each group asks different questions, needs different documents and begins the relationship differently. Dedicated pages let each visitor reach the appropriate explanation without travelling through unrelated information intended for another audience.
A third example is a new product launched alongside an existing range. It might need a dedicated landing page without replacing the entire corporate website. Before deciding, list customer intentions and the information needed for each. Independent subjects are a reason to consider separate pages, while questions leading to the same decision may fit together. Industry alone does not determine the answer. Two photographers may have very different services, audiences and enquiry processes even though their businesses share the same category.
Arrange content around questions before purchase
Start with what you offer, who it is for and when it is useful. Then present the scope, an example, the working process and conditions needed for a decision. A contact route should appear once the visitor knows enough to act, rather than only after an endless gallery. Shorter copy is not always more helpful. Remove repetition and slogans while preserving the details that prevent misunderstandings: delivery area, exclusions, required materials and how pricing is agreed. These details often matter more than another broad promise.
Sketch the page with real content before judging section heights. Three short process steps do not automatically need a full screen. A meaningful comparison may need more room. Visitors should not scroll across empty space just to reach the next sentence. Check whether headings alone communicate the offer. Ask someone outside the company to identify the next action and explain what they still need before contacting you. Their specific questions provide a useful editorial test and reveal gaps that attractive placeholder content can hide.
Build visual character around the actual offer
An original illustration can explain a service, show relationships between steps or express a brand’s character. Define its job before producing the image. Decoration repeated in every section soon stops contributing. A recognisable motif developed through details, real work photographs and considered typography can be more useful. Combine wide imagery with narrower reading columns, vary the section rhythm and place evidence beside the claim it supports. Use cards and labels where they help a visitor understand or compare something.
Motion should explain change, establish sequence or acknowledge interaction. Avoid making visitors wait for essential information to appear. Design a readable static state and a version that respects reduced-motion preferences. For example, a process illustration can assemble during scrolling while stage names remain available without animation. Also inspect keyboard use, enlarged text and a phone in landscape orientation. Connections between image, copy and action give the page its character. Choose effects that support those connections.
A single page is not automatically a fast page
A long document containing video, oversized photographs and several scripts can be slower than an individual page in a larger site. Decide which assets are needed immediately and which only support later reading. Prepare appropriate image sizes and reserve space for media before it arrives. Add external widgets only when they have a defined job and an owner responsible for their operation. Ease of embedding is not evidence that an element improves the customer’s experience or belongs in the initial release.
web.dev describes Core Web Vitals through loading, interaction responsiveness and layout stability. These are useful assessment areas, but a score does not replace trying the customer’s task. Test on a phone, with a constrained connection and an empty cache. Check whether the menu responds, content shifts unexpectedly and the form behaves predictably. Record the conditions. A single measurement on a fast computer should not be described as every visitor’s experience. Recheck after real photography and marketing tools are added, because they change the page people actually receive.
Make sections and addresses easy to understand
Navigation labels should describe their sections. Check that a link to a particular section works when opened in a new tab and that a fixed header does not cover its heading. The browser’s Back button should behave predictably. On a phone, navigation should not occupy so much space that the content remains difficult to see after it closes. These details matter especially when a long document holds the whole offer. A clear structure helps visitors return to information without remembering how far they scrolled.
Google recommends useful content and understandable organisation. Let the subjects you need to explain determine the number of pages. A separate address can provide a distinct service with its own explanation, examples and context. One-page anchors help navigation but do not create a set of independent service pages. If you plan guides or unrelated categories, give them a place in the architecture. Do not create empty pages differing only by city name. Different reader needs should justify different destinations. Neither a one-page format nor a large collection of URLs guarantees search rankings.
Measure completed actions and enquiry quality
Before launch, name the main action: an enquiry, registration, booking or purchase. Distinguish interest from completion. Clicking a form button does not mean a message was accepted, and reaching the bottom does not establish that someone read everything. Decide which events the chosen measurement system actually records and document its limits. A request counter does not automatically identify which section produced a contact. Agree useful questions first, then select a measurement approach that can answer them with appropriate data.
For example, a campaign may generate enquiries mostly about a service you do not provide. Review the advert promise and opening content before changing a button colour. Repeated questions about conditions may indicate missing scope information. Compare periods with similar traffic sources and record changes. A handful of accidental visits is insufficient evidence that one version has won. Findings should lead to a specific content or design decision. Consider privacy requirements for the actual measurement setup as well, instead of installing every available tracking script in the first release.
Recognise when the website needs more room
Expansion becomes useful when recurring subjects no longer fit one customer route: another audience, detailed documentation, separate project stories or regular editorial publishing. Do not wait until every section contains another nested menu. During the first build, agree how new addresses can be created, who edits content and how existing links will be preserved. A one-page site can be a sensible first stage when its architecture supports separating topics later without rebuilding the entire system. Ask to see how a second page would actually be added.
Before commissioning the site, answer four questions: does the offer lead to one decision, can the main questions form a coherent explanation, where will visitors come from and what will you publish over the coming months? Draft the content and inspect it on a phone. When contacting DigiDraft, include those answers and the materials you already have. They provide a basis for choosing a suitable format. The choice need not be between a tiny brochure and a large portal; a clear homepage with a few useful supporting pages may fit the need.
Questions and answers
When should I choose a one-page website?
It suits one clear offer and one main visitor decision, such as signing up for a workshop. If your services need different explanations and serve different audiences, separate pages can make the information easier to use.
Is a one-page website the same as a landing page?
One-page describes the structure: the main content sits at a single address. A landing page describes a purpose, such as collecting registrations from a campaign. A page can be both, but not every one-page website is built for advertising.
How can I tell when a one-page website needs more pages?
Look for services that need fuller explanations or visitors who must scroll through many irrelevant sections. Check whether campaigns and different search topics need separate addresses. Plan the expansion around those needs while keeping existing links working.