In short
A one-page website is fine for SEO if the only searches that matter are for the business name and one closely related service or location; it is a poor choice for anything that needs to rank for several distinct queries, because each query needs a page whose title, heading and content answer it, and one page can only be about one thing. Single-page sites also lose the internal linking, the topical depth and the expansion room that multi-page sites have. Build the one-pager on a structure that can add pages later, and add them as soon as there is a second question to answer.
Why the page is the unit
Google indexes and ranks URLs. Each has a title, a main heading, and a body that together say what it is about, and each competes for the queries that match that topic. A page about one thing can rank for the cluster of queries around that thing. A page about five things ranks weakly for all of them, because it is not clearly the best answer to any single one.
A one-page site is therefore a site with one topic, in Google's view, however many sections it scrolls through. Its title tag has to name the business; its H1 has to introduce the business; and the sections about services, pricing, team and location all share one URL, one title, and one shot at the results page. Anchor links to sections (#pricing) do not create separate rankable pages; Google treats them as one document.
Where the limit does not matter
The searches that matter are for the name. A restaurant, a freelancer, an event, a local trade whose customers arrive through Google Business Profile, referral or social. The site's job is to rank for the business name and to convert; one good page does that, and adding pages would add nothing.
One service, one place. A single-service local business can rank a one-page site for "service + town", because the page is genuinely about exactly that.
A landing page or campaign. Built to convert paid traffic, never intended to rank.
A launch placeholder. Something to be found by name while the real site is built.
For these, a fast, well-written single page is the correct choice, and the minimal site argument applies.
Where it caps growth
Several services. A firm offering accounting, payroll and tax advice needs a page for each, because "payroll services" and "tax adviser" are different queries answered by different pages. A one-pager can rank for one of them, weakly.
Several locations. Same logic; each location query wants a page about that location.
Questions customers ask. The answer pages that bring pre-sold visitors have to be pages. There is nowhere to put them on a one-page site.
Topical authority. Ranking for a subject rather than a single query needs a body of pages that cover it. A one-page site has no body.
Internal linking. Multi-page sites pass authority between their pages and signal structure through links. A single page has nothing to link to.
Content freshness and expansion. Adding a section to a one-page site dilutes the page; adding a page to a multi-page site strengthens the site.
The practical sign: if you can list three or more distinct things people would search for that your business should answer, a one-page site is holding you back.
The technical mistakes
One-page sites are often built with page builders and single-page-application frameworks, which introduces problems that have nothing to do with page count:
- Everything rendered by JavaScript, so crawlers that do not execute it see an empty page. Server-rendered or static HTML avoids this.
- One title for everything. The title tag should still lead with the primary service and location, not just the name.
- Heavy assets. Full-screen images and video in every section, all loaded at once, on the one page that has to be fast.
- No heading structure. Sections styled as headings but not marked up as H2s lose the structural signal that helps Google understand the page's parts.
- Anchor links treated as pages in the sitemap and in internal links, which confuses rather than helps.
A single page that is static HTML, fast, with a keyword-led title, proper H2 sections and one primary action, is as well optimised as one page can be.
Building one that can grow
Build the one-pager as the homepage of a site that has room for more, not as a self-contained artefact. That means a real site structure with a navigation that can gain items, a URL scheme that supports /services/payroll/ when it is needed, and a platform that can add pages without a rebuild. Then add pages in the order the queries justify: the second service, the first customer question, the location page. Each one is a new chance to rank, and the homepage becomes the hub that links to them, which is the topic cluster pattern in miniature.
The decision
If the business needs to be found by name and for one thing, one page is enough and it should be excellent. If it needs to be found for several things, or plans to, the constraint is structural and no amount of on-page optimisation removes it; the answer is more pages, each about one thing. If you are unsure which situation applies, list the searches you want to win and count them. If you would like that list built and turned into a site plan, book a call.
Common questions
Can a one-page website rank on Google?
Yes, for the business name and for one topic, such as a single service in a single location, provided the page is static or server-rendered, fast, and has a keyword-led title and proper headings. It cannot rank well for several distinct queries, because each needs a page about that specific thing.
Do anchor links on a one-page site count as separate pages for SEO?
No. Sections reached by anchor links such as #pricing are parts of one URL, and Google indexes and ranks that URL as a single document with one title and one topic. Listing anchors in a sitemap or treating them as pages does not create additional rankable entries.
Is a single-page website bad for SEO?
Not bad, but limited. It can compete for one topic and the brand name, and it lacks the internal linking, topical depth and expansion room a multi-page site has. Single-page-app builds that render everything with JavaScript add a further problem, since many crawlers see an empty page. For a business needing to rank for several queries, it is the wrong structure.
When should I move from a one-page site to a multi-page site?
As soon as there is a second distinct thing people search for that the business should answer: a second service, a second location, or a customer question worth a page. Each new page is a new chance to rank. Build the one-pager on a structure that can add pages so the move is an addition rather than a rebuild.
What is the best way to optimise a one-page website?
Serve it as static or server-rendered HTML, keep it fast with optimised images and no autoplaying video, give it a title tag that leads with the primary service and location rather than just the name, mark up sections with real H2 headings, keep one clear call to action, and set up a complete Google Business Profile that links to it.
