Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
SEO

Opening Hours Markup for 24x7 Emergency, OPD and Holiday Schedules

Model a 24-hour emergency desk, split OPD sessions and festival closures in openingHoursSpecification, and keep website, markup and Google Business Profile hours in agreement.

Opening Hours Markup for 24x7 Emergency, OPD and Holiday Schedules

Most hospital and clinic websites state their hours in at least four places: the footer, the contact page, the structured data and the Google Business Profile. Add the phone greeting and the reception desk, and you have six versions of the truth. They agree on an ordinary Tuesday. They stop agreeing on the first public holiday, the first festival week or the first time the emergency desk and the outpatient department keep different schedules.

This article is for the marketing or web lead of a clinic group or hospital who has to publish those hours once and keep them right. It covers how to model a 24-hour emergency desk, split OPD sessions and festival closures in openingHoursSpecification, and how to keep the website and the Business Profile from contradicting each other. It is a markup and process guide, not a clinical one: what the emergency service actually offers is for the hospital's clinical and operations leadership to state.

A patient who sees "Open 24 hours" in Maps and finds a closed OPD counter has a small, concrete reason to distrust everything else you publish. Fixing that is cheaper than most SEO work.

Start with one table, not with markup

Structured data is the last step. Before writing any JSON-LD, build a single hours register with one row per service point, not one row per building. A typical 200-bed hospital in Pune (hypothetical) has at least these:

Service pointPatternTypical trap
Emergency / casualtyEvery day, all hoursPublished as the hospital's hours, so OPD looks open at 3 a.m.
General OPDTwo sessions a day, closed SundayMarked up as one block from morning to evening
Specialty OPDVaries by consultant and weekdayCopied from last year's roster
PharmacyLonger than OPD, sometimes 24 hoursMissing entirely
Lab sample collectionEarly morning start, shorter on holidaysHours of the lab, not the collection counter
Appointment desk / call centreOffice hoursShown as the building's hours

Each row needs an owner who can change it and a date it was last confirmed. The register is the source for the page copy, the markup and the Business Profile. If a developer can edit the markup without touching the register, you will drift.

Decide early which hours the location has. For a hospital, the honest answer for the main entity is usually "the building is always open, individual services are not." Modelling the building with a narrow OPD window and then separately declaring an emergency department is the more accurate and the more readable option.

The core properties

Google's local business structured data documentation lists the properties it reads for hours: openingHoursSpecification containing dayOfWeek, opens, closes, and optionally validFrom and validThrough. The schema.org definition of OpeningHoursSpecification adds one rule worth remembering: if closes is earlier than opens, the range is assumed to run past midnight into the next day.

Three details from the Google documentation matter for healthcare:

  • All-day hours. To show 24-hour opening, set opens to 00:00 and closes to 23:59. Set both to 00:00 to show a day as closed.
  • Seasonal or one-off hours. Use validFrom and validThrough together. Google's own example is a winter closure expressed as opens and closes both 00:00 for a date range.
  • Departments. The documentation has a pattern for a business with several departments, each with its own name and hours. This is the pattern an emergency desk needs.

The schema.org vocabulary also has a simpler openingHours text property. Prefer the structured form. It handles split sessions and date ranges, and it is easier to generate from a register.

Modelling a 24-hour emergency desk

The mistake is to put the emergency hours on the hospital and let everything else inherit them. Instead:

  1. Give the hospital entity (Hospital, or MedicalClinic for a smaller site) the hours of the general outpatient service, or no hours at all if it has no single meaningful pattern.
  2. Declare the emergency service as a department with its own name (for example "Emergency Department"), its own telephone and its own openingHoursSpecification.
  3. For the emergency department, list dayOfWeek as all seven days, opens 00:00, closes 23:59. One object with an array of days is enough.

Two cautions. First, only declare 24-hour emergency opening if the service genuinely operates that way at that location; a clinic that is "open for emergencies by phone" is not a casualty department, and the clinical team should agree the wording on the page. Second, do not use markup to make claims the page does not make. Google's general structured data guidelines say markup must represent content visible to the user. The emergency hours should appear as text on the page, near an emergency phone number, before they appear in JSON-LD.

Modelling split OPD sessions

Many Indian OPDs run a morning and an evening session with a closed gap in between. Express each session as its own object and repeat the weekday:

  • Monday to Saturday, 09:00 to 13:00
  • Monday to Saturday, 16:00 to 19:00

Do not collapse these to 09:00 to 19:00, which tells patients the counter is open at 2 p.m. When Sunday has a reduced session, give it a separate object rather than appending it to the weekday array.

If different departments run different sessions, a single location-level block cannot be right. Use department entries, one per OPD specialty block that has distinct hours, and keep the location-level hours to the front desk or leave them off. A three-line department list that is correct beats a forty-line list that is half stale.

For consultants who visit on fixed days, resist the urge to encode their rota as the clinic's hours. Doctor availability belongs on the doctor's page and in the booking system; a Business Profile and a LocalBusiness block describe the place.

Want this applied to your practice? Get a free seo audit.

Book my free audit

Modelling festival and holiday closures

Holiday exceptions are where most of the contradictions begin. Google's documentation describes a date-bounded object: the same opens and closes of 00:00 mean closed, and validFrom and validThrough give the range. Use that for the OPD or the clinic as a whole.

Rules that prevent trouble:

  • Scope the closure. Diwali closing the OPD does not close the emergency department. Put the exception on the department that is affected, not on the entity as a whole.
  • Dates move. Several Indian festivals follow lunar calendars, and regional holidays differ by state. Keep a holiday calendar per location, owned by someone in operations, and agree the dates with the facility head, not from a generic list.
  • Expire exceptions. A validThrough date in the past is clutter at best. Remove exceptions once they have passed, and make that part of the monthly check.
  • Publish early enough. Patients plan around the week before. Putting a visible notice on the location page and the booking flow matters more than the markup.

In a markup test, a date range that appears to include the last day as closed can behave differently depending on whether validThrough is read as inclusive. The schema.org definition says the item is not valid after that date, so a range ending on the final closed day is the natural reading. Validate with a date that falls on the boundary and confirm what the tool and the Business Profile show.

Keep the Business Profile in agreement

Google Business Profile has its own hours model. The Business Profile help page on editing business information describes regular hours, special hours for holidays, and more hours for features that run on a different schedule from the main business. Use them as follows:

  • Regular hours match the register's default pattern for the location.
  • Special hours are entered for every date in the holiday calendar, on the same day you publish the website notice.
  • More hours is the place for a service that runs on a different timetable, where it is available for your category. Check which options your category offers rather than assuming.

The Business Profile and the website are separate systems, and Google does not promise to reconcile them. When they differ, patients see whichever surface they landed on, and your phone line takes the call. Our guide on Business Profile booking links deals with the equivalent problem for appointment URLs, and the Business Profile service page covers the wider profile set-up. For groups with many sites, the multi-location SEO work is mostly about enforcing exactly this single-register discipline.

An audit you can run on your own site

You do not need a client dataset to find these errors. This is the method.

  1. Extract. Crawl your location and department pages and pull every openingHoursSpecification block, plus the visible hours text. Any crawler that can render JavaScript and export structured data will do.
  2. Normalise. Convert both into rows of location, service, weekday, opens, closes, valid from, valid through.
  3. Compare to the register. Flag three classes of error: markup that differs from the register, visible text that differs from the markup, and pages with no hours at all.
  4. Compare to the profile. Export hours and special hours from each Business Profile and diff them against the register in the same format.
  5. Add Search Console context. In the Performance report, filter queries containing words such as "emergency", "24 hours", "open now" and "open on Sunday". Note which pages receive them. Those pages carry the highest cost of being wrong, so fix them first.
  6. Check the exceptions. List every validThrough date and mark those already in the past.

Do not read much into a single export. What you are looking for is the pattern of where the contradictions occur: a particular template, a particular location manager, or a plugin that writes its own markup. That tells you whether the fix is a template change or a process change.

Failure modes to look for

  • Two sources of markup. The theme outputs one block and an SEO plugin outputs another, each with different hours. Check the rendered page, not the template.
  • The 23:59 problem. Teams sometimes publish 00:00 to 24:00 or 00:00 to 00:00 for 24-hour opening. Per Google's documentation, 00:00 to 00:00 means closed. Use 23:59 for the close.
  • Timezone and format. Use 24-hour HH:MM times without a timezone offset for a single-timezone India location, and keep the format consistent across the site.
  • Phone IVR out of sync. The recorded greeting still says the old Saturday closing time. It is not SEO, but it is the same error.
  • Copy-paste across branches. A new branch inherits the flagship's holiday list.

Checklist before you publish

  • One hours register, one owner per location, with a confirmed date.
  • Emergency desk declared as a department only where the service genuinely runs 24 hours, with visible matching text.
  • Split sessions as separate objects, not one long block.
  • Holiday closures scoped to the affected department, with real dates and an expiry plan.
  • Business Profile regular, special and more-hours entries matched to the register.
  • A monthly diff of site markup, visible text and profile hours.
  • Markup validated with the Rich Results Test and re-checked after any theme or plugin update.

The register is also what keeps NAP consistency intact across listings. It is the real deliverable. Once it exists, the markup is a build step rather than a recurring editing job, and the contradictions stop at the source.

Filed underopeningHoursSpecificationhospital opening hours schemaemergency 24 hours schema markupopening hours markup clinicgoogle business profile special hoursholiday hours structured data

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free seo audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to opening hours markup for 24x7 emergency opd and holiday.

Explore client work →