What a Business Website Should Include in 2026

By Lazar Milicevic · Published September 16, 2026 · 10 min read

You're a small business owner looking at three quotes for a new website. One is $800, one is $4,500, one is $12,000. The proposals all say "responsive design, SEO, modern stack." You have no way to tell what you're actually buying, or which of these sites will still be earning its keep in three years. That's the problem this post solves.

I've built and inherited enough business websites to know that the visible design is maybe 20% of what determines whether a site pays for itself. The other 80% is decisions you can't see in a mockup: how the site loads, how it's indexed, how leads reach your inbox, how you'll change it next year without paying the original agency again. Here's a working checklist for a business website in 2026, with the tradeoffs made explicit.

Start with the job the website does, not the design

A business website has one measurable job: turn qualified traffic into contact events (calls, form submissions, bookings, purchases). Everything else is scaffolding. Before you look at a single mockup, write down: who is the visitor, what do they need to know in the first 15 seconds, and what is the single next step you want them to take?

Most underperforming SMB sites fail this test. They open with a slideshow of stock photos, then three paragraphs about "our mission." A visitor who came from a Google search for a specific service has to scroll and hunt for confirmation that you do the thing they need. Fix this first and half the other problems get smaller.

Practical rule I use for the homepage:

• Above the fold: what you do, who it's for, one primary action button. That's it.
• Below the fold: proof (client logos, case studies, reviews), specifics of what you offer, pricing signal if you have one, secondary action.
• Footer: contact info, service area, hours, physical address if relevant, links to policy pages.

Every page after the homepage should assume the visitor arrived from search and doesn't know you. Answer their query in the first paragraph. Save the story for the About page.

Responsive is table stakes; performance is the actual differentiator

"Mobile responsive" stopped being a feature around 2015. What matters now is how the site performs on a mid-range Android phone on a 4G connection, which is how most of your traffic actually experiences the site.

Google's Core Web Vitals are the metrics that matter here, and they map to real user behavior. The three you check:

You can check any live site in about 30 seconds:

# From the command line, using Google's PageSpeed Insights API
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://example.com&strategy=mobile"

Or just paste the URL into PageSpeed Insights. If your current site scores under 50 on mobile, you're bleeding traffic before you've had a chance to earn it. Google confirms Core Web Vitals are a ranking signal, and there's a well-documented correlation between LCP and bounce rate.

What actually drags performance down on typical SMB sites:

1. Uncompressed hero images. A 3.2 MB JPG from the photographer, uploaded as-is. Convert to WebP or AVIF, resize to actual display dimensions.
2. Bloated page builders. Some WordPress builders ship 400 KB of CSS and JS before you've added any content.
3. Third-party scripts. Chat widgets, tracking pixels, embedded videos loaded eagerly. Each one is a tax on load time.
4. No caching / no CDN. Serving every request from a single origin server in one region.

If you're getting quotes, ask each vendor: "What's your target Lighthouse score on mobile, and will you write it into the contract?" The good ones will say 90+. The vague ones will change the subject.

SEO foundations you cannot retrofit cheaply

Search visibility isn't a plugin you install after launch. It's baked into the site's structure, and fixing it later costs more than doing it right the first time. The non-negotiables:

Clean URL structure. /services/roof-repair beats /page?id=47. URLs should be human-readable, stable, and match the page hierarchy.

Proper heading hierarchy. One H1 per page, then H2s for sections, H3s for subsections. Not for styling — for semantic structure that both search engines and screen readers rely on.

Meta titles and descriptions per page. Auto-generated titles like "Home | Company Name" are wasted real estate. Every page needs a specific, keyword-relevant title under about 60 characters and a meta description that reads like an ad for the page.

Schema markup. Structured data (JSON-LD) tells search engines exactly what the page is about. For a local business, at minimum:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Your City",
    "postalCode": "12345",
    "addressCountry": "US"
  },
  "telephone": "+1-555-123-4567",
  "openingHours": "Mo-Fr 09:00-17:00",
  "url": "https://yourbusiness.com"
}

Add Service, Product, FAQPage, or Review schema where relevant. This is table stakes for showing up in rich search results and increasingly for being cited by AI answer engines.

XML sitemap and robots.txt. Auto-generated, submitted to Google Search Console. Also verify the site in Google Search Console on day one — this is where you'll actually see what search terms bring people in.

Content that answers real questions. Google's Helpful Content system rewards pages that answer the exact query with first-hand specifics and punishes thin, generic pages built for keyword bait. Write for the person, not the crawler.

Analytics that answer actual questions

If you can't answer "how many leads did the site generate last month, and where did they come from," the site is a black box. You need analytics wired in from launch, and you need to measure the thing that matters — conversions, not pageviews.

Minimum stack:

• Google Analytics 4 with configured conversion events (form submissions, phone clicks, booking completions).
• Google Search Console for organic search performance, indexing status, and Core Web Vitals in the wild.
• A simple session recorder (Microsoft Clarity is free and lightweight) for the first 90 days after launch, so you can watch how real people actually use the site.

Configure conversions before you launch, not after. The most common mistake I see: a site runs for a year, the owner has no idea which page drives the most calls, and the tracking was never set up. Any half-competent developer can wire phone-click and form-submit events into GA4:

<a href="tel:+15551234567" 
   onclick="gtag('event', 'phone_call', {'source': 'header'})">
  (555) 123-4567
</a>

For the form, fire the event on successful submission, not on button click — otherwise you'll count failed submissions as conversions and mislead yourself.

Lead capture is where most sites quietly fail

A working contact form is the minimum. A useful lead workflow is what actually moves the needle. Here's the gap:

Minimum: Visitor fills out form → email lands in your inbox → maybe you see it that day, maybe you don't.

Working lead workflow:

1. Visitor submits form (or books a call, or starts a chat).
2. Lead is written to a database or CRM (even if that's just a Google Sheet at first).
3. You get a real-time notification (email, SMS, or Slack).
4. The visitor gets an automated acknowledgment within seconds, with clear next steps and a calendar link if relevant.
5. If they don't hear back within a defined SLA, a follow-up is triggered automatically.

Speed to first response is one of the best-documented factors in lead conversion — studies from Harvard Business Review and others have found that response time in the first hour dramatically outperforms slower responses. Yet most SMBs respond in days.

A minimal working webhook handler for form submissions, deployable on any Node runtime:

export async function handleFormSubmit(req, res) {
  const { name, email, phone, message, source } = req.body;
  
  // 1. Persist the lead
  await db.leads.insert({ name, email, phone, message, source, 
                          created_at: new Date() });
  
  // 2. Notify the team
  await slack.postMessage({
    channel: '#leads',
    text: `New lead: ${name} (${email}) — from ${source}`
  });
  
  // 3. Auto-respond to the visitor
  await sendEmail({
    to: email,
    subject: `Thanks ${name} — we got your message`,
    template: 'lead_ack',
    data: { name, calendarLink: 'https://cal.com/yourbiz' }
  });
  
  res.status(200).json({ ok: true });
}

This is 30 lines of code that converts a passive form into a workflow. Every SMB site should have some version of this running.

Content management, ownership, and the "who owns the site" question

Ask the vendor: "If I fire you tomorrow, what do I own and where does it live?" A shocking number of small business owners can't answer this about their current site.

You should own, in your name:

• The domain registration (registered with a registrar you control, not the agency's account).
• The hosting account (or at minimum, full admin access and export rights).
• The Google Analytics, Search Console, and Google Business Profile accounts.
• The source code, in a Git repo you have access to.
• All content, images, and any custom illustrations or photography.

CMS choice matters less than most vendors pretend. WordPress, Webflow, a headless CMS with a static frontend — all are defensible. What matters is that a non-technical person can edit text and swap images without a developer, and that a technical person can hand off to another developer without a rewrite.

Two anti-patterns to avoid:

1. Proprietary builders you can't export from. If the vendor's platform locks you in, your migration cost is another full build.
2. Custom code with no documentation. A one-off React app built by a freelancer who then disappears is a liability, not an asset.

How to evaluate cost and long-term value

Price is easy to compare. Value is harder. Here's the framework I give clients:

Year 1 total cost = build cost + hosting + domain + any licenses + expected content updates + tracking/analytics setup.

Year 2-3 total cost = hosting + updates + security patches + content additions + any redesigns.

A $800 site that needs a $6,000 rebuild in 18 months is more expensive than a $4,500 site that's still working in year four. A $12,000 site that generates 20 qualified leads a month can pay for itself in the first quarter, depending on your ticket size.

Rough tier expectations for the US SMB market (verify current pricing with vendors — these are qualitative bands, not fixed rates):

The right question isn't "which is cheapest." It's "which of these can I still be growing on in three years, and what does that path cost total?"

Ask vendors for two references from clients whose sites shipped 18+ months ago. Then check those sites' current PageSpeed scores and whether they're still on the platform they launched on. That tells you more than any proposal.

How BizFlowAI approaches this

We build business websites where the site itself is only half the deliverable. The other half is the automation layer behind it: the lead workflow, the CRM sync, the AI-assisted first-response, the follow-up sequences, the internal notifications. A site that captures a lead well is worth more than one that just looks good, and both cost roughly the same to build if you plan for it from day one.

For SMB clients, we typically ship a fast, SEO-clean site paired with a lead pipeline that acknowledges the visitor within seconds, routes qualified leads to the right person, and gives the owner a weekly summary of what's converting and what isn't. That's the layer where AI actually earns its place — not a chatbot on the homepage, but the boring workflow plumbing that means no lead falls through the cracks.

Work with BizFlowAI

If you'd rather have this built for you, that's what we do: production AI automation for solo founders and small teams — agents, integrations, and document pipelines that actually ship.

Book a free discovery call — 30 minutes, we map the highest-ROI automation in your workflow. No pitch deck, just engineering.

More guides like this on the BizFlowAI blog.