The new-business
website checklist.

1. Define the website’s job

Start with one sentence: “After visiting this website, the right customer should understand ___ and do ___.” A landscaper may want a homeowner to request an estimate. A retail store may want a visitor to confirm hours, directions, and product categories before visiting. A real-estate professional may want a buyer or seller to ask a local-market question.

This sentence keeps the first release focused. If the goal is a qualified enquiry, the site needs persuasive service information and a dependable enquiry path. It does not automatically need accounts, a dashboard, online payments, inventory synchronization, or a custom scheduling system.

2. Gather the information customers actually need

A designer can improve presentation, but the owner remains the source of truth. Gather accurate information before design begins so the project is not delayed by missing hours, unclear services, or photographs nobody has permission to use.

• Business name exactly as customers should see it
• Primary service area, storefront address, or an accurate statement that service is remote
• Public phone and email, plus the person or inbox that will answer enquiries
• Current hours, holiday handling, and the best time for customers to call
• A short list of core services or product categories with honest descriptions
• What makes the business a good fit and what it does not offer
• Original photographs, licensed images, logo files, and any required brand rules
• Required legal, licensing, brokerage, accessibility, or regulated-product disclosures

Choose one primary call to action

“Request an estimate,” “Ask about availability,” and “Schedule a consultation” create different expectations. Pick the action the business can reliably fulfill. A form should ask only for information needed to respond; every unnecessary field makes the visitor do more work.

Use proof carefully

Real photographs, licenses, public work samples, and permissioned testimonials can reduce uncertainty. Do not invent reviews, performance numbers, client results, or team size. If a project demonstrates capability but was not a paying client engagement, label it as work or a product—not a testimonial.

3. Keep the important accounts under owner control

The business should control its domain registration, primary email, billing relationship, and recovery methods. A developer can be granted limited access without becoming the permanent owner of the account.

• Register the domain in an account the business controls
• Turn on multi-factor authentication and save recovery codes securely
• Use role-based or limited access when the provider supports it
• Never send an account password by email, text, or a project form
• Document where the code, domain, DNS, form delivery, and backups live
• Write down what happens to hosting and support after the included term

For a Cloudflare-managed domain, a limited authorization flow or exact guided DNS changes can connect the site without transferring the domain or sharing the full account password. The safe method depends on the provider and the client’s existing setup.

4. Verify the launch instead of assuming it worked

A page appearing on one laptop is not a launch test. Check the public domain, common screen sizes, the actual form-delivery path, and the way search engines are instructed to crawl the site.

• HTTPS works and HTTP redirects to the preferred HTTPS address
• Preferred domain versions redirect consistently
• Navigation, buttons, forms, email links, phone links, and external links work
• Every indexable page has a unique title, description, main heading, and canonical URL
• The sitemap lists the real public pages and is referenced in robots.txt
• Private, payment, success, and duplicate pages are excluded from search where appropriate
• Images have useful alternative text when they communicate content
• The contact form rejects obvious abuse and sends a real test notification
• The owner knows how and where incoming enquiries will arrive

After launch, add the domain to Google Search Console, verify ownership, submit the sitemap, and inspect important pages. Search visibility is not immediate: crawling, indexing, and ranking are separate steps, and no technical checklist guarantees a first-page position.

5. Measure actions that matter

Google Analytics can show visits, page paths, and configured events. Google Search Console shows how Google crawls the site and, after data accumulates, which searches and pages produce impressions and clicks. Neither tool creates rankings merely by being installed.

For a lead-generation site, the most useful early measurements are usually successful enquiry submissions, clicks to call or email, and the pages people visit before contacting the business. Avoid collecting more personal information than the business needs, disclose enabled analytics, and obtain consent where applicable.

6. Ask these questions before paying

• Exactly which pages and features are included?
• Who supplies and approves the words, images, and legal disclosures?
• Is a working contact or quote backend included, or only a visual form?
• Who owns the domain, source code, accounts, and finished files?
• What outside subscriptions or transaction fees are not included?
• How many revision rounds are included, and what counts as a new feature?
• What technical SEO work is included, and is ongoing content or link work separate?
• How will forms, redirects, HTTPS, mobile layouts, and indexing instructions be tested?
• What happens to the site when the hosting or maintenance term ends?

A clear written answer to these questions matters more than a long feature list. It gives both sides a shared definition of finished.