The LocalServePro guide

Starting a Local Business in 2026? Here’s How I’d Build My Website.

Start with a website. Build whatever your business needs next.

ChatGPT Sites: minimal setup · ChatGPT + GitHub + Cloudflare: my recommended foundation

Choose Sites if you want to get online quickly without managing hosting or code. Choose your own GitHub and Cloudflare accounts if you want more control over your code, infrastructure, and future business tools. Both can be a useful starting point.

The Easy Way

Just get your website online.

  1. Create a business Gmail account and choose the business number customers should call. Google Voice is one option; check plan suitability and eligibility.
  2. Open ChatGPT Sites. Confirm Sites is available in your account and check current pricing and usage limits before committing to it.
  3. Describe your business and provide services, cities, hours, phone number, and real photos. Use the starter prompt below.
  4. Ask for a simple mobile-friendly site. Review the text, photos, phone buttons, and any form. Ask to save a version without publishing while you review.
  5. When ready, publish with the audience you intend. Check the live link on your phone. If you want a custom domain, confirm the current domain options and requirements in Sites before buying or connecting it.
  6. For updates, reopen the Site and describe the change. Verify the published result. Add your website to your Google Business Profile.

Know the trade-offs before you choose.

Sites manages hosting and publishing, so you do not set up a separate deployment stack. Available features, plan limits, and future pricing depend on the platform. Check the current terms in your account.

The official documentation checked for this guide does not establish a universal one-click export or migration guarantee. Before relying on portability, confirm how you can obtain the source, export any stored data, and replace platform-specific services. Moving files alone may not recreate a hosted app elsewhere.

Checked October 31, 2026. Sources: Official Sites documentation and pricing guidance. This guide does not promise permanent free hosting or a specific future export feature.

One process, from the beginning

ChatGPT + GitHub + Cloudflare

ChatGPT → GitHub → Cloudflare

Your accounts. Your domain. Your files. Start with one useful page, then add a working lead form and business tools when you need them. This is the complete process, including the setup lessons from building LocalServePro.

What you’ll need before starting

  • Your business name and phone number
  • A list of services, cities served, and working hours
  • 3–5 real photos of you or your work, with permission to use them
  • A short description of your business in your own words
  • A credit card for domain registration

Use one business email for your accounts, enable two-factor authentication, and keep recovery information safe.

Expected costs

ItemWhat to budget
DomainRoughly $10–$20/year for many common domains. Actual registration and renewal prices vary.
Gmail & GitHubFree accounts can be enough to start. Custom-domain email and extra features may cost more.
Google VoiceChoose a business-appropriate plan. No-charge consumer service has restrictions; paid plans and some calls cost extra.
ChatGPTFree entry point; the coding workflow you choose may require a paid plan or have usage charges.
Cloudflare hosting, D1 & emailA small static site may fit free allowances. Sending confirmations to arbitrary customer addresses through Cloudflare Email Sending requires Workers Paid. Database and email usage have plan limits; check current pricing and overages.
Help from SeanFree initial 20-minute consultation. Optional hands-on help: $75/hour, agreed before work begins.

Planning estimates in USD, reviewed October 31, 2026. The guide is free; your accounts and usage have their own costs. Check Cloudflare, Google Voice plans, and the current plans in your ChatGPT account.

Create your business email and phone number.

Start with a dedicated Gmail account, such as smithplumbing@gmail.com. Use the same address to register your business tools. Later, you can add an address on your own domain, such as john@smithplumbing.com.

I recommend Google Voice to keep business calls separate from your personal number. Choose a plan suitable for business use and your location. Google’s no-charge consumer option has eligibility and use restrictions; business plans may cost money. Set up voicemail and test incoming calls and texts before publishing the number.

Enable two-factor authentication on your accounts. Save passwords, recovery codes, and account ownership details somewhere safe.

Ready when: You can receive email and a customer can reach your business number.

Create Cloudflare and buy your domain.

Create your Cloudflare account, then use Cloudflare Registrar if it supports your chosen domain extension. Cloudflare can manage your domain, DNS, and website hosting in one place.

Choose a short, easy-to-spell name close to your business name. A .com is usually a good starting point. Budget roughly $10–$20 per year for many common, non-premium domains; check the actual registration and renewal price before paying. Turn on renewal reminders or auto-renew.

Already own a domain? Keep it. Save existing DNS records before changing anything, especially records used by your email. You can build the new site before switching the live address.

Ready when: You own the domain, can access its DNS settings, and know its renewal cost.

Create ChatGPT and GitHub accounts.

Create your ChatGPT account and GitHub account. ChatGPT helps build and change the site; GitHub stores the code and its history. Start with a private repository for your website.

Confirm that the coding tools in your ChatGPT environment can edit and publish to GitHub. A free chat account alone does not guarantee that capability. Available tools, plans, and usage limits can differ.

Ready when: You can sign in to both accounts and identify your website repository.

Connect ChatGPT to the correct repository.

In the coding workflow you will use, connect GitHub and authorize access to your website repository. Prefer access to that repository only. Ask ChatGPT to read the files and make a small, reviewable change to verify the connection.

Keep account ownership in your name. Never put passwords or API tokens in prompts, public files, or repository code. Use the service’s designated secrets settings when a credential is needed.

Ready when: ChatGPT can read and update the intended website files.

Build one useful page with your real information.

Ask ChatGPT to interview you before drafting. Supply your services, cities served, hours, phone number, and real photos. Keep your own voice. Check every claim; never invent reviews, licenses, credentials, or project photos.

Make the page work on a phone. Put a tappable phone button in the top navigation and above the fold. Show what you do, where you work, and how to contact you. Add a short form only if you will connect and test it.

Ask it to keep public HTML and images separate from server code and secrets. For a Workers project, commit an explicit Wrangler configuration identifying the Worker entry point and asset folder. A Pages _worker.js must not be uploaded as a public asset.

Ready when: The mobile page represents your business accurately and the call buttons dial the right number.

Connect GitHub to Cloudflare Workers Builds.

For a basic site, open Workers & Pages → Create application → connect your GitHub repository and create a Worker with Workers Builds. Authorize access to this repository. In the Worker’s Builds settings, enable automatic builds and select main as the production branch and use the build and deployment settings that match your repository. Use Workers with static assets and API routes, with server code outside the public asset folder.

With Cloudflare’s native GitHub integration, a push to the production branch can publish automatically. You do not need GitHub Actions or a Cloudflare API token just to publish that basic site.

If your app needs database migrations, configure the migration-and-deploy path in step 8. Use one production deployment path so a second build cannot publish before the database is ready.

Ready when: A small GitHub change reaches the Cloudflare preview successfully.

Build your lead form and enable email when needed.

Decide what a submission means: an inquiry, a request awaiting approval, or a booked appointment. Make the success message and emails agree. Collect only what you need: name, contact details, and the question or job details.

  1. Ask ChatGPT to create a server endpoint with validation and spam protection, and save submissions in Cloudflare D1. Keep the database binding and credentials on the server.
  2. Add a protected admin view so you can see every submitted detail, notes, and notification failures. For booking, manage available times, use an explicit time zone, and prevent double booking.
  3. Enable a Workers Paid plan for sending to arbitrary customer addresses. In Cloudflare Email Sending, add your sending domain. Apply the DNS records Cloudflare provides and wait for the domain’s sending status and DNS configuration to be ready.
  4. Connect Email Sending to the Worker using its supported binding or API. Configure the sender on the verified domain and your owner notification address on the server.
  5. Send the owner notification and customer confirmation through the same sending service. A verified sending domain is different from a verified destination: an Email Routing binding limited to verified recipients cannot send to arbitrary customers. Use Email Sending with the appropriate recipient permissions for customer confirmations.
  6. Test with your own email and another customer-style address. Confirm the record is saved, both emails arrive, reply addresses work, and failed email delivery does not erase the booking. Check spam folders and service logs.

Keep transactional confirmations separate from optional marketing permission. Add retry/status handling for failures. Do not claim automated texts, calendar sync, or payments unless you actually built and tested them. Our consultation system is this site’s first example.

Ready when: A test lead appears in admin and both intended emails arrive with accurate booking details.

Automate database updates safely, if your app needs them.

Skip this for a page without a database. For an app like this one, keep migration files in GitHub and apply them before deploying the code that uses them. Cloudflare tracks applied D1 migrations, so the same migration is not applied twice.

This is an advanced, optional example of how this existing site deploys its database changes. It is not required for your basic website. LocalServePro keeps its established workflow; do not add a second publishing path. To reproduce this app’s database workflow:

  1. Have ChatGPT commit the Worker configuration, tests, additive migration files, and deployment workflow. Reuse the existing D1 database and verify its binding and ID.
  2. Create a Cloudflare API token scoped to your account with Workers Scripts: Edit and D1: Edit. Add Pages permissions only if deploying Pages. Tokens are shown in full when created; if lost, replace the token and update the secret.
  3. In GitHub, open Settings → Environments and create prod. Add environment secrets CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, and, for this app’s admin login, LSP_ADMIN_KEY. These are secrets, not public variables. The Cloudflare Account ID is in your account overview; it is not the Zone ID.
  4. Generate a unique admin password in a password manager or with openssl rand -hex 32. Save it securely and put it only in the admin secret setting.
  5. Make the deployment job reference environment: prod so it can read those secrets. Run tests and migration checks, then wrangler d1 migrations apply <database> --remote, then deploy using the configured database binding. Install the admin key as a Worker runtime secret.
  6. Disable a duplicate native Cloudflare build when Actions owns deployment. Check the GitHub Actions run and Cloudflare deployment logs before calling it live.

Keep migrations additive and backward-compatible whenever possible. Never automatically run destructive production migrations, reset the database, overwrite customer data, or rewrite already-applied migrations. Back up data and plan recovery before schema changes. A failed deployment does not necessarily undo a migration that already ran.

Ready when: The tested workflow updates the existing database and deploys without manual SQL or a second competing build.

Add privacy, terms, and a recovery plan.

Before collecting leads, explain what information you collect, why you use it, where it is stored, who processes it, and how customers can ask for access or removal. Keep optional marketing permission separate from booking. Publish terms covering your actual services, fees, responsibilities, and appropriate liability limits.

See our simple Privacy and Terms pages for this site’s approach. Adapt policies to your business and location; have a qualified adviser review them where needed. A template cannot guarantee legal protection or replace data security.

Keep recoverable copies of your site and important customer records. GitHub stores code history, not a backup of your live D1 customer database. Know who can restore the site and database, and how you would recover lost account access.

Ready when: Your policies match what the app does and you have a practical backup and recovery plan.

Connect your domain and test the entire customer journey.

Attach your domain in the Cloudflare project’s custom domain settings. Follow the DNS instructions for that project; preserve records used by email and other services. Choose your main address and redirect any www version you use. Redirect valuable old pages when replacing an existing site.

Test HTTPS, mobile layout, phone links, the contact form, saved lead details, owner and customer emails, and protected admin access. For bookings, verify the time zone and try booking the same slot twice. Check failure messages as well as the happy path.

Ready when: A real customer can visit your domain, reach you, and receive the outcome your page promises.

Set up Google Business Profile and indexing.

Create or claim your Google Business Profile, complete verification, and add accurate services, hours, phone, website, and real photos. Eligible service-area businesses should follow Google’s address-display rules. You can begin this while building the site.

Ask customers for honest reviews after a job, without incentives or screening for only happy customers. Add your site to Google Search Console, verify ownership, and submit your sitemap if you have one. Neither step guarantees rankings or immediate indexing.

Ready when: Your business details are consistent and you have a repeatable way to ask for genuine feedback.

Maintain it from the same accounts.

For future changes, tell ChatGPT what needs updating, review the result, and publish through GitHub → Cloudflare. Check the live page after deployment. Update services, photos, hours, and prices as your business changes.

Review renewals, billing limits, account recovery, backups, and any expiring deployment token. Check the form and email delivery regularly. Add business tools only when they solve a real problem; the same foundation can grow with you.

Ready when: You know how to request a change, verify deployment, and recover your accounts and records.

A starter prompt you can copy.

Help me build a simple website for my local service business. Interview me one question at a time about my services, cities served, customers, phone number, and how I work. Ask for real photos. Use plain language and my personality. Do not invent reviews, credentials, or promises. Make a click-to-call number the primary action, with a short contact form only if we connect and test it. Before building, help me choose between ChatGPT Sites for minimal setup and ChatGPT + GitHub + Cloudflare Workers for more control. Start with one useful page. Explain costs and any account setup before I commit.

Later, when you need more

Cloudflare D1 can store lead records, Turnstile can help protect forms from spam, and email functionality can send notifications. Scheduling, estimates, and other tools are separate projects to build and test. None comes automatically with a basic website.