Estimated reading time : 2 min · Published October 4, 2026
Define hours for each service
Separate venue opening, telephone reception, delivery and appointments. Online booking at any time does not imply continuous reception. Show breaks as two distinct time ranges; explain access conditions without making visitors guess what is open.
For each location, record the time zone, validity period and person who confirms the hours. A period crossing midnight should be understood from the starting day into the next day. Ask someone unfamiliar with the organization to review that example.
Treat exceptions as dated data
Record exact dates for closures or shorter opening hours and the planned reopening date. Avoid wording such as ‘closed tomorrow’, which quickly becomes inaccurate. A public holiday does not establish whether a place is open: ask the responsible person to confirm.
Schema.org distinguishes normal hours from dated exceptions through specialOpeningHoursSpecification. Google Business Profile also supports special hours. The website, structured data and platforms should describe the same verified situation, without blindly copying an old calendar.
Synchronize and check published versions
Keep hours in shared data when the system allows; translate explanations, not the actual calendar. Spell out the month if a numeric date could be misunderstood. Schedule a check after each exception ends to remove outdated notices.
Test a normal day, a break, a closure and reopening. Check location pages, contacts, booking links and mobile versions. When a time remains uncertain, offer a confirmation contact instead of calculating an ‘open’ status from incomplete data.
Reference documents
Content updated on October 4, 2026
