Clean Hours Markup Takes One Format and One Source
-
Your website can tell Google exactly when you are open. Opening hours schema is a short block of hidden code that lists each day and time, so Google does not have to guess from the words on your page.
-
Times and day names must follow a strict pattern. Full day names and 24-hour times work. Entries like “9am” or “Mon-Fri” do not.
-
Your website and your Google listing should show the same hours. When they disagree, customers see the wrong answer and Google sees a mismatch.
-
One-day changes belong in your Google listing. Holiday closures are quicker to set there and easier to take down afterward.
It is a Saturday morning in Winter Park. Someone searches for your shop, sees the word “closed,” and drives to the next result. Your doors were open the whole time, but the hours Google found said otherwise.
Hours are a small detail with an outsized effect, and the code that carries them is easy to get wrong. Schema markup (structured data, a way of labeling facts on a page so search engines can read them) has a dedicated field for hours, and Google has firm expectations for how it is filled in.
This article settles what a correct entry contains, which mistakes break it, and how to keep your website and your Google Business Profile telling the same story.
Which Schema Fields Does a Local Business Need for Hours?
The Short Answer
A local business marks up opening hours with the OpeningHoursSpecification type inside its LocalBusiness schema. Each entry names the days using full day names and gives opening and closing times in 24-hour format. Days that share hours can be grouped into one entry, and the hours must match what visitors see on the page.
The Fields Inside Each Entry
A clean entry is short. You can supply a single block or a list of them, and each one draws on the same few pieces.
Every hours entry in your LocalBusiness schema uses these fields:
-
dayOfWeek names the day or days the entry covers, written as full names such as Monday
-
opens gives the opening time in 24-hour format, such as 11:30
-
closes gives the closing time in the same format
-
validFrom is an optional start date, written year first, for seasonal hours
-
validThrough is an optional end date in the same format
Schema.org, the shared vocabulary behind this markup, defines the same five fields. Google Search Central, Google’s documentation site for search, lists the hours property as recommended but optional, and notes that opens and closes follow an hour, minute and second pattern, although its own examples use hour and minute only. Leave out both date fields and the hours apply all year.
Patterns for Late Nights and Closed Days
Say a florist in Winter Park opens Monday through Friday from 09:00 to 17:00 and Saturday from 10:00 to 14:00. That schedule needs two entries: one listing the five weekdays with one pair of times, and one listing Saturday with another. Sunday gets no entry, which reads as closed, or you can add one that sets opens and closes to 00:00 to say so plainly. Either way, the times are written the same year-round.
Most shops group days. A salon in Lake Mary might cover the weekdays in one entry and the weekend in a second, which beats writing seven.
Google documents three special cases. A late-night business uses a single entry where the closing time is earlier than the opening time, such as opening at 18:00 and closing at 03:00 on Saturday. A business open around the clock sets opens to 00:00 and closes to 23:59. A closed day sets both opens and closes to 00:00.
Schema.org itself has no separate closed field. A day with no opening time reads as closed, and a closing time earlier than the opening time is read as running into the next day.
Formatting Mistakes That Break Hours
A schema validation analysis by J.A. Watte, published in September 2026, flags the entries that leave Google with unusable hours:
-
Times written as “9am,” “9:00” or “9:00 AM” in place of 09:00
-
Day values such as “Mon” or “Mon-Fri” where full day names belong
-
An opening time with no closing time, or the reverse
-
Hours squeezed into one text string when a full entry would work
-
Hours that appear in the code but nowhere on the visible page
These errors share one cause: the value makes sense to a human reader but means nothing to a program. According to the same analysis, a value like “9am” is not a usable time, so the hours on the page add nothing to what Search or an assistant displays. The page can look perfect to a visitor while the code says nothing useful.
Google Search Central recommends checking local business markup with its Rich Results Test. Fix every critical error it reports. Google says the non-critical ones are optional for rich result eligibility.
How Do You Keep Site and Profile Hours in Sync?
Pick One Source of Truth
Google defines Business Profile hours as your regular customer-facing hours of operation, meaning the times when someone can reach you in person or by phone. According to BrightLocal, an agency that tracks local listings, those regular hours drive the open or closed label searchers see.
Write the same hours into your markup. Google Search Central’s guidelines state that structured data must be a true representation of the page content, and that you should not mark up content visitors cannot see. The hours in your code, the hours printed on your contact page and the hours in your profile should all agree, whether your shop is in Maitland or Sanford.
Your profile has a weak spot that your own code cannot fix. BrightLocal reports that Google may pull hours from third-party sites such as Yelp and Facebook and can accept outside edits, and that a correction can take several days to publish. Check those listings whenever your schedule changes.
When your schedule changes, update every place that shows it:
-
The hours printed on your contact page
-
The hours in your site footer or header
-
The hours inside your structured data
-
Your Google Business Profile
-
Third-party listings such as Yelp and Facebook
The cleanest hours markup is the one that says exactly what your website and your Google listing already say.
Where Holiday Hours Belong
Holiday hours, one-off closures and event days change too often to hard-code. Google’s documentation does allow validFrom and validThrough for a seasonal closure, so a long seasonal schedule can live in your markup. Short changes are easier to manage as special hours in Google Business Profile.
For a holiday closure in your listing, work through these steps in order:
-
Confirm your regular hours are set, because special hours cannot be added without them
-
Add the special date and enter the closure or the changed hours
-
Use special hours for closures of up to six consecutive days
-
Mark the business temporarily closed for seven days or more
When This Advice Falls Short
Markup cannot rescue a profile that carries wrong hours, and Google lists the hours property as optional, so a page without it is not broken. If answering the phone after closing is your habit, remember that Google’s definition covers only regular customer-facing hours.
Test again after every template or plugin update. Page edits can quietly change what the code prints. Rerunning the Rich Results Test takes a minute and catches a broken entry before a customer in Altamonte Springs or Kissimmee finds the wrong hours.
Some sites print hours from a template or plugin, which makes the code harder to inspect. Our web development team can confirm what the page outputs, and our technical search engine optimization service lists structured data implementation among its possible technical work. For a business in Oviedo or elsewhere in Seminole County FL, ongoing site maintenance keeps hours current after changes.
Back to that Saturday in Winter Park: with matching hours in the markup, on the page and in the profile, the searcher sees that you are open, and the next stop is your door in Orlando or anywhere else across Central Florida.
Get Your Hours Markup Checked
Our team can compare your site code, your page and your profile and point out what needs fixing
External References
-
Google Search Central, Google’s official documentation for search and structured data
-
Schema.org, the shared vocabulary that defines the OpeningHoursSpecification type



