Seasonal hours change control for local profiles is the process that publishes holiday, event, and temporary hours to Google Business Profile, Apple Maps, Bing Places, and other local place cards — then verifies the public result — without leaving stale "Open now" signals. It is a core local listing management / local listings management workflow. Definition hub: What is local listing management?.
This page is change-control for hours — not a full definition and not a software comparison.
Why hours break local discovery
Customers trust maps for "open now." Wrong holiday hours create wasted trips and bad reviews. Google documents how to edit business hours and special hours. Representation guidelines still require that public facts match the real-world location.
Seasonal mistakes usually come from process gaps: POS calendars update, but place cards do not; one market publishes special hours and another does not; temporary closures never get reversed.
Change-control checklist
- Source of truth — one approved hours calendar per location (regular + special + temporary closed).
- Cut-off — publish special hours at least several days before the holiday when the publisher allows scheduled changes.
- Tier 1 first — Google, Apple Maps, Bing Places before long-tail directories (publisher priority).
- Named publisher — who clicks publish (see local listing management RACI).
- Verify — open the public place card the next day; screenshot or ticket the proof (QA evidence).
- Revert — calendar reminder to clear temporary closures and restore regular hours.
Regular vs special vs temporary closed
| Type | Use when | Risk if skipped |
|---|---|---|
| Regular hours | Default weekly schedule | Baseline "open now" wrong all year |
| Special hours | Holidays / one-off dates | Maps show open on closed days |
| Temporary closed | Short operational shutdown | Customers arrive; reviews follow |
| Permanently closed | Location ends | Use open/move/close playbook instead |
For permanent exits or address changes, use Open, move, and close playbook for local listings.
Multi-location pattern
Run one brand calendar template, then location exceptions. Corporate remains Accountable for the template; locations are Responsible for exception requests. Do not let each store invent keyword-stuffed holiday names on Google.
Related reading (local cluster)
- What is local listing management?
- Local listing management RACI for multi-location teams
- Local listing change QA evidence standard
- Local listing management publisher priority checklist
- Sibling term: What is business listing management?
Frequently asked questions
Do we need special hours on every directory?
Prioritize local-intent surfaces customers use for nearby discovery. Tier 1 maps first; long-tail directories after.
Is this the same as NAP consistency?
No. NAP is identity. Hours are operational availability. Both belong in local listing management, but hours change more often and need their own control loop.