A homeowner looking for a cleaning company and a customer trying to book their usual cleaner may land on the same homepage. One needs to figure out whether the business is a good choice. The other already knows the company and wants to get something done.

A homepage built entirely around winning new customers can make the second visitor start over. But a homepage dominated by account links and scheduling shortcuts may leave a newcomer wondering what the company actually does. A small service business needs a clear first impression and a practical way back for people who have hired it before.

The solution usually isn't two homepages. It's deciding which information must be visible to everyone and which tasks deserve their own short route.

Start with two visits, not two customer personas

Imagine a fictional residential cleaning company called Cedar House Cleaning. It serves a defined group of neighborhoods, offers one-time and recurring house cleaning, and takes requests through a form. Its office confirms appointments after reviewing availability. Customers can also call to change an existing booking. Cedar does not have an online account portal.

Consider two visits to its website.

Maya has never used Cedar. She wants to know whether the company cleans apartments in her neighborhood, what a standard visit covers, and how to request an estimate. A big "Book Now" button won't answer those questions if the company has not explained its services or whether a booking can actually be completed online.

Jordan hired Cedar last month. Jordan wants another visit, preferably with similar instructions, and does not need to read the company's story or compare every service again. A prominent "Get a Quote" form that asks for all the same details creates unnecessary work.

These are visits with different goals, not permanent labels for people. Jordan may need to evaluate a new deep-cleaning service later. Maya may arrive knowing exactly what she wants because a neighbor referred her. Design for recognizable tasks rather than assuming the website can identify who's new.

Give first-time visitors enough information to decide

The upper part of Cedar's homepage should answer basic questions without making visitors hunt through several pages:

  • What does the company do? Residential cleaning, with a plain distinction between standard, deep, and recurring work if those are actual services.
  • Where does it work? The service area, or a direct way to check an address before sending a detailed request.
  • What is the next step? A clearly named estimate request, with a realistic explanation of how the company responds.

A headline such as "Residential House Cleaning in Northside and Nearby Neighborhoods" may be less flashy than "A Fresh Start for Every Space," but it tells an unfamiliar visitor more. The exact location and service claims need to match what the business actually offers.

Below that first explanation, newcomers may need a concise service overview, actual examples of completed work if permission is available, and credible customer feedback. The homepage doesn't need to reproduce every service page or every review. It needs to give people enough context to choose where to read next.

For Cedar, a primary action might be Request a Cleaning Estimate. Its form should say that sending a request does not confirm a date. That avoids treating the button label as a promise the operation cannot keep.

Add a return path without burying the introduction

Existing customers shouldn't have to pretend they're shopping for a provider again. Cedar could place a small, clearly labeled group of task links immediately after the opening service summary:

Already a customer?

  • Request Another Cleaning — opens a shorter repeat-service inquiry that asks only what Cedar needs to respond.
  • Change an Existing Appointment — goes to the contact route Cedar actually monitors for scheduling changes.
  • Ask a Question About a Recent Visit — uses a clear support contact method, with realistic response expectations.

That group is a design example, not a requirement to build three new pages. If Cedar handles all three requests by phone, a single "Existing Customers: Call Our Office" link with accurate staffed hours could be clearer. If its scheduling software truly supports confirmed online rebooking, the label can reflect that capability. A mere request form should not be called instant booking.

The return path need not be the biggest element on the homepage. It just needs to be easy to notice and accurately named. A customer who already trusts the company should be able to recognize the right action without reading a sales pitch.

Avoid making people choose "new" or "returning" before they can browse

A homepage that opens with two large doors—"I'm New" and "I'm a Customer"—may seem neatly organized. It also adds a decision before visitors have seen the services or contact information. Someone who used the company years ago might not know which route applies. Someone comparing a new service may need both.

Keep the ordinary homepage available to everyone. Put useful shortcuts alongside the main content rather than requiring identification, login, or a choice of visitor type. Reserve account sign-in for situations where there is a real customer account system and a task that requires it.

This also avoids creating two competing versions of basic facts. Service area, offered services, office hours, and contact details should come from the same accurate information regardless of which link the visitor follows.

Prioritize tasks, not equal-sized buttons

There is no rule that both audiences must get exactly half the screen. Placement should reflect what the business needs visitors to do and how often those tasks arise.

Suppose Cedar receives mostly first-time estimate requests but a steady stream of repeat-booking calls. A sensible layout could be:

  1. Clear service-and-location introduction, followed by Request an Estimate.
  2. Short service overview and a link to coverage details.
  3. A visible Already a Customer? area with direct repeat-booking and appointment-help routes.
  4. Genuine proof of work and a brief explanation of the estimate process.
  5. Contact information and availability expectations.

This isn't an evidence-based universal order. It's a starting arrangement to test against the business's actual work. A company built mainly on recurring lawn-care visits might give "Schedule Your Next Visit" more prominence. A contractor whose repeat projects all require a new site assessment may be better served by one clear inquiry path with an optional "Previous customer" field.

On a phone, don't make returning customers scroll past a large gallery before reaching their shortcut. Equally, don't lead first-time visitors into a scheduling widget before explaining what can be scheduled. Both tasks should remain findable without the homepage becoming a dashboard.

Keep the homepage honest about what each action does

The wording on a button matters because it sets an expectation.

"Book Your Cleaning" suggests a reservation can be completed. "Request a Cleaning Date" suggests the office still needs to confirm. "Manage Appointment" suggests a self-service function that Cedar does not offer. Those labels aren't interchangeable.

A button should take visitors to the action it names. If a repeat customer opens "Request Another Cleaning," the next page should recognize that task rather than presenting a generic "Tell us about your business" form. If an appointment change must happen by phone, say so before someone spends time filling in a form that can't handle the request.

The U.S. Web Design System's link guidance recommends meaningful link text and links that go directly to relevant destinations. Its guidance is written for federal websites, but the principle is useful when deciding whether a service company's shortcut actually helps.

Check the experience by giving people realistic tasks

A homepage can look balanced while still failing both groups. Test it with the specific actions that matter, rather than asking whether people like the design.

Ask someone unfamiliar with Cedar to find a standard cleaning service, check coverage, and explain what happens after submitting an estimate request. Separately, ask someone who knows the company to find the fastest supported way to request another visit or change an appointment. Let them try on a phone, without coaching.

Notice where each person hesitates, which label they select first, and whether the destination supports the task. A few informal observations can reveal unclear wording or dead ends; they do not establish a conversion-rate improvement or substitute for wider research.

The W3C guidance on consistent navigation emphasizes predictable ordering of repeated navigation across pages. Keep core routes recognizable as customers move from the homepage to booking, services, or support. W3C also explains why multiple ways to locate pages can help people with different navigation needs. Those accessibility principles support sensible alternatives to hiding an important task behind one hard-to-use control.

Let repeat-customer needs evolve with the business

When Cedar starts offering an actual customer portal, its homepage could link to it. Until then, a clear phone number or repeat-request form is more useful than an empty "My Account" feature. If repeat bookings are frequently handled incorrectly, the solution may involve office workflow and scheduling tools—not just moving a link higher on the page.

Review the homepage after a genuine change in services, booking procedures, or customer support. Look at the types of inquiries arriving, the tasks people report struggling with, and the accuracy of the promised next steps. Keep the introductory explanation strong enough for a stranger, and make established customers' common tasks easy to find.

A homepage has to introduce a business only once to each new visitor. It has to remain useful every time someone comes back.

Sources and Further Reading