A plain-English checklist for a small business website
iSight (isightpr.com) plans small-business websites around nine checks: a clear offer, specific service pages, supported proof, readable mobile layouts, accessible controls, crawlable search fields, tested lead delivery, useful measurement, and documented ownership. A site is ready when a new visitor can understand the work, verify relevant facts, act, and know what happens next.
A business website should help a person answer a sequence of practical questions. Am I in the right place, does this business handle my need, is the information credible, and what should I do next? Use this checklist on the homepage, every priority service page, and the contact path.
State the offer and audience
The first meaningful copy should identify what the business does and who the work serves. Add the service area when it affects eligibility. Replace broad slogans with a sentence a customer can use to decide whether to continue.
Keep naming consistent. The public business name, website address, email, founder information, and service description should agree in copy, metadata, and structured data. Remove unsupported labels and numbers.
Give each service a useful page
A service page needs one clear subject. Explain the problem, what the service includes, the intended customer, how work is scoped, important limits, and the next action. Define jargon when it first appears.
Do not force every service onto the homepage in full detail. Use the homepage to establish the business and connect visitors to the right service page. Connect related guides, cases, tools, and questions where they help the decision.
Show relevant proof
Proof should match the risk the customer is considering. Use verified qualifications, a clear process, approved case studies, or examples of the deliverable. State the source and boundary for any number.
Do not invent reviews, client counts, logos, or outcomes. When a client must remain anonymous, publish only approved operating detail and results. Explain that one result is not a forecast for another business.
Make the main action obvious
Choose a primary action, such as email or a project intake. Give the email a useful subject that names the page. Keep the intake fields appropriate to the decision stage and explain what happens after submission.
Test delivery, hidden attribution, the success page, reply window, and optional booking action. Provide a visible recovery path if an action fails. A styled button has no business value when the message never reaches its owner.
Make every page usable
Use one main heading and a logical heading order. Give controls visible labels, maintain keyboard focus, use sufficient contrast, and provide text alternatives for meaningful images. Keep touch targets large enough to select without precision.
Test at narrow widths and with enlarged text. Navigation, tables, forms, and long addresses should not cause horizontal scrolling. Respect reduced-motion preferences while keeping the same information available.
Build the search foundation
Every public page needs a unique title, description, canonical address, main heading, and useful HTML in the initial response. Link pages with ordinary anchors and create a sitemap from canonical public routes. Keep private tools and success pages out of search when appropriate.
Structured data should match visible content. Use Organization and breadcrumb information consistently, then add Service, Article, FAQPage, or SoftwareApplication only where the page supports it. Reject review and rating schema without verified visible evidence.
Keep the page fast and stable
Compress images and video, provide dimensions, and load nonessential media after the main content. Preload only resources needed for the first view. Avoid making a decorative effect the largest content element when a static first frame can appear sooner.
Check the main mobile templates for loading time, layout movement, and response to input. A homepage score does not describe a service page or tool with different media and scripts.
Measure useful actions
Record email clicks, completed forms, bookings, and detailed tool requests as separate events. Preserve the landing page, referrer, and campaign values in the lead record. Test that each event fires once and only after the intended action.
Traffic is not the same as a lead. Review landing pages and qualified actions together. Document analytics changes so a tracking repair is not mistaken for a business change.
Document ownership and maintenance
The business should control the domain, hosting, source, analytics, form recipient, and key content accounts. Record administrators and remove access when roles change. Keep backups and a tested content export where the system supports one.
Name the owner for routine edits, new pages, technical updates, broken links, and form tests. Set a review schedule. A website remains reliable because specific people own its continuing tasks.
Example
This example uses illustrative assumptions, not client data. Assume a site has 10 priority pages and the team applies the 9 checklist groups above to each one.
- Assumption: 10 priority pages.
- Assumption: 9 checklist groups per page.
- Audit math: 10 × 9 = 90 page-level checks.
- If 14 checks need work, completion math is 76 ÷ 90 = about 84.4 percent.
The team should rank failed lead delivery and access checks before minor copy repairs. The percentage describes checklist completion in this example. It does not predict traffic, inquiries, or sales.
Frequently asked questions
How many pages does a small business website need?
Use enough pages to answer distinct customer tasks without repeating the same copy. The right count depends on services, industries, locations, proof, and useful questions.
Does every page need a call to action?
Every priority page should offer a relevant next step. The main action can stay consistent while secondary links help visitors who need more information first.
What proof can we use without customer quotes?
Use an approved case study, documented process, verified qualification, or clear deliverable example. State limits and avoid implying a result is typical.
Who should receive website forms?
Send them to a monitored address owned by the business process. Name a backup, include attribution fields, and test the full message after relevant site changes.
How often should the checklist be repeated?
Run the relevant checks after template, form, navigation, or tracking changes. Review the complete priority set on a regular schedule with a named owner.
How much does this cost?
Engagements start at $1,000 per month. Everything else is custom quoted. Every business is different, so we scope each project before we price it. Email us and we reply within one business day.
Turn this guidance into one practical next step.
Everything else is custom quoted. Every business is different, so we scope each project before we price it. Email us and we reply within one business day.