Website Development Checklist: What to Lock Down Before You Start

A website build usually doesn’t go sideways because someone can’t code. It goes sideways because the essentials weren’t decided early, so every week becomes a new round of “actually, we also need…”

That’s how projects bloat, timelines slip, and you end up with a website that technically works but is fragile, hard to update, and weirdly expensive to improve.

This checklist is for non-technical directors who want control without getting buried in jargon. It’s designed to help you brief a developer properly, spot risk early, and get a site you can actually build on.

1) Define the outcome in one sentence (or the project has no centre)

Before you talk pages, design, or platforms, lock this down: What is the website supposed to make happen for the business?

Good answers sound like outcomes:

• “Generate qualified enquiries for these three services.”
• “Reduce sales time by answering the common objections upfront.”
• “Support growth into a new market by proving credibility fast.”

Bad answers sound like vague activity:

• “Modernise the site.”
• “Make it look professional.”
• “Get it up.”

Once the outcome is clear, two decisions become easier:

• what to prioritise (and what to leave for later)
• what “done” actually means

Quick check: If you can’t explain success without mentioning design, you’re not clear yet.

2) Lock the scope the right way (jobs to be done, not a page list)

Most page lists are fiction. They change the moment someone remembers a service, an industry, or a compliance requirement.

Scope the build like this instead:

• Must-have journeys (what a visitor must be able to do and what do we want them doing)
• • enquire
  • book
  • request a quote
  • compare options
  • find proof fast
• Must-have content types (what you will publish repeatedly)
• • services
  • case studies
  • locations
  • industries
  • resources / FAQs
• Must-have integrations
• • forms to CRM
  • email automation
  • booking tools
  • analytics and conversion tracking

This stops the project becoming “a stack of pages” and turns it into a system that supports the business.

Not sure where to start? Look at your last 20 enquiries and write down what people asked before they contacted you. Those questions belong on the site.

3) Sort your content before anyone designs anything

This is where most projects waste weeks. People think content is “later”, then the design gets approved with placeholder text and everything breaks when real copy shows up.

Do these three things early:

1. Content inventoryList what exists now: pages, PDFs, brochures, case studies, product sheets, old landing pages.
2. Content gapsWhat must exist to sell the work properly? Proof, process, FAQs, comparisons, team credibility.
3. Content ownershipWho writes what, who approves it, and what the deadline is.

If you want speed, this is the fastest lever you control.

4) Measurement and lead handling

A website can “look great” and still fail because nothing is measurable and nobody follows leads properly.

Lock down:

• What counts as a conversion (form, call, booking, download)
• Where those leads go (email inbox is not a system)
• What you want to see monthly (lead volume, lead quality, top pages, drop-offs)

If you’re relying on organic search long-term, page experience and performance matter too. Google states Core Web Vitals are used by its ranking systems, and recommends aiming for good CWV as part of page experience. 

This doesn’t mean “chase a perfect score”. It means don’t ship something slow and unstable and then act surprised when performance and rankings are harder than they need to be.

5) Hosting and environments (where “small choices” create big pain later)

Most directors only think about hosting when something breaks. That’s backwards. Hosting decisions affect speed, stability, backups, and how safely changes can be made.

At minimum, confirm:

• Where the site is hosted and who controls the account
• Backups (frequency, retention, and restore testing)
• A staging environment (so changes can be tested before going live)
• Monitoring (uptime and basic error alerts)

If you want this handled as part of a stable system, this is where Hosting matters.

6) Security, accessibility, and “boring checks” that prevent expensive problems

These aren’t nice-to-haves. They’re the stuff that stops incidents, churn, and reputational damage.

Security basics

Your biggest practical risk in modern websites is dependency sprawl. The more plugins, add-ons, and third-party components you stack, the more surfaces you have to maintain.

So your checklist item is simple:

• keep dependencies minimal
• keep them maintained
• have a patching plan

Accessibility baseline

Even if you’re not chasing formal compliance, accessibility is part of building a site that works for real people. WCAG 2.2 is the current W3C recommendation and is the sensible reference point for modern builds. It helps guide websites to higher accessibility standards so everyone can use them.

Your practical checklist item:

• readable contrast
• keyboard navigation works
• forms are usable and error messages are clear

Basic auditing

If you need a simple way to sanity-check performance, accessibility, and best practices, Lighthouse is the standard starting point and runs in Chrome. 

This is also where ongoing care matters. A good build still needs upkeep, otherwise it drifts. That’s why Website Maintenance exists.

7) QA and launch (make “done” measurable)

Before launch, you want more than it “looks good on my laptop”. Here are the minimum checks you or your provider should be covering:

• Mobile and desktop layouts are clean across common devices
• Forms submit correctly and land in the right place
• Thank-you pages or conversion events are tracked
• Redirects are in place if URLs changed (so you don’t lose existing equity)
• Pages load fast enough that people do not bounce out of impatience
• Backups are running, and someone knows how to restore

8) Copy/paste checklist

Outcome:

• Success outcome defined in one sentence
• What's your primary conversion action agreed (enquire / book / quote / buy)
• Top 3 objections your site must answer listed

Scope:

• Must-have user journeys mapped
• Must-have content types listed (services, case studies, FAQs, etc.)
• Must-have integrations listed (CRM, booking, analytics)

Content:

• Content inventory completed (what exists now)
• Content gaps identified (what must be created)
• Ownership and deadlines set for writing and approvals

Measurement

• What counts as a conversion agreed
• Where leads go agreed (CRM / workflow, not just inbox)
• Reporting expectations set (monthly basics)

Hosting + Environments

• Hosting account ownership confirmed
• Backups set (frequency + retention)
• Staging environment confirmed
• Basic uptime/error monitoring in place

Security + Accessibility:

• Dependency plan (minimal plugins, maintained components)
• Update/patch responsibility assigned
• Accessibility baseline agreed (forms, contrast, keyboard use)

Quality Assessment + Launch

• Mobile QA done
• Forms tested end-to-end
• Tracking tested (events or conversion goals)
• Redirect plan confirmed if URLs change
• Handover pack confirmed (access, docs, training)

Post Launch:

• Maintenance plan agreed (who does what, how often)
• First 30-day optimisation check scheduled

What to do next

If you’re doing this internally, use the checklist to produce a one-page brief, then commit to a realistic scope and timeline.

If you’re hiring an agency, the same checklist becomes your filter. Any decent team should be able to walk through it calmly, explain trade-offs in plain English, and show you how they prevent fragility.

If you want us to apply this to your business and turn it into a plan you can trust, start here: Website Development. And if you want proof of how we build and stabilise these systems, see Case Studies.