If you build websites for local businesses (a hardware shop, a pharmacy, a neighbourhood supermarket, a salon), you have probably noticed that the brief you get and the site the business actually needs are two different things. The owner asks for "something modern with animations". What brings them customers is a page that loads on a cheap phone in a car park and tells someone, in five seconds, whether the shop is open and has what they want.
Here is the checklist I keep coming back to when scoping a small-business site. None of it is clever. All of it gets skipped surprisingly often.
1. Answer the three questions people actually arrive with
Almost every visitor to a local shop's website wants one of three things: Are you open? Where are you? Do you have X? Put the opening hours, a tappable phone number and a map link above the fold on mobile. Write the hours as plain text, not inside an image, so search engines and screen readers can read them.
Add holiday and festival hours as a small, dated notice that the owner can update without calling you. A site that says "Open today" on a day the shutters are down does more damage than having no site at all.
2. Make one source of truth for business details
The shop name, address and phone number should be written exactly the same way on the website, the Google Business Profile, WhatsApp Business and any directory listing. "Shop No. 4, Main Road" on one and "4 Main Rd." on another is a small thing, but it confuses customers and weakens local search.
Practically, keep those details in one config file or CMS field and render them everywhere from there. Then add LocalBusiness structured data built from the same values:
{
"@context": "https://schema.org",
"@type": "HardwareStore",
"name": "Example Hardware & Paints",
"telephone": "+91-00000-00000",
"openingHours": "Mo-Sa 09:00-20:00",
"address": {
"@type": "PostalAddress",
"streetAddress": "Shop 4, Main Road",
"addressLocality": "Your Town",
"addressCountry": "IN"
}
}
(Those values are placeholders; use the client's real ones.)
3. Build product or service pages around how customers search
Nobody searches for "Our Offerings". They search for "PVC pipe fittings near me", "medicine home delivery in [town]" or "bridal makeup price". Give each main category its own short page with a real heading, a few honest lines about range and price bands, and a photo the owner actually took. Ten useful category pages beat one long page with every item jammed into a carousel.
If the shop already keeps its item list in billing software, ask whether you can export categories and price ranges from it. It saves the owner hours of retyping and keeps the website closer to what is really on the shelf.
4. Budget for slow phones and patchy data
Many of your client's customers are on a mid-range Android phone with a weak signal. Test on a throttled connection, not on your fibre line. Compress images, avoid loading three font families, and do not autoplay a video hero. A static or mostly static site served from a CDN is often the right call for a shop that changes content once a week.
Lighthouse is a good start, but nothing replaces opening the site on a ₹10,000 phone at the shop counter.
5. Give the owner a way to update the two things that change
In practice, a small shop owner updates two things: offers and hours. Everything else stays the same for months. Make those two things editable in a way they will actually use, even if it is a simple form or a single Markdown file, and leave the rest locked down. A full CMS with twenty menus usually means the site is never updated after launch.
6. Decide early whether they really need online ordering
Online ordering sounds attractive, but it creates a stock problem. If the website says an item is available and the shelf is empty, the shop has to call and apologise. If the business wants to take orders, the website needs to read stock from the same system the counter uses, or the owner must accept a "call to confirm" step. Have that conversation before you quote, not after launch.
7. Plan the boring parts: hosting, renewals and backups
Write down who owns the domain, where it is registered, when it renews and where the backups live. Put the domain in the client's name. A lot of small-business site disasters are not hacks or bugs. They are an expired domain, or a hosting account tied to a freelancer who has moved on.
Also check the site for injected spam a few times a year, especially on older WordPress installs. Hacked pages full of hidden casino or pharma links are common on neglected small-business sites, and the owner usually has no idea until search traffic drops.
When to build it yourself and when to bring in a specialist
A simple brochure site with these seven points covered is well within reach for a solo developer. If the client wants ordering tied to live stock, multiple branches, or a site that grows into an e-commerce store, it can be easier to work with a team that already handles both the website and the shop's billing side. Caddayn, for example, offers website development for small businesses alongside its retail billing tools, which is the kind of setup that saves you from wiring stock data between two unrelated systems.
Whichever way you go, the test is the same: can a customer on a slow phone find out, in a few seconds, whether the shop is open and has what they need? If yes, the site is doing its job.
Jacob
Top comments (0)