Holiday hours on Google disagree with your location page
Reconcile holiday hours across a location page, LocalBusiness markup, and Google Business Profile, including closed days and branches with different hours.
By Crawlito · 5 min read
In short
- Special hours in Google Business Profile can describe temporary changes without rewriting weekly hours.
- A dated exception on a location page needs the branch, local date, and actual hours.
- Google documents dated openingHoursSpecification entries for seasonal hours on the website.
On this page
- Identify the branch and the service that really changed
- Update the business profile and the public branch page
- Express a dated exception in the branch markup
- Verify it from the customer's starting point
- Test an exception at the local midnight boundary
- Frequently asked questions
- Inspect one affected branch
When Google Maps and your website disagree about holiday hours, work on the individual location, the individual date, and the kind of service the customer wants. Update special hours in the correct Google Business Profile and publish the same verified exception on the branch page. Check the visible schedule and its structured data after the update. Google Business Profile’s special hours instructions
Identify the branch and the service that really changed
Ask an operational question before editing the listing: if someone arrives at the address at four in the afternoon on the holiday, can they get the service named on the page? A showroom can close early while a pickup desk remains open. A telephone line can stay open after the building closes. A single unqualified time copied into every system can describe all of those services incorrectly.
Create a small exception record with the branch identifier, public name, street or district, local date, normal hours, exception hours, and the person who confirmed them. Use a location-specific identifier already used by the branch directory. A shared trading name makes it easy to edit a sibling branch on the opposite side of a city. When operations supplies a spreadsheet, verify whether blank means closed, standard hours, or awaiting confirmation.
Write the actual date for each affected year. A local holiday changes weekday from year to year, and a school-break schedule may be set by a regional office. A banner that only says “Closed Monday” can remain on a cached page long after anyone remembers which Monday it referred to. Give the customer a full date and, when helpful, the next opening time at that location.
Update the business profile and the public branch page
Google's special hours feature can handle a temporary change without replacing the ordinary weekly schedule. Open the profile for the affected address and verify the business name and location before saving. Review the separate guidance for longer closures and for businesses with other service hours if those cases apply. The feature has documented limits, so check the help page against the closure you actually need to represent.
On the website, place the exception near the normal hours on the individual branch page. If you also publish a regional announcement, link it to the affected branches and distinguish those following their normal hours. A customer arriving directly from search on the branch URL may never visit the regional article or homepage banner. The guide to local service pages explains how to make location facts understandable at their point of use.
An example for a fictional shop could read “Riverside showroom, December 24: open 09:00–13:00 local time. December 25: closed. The service desk follows its usual hours on December 26.” Replace this example with your confirmed schedule and name the service if different departments keep different hours. Avoid an image-only announcement. Ordinary text can be read, copied, searched, or spoken by a device as part of the location page.
Express a dated exception in the branch markup
Google's LocalBusiness documentation shows seasonal periods using openingHoursSpecification with validFrom and validThrough. Its example for a closure sets opens and closes to 00:00. Below is a fragment for one closed day to merge into the existing location entity. It describes a fictional date and belongs alongside the maintained weekly data. Google’s LocalBusiness structured data guide
{
"@type": "OpeningHoursSpecification",
"validFrom": "2026-12-25",
"validThrough": "2026-12-25",
"opens": "00:00",
"closes": "00:00"
}Inspect which branch owns the entity in the public output. A schema block that identifies the head office while showing a local shop's hours creates an ambiguous record. Branch name, address, page URL, and visible schedule should describe the same establishment. If several locations share a template, populate the exception from the selected branch record rather than a global marketing field. See how organization and local entities fit together.
For early closure, use the actual local opening and closing times for the dated interval. Test the dates immediately before and after the exception as well as the exception itself. A template that overwrites normal hours instead of adding the limited exception can leave the shop shown as closed every Friday for the rest of the year. Inspect the fully generated graph and check the public display at those boundaries.
Verify it from the customer's starting point
Start from the maps listing for the branch and follow its website link. Confirm that it lands on the correct address. Then start from the site's location directory and follow the reverse path. Compare hours for a normal day, the holiday, and the first normal day afterward. Check both phone and desktop layouts, since a compact “Today” panel can read from a separate schedule component while the full table is correct.
If a discrepancy remains, identify the two surfaces that disagree and the time of your inspection. For example, the branch page and its HTML data may have the new closing time while the profile still shows ordinary hours. That points to the profile update or its current display state. If the page is wrong in both mobile and desktop while the profile is right, check the website's data source and any cached branch page. The CDN freshness guide helps trace an old response to its serving layer.
Save a small dated record for the next holiday. Include an unaffected neighboring branch so future changes prove that the exception stays local. A customer trying to collect an order cares about a single reliable answer. A short public note explaining an unusual service arrangement does more for that person than a technically valid schedule with an unexplained exception.
Test an exception at the local midnight boundary
Suppose a business manages stores in two timezones from one scheduling system. Shortly after midnight at headquarters, a western branch still has several hours left in the previous local day. If its page uses the server's calendar date for the “Open today” panel, it can show the holiday closure a day early for customers browsing that branch. A static list of dates farther down the page may still look entirely correct.
In a preview or deterministic component test, compare the same instant at headquarters and at the affected location. Check the last hours of the local day before the exception, the first hours of the exception, and the first day after it ends. Keep the location's timezone alongside its schedule in the test data. For an overnight service, ask the operations team which calendar day owns the part of the shift after midnight. Translate that answer into visible wording someone arriving late at night can understand.
Frequently asked questions
Must we change normal weekly hours for a single holiday?
Use the special hours feature for a temporary exception that fits Google's documented conditions. Preserve the ordinary schedule for unaffected dates.
Will changing website markup immediately update Maps?
The public website and the business profile are separate surfaces. Check each directly and record what it currently displays.
What if all locations share the same holiday closure?
You can maintain a common schedule internally. Confirm that it applies to every listed branch and publish the correct dated information at each customer entry point.
Inspect one affected branch
Run the free page check on the individual location page after publishing the holiday schedule. Use the visible branch name and date to confirm you tested the right URL.
Filed under Structure and schema. Topics: local-seo, structured-data, google