gaash.ai

Brand & Positioning · 7 min read · September 26, 2026 · , gaash.ai

Pickup times, a delivery area, a pharmacist by name: a pharmacy's own facts

A neighborhood pharmacy has facts that belong to one address: when a prescription dropped off in the morning is ready, how far it delivers and on what terms, when a pharmacist is at the counter to talk to, which services it offers in person, and how to check whether an item is in stock. State each as your own, with the times in brackets, and compare yourself with no one.

Facts that belong to one address

Some facts about a pharmacy exist because it has a counter on a street: a time by which a prescription dropped off today is ready, an area its driver covers, a pharmacist who is there on stated days, a room where a conversation is private, a shelf someone can phone to ask about. Each is a fact the pharmacy sets, and each can go on a page as a sentence someone can check. Together they are the pharmacy's unique selling proposition, stated as facts rather than as a slogan.

What the page does not do is compare. It says nothing about other pharmacies, however they serve their customers, and nothing about being faster, closer or friendlier than anyone. A comparison is a claim about businesses you do not run, which nobody reading it can check, and in health advertising it is also a question for your regulator. Your own times and terms stand on their own.

The facts that belong to one pharmacy's address, and a bracketed sentence for each. Brackets are yours.
The factA sentence the page carries
Same-day pickup"Prescriptions dropped off by [11 a.m.] are ready by [4 p.m.] the same day, Monday to Saturday, when the item is in stock."
Delivery"We deliver to [neighborhoods or postal codes] on [days]. Orders in by [1 p.m.] arrive between [4 and 7 p.m.] that day."
A pharmacist to talk to"A pharmacist is at the counter [whenever we are open], and on the phone at [number] from [time] to [time]."
Services in person"[Service, as your license names it]: [walk-in or booked], [days], with [pharmacist's name]."
Checking stock"Call [number] or message us at [channel] to check an item; we reply within [an hour] while we are open."
Access"Parking at [where]; a step-free entrance on [street]; a private consultation room on request."

Same-day pickup, written as times

A pickup promise without a time gives a reader nothing to plan around. Write the cut-off and the ready time, the days they apply, and the one condition that changes them, which is whether the item is in stock. Then say what happens when it is not: "If we need to order it in, we'll call you with the day it arrives." That sentence answers the next question before anyone has to ask it.

Refills and transfers get lines of their own, because they run on different clocks. A refill requested by [time] through [the phone line or the app] is ready [when]. A transfer is ready [within (time) of the other pharmacy sending it], and the page says what the customer brings or tells you to start one. Each line is your policy, written the way the counter would say it, and it changes on the day your practice does.

Keep pickup times apart from opening hours. If your counter stops taking new prescriptions an hour before it closes, the page says so, because the question being asked is when a prescription will be ready, not when the door locks. Holiday weeks change both, and late nights and holidays covers how those hours are posted.

The delivery area, and the terms that come with it

State the area the way the people in it would name it: neighborhoods by name, postal codes, or a radius from the pharmacy with the landmarks at its edge. Then the terms: the days, the cut-off for same-day orders, the delivery window, [the charge, as of (date)] or no charge, what the driver asks for at the door, and what happens when nobody is home. What can be delivered, and to whom, differs by jurisdiction for some items; the page states your own practice and leaves the rule to your regulator.

One delivery page carries the whole area. A page for each neighborhood with only the name swapped is what Google's spam policies describe as doorway abuse, pages aimed at particular places that lead to one page. List the neighborhoods on the delivery page itself. A pharmacy with a second location gives that location's page its own area.

In the structured data, delivery is a Service the pharmacy provides, with areaServed for the area and hoursAvailable for the window. schema.org lets areaServed take a GeoCircle, a circle given by a center point and an approximate radius, in meters unless another unit is stated, or a list of places by name. The provider points at the pharmacy's own node.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "[Prescription delivery]",
  "provider": { "@id": "https://www.example.com/#pharmacy" },
  "areaServed": {
    "@type": "GeoCircle",
    "geoMidpoint": {
      "@type": "GeoCoordinates",
      "latitude": "[latitude]",
      "longitude": "[longitude]"
    },
    "geoRadius": "[radius in meters]"
  },
  "hoursAvailable": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "[16:00]",
    "closes": "[19:00]"
  }
}

A pharmacist to talk to, by name and by hour

A pharmacist at the counter is a fact about one address, so name them. Each pharmacist gets a line on the about page: the name, the title as the licensing body writes it, the days they work, the languages they speak, and what they are there for, which is questions about medicines, answered in person or by phone and never on the page. Say when a private conversation is possible: a consultation room, a quieter hour, a call back at a time the customer chooses.

In the markup, each pharmacist is a Person with a jobTitle, knowsLanguage for the languages, worksFor pointing at the pharmacy, and hasCredential holding an EducationalOccupationalCredential, recognizedBy the licensing body and validIn the jurisdiction. The pharmacy's own license is hasCertification with a Certification on the pharmacy's node. Keep every credential in the licensing body's words, and give the public register's lookup, where one exists, as the address a reader can check.

Both belong to the pharmacy's LocalBusiness schema, typed ["Pharmacy", "LocalBusiness"] as the overview for pharmacies explains, and both say only what the about page says.

Services in person, and a way to ask about the shelf

List the services your license covers where you operate and that you offer at this address, each with walk-in or booked, the days and who provides it. How to word a service page without a health claim is in stating what you offer; the point here is that each service is a fact about the counter: offered here, on these days, by this person.

Stock is the question people phone about, so give them the way to ask it. Say how to check an item (a call, a message, a form), how quickly you reply while you are open, and how ordering works when you do not have it: the cut-off for items you order in, and how you let the customer know. A live stock list of medicines is not the answer. Which products can be named on a public page at all differs by jurisdiction and by kind of product, and that is for the pharmacist in charge and counsel to decide.

The Business Profile's product listings are no place for that list either. Google's Business Profile guidelines, read on the day of writing, do not allow content related to regulated products in the in-store products a profile shows, and they name pharmaceuticals and health or medical devices among them. The way to ask about stock is the pharmacy's own: its phone, its message line, its counter.

Checking what answers say about one address

Put these facts into your panel as questions someone nearby would type: "pharmacy that delivers to [neighborhood] today", "pharmacy near [the station] where i can pick up a prescription by [5 pm]", "pharmacist who speaks [language] near [neighborhood]". Record whether each AI assistant's answer named you, whether the pickup time, the area and the hours it gave match your page for that day, and which page it cited, as measuring a pharmacy need by need lays out. A mismatch points to the page or listing that still carries an old time.

Common questions

Should our page say we are faster or friendlier than the alternatives?

No. A comparison is a claim about businesses you do not run, and nobody reading it can check it. State your own times and terms instead: when a prescription is ready, where you deliver, when a pharmacist is there and in which languages. A reader who is comparing can do the comparing, and your facts are the part of it you control.

Our delivery area changes by day. How do we state that?

As a small table on the delivery page: each day, the neighborhoods or postal codes covered, the cut-off and the window. In the markup, give each delivery round its own Service node with its own area and hours, so the days and the areas stay paired. Change the table and the markup together, on the day a round changes.

Do we publish the delivery charge?

Where the pharmacist in charge and your counsel are content for a price to appear, write it as a bracketed, dated figure beside the terms: "[charge] per delivery, no charge on orders over [amount], as of [date]." Keep it on the delivery page only, so a change happens in one place, and take it off old flyers the day it changes.

We have two locations. Whose facts go where?

Each location's page carries its own: its pickup times, its delivery area, its pharmacists and their days, its hours. The name stays the same everywhere, so the business reads as one entity, and each location is its own node in the markup, pointing back at the business, as the article on several locations sets out.

Sources

No figures are quoted on this page. The markup properties are schema.org's and the rules on doorway pages and profile products are Google's, linked where they are stated; the product line from the Business Profile guidelines was read on the page on the day of writing. Every time, area and charge is a bracketed template, and the page compares the pharmacy with no one.

Sources: schema.org, Service · schema.org, areaServed · schema.org, Person · schema.org, Certification · Google Search Central, spam policies · Google Business Profile guidelines

All articles