Business Website Checklist: 10 Things to Check Before You Hire a Developer
By Rankora Digital · · 6 min read
A website is a long-term investment, and many of the problems owners discover later could have been avoided with the right questions at the start. Use this checklist when you talk to a developer or agency, so you end up with a site that loads fast, can be found on Google and belongs to you.
1. A clear goal and page plan
Decide what the site must achieve: phone calls, WhatsApp enquiries, bookings or online sales. A good developer will ask about this first and propose pages around it, instead of starting with colours and templates.
2. Mobile-first design
Most local searches happen on phones. Ask to see the design on a real phone, not only on a desktop mockup, and check that buttons, text and forms are easy to use with one thumb.
3. Speed
Ask how they optimize images, fonts and code, and how they will test the finished site. You can check any page yourself with Google PageSpeed Insights. A slow site frustrates visitors and can hurt search performance.
4. SEO basics built in
- A unique page title and description for every page.
- One clear main heading per page, with sensible subheadings.
- A sitemap and robots file, and canonical URLs.
- Structured data such as LocalBusiness and FAQ where relevant.
- Separate pages for separate services, not one long page for everything.
5. You own everything
Your domain, hosting account and website code should be registered in your name or handed over to you. Be cautious if a developer insists on keeping the domain or hosting under their own account.
6. Easy ways for customers to contact you
Put your phone number, WhatsApp link and enquiry form where visitors can reach them without hunting. Clear calls to action matter more than decoration.
7. Analytics and Search Console
Ask that Google Analytics and Google Search Console are connected at launch, and that you get access. Without them you cannot see where visitors come from or which searches find you.
8. Security basics
The site should run on HTTPS, keep software up to date and avoid collecting data it does not need. Ask what happens if something breaks after launch.
9. A content plan
Decide who writes the text and supplies photos. Real photos and clear, specific descriptions of your services usually perform better than generic copy, so budget time for content, not just design.
10. Written timeline, payments and support
Get the scope, timeline, payment milestones and post-launch support in writing before work starts. Ask what is included after launch and who to contact when you need changes.
Red flags
- A guarantee of a number-one Google ranking.
- No portfolio or examples of live websites.
- Unwillingness to hand over domain, hosting or code.
- Vague pricing with surprise charges later.