A pharmacy group has the same digital problems as an independent, multiplied by the number of branches and complicated by one question: is the group one brand or several? Get that decision right and the rest — websites, Google profiles, dashboards, delivery, apps — follows a pattern. Get it wrong and the group runs five slightly different versions of everything. This guide sets out how small and medium UK pharmacy groups should structure their web presence, their patient journeys and their reporting.
Decide the brand question first
Three situations are common:
- One name, several branches (“Smith’s Pharmacy, Walsall / Wednesbury / Bilston”). One website, one identity, a page per branch.
- Different trading names, one owner (acquired pharmacies that kept their local names). Usually one site per name, because patients know the local name and the Google profiles and NHS listings carry it; a light group identity in the footer if you want it.
- A hybrid moving from the second to the first over time. Build for the destination: one site with branch pages, and redirect each old local domain to its branch page as it is retired.
The test is what patients search for. If they search the local name, keep it visible; if they search the group name, lead with it.
One site with branch pages: the structure
- Homepage for the group: what you are, where you are, the three patient actions, and a branch picker.
- A page per branch at its own URL (/branches/walsall), with that branch’s address, hours, map, phone, services actually offered there, its own
Pharmacystructured data, and a link to its own Google Business Profile. This page is what ranks for “pharmacy Walsall”; it must be substantial, not a card. - Group-wide service pages (Pharmacy First, travel clinic, weight management) written once, with a “available at” list linking to the branches that offer them.
- Forms that know the branch. Repeat and nomination requests either ask which branch or inherit it from the branch page, so submissions route to the right team.
- Shop, if you have one: collection at any branch; delivery routed by postcode to the covering branch.
What not to do: one page per branch that is a copy of the homepage with the town name changed. Google treats near-duplicates as one page and ranks none of them well.
Google Business Profiles
One profile per branch, each verified, each with its own hours, photos, services and reviews, each linking to its branch page rather than the group homepage. Manage them from one Business Profile account with a location group so ownership never sits with a branch manager who leaves. The Google Business Profile guide applies to each branch; local SEO is fought branch by branch.
NHS listings and consistency
Each branch has its own ODS code, NHS.uk profile and EPS nomination identity. Keep the name and address format identical across the website, Google and NHS Profile Manager for each branch; a group that spells its branches three different ways in three systems loses matching in all of them.
Dashboards that respect the org chart
Branch teams need to see their own queue and nothing else; the group needs to see everything. The admin system should support per-branch views with tab-level access, and group reporting across nominations, bookings, repeats and orders. Without this, groups either give everyone everything (a data-protection problem) or give branches nothing (a service problem).
Delivery across branches
Groups with overlapping areas often run rounds that cross each other. Delivery software with multi-branch support — shared drivers, per-branch rounds, group reporting — lets you consolidate rounds by geography rather than by which branch dispensed. Routly’s multi-branch mode is built for this; the delivery cost calculator per branch will show where consolidation pays.
An app for the group
A group is the case where a white-label app makes most sense: one app, one brand, a branch picker, per-branch orders and bookings, and push notifications from whichever branch is serving the patient. It only works on top of the branch-page website structure above, because the app draws on the site’s content and stock. See the White Label App and what a white-label pharmacy app is.
Governance
- One owner for digital across the group, with a named deputy at each branch for hours and service changes.
- A quarterly check of every branch’s hours, services and superintendent details on the website, Google and NHS.uk.
- One data processing agreement covering all branches, and one privacy notice with a branch list.
- Domains registered to the group company, never to a branch or an individual.
- A monthly sheet: nominations and items per branch, bookings per branch, website submissions per branch.
Migrating a group onto one structure
Do it branch by branch, not all at once. Build the group site with all branch pages, launch it on the group domain, then redirect each old local site page-for-page to its branch page as its contract ends. Rankings transfer if the redirects are one-to-one; switching provider without losing rankings covers the mechanics and applies to each old site.
Pharmacy group websites describes how PharmGrowth builds this structure, with per-branch dashboards and Routly and the White Label App across the group.