Your website has one job: turn a visitor into a call, text or email. For a Surrey business with customers in two languages, that means the Punjabi reader should land on a page written for them, in a script they read, with the same easy way to reach you. We build sites that do that without doubling your costs.
We're a marketing and web service. We're not a contractor; we build the site that sells your work, not the work itself.
What it is
A two-language local website is an ordinary fast, clear business site with a second set of pages for the language that matters to your customers. The details make the difference:
- Separate addresses. English pages and Punjabi pages each have their own URL, such as
/pa/for Punjabi. Google's documentation recommends separate URLs for each language version rather than switching text on the same address. - Language tags. Each version points to the other with hreflang tags, which Google uses to understand localized versions of a page.
- Human copy. English is written by us. Punjabi is written by a qualified native-speaker translator working from our brief, and reviewed by someone who knows your customers.
- The same contact path. Call, text and email are visible on every page in both languages, and a Punjabi caller reaches someone who can talk with them, or gets a clear promise of a callback.
Who it suits
- Surrey businesses whose current site is slow, out of date or hard to use on a phone
- owners who get Punjabi-speaking customers today and want the website to welcome them properly
- anyone about to run Punjabi ads, because those ads need a Punjabi page to land on (see Punjabi and English ad campaigns)
If you only serve English-speaking customers, skip the Punjabi pages. A fast English site is still worth having, and nothing here forces a second language on you.
What's included
- Page plan. Which pages exist in English, which in Punjabi, and why. Usually 6 to 12 English pages and 3 to 6 Punjabi ones at launch.
- Copy. English service pages that say what you do, where in Surrey you work and what happens after someone calls. A translator brief for the Punjabi set.
- Build. A fast, mobile-first site with clear call, text and email buttons and no clutter.
- Search set-up. Titles, descriptions, hreflang, structured data that matches the page, sitemap, and Google Search Console in your name.
- Tracking. Separate tracking for calls, texts and emails from each language version.
- Handover. Logins, a short guide for editing text, and ownership of everything.
Timeline
| Week | Work |
|---|---|
| 1 | Page plan, brief, content gathering (photos of your real work help) |
| 2–3 | English copy, design and build; translator works on the Punjabi pages |
| 4 | Punjabi pages added, reviewed, tested on phones; launch |
| 5–8 | Watch the data, fix friction, add pages where visitors ask for them |
Timing depends mostly on how fast the translated copy and your photos arrive.
How we measure it
- enquiries per 100 visitors, split by language
- the share of visitors who reach a contact action on a phone
- page speed on mobile data, checked at launch and quarterly
- for Punjabi pages: visits from search, plus enquiries that mention the Punjabi page or arrive on its tracked number
Mistakes to avoid
- Mixing both languages on one page. It confuses readers and search engines alike.
- Translating the whole blog first. Translate pages that sell, then decide.
- Using stock photos of strangers as "our team". Real job photos, even rough ones, build more trust.
- Hiding the phone number behind a menu. Put it at the top and bottom of every page.
- Forgetting the Punjabi side after launch. If English prices or services change, the Punjabi pages must change too. Put it on a checklist.
A site works best alongside local search across the six town centres. Prices for site work under each plan are on the pricing page.
Frequently asked questions
Why not just add a Google Translate button?
Automatic translation often gets trade terms wrong, Google may not index the translated text as a proper page, and a customer can tell when a page wasn't written for them. Real Punjabi pages for your main services work better and cost less than translating everything.
Do I need every page in Punjabi?
No. Start with your home page, your two or three main services and the contact page. Add more only when the Punjabi pages are getting visits and enquiries that justify it.
Who owns the website?
You do. The domain, the hosting account, the content and the analytics are set up in your name, and you keep them if you stop working with us.
Gurmukhi or Shahmukhi?
Punjabi is written in both scripts, and the right choice depends on who your customers are. Your translator should confirm which script your audience reads before any page goes live.