Your Inbox, Handled: Building a Virtual Assistant Website
A virtual assistant website works when a busy owner can see what you take on, how working together runs and how to book a first call. Build five clear pages around that, and prove every claim on the page.
- No coding required
- Live in minutes
- Blog, SEO and chatbot tools included
To build a virtual assistant website that books discovery calls, show what you take on, how working together runs and how to book a first call. Use five short pages, each with one job. Say plainly what you handle, how you protect client data, and what a package of hours covers.
- Google uses the mobile version of a site's content for indexing and ranking, so the phone view is the one that counts. Google on mobile-first indexing
- The US Federal Trade Commission's rule, in force from 21 October 2024, bans fake or misleading consumer reviews and testimonials. FTC announcement
- Since April 2025 UK law bans posting or commissioning fake reviews, with fines of up to 10% of global turnover. UK government
- WCAG 2.2 is the current version of the Web Content Accessibility Guidelines. W3C
- AI Web Maker built the sample site in this guide, 5 pages, in 48 seconds. The sample's page
What must a virtual assistant website do for its visitors?
It must help a busy owner decide quickly whether you can take work off their plate. Then it must make the first call easy to book.
Your visitors are owners, consultants and professionals who are short of time. They rarely browse. They arrive with a task in mind, such as inbox management, scheduling, invoicing or research, and they want to know whether you do it. They also want to know whether you can be trusted with their accounts. A page that answers both questions fast wins the call.
The site has three jobs. It shows the tasks you take on, so nobody has to guess. It explains how working together runs, so the idea of hiring someone remote feels safe. And it gives one clear next step: a discovery call. Everything else on the site supports those three jobs.
Think about what the visitor fears. They fear explaining everything twice, losing control of their email, handing over passwords, and paying for hours that vanish. A good website answers these fears in plain words before the visitor has to ask. You do not need long pages for that. You need honest, specific sentences in the right places.
Clearday Virtual Assistance, the sample business used in this guide, shows the pattern. It is fictional, and its people, reviews, prices and contact details are invented. But its home page opens with "Hand off the admin. Get your days back." That one line names the pain and the result. The sections below it then explain what is taken on, what changes and how to start.
Which pages does a virtual assistant website need?
Five pages are enough: Home, Services, How It Works, About and Contact. Each has one job, and together they lead to the call.
More pages can wait. A solo or small virtual assistant business does not need a dozen. It needs a few pages that are finished, specific and easy to scan on a phone. You can always add a page for a specialism later, such as a separate page for a niche you serve.
| Page | What it must do | Where to see it on the sample |
|---|---|---|
| Home | Name the problem, show what you take on, point to the call | Home |
| Services | List the tasks and tools, and how support is delivered | Services |
| How It Works | Walk through the first conversation, setup, daily contact and packages | How It Works |
| About | Show the person, their background and how they like to work | About |
| Contact | Take a short enquiry or discovery call request | Contact |
Keep the menu short and in this order. A visitor who reads the pages left to right moves from "what do you do" to "how does it work" to "who are you" to "how do I start." That is the order of a hiring decision, and the menu should follow it.
Every page should end with the same next step, so the visitor never has to hunt for it. Repeating the call to action is not pushy. It is a kindness to someone who read half a page and got interrupted by a client.
What should the homepage say?
It should say what you take on and why that helps, in the first screen. Then it should point to a discovery call.
Start with a headline that names the result, not your job title. "Virtual assistant" tells a visitor little, because they may not know what you do day to day. "Hand off the admin. Get your days back." tells them what changes. The sample's home page then follows the pain with a section on how running a business should not mean living in your inbox.
Next, give a short overview of what you take on. Three to six items is plenty: email and calendar, scheduling and travel, invoicing and expense tracking, research, document preparation, social media posting. Link each group to the Services page for detail. Then add a "what changes" section that describes the outcome in the owner's own life: fewer hours on admin, fewer dropped balls, a clearer start to the week.
Show the person early. The sample's home page includes a "Who you'll work with" section, which matters more for this trade than for most. A virtual assistant is a relationship, not a product. Visitors want a face, a name and a sense of how you speak before they trust you with an inbox.
Close with a call to action that matches how people actually hire. Most do not want to commit to a package from a web page. They want a short conversation to see whether it fits. Offer that, and say how long it takes and what happens after.
How do you present services, tools and packages?
Group tasks by type and name the tools you work in. Then explain how hours are bought, so a visitor can picture the arrangement.
Vague service lists lose clients. "Admin support" could mean anything. "Managing your inbox, drafting replies for your approval, and keeping your calendar clear of clashes" is something a visitor can picture. Write each service as a task with a result, in the words an owner would use.
Name the tools you use. If you work in Gmail, Google Calendar, Outlook, Slack, Asana, Trello, QuickBooks or a particular CRM, say so. A visitor who already uses those tools relaxes. A visitor who uses something else can ask about it on the call. Only list tools you actually work in, because the first call will test the claim.
The sample's Services page is organised around the kinds of support offered, how support is delivered and custom or one-off tasks. That last section is worth copying. Many owners have a task that fits no list, such as organising a conference trip or cleaning up a contact database. Saying you take custom requests invites those enquiries.
Explain packages by hours in plain terms. A package of hours is simply an agreed amount of your time each month. State what happens to unused hours, how tasks are logged and how a client asks for more. Whether you publish prices is your choice. If you do, use your own real figures and keep them current. If you do not, say how pricing is arranged, as the sample's How It Works page does in its section on pricing and packages. Either way, never leave the visitor wondering how billing works.
How should you explain how working together works?
Walk through the process in order, from first call to daily contact. Remove each worry before the visitor has to voice it.
A dedicated How It Works page is the most useful page on a virtual assistant website. Hiring someone remote feels uncertain. A clear process turns uncertainty into a plan the visitor can picture, and it does so without any hype.
The sample's How It Works page covers four things in order: from first conversation to getting started, what the client needs to provide or set up, how communication works day to day, and how pricing and packages are arranged. That sequence is a good template. Adapt the details to your own way of working, and keep each section to a short paragraph.
Be concrete about onboarding. Say what you ask for in the first week: access to a shared inbox, a calendar, a list of recurring tasks, preferences for tone and timing. Say how access is granted. Say what you do not need. Visitors worry about handing over too much, and a list of what you need and what you never ask for answers that worry directly.
Be equally concrete about daily contact. Say where messages go, whether that is email, Slack or a shared task board. Say when clients can expect replies, which hours you work and which time zone you work in. Say how you report on completed tasks. Predictable communication is a large part of what clients are really buying. Do not promise response times you cannot keep.
How do you handle confidentiality and client data on the site?
State plainly how you protect client information, and never claim a protection you do not practise. This is the section that decides whether an owner trusts you.
A virtual assistant often sees email, calendars, invoices and client lists. A visitor knows this. If your site says nothing about it, they will assume you have not thought about it. A short, honest section on confidentiality and data handling can be the reason someone books a call.
Cover the practical points in your own words. Say whether you sign a confidentiality agreement or a data agreement, and offer to sign the client's own. Say how you receive access: through shared access or delegated permissions rather than by being sent a password in a message. Say whether you use a password manager and two-step sign-in on your own accounts. Say how you keep client files separate, and what happens to the client's data when the work ends. Only list what you really do.
Do not copy a legal promise from another site. Data protection rules differ by place, and whether they apply to you depends on where you and your clients are. This guide can only give general information, not legal advice. Check your own regulator, your professional association or a qualified adviser before you write terms about data, and have the agreement you offer reviewed by someone qualified.
Keep the tone factual. Words like "bank-grade" and "military-level" add nothing a visitor can check. "I sign your confidentiality agreement before I see anything" is a sentence a visitor can check, and it does more work.
How do you build trust with reviews and a real person on the page?
Use real testimonials and a real face and name. The rules on reviews are strict, and they apply to you.
The About page carries much of the trust. The sample's About page covers the founder's background, why the business was started and how they like to work with clients, then ends on a call to action. That order suits this trade: who you are, why you do this work, and what working with you feels like. Use a real photograph and your real name. Say what you did before this work, because experience in an office, a clinic or a studio tells a visitor which kind of business you understand.
Testimonials help, but they must be real. The US Federal Trade Commission announced a rule, in force from 21 October 2024, that bans fake or misleading consumer reviews and testimonials, such as reviews by people who do not exist or who had no real experience with the business. You can read the announcement and the FTC's questions and answers on the rule. In the UK, posting or commissioning fake reviews has been banned since April 2025, and the CMA can fine a company up to 10% of its global turnover, as the UK government explains. Rules differ by place, so check your own regulator.
In practice: quote only clients who really worked with you, with their permission, and do not edit a quote to say something they did not. Do not offer anyone a reward in return for a good review without checking the rules first. If you have no testimonials yet, leave the section out. An honest empty space beats an invented quote, and you can add real ones as they come.
If you mark up reviews with structured data, Google asks that you do not mark up fake reviews or content that visitors cannot see. Its general structured data guidelines say so directly, and its review snippet documentation covers the markup itself.
How does a visitor book a first call?
Give one clear path to a discovery call, and keep the form short. Every extra field costs you enquiries.
The Contact page has one job: turn a decision into a message. The sample's Contact page is built around a single enquiry form, headed "Send an enquiry." That is the right amount of page. Resist adding a map, a long list of social links or a second form.
Ask only for what you need to prepare for a good first call: a name, an email address, and a short note on what the visitor would like help with. A phone number can be optional. Add a line saying how soon you reply and what happens next, so the visitor knows the message will not vanish. A visitor who has to guess what comes after "Send" often does not send.
Make the form work for everyone. The W3C's forms tutorial recommends labelling each control, giving clear instructions, validating input and telling users plainly when something succeeds or fails. It also notes that users prefer simple, short forms and are more likely to abandon one that asks for excessive data. Put a visible label on every field rather than relying on faint placeholder text, and make the error messages say what to fix.
The Services and How It Works pages should also point to the call. Put a short line and a button at the foot of each, as the sample does, so a visitor who is convinced halfway down never has to scroll back up. A discovery call is a low-commitment step, and your wording should say so.
How do you make the site work on phones and for every visitor?
Design for the phone first, keep the pages light, and follow accessibility guidance. Many busy owners read on their phones between meetings.
Google uses the mobile version of a site's content for indexing and ranking, which it calls mobile-first indexing; see its guidance. So the phone view is the version that counts for search as well as for readers. Check that every page reads well on a narrow screen: short paragraphs, buttons big enough to tap, and nothing that needs zooming.
Accessibility matters for every visitor, and it is also part of how businesses open to the public are expected to behave. The US Department of Justice's web guidance says Title III of the ADA prohibits discrimination against people with disabilities by businesses open to the public. It names the Web Content Accessibility Guidelines as helpful technical standards, and WCAG 2.2 is the current version, a W3C Recommendation since October 2023. This is general information, not legal advice, so check the rules where you work.
The same DOJ guidance lists common barriers, and they are easy to avoid. Poor colour contrast, colour alone used to give information, images without alt text, videos without captions, inaccessible online forms and mouse-only navigation are all fixable. Give every image a short description. Make sure text stands out clearly from its background. Check that you can reach every link and button with a keyboard alone.
Speed helps too. Use a few well-chosen photos rather than many, and avoid autoplaying video. A virtual assistant is selling calm and efficiency, and a slow, cluttered site says the opposite.
How do local customers find a virtual assistant website?
Many clients search for a virtual assistant by the work they need, but some look near home. Cover both with honest, specific pages.
Most virtual assistants work remotely for clients anywhere, so your location may matter less than your specialism. Still, some clients prefer someone in their country or time zone. Say where you are based, which time zones you work in and which languages you work in, on the About or Contact page. These details help the visitor and the search engines understand who you serve.
If you have a business address or a service area, Google's guidelines for a Business Profile ask a business to represent itself as it is consistently represented and recognised in the real world: its real name, address, phone number and hours. Keep those details identical on your website and your profile. Google also supports LocalBusiness structured data, which can tell it your hours, departments and other details.
Write for people first. Google's ranking systems are designed to prioritise helpful, reliable information created to benefit people, not content made mainly to rank in search; see its guidance on helpful content. For you, that means pages about real tasks, written the way a client would describe them. A page that explains how you handle a client's inbox will serve a searcher better than a page stuffed with the same phrase.
If you want a second opinion once the site is live, AI Website SEO Tools checks the pages of any website for the problems that keep it out of search results and says how to fix each one.
How do you build a virtual assistant website with AI Web Maker?
Give AI Web Maker your business name and a short description, then edit what it builds. It plans the pages, writes the words, chooses the photos and sets up the forms.
Every step below has a place on the sample, so you can compare your own site with a finished one. A virtual assistant business website example is easier to judge when you can click through it. Clearday is fictional, but the build is real: AI Web Maker made it in 48 seconds from a short description.
- Open the AI Web Maker builder and enter your business name, an email, a phone number and a short description of what you do. Name your main tasks and the kind of client you serve.
- Watch the website being built. AI Web Maker plans the pages, writes the words, chooses the photos and sets up the forms, much as it did for the sample's five pages.
- Preview every page before anything goes live. Open the Home page and check that the first screen says what you take on and why.
- Edit each page in the editor. Change the words, the photos, the sections, the services, the prices and the hours. Replace any wording that does not sound like you. Add your real tools, your real process and your real confidentiality practice.
- Check the Services and How It Works pages against the sample. Make sure the tasks, tools and package arrangements are accurate, and that you can keep every promise.
- Test the Contact form yourself on a phone. Send an enquiry and see what arrives. Then ask a friend to try it and tell you where they hesitated.
- Go live when you are happy. Building and previewing cost nothing. Going live costs $119 a year of hosting, and the domain name is paid separately.
If you want to see what the finished result looks like first, open the sample website's page or click through the live sample. Then start your own version with the builder.
Frequently asked questions
How many pages does a virtual assistant website need?
Five pages are enough to start: Home, Services, How It Works, About and Contact. That is the structure of the Clearday sample, and it covers what a visitor needs to decide on a first call. Add pages later only if you have something specific to say, such as a niche you serve. A few finished pages beat many thin ones.
Should I publish my prices?
That is your choice, and both approaches work. If you publish prices, use your own real figures and keep them current. If you do not, explain how pricing and packages are arranged, as the sample's How It Works page does. What matters is that a visitor understands how billing works before the call, so no one is surprised later.
How do I show I can be trusted with client data?
Describe what you actually do: a signed confidentiality agreement, delegated access instead of shared passwords, and how files are kept apart. Do not claim protections you do not use. Rules on data differ by place, so check your regulator or a qualified adviser before writing legal terms. A plain, honest section beats impressive-sounding claims.
Can I use testimonials if I am just starting out?
Only if they are real. The FTC's rule bans fake or misleading reviews and testimonials, and UK law has banned fake reviews since April 2025. If you have no genuine testimonials yet, leave the section out and add real ones as clients give them, with their permission. An empty space is better than an invented quote.
How do I make the site work for every visitor?
Check it on a phone, label every form field, describe images with alt text, keep text easy to read against its background and make sure you can reach everything with a keyboard. The DOJ's web guidance names WCAG as helpful technical standards and lists these as common barriers. Rules differ by place, so check your own.
Your Plan for This Week
You can finish a first version in a few sittings. Treat each as small and specific.
On day one, write your list of tasks and tools in plain words, and decide which five or six you want to be known for. Write one sentence on what changes for a client who hands each over. This list becomes your Services page and the heart of your homepage.
On day two, write how working together runs: the first call, what you need in week one, how you communicate and how packages of hours work. Write your confidentiality practice in the same sitting, using only what you really do. If you offer an agreement, have it checked by someone qualified.
On day three, gather what proves you: a clear photo, your real background, and any testimonials you have genuine permission to use. On day four, open the builder, enter your details and let AI Web Maker build the five pages. Then edit every page until it sounds like you, and compare it with the live Clearday sample.
On day five, test it on a phone, send yourself an enquiry, and ask someone busy to find your first-call button in ten seconds. Fix what slows them down. Then go live, and tell your first client where to look.
Build your website in Minutes and get the AI Tools that work
Start Building Your Website →