Your Manchester Business Website: What to Get Right Before You Launch
Local sites do not lose enquiries because they look dated. They lose them because nobody can tell whether you cover their postcode or how to reach a human. The build decisions that matter.

Most local sites do not lose enquiries because they look dated. They lose them because someone in Chorlton or Salford cannot tell, in the ten seconds they give you, whether you cover their postcode and how to reach an actual person.
A Manchester business website has a narrower job than a national one. It is not trying to win the country. It has to convince someone within roughly a forty minute drive that you exist, that you are real, and that getting in touch is not a chore. Nearly every build decision that matters follows from that, and most of them are structural rather than cosmetic. Here is what to get right before you launch.
Put your contact details in the HTML, not in a picture
A phone number baked into a header image is invisible. It cannot be tapped, copied, selected, read out by a screen reader, or parsed by anything that reads your page. The same applies to an address sitting inside a designed banner. Your business name, address, phone number and opening hours belong in real text, in the markup, on every page — the footer usually, and again in full on the contact page.
Then mark them up properly. Google's LocalBusiness structured data documentation sets out the properties it understands: address, geo coordinates, opening hours, departments, price range. Structured data is a signal, not a guarantee of anything, and anyone who tells you it is a ranking lever is overselling it. What it does do is remove the ambiguity about who you are and where you operate. For a local firm, that ambiguity is the whole problem.
On mobile, wrap the number in a tel: link. A number that cannot be tapped is a number someone has to memorise on the way back to the van, which means they will ring whoever is easier instead.
One page per service per area, and mean it
The standard mistake is a single "Areas We Cover" page listing forty towns in a bulleted column. That page ranks for nothing, says nothing, and reads like filler because it is filler. Worse is the templated version: thirty near-identical pages where only the place name changes.
A page earns its place when it has something specific to say. If you fit commercial flooring in Stockport, that page should cover the sort of buildings you work in there, typical lead times, access and parking realities, and the kind of job you have actually done. The test is simple: if you cannot write four honest paragraphs about doing that work in that place, do not build the page. Three real location pages beat thirty thin ones, and they will not leave you with a site full of near-duplicate content to clean up later.
Your map embed is probably the slowest thing on the page
Almost every local site drops an interactive Google Map into the contact page, and almost nobody drags it. What it does reliably is pull in a large chunk of third-party JavaScript at exactly the moment the page is trying to render.
Google's own guidance on third-party embeds recommends replacing embeds like this with a facade — a static image that looks like the map and links out to the real thing when clicked — or at minimum adding loading="lazy" to the iframe so it only loads when someone scrolls near it. Either approach costs an hour and takes the weight off your first render.
That matters because Largest Contentful Paint, the metric for how quickly your main content appears, should come in at 2.5 seconds or less for the 75th percentile of visits. That is difficult to hit when a map nobody asked for is competing with your hero image for bandwidth on a phone somewhere along the M60. A screenshot of your location with a "get directions" link does the same job for the visitor and none of the damage.
Build the form for someone standing in the rain
Your enquiry form will be filled in on a phone, one-handed, often outdoors, frequently by someone who has already contacted two of your competitors. Build for that person.
Ask for the fewest fields that let you actually respond — name, contact method, and a short description of the job. Set the right input types so the numeric keypad appears for phone numbers and the email keyboard for email. Reserve space for validation messages so the layout does not jump when one appears. And send people to a real confirmation state, not a silent scroll back to the top, so nobody submits the same form three times wondering whether it worked.
Then test it on an actual handset, on mobile data, not a desktop browser squeezed narrow. Most broken forms we find were never tested the way real people use them. This is the cheapest conversion rate work available to a local business, and it is almost always where the biggest leak is.
Answer the boring questions before anyone has to ask
Do you cover my postcode. Are you insured. How quickly can you come out. Do you charge for a quote. Is there parking. Do you work weekends.
These are unglamorous, and they are what actually decides whether someone contacts you or closes the tab. Put the answers on the page in plain language. Every question a visitor has to ask by email is a question that delays your reply by a day and gives them a reason to ring someone else in the meantime.
Fix the site before you turn the ads on
This is the part worth being blunt about. Paid traffic magnifies whatever your site already does. If your contact details are trapped in an image and your form fails silently on iOS, Google Ads will simply help you pay to find that out faster. The same goes for organic search: ranking a page that cannot convert is an expensive way to generate bounce data.
Get the structure right first. It is not glamorous work, and it is the difference between a site that quietly collects enquiries and one you end up apologising for. If you want a second opinion on where yours is leaking, or you are planning a rebuild, get in touch and we will tell you straight.

