Small Business Website Checklist: Pages, Content, and Launch

A small business website is ready to launch when its business facts are accurate, essential pages are complete, navigation works on a phone and keyboard, forms deliver to the right owner, and the public domain has valid search and analytics settings. Use the checklist below before publishing, then repeat the delivery and URL checks on the live site.

The essential pre-launch checks

Fix every Must fix item before launch. Useful next items may follow soon after launch when they do not block a customer from understanding or contacting the business.

• [ ] Must fix: The business name, phone, email, address or service area, hours, and services are current.
• [ ] Must fix: Home, service, about, contact, and applicable policy pages are complete.
• [ ] Must fix: Every navigation, button, phone, email, and external link opens the intended destination.
• [ ] Must fix: Every form accepts a test submission and delivers it to the responsible person or system.
• [ ] Must fix: The website is readable and usable on a real phone.
• [ ] Must fix: Visitors can use the main navigation and forms with a keyboard.
• [ ] Must fix: The business controls the domain, website account, and billing access.
• [ ] Must fix: Public pages load over HTTPS without a browser warning.
• [ ] Must fix: Draft, account, and private pages are not publicly exposed.
• [ ] Must fix: Intended public pages are not blocked from search.
• [ ] Useful next: Analytics records the actions the business needs to measure.
• [ ] Useful next: Search Console verifies the public domain and receives the sitemap.
• [ ] Useful next: The owner has a schedule for checking forms, facts, access, and renewals.

This checklist works with any platform. If you still need to build the site, follow the full guide to create a small business website.

Business facts and required pages

Check the website against one approved source document. Do not rely on memory while reviewing separate pages.

Business facts

• [ ] Must fix: The public business name is written consistently.
• [ ] Must fix: The phone, email, address or service area, and hours are accurate.
• [ ] Must fix: Every listed service is currently available.
• [ ] Must fix: Prices, ranges, minimums, financing, and estimate language are approved.
• [ ] Must fix: Licenses, certifications, insurance, memberships, and awards can be verified.
• [ ] Must fix: Reviews and project results have permission and accurate attribution.
• [ ] Must fix: The business owns or has permission to publish supplied photos and graphics.

Essential pages

• [ ] Home: States what the business does, whom it serves, where it works, and what the visitor should do next.
• [ ] Services: Gives each important service enough detail for a customer to identify the right option.
• [ ] About: Identifies the business and provides relevant reasons to trust it without unsupported claims.
• [ ] Contact: Includes the usable contact methods, hours, location or service area, and response expectations the business can meet.
• [ ] Policies: Includes the privacy, refund, cancellation, shipping, warranty, accessibility, or other policies that apply to the business.
• [ ] Useful supporting pages: Adds staff, location, work, reviews, FAQ, menu, product, or resource pages only when customers need them.

The required legal and policy pages depend on the business, location, information collected, and services offered. This checklist cannot determine legal compliance. Ask qualified counsel about requirements that apply to your business.

Trust and conversion checks

A visitor should be able to verify the business and complete the intended action without guessing. A form appearing on a page does not prove it delivers, and an embedded calendar does not prove an appointment is confirmed.

• [ ] The primary action is easy to find on the home and service pages.
• [ ] Calls to action use specific labels such as "Request an estimate" or "Call the office."
• [ ] Phone and email links use the correct details.
• [ ] Reviews identify a source or have permission for publication.
• [ ] Credentials appear only where they are current and relevant.
• [ ] Forms request only the information needed for the stated purpose.
• [ ] Error messages explain what the visitor needs to correct.
• [ ] The success screen explains what happened and what comes next.
• [ ] The submission reaches the correct inbox, CRM, or operating queue.
• [ ] The responsible owner receives a useful notification.
• [ ] Calendar, payment, map, upload, and other third-party tools open and complete the expected action.

How to test a contact form

Use a test record that is easy to identify, such as Launch test 2026-09-28, and complete the form from a private browser window. Save the public page URL, submission time, values entered, success message, receiving system, and notification recipient. Confirm the record can be opened and answered, then remove it if retention is unnecessary.

Repeat the test after the public domain is connected. A successful preview test does not prove the live domain, notification rules, or third-party connections behave the same way. Confirm that the live submission reaches the correct inbox or system and that the responsible person receives the notification.

Mobile and accessibility checks

Review the actual website at several widths and with more than one input method. Automated scanners can find some problems, but they cannot decide whether the content, labels, order, and interactions make sense.

• [ ] Open every important page on a real phone.
• [ ] Confirm the page does not require horizontal scrolling at normal zoom.
• [ ] Check that text remains readable without pinching and zooming.
• [ ] Make sure buttons and links are large enough to select without hitting a neighbor.
• [ ] Confirm menus open, close, and expose every destination.
• [ ] Zoom the desktop browser to 200 percent and confirm content remains available.
• [ ] Use the Tab key to reach navigation, links, buttons, and form fields.
• [ ] Confirm the keyboard focus indicator is visible.
• [ ] Confirm each form control has a visible label.
• [ ] Check that errors are explained in text, not color alone.
• [ ] Write useful alternative text for informative images.
• [ ] Review text and control contrast.

The W3C Easy Checks provide a useful preliminary review. Passing these checks does not certify conformance with a legal standard or every Web Content Accessibility Guidelines requirement.

Search and launch checks

Search settings should describe each page accurately and allow search engines to reach the public pages you intend to publish.

• [ ] Each important page has one descriptive title.
• [ ] Each page has a useful meta description written for that page.
• [ ] The visible main heading matches the page's subject.
• [ ] URLs are short, readable, and stable.
• [ ] The preferred version of each page has the intended canonical URL.
• [ ] Old URLs that changed have direct redirects to the closest useful replacement.
• [ ] Internal links use descriptive anchor text and lead to live destinations.
• [ ] Broken-link and missing-page checks have been completed.
• [ ] The XML sitemap contains the intended public canonical pages.
• [ ] The robots file does not block required public content.
• [ ] Public pages do not contain a noindex instruction unless that is deliberate.
• [ ] Search Console ownership and sitemap submission are assigned to a business-controlled account.

Google documents title links, canonical URLs, and sitemap creation. These settings help search engines interpret and discover pages; they do not guarantee ranking or a fixed indexing date.

If your platform claims built-in search support, verify its controls against the search checks on this page. Correct settings still require accurate content and ongoing review.

The first checks after going live

Test the public website immediately after DNS or publishing changes. Use a device or connection that did not build the site.

• [ ] Open the final domain over HTTPS.
• [ ] Check both common domain variants and confirm they resolve consistently.
• [ ] Open every navigation destination from the public home page.
• [ ] Submit each important form and confirm actual delivery.
• [ ] Test phone, email, calendar, payment, upload, and map actions.
• [ ] Confirm analytics records a test visit and intended events.
• [ ] Confirm Search Console can inspect the canonical public URL.
• [ ] Open the sitemap and sample several listed URLs.
• [ ] Check redirects from any replaced pages.
• [ ] Confirm unauthorized users cannot reach draft or private content.
• [ ] Record who owns the domain, website, analytics, Search Console, forms, and billing.

Collect only the analytics and personal information the business needs, and document why each tool is present. More tracking is not automatically better measurement.

Copy or print the checklist

Print this page or copy it into a project document. Keep the priority labels and pass conditions, assign an owner to each failed check, and record the evidence required to close it. Any digital checkbox version should remain readable without JavaScript.

Routeless Go is one option for a straightforward site. Booking, payments, portals, complex integrations, large migrations, and bespoke design requirements need separate scope.

Frequently asked questions

What pages are essential for a small business website?

Most need a home page, service information, an about page, a contact page, and applicable policies. Add location, staff, work, review, menu, product, or resource pages when customers need them.

How do I test a contact form?

Submit a labeled test from the public page, confirm the success message and delivery, and check the owner notification and reply path. Repeat the test after connecting the final domain.

What should I check on a phone?

Check text, navigation, buttons, forms, calls, maps, calendars, images, and page width on a real phone. Complete the primary action without a desktop, using cellular data as well as Wi-Fi when possible.

Can I use this checklist without Routeless Go?

Yes. These checks apply to hosted builders, content management systems, and custom websites. Confirm platform-specific settings, ownership, cancellation terms, and export options with your provider.

Does this checklist prove accessibility or privacy compliance?

No. Legal requirements depend on the business, jurisdiction, users, data, and operating process. Use qualified legal and accessibility professionals for an applicable compliance review.

Sources

• W3C Easy Checks
• Google title link guidance
• Google canonical URL guidance
• Google sitemap guidance