How do you set up a small-business website without turning the launch into a technical project? Use this order: define what the site must do, choose where it will be built and hosted, plan the essential pages, prepare and review the content, connect the right domain, test the live experience, publish, and assign an owner for ongoing updates.
No-code builders can make a basic website possible without programming, but they do not decide your content, permissions, accessibility, DNS, email continuity, or maintenance process. This guide uses HubSpot as a documented example. Product plans, account permissions, editor options, and publishing limits can change, so confirm the current details in your account before committing to a workflow.
The practical distinction is between building a site and making it ready to operate. A polished preview does not prove that the intended domain, forms, redirects, mobile layout, or lead-handling process will work after publication.
How do you set up a small-business website?
- Define the site’s purpose, audience, primary action, and accountable owner.
- Choose the builder and hosting arrangement before selecting a theme.
- Plan the minimum useful pages and prepare approved copy and assets.
- Review page settings, accessibility, search readiness, and mobile presentation.
- Choose the root-domain or subdomain architecture before changing DNS.
- Run separate content, technical, and domain checks before publishing.
- Assign responsibility for updates, forms, accounts, renewals, and reporting.
For a simple service business, the first release usually needs a Home page, About page, Services or Products page, and Contact page. A blog is optional. Add one only when someone can publish useful, relevant material consistently.
Choose the builder and hosting arrangement before designing
A website builder is software for creating and editing pages. Hosting is the service that makes those pages available online. Some platforms combine editing, hosting, and content management; others can be combined with separate hosting, a CRM, or another publishing system. Compare the operating arrangement rather than choosing from a template gallery alone.
- Ownership: Who controls the account, domain registration, content, billing, and administrator access?
- Publishing: Does the plan support the pages and content types you need, and can the intended owner publish them?
- Maintenance: Can someone in the business update pages, manage forms, renew the domain, and respond to technical issues?
- Connections: Must enquiries reach an existing CRM, inbox, booking system, or sales process, and who will monitor that handoff?
- Hosting: Will one platform host the complete public site, or will different platforms serve different content?
- Permissions: Who can manage the website platform, DNS provider, registrar, and email records?
HubSpot currently advertises a free drag-and-drop website builder and free custom-domain connection, alongside paid Content Hub functionality. The connection statement refers to connecting a domain, not buying or renewing one, and it does not mean every publishing need or premium feature is included. Check the current account limits before building around a particular feature. See HubSpot’s website builder overview and its page-editor documentation. For account configuration or CRM handoffs, HubSpot systems support may be relevant.
HubSpot’s Marketplace currently lists hundreds of website themes and templates, including free and paid options. Marketplace listings and requirements change, so select a theme only after confirming that it is available to your account and supports the page types you need.
Choose the platform for ownership, publishing requirements, and maintenance responsibility. Choose the theme only after those operating decisions are settled.
Plan the site structure and create useful pages
Start with the smallest set of pages that helps a potential customer understand the business and take a next step.
- Home: Explain what you offer, whom you serve, and where visitors should go next.
- About: Provide relevant experience, approach, and information about the people behind the business.
- Services or Products: State what is included, who it is for, what constraints apply, and how someone can enquire or buy.
- Contact: Provide a working contact method, useful business details, and a clear form if one is needed.
Before opening the editor, prepare a brief for each page. Record its audience, purpose, primary action, owner, approved facts, required assets, and any claims that need business approval. Then use this sequence: approve copy and images, build the page in the editor, review desktop and mobile layouts separately, test navigation and forms, and have the named page owner approve the final version.
HubSpot’s current editor documents starting from a blank page, a template, an existing page where applicable, or AI-assisted creation. It also documents theme-level styling, responsive editing, page settings, and immediate or scheduled publishing. Exact options can vary by page type, theme, account, and subscription.
AI can help draft or revise text from an approved brief, but it should remain a drafting aid. For example, provide the approved service scope, service area, audience, tone, and call to action, then ask for a Services page draft. The reviewer should check every factual claim against the brief, remove unsupported guarantees or results, check accessibility and image rights, and approve the final copy before it enters the editor. The AI does not decide whether the page is ready to publish.
When enquiries need to be routed and followed up reliably, assign an owner for that process as well as for the page. CRM systems consulting can help define that system responsibility.
Prepare pages for search and accessibility
Review the actual page and its settings rather than relying on an SEO score. For each intended indexable page, check the following:
- A distinct, descriptive page title.
- A useful URL slug and one preferred URL.
- A page-specific meta description that accurately summarizes the content.
- A clear heading structure that helps people scan the page.
- Useful alt text for meaningful images, with no unnecessary description for decorative images.
- Images sized appropriately for the page rather than uploaded at unnecessarily large dimensions.
- Correct language, HTTPS, canonical or preferred URL settings, and sitemap behavior where applicable.
HubSpot’s SEO recommendations can identify omissions such as missing titles, descriptions, alt text, image sizing, HTTPS, and other technical settings. Treat those recommendations as a diagnostic checklist, not a ranking score.
You control the page content, title, description, and preferred URL you provide. Google may select different title-link or snippet text from several page signals. Write accurate fields for people, then review the rendered page instead of forcing keywords into every field.
Google may generate a snippet from page content instead of using the meta description. It can also select or rewrite a title link using the title element, visible headings, page text, anchor text, and other signals. A sitemap can help discovery, but it does not guarantee indexing or ranking. Google explains these distinctions in its guidance on snippets, title links, and sitemaps.
Choose the domain architecture before changing DNS
A root domain is the main name, such as example.com. A subdomain adds a prefix, such as offers.example.com. If one platform will host the entire public site, the root domain may be appropriate. If the main site and supporting content will live on different platforms, use separate subdomains for the separate hosting destinations.
For example, a business might keep its existing WordPress site at example.com while hosting HubSpot campaign pages at offers.example.com. That architecture must be agreed before the pages are designed and before DNS is changed.
A root domain or subdomain can serve content in only one location at a time. Connecting a hostname that already serves live pages can disrupt them. Before editing records, identify what the hostname currently serves, back up the existing site, record relevant DNS settings, and confirm which provider handles business email. Preserve unrelated MX, SPF, DKIM, DMARC, TXT, and verification records unless an authorized administrator has approved a change.
HubSpot’s domain-connection guide documents the need for access to the DNS provider and an appropriate HubSpot permission, such as Super Admin or Domain Settings permission. Its instructions generally distinguish CNAME records for subdomains from A records for root domains. Use the values shown in the authorized account, not generic examples copied from another setup.
DNS changes can take time to appear across resolvers. Timing depends on provider setup, record type, TTL, caching, nameservers, and resolver behavior. A third-party DNS checker can provide a useful diagnostic, but authoritative DNS configuration remains the source of truth when results differ.
Run a launch check, then publish
Content readiness and domain readiness are separate gates. Approved pages do not prove DNS is correct, and correct DNS does not prove the pages are ready. Name one launch owner to record the intended hostname, approvals, unresolved exceptions, and go or no-go decision.
- Page owners approved the content, contact details, claims, and calls to action.
- Desktop and mobile layouts, navigation, links, and forms have been tested.
- The intended hostname resolves to the correct site and HTTPS works.
- DNS changes preserve the records and services that should remain, including email.
- Preferred URLs, canonical settings, status codes, and necessary redirects have been reviewed.
- A test form reaches the intended inbox or lead-handling process.
- A named launch owner recorded each pass or accepted exception.
Open the live site on a phone, follow the main navigation, open key pages directly, submit a test form, and confirm that analytics records the test visit if analytics is configured. If a DNS check disagrees with the expected result, ask the DNS administrator to verify the authoritative records.
HubSpot’s editor documents immediate or scheduled publishing. Select the option that matches the approved launch plan rather than relying on a specific button color or interface label.
Keep the site useful after launch
Assign responsibility for software and account access, content updates, forms, analytics, domain renewal, and technical escalation. If the business cannot cover these tasks internally, outsource them with a defined scope, response expectations, access policy, and approval process. Maintenance cost varies by site, provider, scope, and response requirements, so one personal price is not a market benchmark.
Set a monthly review that produces named actions. Check useful visitor actions and broken journeys, update stale pages, inspect lead or sales outcomes, verify forms and key links, and assign corrective work. A blog or historical content program can be useful when it supports the business’s core topics, but publishing thin or irregular posts is not a substitute for clear service pages.
Keep analytics at the correct data grain. An individual pageview is an event or observation. A monthly pageview total is an aggregate. Revenue, expenses, and profit are accounting-period aggregates. Bounce rate and average session duration are calculated metrics whose definitions can vary by analytics platform. Do not place these different row types in one table without an explicit grain and metric-definition field.
If reporting sources are combined, retain the source system, extraction timestamp, timezone, reporting period, metric definition, attribution model, and source run identifier. The following are proposed implementation fields, not a HubSpot-published schema:
- Raw event: one row per pageview or other source event, keyed by the source system and event identifier where available.
- Run observation: one row per extraction or reporting run, keyed by source system and extraction run identifier.
- Monthly metric: one row per site, reporting period, metric name, metric-definition version, and attribution model.
- Financial period: one row per business, accounting period, and ledger source.
For a monthly aggregate, a proposed uniqueness key is site_id + period_start + period_end + metric_name + metric_definition_version + attribution_model. Add the source system or reporting scope when those can vary. If concurrent reporting runs could create duplicates, enforce a database unique constraint or use a transactional upsert. A lookup followed by an insert is not safe as the only deduplication method under concurrent writes. Confirm the actual export or integration capabilities before promising an automated feed.
A website is ready to operate when someone is accountable for keeping it accurate, functional, secure, connected to the business, and measurable. Launch the minimum useful pages, verify the domain and key journeys, then let monthly evidence determine which improvements deserve attention.