It depends entirely on whether you need to rank. A single page site is a fine choice for a focused campaign, an event, or a product with one job. It is a poor choice for a business that wants organic traffic, because one page can only be one answer to one question, and search rewards sites that answer many.
We get asked this on most new projects. Single page sites look modern, they feel fast, and they are cheaper to build. Clients see a beautiful one page portfolio and want that. Sometimes we agree. More often we push back, and it is worth explaining exactly why rather than just asserting it.
The honest answer is that this is a trade, not a right answer. You are trading discoverability for simplicity. If you know that is the trade you are making, either choice can be correct.
A single page site puts all content at one URL, with navigation that scrolls to sections. A multi-page site gives each topic its own URL, its own title tag, and its own entry in Google's index. The difference is not visual. It is how many separate things a search engine can find and rank.
That framing matters because people compare the two on looks. Visually, a good single page site and a good multi-page site can be nearly identical, since a multi-page homepage still scrolls through sections. The difference only shows up in the address bar and in the index.
Each URL is a ranking target. A page is what Google returns, what a link points to, and what an answer engine cites. A section of a page is none of those things. When you collapse ten topics into one URL, you have not simplified your site. You have reduced ten possible search results to one.
There is also a content ceiling. One page that tries to cover pricing, services, about, case studies, and contact ends up covering each of them shallowly, because the page would be unreadable otherwise. Depth needs room, and room means separate pages.
Because Google ranks pages, not sections. Your one page gets one title tag, one meta description, and one canonical URL. Every query you want to rank for competes for the same slot. Google cannot send someone to your pricing section, because as far as the index is concerned there is no pricing page.
Anchor links do not solve this. A link to a section fragment is still the same URL to Google. Google's URL structure guidance is explicit that you should avoid URL fragments for changing content and use the History API instead. Fragments are for jumping within a document, not for defining separate documents.
The keyword targeting problem compounds it. Good SEO means matching a page to a search intent, and intents differ. Someone searching for what your service costs wants a different page from someone searching for whether you work with their industry. One page cannot be the best match for both, so it ends up being a mediocre match for each.
This is the same reason topical depth works. Building genuine coverage of a subject requires multiple pages that each go deep on one part of it, which is the whole mechanism behind building topical authority. A single page site cannot build topical authority, because it has nowhere to put the depth.
When search is not the acquisition channel. A campaign landing page fed by paid ads, a conference microsite, a product launch page, or a personal portfolio shared by link are all good single page candidates. In each case traffic arrives from somewhere other than a search result, so the ranking cost is not a cost at all.
Focus is the real benefit. A page with one call to action and no navigation gives a visitor nowhere to wander. For paid traffic, that is exactly what you want, because every exit path you remove is a leak you have plugged. Our guide to designing a high converting landing page gets into how far that principle goes.
Speed of delivery is a genuine advantage too. In our own work a focused landing page runs about three to four weeks, against four to eight weeks for a full site build. If you are testing an offer and need to be live quickly, that difference is real.
The mistake is using a single page for a business that needs inbound traffic. A local services company, a SaaS product, an agency, or anything with a content strategy needs URLs to rank. Choosing one page there is choosing to be invisible in search.
More than most people assume, which is the strongest argument in favour of single page sites. Ahrefs studied 3 million search queries in 2017 and found the average number one ranking page also ranked in the top ten for nearly 1,000 other relevant keywords, with a median of around 400.
We include that figure because it genuinely cuts against our own position, and pretending otherwise would be dishonest. A single strong page does not rank for one thing. It ranks for hundreds of variations of the same thing, so the fear that one page equals one keyword is wrong.
The catch is in the word relevant. Those hundreds of keywords are all variations on one intent. A page ranking for best running shoes also ranks for top running shoes and running shoes for beginners, because those are the same question phrased differently. It does not also rank for how to clean running shoes, because that is a different question.
So the real limit is not keyword count. It is intent count. One page covers one intent extremely well and its many phrasings. If your business serves five distinct intents, you need five pages, and no amount of length on one page changes that.
Not necessarily, and this is where the terms get confused. A single page application is a technical architecture where JavaScript swaps content without full page loads. It can still have many real URLs. A single page website is a content decision to put everything at one address. The first is fine for SEO. The second is the constraint.
Google handles single page applications, but with conditions. Its JavaScript SEO documentation describes processing in three phases, crawling, rendering, and indexing, with Googlebot queueing pages that return a 200 status for rendering in a headless Chromium browser. Google warns that a page may sit in that queue for a few seconds, but that it can take longer.
The requirement is real URLs. Google says to use the History API to implement routing between views rather than loading different content behind fragments, and to make sure links use proper anchor tags with href attributes so Googlebot can follow them. Meet those conditions and a React or Vue app indexes fine.
Miss them and you get the worst of both worlds. We have inherited sites where the framework generated no crawlable links and every view lived behind a fragment, so Google saw exactly one page no matter how much content existed. That failure mode is covered in more detail in our piece on JavaScript rendering and why AI crawlers miss your content.
You lose the ability to link to anything specific, internally and externally. Every backlink you earn points at your homepage. Every internal link points at your homepage. All authority pools at one URL, which sounds good until you realise there is nothing to distribute it to.
External links are where this bites hardest. When someone writes about your pricing or references your case study, they link to your site. On a multi-page site that link lands on the relevant page and strengthens it for the relevant queries. On a single page site every link lands on the same place regardless of subject.
Google's URL guidance also warns that if URLs do not meet its criteria, Google Search will likely crawl the site inefficiently. It recommends readable words rather than long identifiers and hyphens rather than underscores. None of that guidance has anywhere to apply on a site with one URL.
Analytics gets worse too. Page level reporting is how you learn which topics people care about. Collapse everything to one page and every session looks identical in Google Analytics, so you lose the feedback loop that tells you what to build next.
Roughly the way Google does, with one extra penalty. Answer engines like ChatGPT, Perplexity, and Google AI Overviews cite specific URLs. A model that wants to attribute a claim about your pricing needs a URL that is about pricing. Given a single page site, it either cites the homepage vaguely or picks a competitor with a cleaner match.
Retrieval works on chunks of text matched against a question, and a focused page is easier to match than a sprawling one. A page that is entirely about one subject gives a retrieval system a clean, unambiguous signal. A page covering eight subjects dilutes that signal across all of them.
The rendering issue matters more here too. Many AI crawlers do not execute JavaScript at all, so content that only appears after a script runs is invisible to them in a way it is not to Google. A client side rendered single page app can be indexed by Google and still be a blank page to an answer engine.
This is why we prerender. Serving real HTML at a real URL costs nothing at runtime and means every crawler, whether it runs JavaScript or not, sees the full content. It is the cheapest insurance available against a whole class of invisibility problems.
Yes, and this is what we usually recommend. Build a homepage that scrolls through every section the way a single page site would, then give each of those sections a real page of its own with proper depth. The homepage is the overview. The pages are the substance.
Visitors who like scrolling get the experience they wanted. Visitors who arrive from a search for one specific thing land on the page about that thing. Nobody is worse off, and you have not sacrificed the index.
The homepage sections then become internal links rather than dead ends. A short pricing summary on the homepage that links to the full pricing page does two jobs at once. It answers the skimmer and it passes authority to the page that needs to rank.
Across 150 or so projects this pattern has been the default for a reason. It costs a little more than a single page and delivers a site that can actually grow, because adding a topic means adding a page rather than making one page longer.
Ask one question. Do you need people to find you through search? If yes, build multiple pages, one per distinct thing someone might search for. If no, and traffic will come from ads, email, or direct sharing, a single page is a legitimate and often better choice.
If you already have a single page site and you want search traffic, you do not need to rebuild it. Keep it as the homepage and start adding real pages underneath, one per service or topic, linked from the relevant sections. That is an additive change rather than a redesign.
If you are not sure which side of the line you fall on, we are happy to talk it through. It usually takes one conversation about where your customers actually come from, and the answer is often clearer than people expect. Come find us at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.