Create a branch data source before writing pages
Record the official name, address, phone, opening hours, GPhC premises number, NHS profile, services, booking route and operational notes for every branch. Assign an owner and a review date. The website, Google profile and internal systems should draw from or be checked against that record.
This prevents a common failure: one central team updates the group service list but a branch has stopped offering an appointment, changed hours or uses a different number.
Give every real premises a useful page
A branch page should do more than swap the town name. Include the actual entrance and access information, verified contact details, current hours, services available there, booking options, local areas served and links to official records. Use genuine branch photos when permission exists.
Link from a group location finder and between nearby branches where that helps patients. The canonical should point to the page itself, and the sitemap should include only live, indexable routes that do not redirect.
Manage one eligible Google profile per location
Use consistent real-world naming and the correct branch URL. Avoid duplicate profiles, keyword additions and virtual addresses. Give central and branch teams a documented access model so suggested edits, reviews and special hours are handled without losing ownership.
Separate shared services from branch availability
A group can maintain shared, pharmacy-approved service explanations while each branch page declares whether and how that service is available. The booking route should carry the chosen location and service forward. If availability differs by day or pharmacist, state how the patient can confirm it.
Control duplication without making pages thin
Opening paragraphs, directions, local partnerships, team details and service availability should be genuinely branch-specific. Shared clinical explanations can be reused carefully when they remain accurate, but the page still needs local value. Do not publish dozens of city pages for areas where the group has no premises or meaningful service evidence.
Report at group and branch level
Group totals show overall direction but can hide a failing location. Report visibility, profile actions, page visits and bookings by branch, then compare with hours, capacity and service mix. Use the same event definitions everywhere so a group total is not built from incompatible numbers.
EA Pharma Group is a public example of the structure: six pharmacies across Selby, Rotherham and Dewsbury, with branch pages, service availability and booking routes inside one website. The public structure is observable; private performance data should only be published with permission.