One company, several doors
A buyer in Thrissur is not looking for your Kochi address. A buyer standing outside the Kozhikode branch is not looking for a page that says “serving all Kerala” and a pin in Ernakulam. Local search for a multi-branch firm is mostly hygiene: the name, address and phone that Google already has must match the door, the visiting card, and the page you publish. The rest is restraint — what you must not duplicate.
This is website work, not application work. Anonymous visitors are the users. They want a phone number that rings, hours that are true this Saturday, and a map that does not send them to last year’s rented floor. If you also need a logged-in branch tool for stock or job cards, that is a different job with a different estimate. The line is on website versus web application. Mixing them in one “SEO website” quote is how the pretty location pages ship and the desk still runs on WhatsApp.
We build the public side as web development: fast pages, clean URLs, hours and addresses that a human can edit without calling a developer every time a branch changes its weekly off. The advice below is what we would put in the brief before anyone opens a theme.
NAP: name, address, phone — the same three facts everywhere
NAP is the name on the fascia, the address a courier would use, and the phone that a person will answer. For each branch those three facts must be identical on the Google Business Profile, the location page, the footer if you show it, the directories you still care about, and the visiting card the manager hands out. “Almost the same” is how you split reviews and confuse the map.
Pick one spelling of the legal or trading name and keep it. If the Kochi board says one thing and the GST certificate says another, choose the name people search and put the legal name in small type where you must. Do not invent a slightly different brand per city so each profile “looks unique”. Google is trying to understand one business with several locations. Help it.
Addresses in Kerala are messy: building names, landmarks, pincodes, and a road that changed name. Use the form that matches the board and the post. Do not write “near the old bus stand” on the website and a survey number on Google. Landmarks can sit in the description. The address field should look like a delivery label.
Phone numbers should be the branch number, not a single call-centre line that then asks “which city?” unless that is truly how you operate. If you have one number for the whole firm, say so on every profile and do not pretend each pin has a local receptionist. A missed call on a Saturday is a ranking problem only after it is a customer problem.
One Google Business Profile per real door
If a customer can walk in, that location can have a profile. If a customer cannot walk in — a godown, a back office, a relative’s address used for registration — do not create a profile to “cover the district”. Fake locations get you short-term map dots and long-term suspensions. Service-area businesses can declare the area they serve without dropping a pin on a house they do not open to the public. Use that tool honestly.
Each profile gets its own category, hours, photos, and reviews. Do not manage five branches from one profile with a note in the description. The map pack is local. A Thrissur search should be allowed to show the Thrissur door even if Kochi is the head office and has more reviews.
Hours must be the hours on the door. Festival weeks change. Onam week, you will close or run a skeleton shift. Update the profile that week. A page that says 9–6 when the shutter is down is worse than no page. The same is true for the weekly off. If Kozhikode is closed on Sunday and Palakkad is not, those are two facts, not one “usual hours” paragraph copied five times.
Photos should be of that branch: the fascia, the counter, the parking, the people who work there if they agree. A stock photo of a reception in another country, reused on every profile, tells Google and the customer the same lie. Take new pictures when you paint the wall. It is not branding theatre. It is evidence that the place exists.
One page per location on your site
The website should have a real URL for each branch — not a popup on a single “Contact” page, and not a PDF of addresses. The page needs the NAP, a map or an embed that matches the profile, hours, what that branch actually does, and a way to call or get directions. If Kochi does service and sales, and Kollam only does sales, say so. A buyer who drives to Kollam for a job you only do in Kochi will not leave a kind review.
Link the page to the Google profile and the profile to the page. Use the same name and address string. If you list all branches on a directory page as well, that is fine — it is a table of doors, not a substitute for the pages. The directory page is for humans who already know you. The location page is for the search that named a city.
Each location page is still part of one website. Share the header, the brand, the service explanations that are truly company-wide. Do not build five miniature sites with five menus and five slightly different phone numbers in the header. That is how NAP drifts. One site, several doors, one place to edit the facts.
What not to duplicate
Do not write one 800-word essay and swap “Kochi” for “Thrissur”. Google has seen that page a million times. The customer has too. Duplicate location pages waste the crawl and teach the brand nothing. Unique facts belong on the location page: parking, landmark, services that branch offers, languages at the counter, a note about the one-way road, photographs. Shared facts belong once, on the service pages.
Do not copy the same testimonial onto every city page with a different first name. Do not invent reviews. Do not publish a Malayalam paragraph that is a machine translation of the English one if nobody at that branch can stand behind the wording. A short, true Malayalam line from the manager is worth more than a long, floating one.
Do not create a location page for a city you visit twice a month. If you are a service-area firm — you go to the customer — say which districts you cover on one honest page, and keep the profiles aligned with that. A pin in every taluk you have ever driven through is not a strategy. It is a cleanup project for next year.
Do not stuff every page with the same list of “best in Kerala” phrases. Local search is won by consistency and usefulness, not by a keyword in every heading. If you need a company-wide story — who you are, what you sell, why a buyer should care — write it once. Point the location pages at it. That is internal linking, not duplication.
Categories, services, and the jobs each branch actually does
Google’s categories are crude. Pick the one that matches the door, not the most flattering one in the list. Secondary categories can list the extra work that branch really does. If only the Kochi branch runs a workshop, do not put “workshop” on the Thrissur profile because the brand as a whole offers it. The map user is choosing a door, not a brochure.
The same rule applies to the website. A services page can say the firm offers service, sales, and spare parts. The Kollam page should say what Kollam does on a Tuesday. If the answer is “call Kochi”, write that. Honesty converts better than a copied service list that sets the wrong expectation.
Products that change by branch — tyres in stock, a consultant who sits in one office on Wednesdays, a machine that exists in one factory — are location content. Products that are the same everywhere belong on the main catalogue. That split is also how you avoid turning the site into five stale inventories. Inventory behind a login is an application. A public “we usually carry” sentence is a website.
Reviews stay on the door that earned them
A good review in Kozhikode should stay on the Kozhikode profile. Do not ask happy customers to review the head office because that profile has more eyes. You are training Google that the work happens somewhere else. Reply on the same profile, in the language the customer used if you can do it well. A templated English reply on a Malayalam review looks like a call centre that does not know the branch.
Do not buy reviews. Do not offer a discount for a star rating. Do not seed five profiles with the same three sentences. The cleanup is slower than the shortcut. If a branch is new and has no reviews, say it is new on the page, keep the NAP clean, and do the work. Empty and true is better than busy and fake.
Malayalam, English, and what people actually type
People search in English, in Malayalam, and in mixed spellings of place names. You do not need a full second site to be findable. You need the branch name and the city the way locals write them, a title that a human would say out loud, and a page that loads quickly on a phone. If you publish Malayalam, have someone at that branch read it. If you cannot maintain two languages, maintain one well and keep the NAP correct. A half-translated site is another form of duplication: two weak copies instead of one clear page.
Place names drift — Cochin and Kochi, Trivandrum and Thiruvananthapuram, Calicut and Kozhikode. Pick the form that matches the board and the search you actually win, and mention the other form once where it helps. Do not build two URLs for the same door. One page, two names in the text if you must, one pin.
A table you can take into the briefing
| Do | Do not | |
|---|---|---|
| NAP | One string per branch, copied exactly | Near-enough wording on each channel |
| Google profile | One profile per walk-in door | Pins on godowns and relatives’ houses |
| Website | One unique page per door | The same essay with the city swapped |
| Hours | The shutter this week | “Usual hours” copied in May |
| Services | What that branch does on Tuesday | The full brand menu on every pin |
| Reviews | On the door that did the work | Pushed to the head-office profile |
Site structure that keeps the facts editable
Give each location a stable URL you will not rename every monsoon. Put the NAP in real HTML, not only inside an image of the visiting card. Mark up the address if you use structured data — and then keep it in sync with the visible text. A schema block that still has last year’s phone is a second system of record for the same three facts. You do not need two.
If a manager can edit hours and the weekly off without a developer, you will actually update them. If every change is a ticket, the page will lie by August. That is a content-model problem, not an SEO trick. It is also why a brochure theme with five hard-coded address blocks becomes expensive: nobody wants to touch it, so NAP drifts, so the map pack shows the wrong number.
A location page can share the company header and still be a short page. It does not need a blog, a megamenu of every product, or a slider. It needs the door. If you want the brand story, link it. If you want the catalogue, link it. If you want a quote form, one form that already knows which branch the visitor came from is enough. Five different forms with five different inboxes is how leads go quiet.
When the “website” is doing a different job
If branch staff must log in to see stock, raise a transfer, or close a job, you have left local search. That is a web application. Price it that way. The public location pages can sit on the same hostname and the same brand. They should not share one estimate with the staff tool. We have watched firms buy a “multi-location SEO site” and then ask why two managers cannot edit the same job without overwriting each other. That failure is in the website versus application distinction, not in a missing keyword.
Local search will not fix a phone that nobody answers. It will not fix a branch that does not do the work the profile claims. Get the door right, then publish the door. The rest of the marketing site can be as ambitious as you like — once the three facts agree.
If you are briefing the public site now, send the NAP table, the list of real doors, and the services each door offers. Ask the vendor to show a location page that is not a copied essay. If they return five city names and one paragraph, you have your answer before anyone talks about rankings. Web development for this job is pages a manager can keep true. Rankings follow the door that exists.