A one-page website puts the main offer and conversion journey on one page, usually with navigation links to sections. It can suit one service, event or focused product. Separate privacy, legal or support pages may still be necessary; one page is a design choice, not a reason to omit information.
TL;DR
- A one-page site fits a focused offer or event when most visitors follow the same short decision path.
- Keep privacy, legal, or support pages separate when the business requires them; one-page navigation does not eliminate those obligations.
- Give sections clear jobs: explain the offer, show relevant proof, answer objections, and provide a contact path.
- The walkthrough uses the WordPress.com page editor; test section links, mobile layout, and the contact form before publishing.
- Assign an owner to receive enquiries, update the offer, and recheck the site after domain or platform changes.
When one page fits
Choose one page when most visitors need the same short decision path: understand the offer, check whether it fits, and take one action. Use separate pages when services have different buyers, locations need distinct details, or important information becomes difficult to find in a long scroll. A privacy notice or support page can sit outside the main page when needed.
For a hypothetical appointment-booking consultant, the main page might explain the service, show the booking process, answer a pricing question, and offer a consultation request. A menu can link to those sections. If the consultant later serves two industries with different requirements and evidence, separate service pages may make those choices clearer. This is a planning example, not a measured result.
A single page does not guarantee faster launch, lower maintenance, or more enquiries. Copy, accessibility, forms, integrations, and support still need owners. Choose the structure after listing the questions visitors must answer, not from page count alone.
Build and launch a one-page site in WordPress.com
This walkthrough uses WordPress.com’s page editor. Its landing-page, page publishing and homepage documentation was checked November 4, 2026. Theme interfaces differ, so use the linked guide for your configuration.
- Define one conversion. For a service business, use “request a consultation.” Decide which fields the team needs and where requests will be handled.
- Create the page. Add a new page and select a suitable layout or build with blocks. Use one clear offer, supporting proof you can substantiate, service details, process, common questions and a contact section. An About section does not have to come first.
- Build navigation. Add clear section headings and stable anchor IDs, then link the menu to those anchors. Test that a fixed header does not cover the destination heading.
- Add contact handling. Use a Form block with labels, required fields, a useful confirmation and the correct recipient. Ask only for necessary information and explain how it will be used.
- Preview and test. Check mobile, keyboard navigation, contrast, image descriptions, zoom and error states. Avoid autoplay audio and unnecessary motion. Compress images and check the page on a slow connection.
- Publish and set the homepage. Complete the editor’s publish checks, then follow the homepage guide for the theme. Verify the site is publicly visible. If a custom domain is required, confirm the plan supports it, follow the provider’s connection instructions and test HTTPS on the final address before sharing it.
- Verify the live journey. Submit a clearly labeled test request, confirm it arrives, reply through the operating process and remove the test record when no longer needed. Test invalid and missing fields too.
- Measure the result. Define a successful-request event only after the form accepts a submission, not on every button click. Check the installed analytics integration and privacy requirements before collecting events. If analytics is unavailable on the selected plan, record received inquiries and their source manually rather than inventing a conversion rate.
For a hypothetical launch test, compare successful requests divided by eligible visits over two complete business weeks before and after a copy change, keeping channel and device mix comparable. This is a planning window, not a sufficient-sample guarantee. With little traffic, use observed task tests and inquiry quality instead of declaring a statistical winner.
Plan the section navigation and contact path
Give each section a question to answer. For the hypothetical consultant, the opening states who the service helps and links to “Request a consultation.” The services section explains what is included; the process section shows what happens after a request; and a short proof section contains only claims the business can support. Place practical details such as service area, pricing approach, and response expectations near the decision they affect.
Use descriptive menu links to jump to sections such as Services, Process, and Contact. Check each link on a phone and with a keyboard. A fixed header should not hide the heading at the destination. Google recommends descriptive, concise link text to help people and search engines understand linked content; it does not guarantee a particular search result.
Before launch, ask someone unfamiliar with the offer to find what the business does, whether it serves them, and how to contact it. Observe the task without directing them. If they cannot find an answer, change the label or section order and test again. The below-the-fold guide explains how to inspect the first view and decide where an action belongs.
Make the contact path work
The action should lead to a real destination: a monitored email address, phone number, booking system, or form. For a form, label each field, explain errors, show a confirmation only after acceptance, and check that the recipient can respond. Test a successful request and an incomplete one on mobile and desktop. Do not collect information the team does not need to handle the request.
If the page later needs more detail than a reader can find comfortably, split the relevant content into a separate page and update the navigation. A focused homepage can remain the entry point while the site grows.
Launch with an owner
Assign someone to receive enquiries, update the offer, and check the page after platform or domain changes. Review the contact journey and the questions people ask before adding new sections. Hapy’s website service options can help scope that work.
