Small Business Website Checklist: 21 Things Every Site Needs
A small business website needs clear service details, real proof, a working contact path, and regular care. Use these 21 checks to review what customers can understand and do, not just how the site looks. Adapt each check to your business and get specialist advice where legal, privacy, or access needs require it.
1. A clear statement of what you do
Read only the first heading and sentence. Can a stranger name the service you provide? Replace broad lines about quality with a plain account of the work. A garage door company should make repairs or installations clear right away. Keep the business name visible, but do not make visitors decode a slogan to learn whether they are in the right place.
2. An accurate service area
Name the places you actually serve and explain any limits. If travel charges or job size affect where you go, state that in plain terms. Do not list every nearby town just to look widespread. If customers visit you, give useful location details. If you work from home and travel to customers, consider privacy before displaying a street address or map.
3. Service descriptions that answer real questions
Explain what each main service includes and what it does not. Use separate pages when the differences matter enough to need more space. A cleaning business might explain regular home cleaning and move-out work separately. Describe the process in terms a customer uses. Avoid long strings of repeated town names or technical words that add little meaning and make the page harder to scan.
4. One clear main action
Choose a main action for each page, such as calling or asking for a quote. Give the button a useful label that explains where it leads. Keep its placement easy to find without covering the page with pop-ups. You can offer another contact method, but avoid making every button compete. A reader should understand the next step without having to study the design.
5. Phone details that work
Check every displayed number against your current business number. On a phone, tap the call link and confirm that it opens the right number. State contact hours if you do not answer around the clock. If calls go to voicemail, make sure the greeting identifies the business and gives a useful next step. Do not claim emergency coverage unless your team truly provides it.
6. A short, tested inquiry form
Ask only for the information you need to begin. Give each field a clear label and explain any required details. Test a valid request and an incomplete one. Check that both the visitor's message and your reply reach their destinations. Repeat this after changing form tools, email settings, or spam filters. A form that looks fine may still fail behind the scenes.
7. Honest expectations after contact
Tell visitors what their request starts. Does someone review photos, call to discuss the job, or arrange a visit? Make clear that a request is not a confirmed booking if that is how your process works. Only promise a response window you can keep. For urgent work, explain any limits rather than leaving someone to assume a web form is watched at all times.
8. Real proof of the business
Show who runs the business and why your team can handle the stated work. Use accurate credentials, clear project details, or relevant experience. Confirm any license or insurance wording before publishing it. Avoid vague badges that have no clear source. A new business can be honest about its start date while still explaining the owner's prior work, training, and approach to customer care.
9. Photos you have the right to use
Choose images that help explain the work or introduce the team. Get permission where needed, especially when a customer, home, or identifying detail appears. Do not present stock photos as completed projects. Keep the original files and a record of permission. Add useful descriptions for meaningful images, and avoid turning a simple gallery into the main source of information about the service.
10. Reviews used with care
Use only genuine reviews and preserve their meaning. Do not make up names, combine several comments into one quote, or hide a paid relationship. Check the review platform's rules before copying content. If you have no reviews yet, offer other proof rather than leaving fake template praise in place. A few honest details are more useful than a large wall of claims nobody can verify.
11. A readable phone layout
Test the site on an actual phone, not just the editor's preview. Look for small text, clipped headings, buttons too close together, and menus that block content. Check both long service pages and the contact page. Important information should not disappear on mobile. Ask someone who did not build the site to find a service and send a test request without coaching.
12. Basic access checks
Use a keyboard to reach links, forms, and menus. Check visible focus, clear labels, sensible headings, and readable contrast. Enlarge the text and see whether key content remains usable. W3C's easy checks can uncover common issues, but passing them is not a full access audit or legal guarantee. Get a fuller review when your risk, audience, or duties call for one.
13. Pages that do not waste time loading
Resize large photos, remove unused media, and avoid effects that delay the main message. Test more than the home page on a normal mobile connection. A slow third-party booking tool may affect a page even when the design itself is simple. Focus on letting visitors read and act quickly. Do not chase a single test score while ignoring a real problem in the contact path.
14. Useful page titles and headings
Give each main page a title that reflects its actual subject. Organize content with clear headings rather than making every line a bold sales claim. Headings help people scan and can help assistive tools navigate. Keep service and area information natural. Repeating the same search phrase in every heading makes the page tedious and does not turn a weak explanation into a helpful one.
15. Accurate connected business details
Compare the site's name, phone number, hours, and location information with your other listings. If eligible, keep your Google Business Profile complete and current, including special hours. Follow Google's rules for names, categories, and service areas. Local ranking depends on several factors, including relevance, distance, and prominence. Correct details support a useful presence, but they do not guarantee a place in the top results.
16. Secure browsing and account protection
Check that the live site uses a secure connection and that its host handles the certificate. Use strong passwords and stronger sign-in checks where available. Give staff only the access they need and remove old users. A secure connection does not make every form or plugin safe by itself. Keep tools current and ask your provider which security tasks belong to you after launch.
17. Privacy information that fits your tools
List what your site collects and why. Consider forms, analytics, booking tools, payment services, and embedded features. Use privacy and consent guidance suited to your location and audience rather than copying another site's policy. Different laws and activities can create different duties. Do not collect sensitive records in a basic contact form just because the editor lets you add a large message box.
18. Control of the domain and key accounts
The business should know who controls its web address, renewal method, host, and email accounts. Keep recovery details current and record who has access. If a provider manages these, get clear terms about access and leaving. Ask what can move to another service and what needs a rebuild. Domain control matters, but it is not the same as ownership of every part of a platform.
19. Working links and safe changes
Open each menu item, service link, booking link, and footer link. If replacing a site, record important old addresses and plan where they should lead. Remove broken test pages and unused template links. Confirm email still works after domain changes. Keep a copy of approved content and a recovery plan suited to your host so an editing mistake does not become a long outage.
20. A useful way to review inquiries
Decide what counts as a useful inquiry before judging results. Record whether requests fit your services and area, while keeping customer data secure. Visitor counts alone do not tell you whether the site helps the business. A call-button click is not always a completed call, and a form event is not a signed job. Use careful labels and avoid double-counting the same request.
21. A named owner for ongoing care
Assign a person to check forms, hours, service details, and tool renewals. Give the checks a repeatable schedule and keep a short log of problems and fixes. Before busy seasons, confirm capacity and contact expectations. A website needs small, steady updates more than endless redesigns. Review this checklist after a major change, not only when you first publish the site.
Turn the checklist into a repair plan
Mark each item as working, needs work, or not relevant, and write down evidence. Fix broken contact routes and serious privacy or access barriers before cosmetic issues. Give each task an owner and a next step. Use the lost leads calculator only to explore your own assumptions; it cannot prove how much business a specific issue has cost. Actual inquiries and customer feedback are stronger evidence.
Common questions
Must I have every feature on this list at launch?
You need to address the purpose of each check, but not every business needs the same tools. A call-led service may not need booking software. Do not add a feature merely to fill a box; make sure customers can understand the offer and reach you safely.
How often should I run these checks?
Run them before launch, after major changes, and on a regular schedule that fits your business. Contact routes deserve frequent attention. Hours, staff, service areas, and legal or privacy needs should be reviewed whenever the business changes.
Should I pay someone to fix the checklist?
You can handle simple content checks yourself if you have access and time. Ask for expert help with technical, privacy, or access issues beyond your skills. Get a written scope so the fix includes testing rather than just a fresh design.