Pharmacy website guide
Replacing a Pharmacy Website Without Losing Important Pages
How to plan a pharmacy website migration around existing URLs, service information, booking links and a careful launch.
By Graham McCann · Updated 11 October 2026
Start with an inventory, not a blank design
Before changing a pharmacy website, list the pages, URLs and booking journeys that already matter. Check Search Console, analytics and the booking provider to understand how patients arrive and what they use.
A service page that looks dated may still receive useful search traffic. Preserve its purpose and URL where appropriate, or plan a redirect to a genuinely relevant replacement.
Agree the migration map
- Record each existing URL and the proposed destination.
- Keep valuable pages at their existing addresses where practical.
- Use direct permanent redirects when a relevant URL changes.
- Check internal links, navigation, canonical tags and the sitemap.
- Avoid redirecting every removed page to the homepage.
Protect the booking journey
Identify the booking links used in the website, Google profile, appointment reminders and other patient communications. Confirm which links are controlled by the website and which belong to the booking provider.
Test on a phone from service discovery to the booking screen. A link opening correctly is one check; completing a representative booking in a suitable test process is another. Do not create real patient appointments as an unlabelled test.
Check pharmacy information before launch
- Opening hours and contact details.
- Current service information and accurate private-service pricing.
- Practitioner and registration details provided by the pharmacy.
- Privacy notices and handling of enquiry or booking information.
- Clinical and promotional wording reviewed by the pharmacy.
Make launch reversible
Keep a backup and record the old configuration. Preview the replacement privately, agree the launch time and know who can restore the old site if something important fails.
After launch, check page responses, forms, booking links, redirects and the sitemap. Monitor indexing and relevant queries rather than assuming an immediate ranking improvement. No migration can promise zero disruption in all circumstances.
Ask for a migration scope
A useful quote explains which pages and integrations move, who approves the content and what checks happen before and after launch. If those details are missing, resolve them before switching websites.