One-Page vs Multi-Page Websites: Which Is Right for Your Business?

A one-page website puts everything a visitor needs – what you do, proof you do it well, prices, answers, a way to contact you – on a single scrolling page. A multi-page website spreads the same story across separate URLs: a home page, service pages, an about page, maybe a blog. Almost every small-business client I have worked with in the last twelve years has asked me some version of the same question: “Do we really need all those pages, or is one enough?” It is a good question, and the honest answer is: it depends on what you sell, how you plan to grow, and where your visitors come from – not on what looks modern or what a template happens to offer.

I have built both kinds hundreds of times – one-pagers for consultants, product launches and restaurants, and thirty-page service sites for clinics, manufacturers and agencies. In this guide I will give you the sizing guidance I give my own clients: what one-pagers genuinely do well, where they hit hard ceilings (especially in search), what multi-page sites buy you for the extra money, how the SEO mechanics actually work in plain language, a business-type table you can find yourself in, honest cost numbers, and – the part most guides skip – how to build a one-page site today so that growing it into a full site later is cheap instead of a rebuild.

Table of contents

• One-page and multi-page: what I actually mean
• What one-page websites do brilliantly
• The ceilings: where a one-pager stops working
• SEO mechanics in plain language: one URL, one intent
• What multi-page websites do better
• Anchor navigation: making a one-pager pleasant to use
• Which businesses need which: a sizing table
• The cost difference, honestly
• The hybrid path: a one-pager built to split
• Migrating from one page to multi-page later
• Frequently asked questions

One-page and multi-page: what I actually mean

The terms get used loosely, so let me define them the way they matter in practice. A one-page website is a site where the primary content lives on a single URL – usually the home page – organised into sections you scroll through: hero, services, about, testimonials, pricing, FAQ, contact. The navigation, if there is one, jumps you between sections on the same page rather than loading new pages. A legal page or two (privacy policy, imprint – mandatory in Germany, where many of my clients are) does not stop it being a one-pager; what matters is that the selling happens on one URL.

A multi-page website gives each major topic its own URL: a home page that summarises, a page per service, an about page, a contact page, and often a blog or case-study section that grows over time. Five pages is a small multi-page site; thirty is a normal one for an established service business.

Two things a one-pager is not. It is not the same as a landing page – a landing page is a one-page design built for a single campaign and a single conversion, usually with the navigation stripped out entirely; I wrote about that separately in WordPress landing pages that convert. And it is not a “starter template” – a good one-pager is a deliberate choice with real advantages, not a cheap placeholder you apologise for. The decision between the two shapes is a business decision first and a technical one second, which is why I always start the conversation with what the business sells and where its customers come from, not with design.

What one-page websites do brilliantly

One-pagers are not the compromise option. For the right business they are the better option, and here is why:

• Focus. One page forces one story told in one order. The visitor cannot wander off to a weak page you forgot to update; they read your pitch the way you sequenced it – problem, solution, proof, price, action. For a business with one core offer, that control over the narrative is worth more than ten scattered pages.
• Launch speed. There is simply less to design, write and build. A custom one-pager goes from brief to live in one to two weeks in my experience; the content – usually the real bottleneck – is seven or eight sections of copy instead of thirty pages of it. If the business needs to be online next month, one page gets it there.
• Small budgets stretch further. Every euro goes into making one page excellent instead of making ten pages adequate. A tight budget spent on a sharp one-pager beats the same budget smeared across a thin multi-page site every time – thin pages hurt you in search and in credibility.
• Events and product launches. A conference, a book, a single product, an app: these have one message and often a deadline. A one-pager matches the shape of the thing it sells.
• Mobile behaviour. On a phone, scrolling is easier than navigating. A well-built one-pager feels natural on mobile – one thumb, one direction – where a deep menu structure feels like work. Given that most small-business traffic is mobile now, this matters more than it did ten years ago.
• Maintenance. One page to keep current means the site actually stays current. I have seen far more embarrassing outdated service pages on neglected ten-page sites than outdated sections on one-pagers.

A client of mine, a consultant in the UK, replaced an ageing eight-page site with a single sharp page. Enquiries went up, not down – because the eight pages had been diluting the pitch, and the one page concentrated it.

The ceilings: where a one-pager stops working

Every advantage above comes with a ceiling, and it is my job to tell you where they are before you hit them:

• Search visibility is the big one. Google ranks URLs, not sections. One URL can realistically rank for one topic cluster – your name, your core service in your city, and close variations. It will not rank for “web design Bristol” and “logo design Bristol” and “brand strategy Bristol” at the same time, because those are three intents and you have one page to answer them with. If search is meant to be a growth channel, this ceiling arrives fast. I unpack the mechanics in the next section because clients deserve to understand the why, not just the rule.
• Analytics granularity. On a multi-page site, “which pages do people visit, where do they leave” answers itself in any analytics tool. On a one-pager everything is one URL: you have to set up scroll-depth and section-visibility events to learn anything, and even then you see engagement, not intent. You can instrument it – I do, with GA4 scroll and visibility events – but you are working harder for coarser data.
• Content growth has nowhere to go. Want to add a case study? A second service? An FAQ that has grown to twenty questions? On a one-pager every addition makes the one page longer and the message less focused – the exact quality that made it good erodes with every “can we just add” request. A one-pager that has absorbed two years of additions is the worst of both worlds: long, unfocused and still one URL.
• Multiple audiences fight for the same screen. If you serve private customers and trade customers, or three distinct industries, one page forces them all through the same story. Each audience scrolls past content meant for someone else, and the pitch weakens for everyone.
• No natural place for trust-building depth. Detailed case studies, team profiles, process explanations – the content that closes bigger, slower deals – needs room a single page cannot give without becoming a scroll marathon.

None of these ceilings matter until they do. The skill is in judging whether your business will hit them in year one or year five – and building accordingly, which is what the hybrid section below is about.

SEO mechanics in plain language: one URL, one intent

This is the part I find myself explaining most often, so here it is without jargon. Google’s index is a list of URLs. When someone searches, Google picks the URLs that best answer that search. A URL earns a ranking through its title, its headings, its content and the links pointing at it – all signals that tell Google “this URL is about X”.

A one-page website has one URL, so it gets one title tag, one H1 and one accumulated pool of link authority. All of it points at one topic. That is genuinely fine – excellent, even – if you want to be found for one thing: “management consultant Hamburg”, your own name, your product’s name. The page can absolutely rank, and rank well, for that cluster of closely related searches.

The problem starts when you want to be found for several distinct things. Each search intent – each meaningfully different thing people type – is a separate competition, and you enter each competition with a URL. A plumber who wants to be found for boiler repair, bathroom installation and emergency call-outs is entering three competitions; with a one-pager he has one competitor entry to spread across all three, while the multi-page plumber down the road has a dedicated, focused page in each. Guess who wins. Section anchors do not fix this: Google occasionally shows fragment links in results, but anchors are not separate index entries, do not accumulate their own authority, and cannot carry their own title tags.

There is a second-order effect too: content publishing. Ranking for informational searches (“how much does a boiler service cost”) requires articles, and articles need URLs. A one-pager has no blog, so it cannot play that game at all. So the plain-language summary I give clients: one URL competes for one intent. Count the distinct things you need to be found for. One? A one-pager works. Three or more? You need pages, or you need to accept that search will not be your growth channel and traffic must come from ads, referrals and social instead – which is a legitimate strategy, as long as it is chosen and not stumbled into.

What multi-page websites do better

The multi-page site’s advantages are mostly the mirror image of the one-pager’s ceilings, but they are worth stating positively because they compound over time:

• Topical spread in search. Every service gets a page, every page enters its own ranking competition with a focused title, heading and content. A site with eight well-written service pages is fishing with eight lines. This is the single biggest commercial difference between the two shapes.
• Service pages that convert as well as rank. A dedicated page can answer everything a buyer of that specific service wonders – process, pricing logic, examples, FAQs – without boring the buyer of a different service. Focused pages convert better than general ones for exactly the reason focused one-pagers beat bloated ones.
• Content that scales without damage. New case study? New page. New service? New page. Twenty blog posts? A blog. The home page stays sharp because growth happens elsewhere. A multi-page site can absorb five years of business evolution without a redesign; a one-pager usually cannot absorb two.
• Deep links for campaigns. Ads, emails and social posts can land people on the exact page that matches the message – a message-match discipline that measurably lifts conversion, as I covered in the landing pages guide.
• Cleaner analytics. Page-level data tells you which services attract interest, which pages leak visitors, and what content earns its keep – with zero custom event setup.
• Room for trust. About pages, team pages, detailed case studies and process pages do quiet work on bigger deals, where buyers research thoroughly before making contact.

The cost of these advantages is real: more content to write, more design decisions, more to maintain, and a longer build. A multi-page site full of thin, hastily written pages is worse than a good one-pager – Google notices thin content and so do humans. Multi-page wins only when you can actually fill the pages properly.

Anchor navigation: making a one-pager pleasant to use

If you do go one-page, the navigation deserves more care than it usually gets, because it is the whole user experience. These are the details I build into every one-pager:

• A sticky header with section links. The menu stays visible as you scroll, and each item jumps to a section: Services, Pricing, About, Contact. Visitors get orientation without leaving the page.
• Smooth scrolling with an offset. Clicking an anchor should glide, not teleport, and the target section must not hide under the sticky header – a CSS scroll-margin on the section headings fixes that. It sounds trivial; half the one-pagers I audit get it wrong.
• Active-section highlighting. As you scroll, the menu item for the section on screen highlights. It is a small script, and it replaces the “where am I” feeling that long pages otherwise create.
• Anchors that update the URL. When each section has a real fragment (yoursite.com/#pricing), people can share and bookmark the exact section, and your ads can link straight to pricing. It also seeds the section structure you will want if the site later splits into pages.
• A mobile menu that closes after the tap. On phones, tapping a menu item must close the menu and land accurately. Broken mobile anchors are the most common one-pager bug I fix.
• A back-to-top control after two or three viewport heights, because the contact form is usually at the bottom but the phone number is at the top.
• Section tracking in analytics. GA4 visibility events per section turn the one URL into something you can actually learn from: if 80% see services but 20% reach pricing, the middle of the page is too long.

Get these right and a one-pager feels effortless. Get them wrong and the format’s biggest strength – flow – becomes its biggest weakness.

Which businesses need which: a sizing table

Here is the guidance I actually give when a client asks. Find your business type; the pattern holds far more often than not:

Two honest caveats. First, the table assumes search matters to you; a business fed entirely by referrals and repeat customers can run happily on a one-pager whatever its type – I have a client, a specialist engineering firm in Germany, that wins six-figure contracts with a one-page site because every deal starts with a phone call, not a Google search. Second, “multi-page” does not mean big: five excellent pages beat fifteen mediocre ones. Size the site to the content you can genuinely make good.

The cost difference, honestly

Numbers, because clients deserve them. At my rate of EUR 15 per hour, a custom-designed, custom-coded one-page WordPress site typically takes 30 to 50 hours – design system, the page itself with editable sections, responsive and performance work, forms, analytics, launch – so roughly EUR 450 to 750. A typical multi-page business site (home, four to six service pages, about, contact, blog set-up) runs 60 to 120 hours, so roughly EUR 900 to 1,800. Bigger sites, stores and integrations go up from there; the full picture with market comparisons is in how much a custom WordPress website costs. With a Western European or US freelancer, multiply those figures by three to six; with an agency, more again.

So the build cost difference is real but not dramatic – roughly double, not ten times. The bigger cost difference is the content. A one-pager needs seven or eight sections of sharp copy; a multi-page site needs a page of genuinely useful content per URL, and that is where projects stall for months. When a client has no content resources, that alone can be the deciding argument for starting with one page.

Two cost traps to avoid. First, the cheap multi-page template that promises twenty pages for the price of one: you get twenty thin pages that rank for nothing and impress nobody, which is worse than one good page (the same false economy I describe in WordPress vs website builders). Second, the expensive one-pager that was not built to grow: it saves you EUR 500 today and costs you a EUR 1,500 rebuild in eighteen months. The hybrid build below is how you avoid that one. Ongoing costs – hosting, domain, maintenance – are nearly identical for both shapes at this scale, so they should not influence the decision.

The hybrid path: a one-pager built to split

This is my standard recommendation for new and growing businesses, and it is the section I most wish other guides included. You can have the one-pager’s launch speed and focus today, and the multi-page site’s growth tomorrow, if the one-pager is engineered for the split from day one. Concretely, this is how I build them:

• Every section is a self-contained, reusable block. In a custom theme I build each section – services, about, testimonials, pricing, FAQ – as its own template part with its own fields, not as one long wall of content in a single editor box. When the time comes, a section becomes the seed of a page instead of copy-paste surgery. This is the core of how I approach WordPress theme development generally: structured, editable sections rather than monolithic pages.
• One intent per section, in writing. Each section gets its own heading that could serve as a future page title, and its copy sticks to its topic. A disciplined section structure today is a page structure tomorrow.
• Content lives in structured fields, not in the design. Testimonials as entries, services as items, FAQs as question-answer pairs. Structured content can be poured into new page templates in hours; content welded into a page builder layout cannot.
• The navigation is a real WordPress menu that happens to contain anchor links. When pages exist, the menu items change from #services to /services/ without touching the theme.
• The URL plan exists before it is needed. I note, at build time, what the future pages would be (/services/x/, /about/, /blog/) so the anchors, headings and internal logic already mirror that map.
• The blog is dormant, not absent. WordPress has the blog machinery anyway; I leave it configured but unlinked. The day the client wants to publish, they publish – no project required.

Built this way, the split is an editing job, not a development project – typically 10 to 20 hours instead of a rebuild. Built the usual way – everything in one page-builder canvas – the split means starting over. The difference costs almost nothing at build time and everything eighteen months later.

Migrating from one page to multi-page later

When the ceilings arrive – usually the SEO one first – the migration itself is straightforward if you sequence it properly. This is the order I follow:

1. Decide the page map from search intents, not from the org chart. List the things the business needs to be found for; each distinct intent becomes a page. Three services people actually search for beats six pages nobody asked for.
2. Write the new pages before touching the site. Each service page should say more than its old section did – process, examples, FAQs, pricing logic. If the page is just the old section with more padding, it will not rank and was not worth splitting out.
3. Turn the one-pager into the home page. The long page becomes a tighter summary: hero, condensed service overview linking to the new pages, best proof, contact. Its job changes from “tell everything” to “route and reassure”. Do not leave the full old content competing with the new pages for the same topics.
4. Swap anchors for URLs. Menu items, buttons and any ads pointing at #services now point at /services/. Old fragment links in the wild need no redirects – fragments were never separate URLs in Google’s index, which is exactly why this migration is SEO-safe. The home page keeps its accumulated authority, and internal links pass it to the new pages.
5. Wire the SEO plumbing. Unique titles and meta descriptions per page, the sitemap updates itself, submit it in Search Console, and add internal links between related pages. Expect new pages to take weeks to months to find their rankings – they are new entrants in their competitions.
6. Instrument and watch. With real pages you now get page-level analytics for free. Watch which service pages attract impressions in Search Console over the following months; that data will tell you what to build next, which is a luxury the one-pager never gave you.

Done in this order, I have never seen the split hurt existing rankings; the home page keeps ranking for the brand and core term while the new pages open new fronts. Done backwards – pages first, content later, home page left bloated – it produces months of duplicate-content mush. Sequence matters more than speed.

Not sure which size fits your business?

I build both – sharp one-pagers engineered to grow, and full multi-page WordPress sites – custom-coded, fast and easy to edit, for small businesses and agencies across Germany, the UK, the USA and Australia. Tell me what you sell and where your customers come from, and I will give you an honest sizing recommendation and a fixed quote – I reply within 24 hours. See custom WordPress development and my portfolio, or get in touch.

Frequently asked questions

What is a one-page website?

A one-page website presents all primary content – services, proof, pricing, contact – as sections on a single scrolling URL, with navigation that jumps between sections instead of loading separate pages. Legal pages aside, the whole pitch lives on one page.

Are one-page websites good for SEO?

For one topic, yes – a one-pager can rank well for one cluster of closely related searches. For several distinct services or topics, no: Google ranks URLs, and one URL cannot compete for multiple separate intents against sites with dedicated pages.

How much does a one-page website cost?

A custom-designed, custom-coded one-pager typically takes me 30 to 50 hours – roughly EUR 450 to 750 at EUR 15 per hour. A comparable multi-page business site runs about double that. Content, not code, is usually the bigger difference.

When should a business choose a multi-page website?

When it offers three or more services people search for separately, serves multiple audiences, plans content marketing, or sells products online. Each distinct search intent deserves its own page.

Can I start with a one-page website and add pages later?

Yes, and it is often the smartest path – if the one-pager is built with self-contained sections, structured content and a planned URL map. Built that way, splitting into pages is an editing job of 10 to 20 hours, not a rebuild.

Do one-page websites work for online shops?

Not beyond a single product. Shops need separate URLs for products, categories and checkout – both for usability and for search. A one-page design can work for launching one flagship product with a simple buy button, but a catalogue needs a multi-page store.

How long does a one-page website take to build?

One to two weeks from brief to launch for a custom build, assuming the content is ready. The multi-page equivalent typically takes three to six weeks – most of the extra time is content, not code.