DEV Community

BudgetWeb
BudgetWeb

Posted on

A Pre-Launch Checklist for Small Business Website Development

Small business sites look simple: a homepage, a few service pages, a contact form. In practice they are where a lot of avoidable production issues show up, because they are often built quickly, handed over to a non-technical owner and then left alone for years.

This is the checklist I find most useful before pushing a small business site live. It is framework-agnostic, so it applies whether the site is built on WordPress, a static site generator, Next.js or a hosted builder.

Content and structure

  • Every page has one clear purpose and a unique <title> and meta description
  • Exactly one <h1> per page, with a logical heading order after it
  • No lorem ipsum, placeholder phone numbers or "coming soon" pages linked from the navigation
  • A real 404 page that helps people find their way back
  • Legal pages (privacy policy, terms, cookie notice where required) are in place

It sounds basic, but placeholder content shipping to production is one of the most common problems on small sites.

Forms

Forms are the whole point of most small business sites, so test them like a user would:

  1. Submit every form with valid data and confirm the email or CRM entry actually arrives
  2. Submit with invalid data and check the error messages are clear
  3. Confirm spam protection is enabled (honeypot field, rate limiting or a privacy-friendly challenge)
  4. Check the "from" address and SPF/DKIM records so notifications do not land in spam
  5. Make sure there is a visible success message or thank-you page

If the site uses WhatsApp or click-to-call links, test those on an actual phone.

Performance

A small site has no excuse to be slow. Before launch:

  • Serve images in modern formats (WebP or AVIF) at the sizes they are displayed
  • Lazy-load images below the fold, but not the main hero image
  • Limit web fonts to the weights you actually use and preload the critical one
  • Remove unused plugins, scripts and tracking tags
  • Enable caching and compression on the server or CDN

Run a Lighthouse or PageSpeed check on the mobile profile and fix anything that blocks the main content from rendering quickly. Pay attention to Largest Contentful Paint and Cumulative Layout Shift, which are usually caused by unoptimised hero images and late-loading fonts or banners.

Accessibility

Accessibility issues are also usability issues, and many are cheap to fix:

  • All images have meaningful alt text (or empty alt if decorative)
  • Colour contrast meets WCAG AA for body text and buttons
  • Every form field has a proper <label>
  • The site can be navigated with the keyboard, with a visible focus state
  • Links have descriptive text instead of "click here"

SEO basics

You do not need an SEO specialist to avoid the obvious mistakes:

  • Remove any noindex tags or "discourage search engines" settings left over from staging
  • Generate an XML sitemap and reference it in robots.txt
  • Set canonical URLs and pick one version of the domain (with or without www, always HTTPS)
  • Add LocalBusiness or Organization structured data with the correct name, address and phone
  • Set up redirects from old URLs if this is a redesign

The noindex leftover from staging deserves special mention. It is surprisingly common, and it quietly keeps a new site out of search results for weeks.

Security and maintenance

  • HTTPS everywhere with automatic certificate renewal
  • Admin accounts use strong, unique passwords and two-factor authentication
  • Automatic backups are configured and a restore has actually been tested
  • CMS core, themes and plugins are up to date
  • File permissions and directory listing are locked down

Write down who is responsible for updates after handover. Many small sites are compromised simply because nobody owned maintenance.

Analytics and tracking

  • Analytics installed once (not twice through two different plugins)
  • Conversions such as form submissions and calls are tracked as events
  • Consent handling matches the regions you serve
  • Search Console is verified and the sitemap is submitted

Handover

Finally, give the owner what they need to run the site without you:

  • A short guide to editing pages and adding posts
  • Login details stored in a password manager, not an email thread
  • A list of third-party services, renewal dates and who pays for them

Wrapping up

None of this is glamorous, but it is the difference between a site that quietly works for years and one that generates support tickets every month. If you want to compare notes with an agency that does this kind of work every day, have a look at how a small studio approaches Website Development and adapt the parts of their process that fit your own projects.

What would you add to this list? I am always looking for items I have missed.

Top comments (0)