I recently had a conversation with a former Pharmacy Mentor client who had moved their website to another provider. They thought the move would be a positive step for their business.
They told me that, almost as soon as the new website went live, their search rankings dropped and they lost a significant amount of business. They are now coming back to us.
That conversation is what prompted me to write this article. When your website is consistently bringing patients into your pharmacy, it is easy to underestimate how much work sits behind that. You see the pages. You may not see everything that helps people find them, trust your pharmacy and book a service.
Changing that website means taking responsibility for the business it already generates. Before anything moves, someone needs to understand what is working and how to protect it.
For me, this is a question of capability and responsibility. A website is part of how your pharmacy operates. The people building or changing it need to understand that connection.
A working pharmacy website is a business asset. Its value includes the patients it helps you reach, the services it helps them access and the income those services contribute.
What does a revenue-generating pharmacy website actually do?
It helps the right people find your pharmacy, understand whether you can help and take an appropriate next step. Your team then delivers the service, and you can connect that activity with a business outcome.
That outcome might be an attended travel consultation, a paid ear-health appointment, a fulfilled retail order or a telephone enquiry that becomes an in-pharmacy sale. Payment does not have to happen on the website for the website to contribute.
A straightforward local website can do this well. Equally, an expensive website with a long feature list can struggle if patients cannot find it, understand it or book a suitable appointment. The useful question is what happens between someone needing a service and your pharmacy delivering it.
Be precise about the outcome. A booking is not the same as attendance. An order is not necessarily fulfilled. Revenue is not profit. NHS nominations and service enquiries have their own operational value, but should not automatically be counted as income.
The differences, side by side
These are approaches to managing a website, rather than two fixed categories of product. An information-led website can already bring in business. The opportunity is to understand that contribution and improve it deliberately.
| Area | An information-led approach | An approach focused on revenue |
|---|---|---|
| Purpose | Describe the pharmacy and list its services. | Give each priority service a clear patient journey and measurable objective. |
| Service pages | Tell patients that a service exists. | Explain suitability, pricing, what happens and how to take the next step. |
| Discovery | Wait for people who already know the pharmacy. | Connect relevant local searches and campaigns to specific service pages. |
| Booking | Provide a general contact form or calendar link. | Make the correct service, branch and available appointment easy to select. |
| Mobile use | Check that pages fit a small screen. | Test the complete journey, including forms, calendars and confirmation. |
| Changing provider | Focus on the appearance of the replacement. | Identify existing sources of business and plan how to preserve them. |
| Operations | Pass enquiries to the team. | Define availability, responsibility, response times and follow-up. |
| Reporting | Count visits and button clicks. | Connect activity with completed services, collected income and costs. |
| Improvement | Make occasional visual updates. | Fix the points where patients struggle and review the results. |
Our earlier guide to good and poor pharmacy websites covers the foundations. The additional step here is connecting those foundations with what happens in your business.
What needs protecting when you change your website?
The conversation with our former client brings this into focus. They described a sharp loss of visibility and business following the move. Understanding the precise causes requires the old and new website records; the timing alone cannot establish every technical fault.
It does, however, raise a question every owner should ask before a transition: what is this website already doing for us, and how will the new provider protect that?
Start with the pages that patients use and the journeys that bring enquiries, bookings and sales. Keep a record of performance before the change. Otherwise, you can end up discussing whether the new site looks better while having no dependable way to assess what happened to the business.
For moves that change page addresses, Google’s migration guidance recommends mapping old URLs to their new destinations, implementing redirects, testing and monitoring. It also recognises that rankings can fluctuate while a changed site is recrawled and reindexed. Careful migration reduces avoidable problems; it cannot guarantee fixed rankings.
If only the hosting changes and the URLs remain the same, Google provides separate hosting-change guidance. Your provider should establish which kind of transition you are making.
Ask for a plan you can understand
- Existing performance: which pages and channels currently bring patients?
- Continuity: what content, page addresses and patient routes are being retained?
- Changed journeys: where will old links take someone after launch?
- Testing: who checks that search engines can access the intended pages and patients can complete the process?
- After launch: who watches performance, investigates a drop and corrects problems?
You should not need to become a developer to get those answers. A capable team should explain the work in terms of the services and patients it supports. That responsibility should be clear before the handover.
Start with the services your pharmacy can deliver well
Once existing performance is understood, decide what you want the website to help you grow. A pharmacy offering ten services does not necessarily need ten campaigns running at once. Choose a manageable number of priorities based on demand, available appointments, staff capability and the cost of delivery.
A local pharmacy might concentrate on travel and ear-health bookings. Another might need a retail ordering route. A prescribing clinic may need a more involved assessment, clinical review and fulfilment process. The website should support the operating model you can deliver consistently.
This is why platform selection follows the service plan. A simple booking website may be entirely appropriate. The WooPW is relevant when ecommerce and prescribing workflows are part of the requirement. Adding complexity without a clear use can create more work for the team and more obstacles for patients.
Relevant traffic is the starting point
Patients need a route into the website. That might be a local search, your Google Business Profile, a recommendation, a link from another organisation or an appropriate advertising campaign.
Match the destination to the reason for the visit. Someone looking for an ear-health appointment in your town should arrive at a page explaining that service at the right branch. Making them search a general homepage adds another task before they can decide whether to book.
Pharmacy SEO and suitable paid advertising can support discovery, but their value depends on what follows the click. Sending more visitors into a confusing booking process can simply produce more unfinished journeys.
Diagnose the constraint before increasing activity. Too few relevant visits suggests a discovery problem. Plenty of suitable visits but few bookings calls for a closer look at the page, offer, availability and booking process. Both problems can exist together, but they need different work.
Follow one patient from search to appointment
Consider someone looking for an ear-health appointment. The following comparison is illustrative; it does not describe the returning client’s website.
- Find the homepage
- Search a general services list
- Look for prices and suitability
- Send an enquiry
- Wait for a response
- Find the relevant service page
- Understand the assessment and price
- Choose a suitable appointment
- Receive confirmation and preparation advice
- Attend the appointment
The stronger page explains what the appointment covers, who the service is suitable for, the pricing basis, location and what to expect. It gives patients enough information to make an informed choice and a straightforward way to ask for help.
The booking journey then needs to carry that context forward. Patients should not have to rediscover their service or branch after clicking through. Forms need clear labels and helpful error messages. The calendar needs to reflect appointments the pharmacy can actually provide.
Test the whole process on a phone. A responsive homepage tells you little about a calendar embedded further down the journey. Check the selection, form, confirmation and any payment step. Keep a usable telephone route for people who prefer assistance or cannot use online booking.
Online prescribing needs a different level of care
A prescribing journey must support assessment and clinical decision-making. Reduce unnecessary repetition and confusing instructions, while retaining the checks needed for safe care. Completing a form or making a payment must not imply that a prescription is guaranteed.
The GPhC’s distance-service guidance is an important reference for the operating model. Marketing also needs care: ASA/CAP guidance on pharmacy and clinic websites explains restrictions on promoting prescription-only medicines to the public. Commercial design must work within those responsibilities.
What difference could a better journey make?
Here is a simple hypothetical example. Both scenarios receive the same number of relevant visits and have the same appointment value and attendance rate. Only the proportion of visits that become bookings changes.
These assumptions are for explanation. They are not industry benchmarks, a forecast or a client result.
| Monthly measure | Scenario A | Scenario B |
|---|---|---|
| Relevant visits | 1,000 | 1,000 |
| Visit-to-booking rate | 2% | 5% |
| Bookings | 20 | 50 |
| Attendance rate | 80% | 80% |
| Completed paid appointments | 16 | 40 |
| Revenue per appointment | £60 | £60 |
| Appointment revenue | £960 | £2,400 |
The calculation is: relevant visits × booking rate × attendance rate × average revenue per completed appointment. Under these assumptions, Scenario B produces £1,440 more monthly revenue.
That is not £1,440 more profit. If each appointment has an illustrative £25 direct delivery cost, those additional 24 appointments contribute £840 before any additional marketing, website costs, overheads and tax. Your actual staffing, consumables, refunds and capacity need to replace these assumptions.
There is another distinction: some additional online bookings may come from people who would previously have called. Moving an existing patient to an easier booking route can be useful, but it is not automatically new business. Avoid counting the same income twice when reviewing channels, deposits and final payments.
The work continues after someone books
A full calendar only helps if the appointments are suitable and the pharmacy can deliver them. Confirmations, preparation information, reminders and straightforward rescheduling all belong in the service design.
Make responsibility explicit. Who responds to an enquiry? Who checks a failed booking notification? Who changes availability when a trained colleague is away? A polished page cannot compensate for requests sitting unnoticed in an inbox.
Appropriate follow-up can support ongoing care and future use of the pharmacy. Its purpose should be clear, and patient service communications should be distinguished from promotional messages. Do not assume that a patient making a booking means they have agreed to every type of marketing.
This is also where staff time matters. A journey that reliably captures the information the team needs may reduce repeated calls and administration. Measure that benefit separately from revenue so you understand both commercial and operational value.
What a published pharmacy example can show
Our Midlands community pharmacy case study describes a website project combining online booking, online ordering and improvements to the patient journey.
For June 2023 to June 2024, the case reports 1,175 in-clinic bookings and £77,292 in online medicine sales. It also estimates £88,125 in clinic revenue by multiplying bookings by an assumed average £75. That estimate should be read differently from recorded sales; it does not establish that every booking became an attended, paid appointment.
The useful lesson is how website capability connects with an operational service. These are Pharmacy Mentor’s published historical results, not an independently audited forecast for another pharmacy. They relate to the UPW used in that project and should not be relabelled as results from the current WooPW product.
When comparing case studies, look for the starting position, reporting period, marketing activity and measurement method. A number becomes much more useful when you understand what produced it and what it includes.
Measure what happens beyond the click
You should be able to have a monthly conversation about the website using the same language you use to run the pharmacy. How many suitable enquiries arrived? How many patients attended? What income was collected? What did delivery and acquisition cost?
- Discovery: relevant visits to the services and branches you want to grow.
- Action: completed enquiries, bookings and orders, with button clicks recorded separately.
- Delivery: attended appointments and fulfilled orders, allowing for cancellations.
- Money: collected revenue, refunds, direct costs and marketing expenditure.
- Continuity: appropriate repeat activity and the team’s ability to handle demand.
Use consistent periods and definitions. Reconcile reports with booking and payment records rather than treating every analytics event as a sale. Recognise that telephone calls, walk-ins and privacy choices can leave gaps in attribution. Keep clinical information out of ordinary marketing reports.
Then act on the pattern. Low relevant traffic points towards discovery. Many visitors but few booking starts suggests a relevance or clarity issue. Many starts but few completed bookings suggests friction. Strong bookings but weak attendance calls for operational review. Rising revenue with little contribution calls for a closer look at costs.
Our guide to pharmacy profit margins develops that final point. More activity needs to translate into a sustainable business, not simply a more pressured team.
Improve the current website or build a new one?
Start with an assessment of what works and what prevents progress. A usable website may need clearer service pages, better booking configuration, reliable measurement or more relevant traffic. Those changes can be more appropriate than a complete rebuild.
A new platform becomes more relevant when the current one cannot support the necessary patient journeys, integrations or maintenance reliably. In either case, the proposal should explain what will improve and how existing performance will be handled.
When comparing providers, ask to see work that resembles your operating model. A local booking website and a prescribing clinic require different capabilities. Ask who is responsible for development, search performance, clinical workflow configuration and support after launch.
Costs still need to be understood: build, hosting, maintenance, licences, payment charges, content, acquisition and staff time. But the decision should be based on the work required and the provider’s ability to deliver it. Price alone tells you very little about either.
Our pharmacy website design and development page explains the different routes we support. Before choosing one, establish your service priorities, the current contribution of your website and the practical result you need next.
Eight questions to take back to your team
- Which services do we want the website to support most?
- How do suitable patients currently find those services?
- Can they understand suitability, pricing and the process without calling for basic information?
- Can they complete the journey comfortably on a phone?
- Does the team reliably handle bookings, enquiries and changes?
- Can we distinguish clicks, bookings, attendance and collected income?
- Do we know which existing pages and journeys need protecting?
- Who is accountable for reviewing and improving performance?
You do not need perfect answers before making progress. You need enough visibility to choose the next useful improvement, and a team that takes responsibility for carrying it through.
That is what I took from the conversation that prompted this article. A website can quietly become an important source of business. When you change it, that contribution deserves the same care you would give to changing any other essential part of your pharmacy.
What does your website contribute to your pharmacy?
If you are reviewing your website or considering a change of provider, talk to us about what is working now, what needs protecting and where there is room to grow.
Talk to Pharmacy MentorFrequently asked questions
Can a pharmacy website generate revenue without selling medicines online?
Yes. A website can help patients find a local service, book an appointment or call the pharmacy. Measure the completed paid service and distinguish online bookings from telephone and walk-in activity where possible. Ecommerce is one option, not a requirement.
Can changing my pharmacy website affect my Google rankings?
Yes. Changes to pages, addresses, content and technical settings can affect search visibility. A migration needs preparation, testing and monitoring. Temporary fluctuations can occur even with a careful move, so no provider should guarantee that rankings will remain fixed.
Why does my website get visitors but few bookings?
Check whether visitors want a service you offer in the location you serve. Then review the clarity of the page, appointment availability, pricing information and the complete mobile booking journey. A visitor count alone cannot identify the problem.
Do I need a new website or can I improve the existing one?
Start by reviewing the current site's performance and constraints. Better service pages, booking configuration, measurement or marketing may be enough. A rebuild is more appropriate when the existing platform cannot reliably support the journeys and integrations you need.
How much revenue should a pharmacy website generate?
There is no reliable universal figure. Demand, service mix, relevant traffic, booking completion, attendance, pricing and capacity all matter. Assess revenue alongside delivery and acquisition costs, using your own records rather than someone else's headline result.
What should I ask a provider before moving my website?
Ask which pages already bring in business, what will be preserved, how changed addresses will be handled, how patient journeys will be tested and who will monitor performance after launch. Request a clear scope, named responsibilities and a plan for investigating problems.

