“We are closed for the winter” – for beer gardens, ice cream parlors, country inns, campsites, boat rentals and farm cafés, this sentence is part of everyday life from November to March. The kitchen is cold, the chairs are stacked, the team is off or working elsewhere. It seems logical to put the website into hibernation as well: switch it off, reduce it to a single “Closed” page or block it for search engines so nobody shows up at a locked door. That is exactly what Google advises against. This article shows what happens technically when a site is switched off, which steps Google recommends instead and how an announcement bar, a popup, a countdown and an open request form carry your website through the break – so that it does not have to be found again when the season starts.
Why the off switch is the wrong answer
Google has published a dedicated guide on temporary closures in its documentation for site owners. It is written for online stores that cannot take orders for a while, which is why it talks about shopping carts, products and delivery times.
A seasonal business is in a different position: in winter it does not sell less, it sells nothing at all, and that is the plan. The principles still carry over, because they are less about the cart than about how Google treats a website that rests for a while. Where this article applies the recommendations to restaurants, campsites and leisure businesses, that is our own conclusion, not a statement by Google. The core message sits in the guide's FAQ: disabling a website completely, even if only for a few weeks, can have a negative effect on indexing (Google Search Central). Google describes taking down the entire site as a drastic step that should be used for a few days at most (Google Search Central). A winter closure does not last days, it lasts months.
Google adds a sentence that reads as if it were written for seasonal businesses: users may still want to find information about your products, services and company even when you are not selling anything right now (Google Search Central). For a seasonal business, take that literally. In winter, hardly anyone looks for a table for tonight, but many people look for something else: a gift card, a date for a wedding or a company outing next summer, a pitch during the spring holidays, the opening date of the season or a seasonal job. Anyone who lands on a dead address or an empty page during these weeks cannot tell whether the business is on a break or has closed for good. Google lists exactly this as the first consequence of a shutdown: customers do not know what is going on with the business if they can no longer find it online (Google Search Central). A beer garden that reopens in March wants its guests to know that in February.
What happens technically when you switch off
If you switch off the server for the winter or let the hosting lapse, visitors and crawlers get error messages instead of pages.
For server errors in the 5xx range, Google describes the process like this: its crawlers slow down crawling, and URLs that are already indexed are kept in the index for now but are eventually dropped (Google Crawling Infrastructure). At the same time, the robots.txt can no longer be reached. In that case, Google stops crawling the site for the first 12 hours and then uses the last successfully fetched version of the file for the following 30 days (Google Crawling Infrastructure). If the error persists beyond that and the site is generally unavailable, Google stops crawling and only checks for a new robots.txt from time to time. For a planned, short shutdown, Google names status code 503: if you absolutely have to disable the site for one or two days, return that code (Google Search Central). For longer periods, the guide describes a homepage that stays reachable with status code 200 as an indexable placeholder (Google Search Central). For a seasonal business, that is only a stopgap. The placeholder replaces the menu, pitch prices, directions and the page for private events – and with them the addresses guests search for in spring.
Scroll table sideways
| Step taken for the winter | What Google says about it | The better way |
|---|---|---|
| Switching off the server or hosting | With server errors, indexed URLs stay in the index for now and are eventually dropped (Google Crawling Infrastructure) | Keep the website online and announce the break |
| Deleting pages or blocking access | Status codes 403, 404 or 410 remove the site's URLs from Google Search (Google Search Central) | Hide sections, keep the pages |
| Setting every page to noindex | On the next crawl, Google drops the page from search results entirely (Google Search Central) | Leave indexing on the default |
| robots.txt disallows all crawling | The content and possibly the URLs disappear from Google Search (Google Search Central) | Leave robots.txt unchanged |
| Removals tool in Search Console | Works only temporarily, for about six months (Google Search Console Help) | Do not use it for a break |
| Limiting functionality, showing a notice | Recommended; it reduces the negative effect on the site's presence in Search (Google Search Central) | The approach of this article |
noindex deserves a closer look because it sounds harmless. Many people treat the rule as a sleep mode: the page stays reachable, it just does not show up in search, and in March you uncheck the box again. Google describes the effect more bluntly. As soon as Googlebot crawls the page and reads the rule, Google drops the page entirely from its search results (Google Search Central). It only returns to the index when the crawler visits again, and when that happens depends on how important the page is on the web: it can take several months before Googlebot revisits a page (Google Search Central). The URL Inspection tool in Search Console lets you request a recrawl, but it cannot force one. If you only remove the rule when the season starts, you open with a website that Google first has to collect again.
The removals tool is not a pause button
Stay online, limit only the functions
Google's recommendation for online stores comes down to a few steps: disable the cart, inform visitors with a banner or popup on all pages, update structured data to reflect the current situation and tell Google about the changes (Google Search Central). Applied to a seasonal business, this means: whatever does not work in winter is switched off or changed, everything else stays. The equivalent of a store's shopping cart is the table reservation for tonight or the booking for next weekend. It disappears or turns into an early booking request for next season. Menu, prices, directions, photos, the page for groups and private events and the FAQ stay where they are. If you manage the menu, offers or events as a collection, you change individual entries in spring instead of entire pages; the article Team, references, menu: managing content as a collection shows how that is set up.
- Reservations for today or this week: switch off and replace with a request form for dates from opening day
- Daily specials, weekly menu and events of the past season: hide them, do not delete them
- Opening hours: state the winter closure with both calendar dates and label the season hours as upcoming
- Menu or price list: keep it online, with a note that menu and prices will be updated for the new season
- Directions, parking, photos, the page for groups and events, FAQ: online and unchanged
- Contact: an address or a form that is actually read in winter, with an honest response time
- Gift cards: say how to order them if you sell gift cards during the winter
Announcement bar and popup: announce the break
The most important sentence of the winter break belongs where visitors cannot miss it.
XICflow offers the announcement block for this, which the documentation describes as a slim bar for an announcement with an optional link (XICflow documentation). It carries the text, a short keyword as a chip in front of it, a link text with a target and one of three color variants: brand, gold or neutral (XICflow documentation). All settings are listed in the overview of blocks for conversion and CTA. The bar is a block on the page where you place it. Because guests coming from search often land directly on the page with the menu, opening hours or directions and do not see the homepage at all, it belongs on the homepage and on the pages that get the most visits. If you have set up visitor analytics, they show which pages those are.
For a notice that should appear on every page, there is the popup in the brand and design area. According to the documentation, it shows a notice or a promotion on every page and visitors can close it at any time (XICflow documentation). You can choose between two display modes, a modal in the middle of the screen or “Banner (bottom)”, four triggers from “Immediately” to “On exit” and three frequency settings, including “Once per session” and “Only once” (XICflow documentation). For a winter closure, a banner at the bottom that appears after a short delay or on scroll and is shown once per session works well: it is there, but it covers less of the page than a window in the middle. Google explicitly recommends banners and popups for this kind of notice and mentions the HTML attribute data-nosnippet, which keeps the text of a banner from appearing as a snippet in search results (Google Search Central). For a winter closure, the sentence in the search result tends to help, because it answers the question before anyone picks up the phone. What else to consider for triggers and frequency is covered in Website popups: showing notices without disrupting visitors.
Announcement bar (homepage, opening hours, directions)
Keyword: Winter break
Text: Until Friday, March 26, 2027 – gift cards and
group requests still available
Link text: How to reach us in winter
Target: /en/contact/
Popup (Banner (bottom), trigger “On scroll”, once per session)
Title: We are closed for the winter
Text: We are back for you from Saturday, March 27, 2027.
We read requests for parties and groups in winter
too and usually reply within a week.
Button text: Request a date for 2027
Button URL: /en/groups/A countdown to the real opening day
In winter, guests no longer ask “Are you open today?” but “When do you open again?”. The countdown block answers that question where everyone can see it.
It has a title, a subtitle, the target date with a time and an expiry text; according to the documentation, once the time is reached the block shows the expiry text, and if that field is empty, the counter disappears (XICflow documentation). For opening day, this means: the target date is the first day of the season with the opening time, and the expiry text says that you are open now and when. Write this text before the countdown goes live, for example “We are open again: Tuesday to Sunday from 11 a.m.”. If the opening moves because of weather or renovation, change the target date and the announcement bar together and publish again. The documentation attaches a clear condition to the block: deadlines have to be real, and a countdown that starts over after it runs out is unlawful advertising (XICflow documentation). This reflects No. 7 of the annex to the German Act Against Unfair Competition: towards consumers, it is unlawful to falsely state that goods or services are available, generally or on particular terms, only for a very limited time in order to push for an immediate decision without leaving time and opportunity to make an informed choice (UWG). A countdown to opening day does not announce a time-limited offer, it states a date; what matters is that the date is correct. If you use the same counter for early-bird prices, the deadline has to be real and must not be quietly extended once it has passed.
Update opening hours and structured data
The opening hours block shows a table by weekday or period; a day without hours counts as closed, and you can add a note below the table (XICflow documentation).
The fields are described in the reference for grids and cards. For a winter closure, there are two clean options. Either the table keeps the season hours, gets the heading “Opening hours from March 27, 2027” and the closure period goes into the note. Or the table shows a single entry “November to March: winter break” during the closure, and the season hours follow in the note. The first option has an advantage: anyone planning an April outing in February sees the upcoming hours right away. The Café Nordlicht demo website among our demos shows what a dedicated opening hours page can look like; why hours should be maintained in one place only is explained in Keeping opening hours and availability reliably current.
The Google guide names a second place where opening hours appear: structured data. If a business has a physical location, it should update the local business structured data to reflect the current opening hours (Google Search Central). For seasonal hours, Google's documentation on local businesses provides the properties validFrom and validThrough; a day that is closed all day is marked by setting opens and closes to “00:00” (Google Search Central). According to Google, hours without validFrom and validThrough apply to the whole year. In XICflow, you enter such data per page under “SEO & meta” in the field for JSON-LD structured data; according to the documentation, this block is output in addition to the automatic data (XICflow documentation). If you already maintain opening hours there, adjust them for the break, otherwise the data for machines contradicts the announcement bar for people.
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "Your business name",
"url": "https://www.example.com/",
"address": {
"@type": "PostalAddress",
"streetAddress": "Street and number",
"postalCode": "Postal code",
"addressLocality": "Town",
"addressCountry": "DE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday",
"Friday", "Saturday", "Sunday"],
"opens": "00:00",
"closes": "00:00",
"validFrom": "2026-11-02",
"validThrough": "2027-03-26"
}
]
}Besides the website, your Google Business Profile shows opening hours in Search and Maps. The profile help is clear on this: if a business stays closed for more than seven days, during the off-season or for an indefinite period, it should be marked as temporarily closed (Google Business Profile Help). Google also points out that temporarily closed businesses may appear after open businesses for general searches (Google Business Profile Help). That makes it all the more important to switch the status back in time for opening day and to state the same period on the website and in the profile. How to keep both in line is described in Setting up and maintaining a Google Business Profile.
Hide instead of delete, use drafts with care
The third typical mistake is tidying up. In November, the page “Summer evenings by the lake” looks superfluous, so it gets deleted.
In XICflow, a deleted page disappears from the internet with the next publish; until then, it stays reachable at its address (XICflow documentation). After that, the address shows the error page for unknown addresses. For Google, URLs that are already indexed and return a status code in the 4xx range are removed from the index (Google Crawling Infrastructure). In June, the same page is back online and has to be found all over again. The better way is hiding: according to the documentation, a hidden section and a hidden block are not delivered, while the page itself remains (XICflow documentation). That way, the weekly menu, the summer event dates and the same-day reservation disappear without losing a single address.
A draft is not noindex – and noindex is not a break
With robots.txt, things are simpler than on many self-managed servers. Google warns against disallowing all crawling in robots.txt, because the site's content and possibly its URLs are then removed from Google Search (Google Search Central). In XICflow, the file is generated anew with every publish: according to the documentation, it allows search engines access and points to the sitemap, and the column for what you can influence says “nothing — the file is generated automatically” (XICflow documentation). You therefore cannot block search engines by accident through robots.txt. That explicitly does not apply to noindex and the draft status; there, what you set is what happens. Before you rebuild the website for winter, set a restore point: in the version history, “Save current state” creates a checkpoint with a short label such as “Summer season 2026”, and the history shows the 200 most recent entries (XICflow documentation). Restoring replaces the current content, saves the present state automatically beforehand and only goes live with the next publish; details are in Publishing and custom domains.
Use the break for requests
A winter break does not mean radio silence. For many seasonal businesses, winter is when the next season gets booked: weddings, company parties, club outings, school trips, pitches for the holidays.
The form block lets you put the fields together freely, from text and number to dropdown and consent, and a form can hold up to 40 custom fields (XICflow documentation). A group request needs only a few: the occasion as a dropdown, preferred date, alternative date, number of guests, name, email address and a field for special wishes. Submitted requests land in the requests area; if you wish, every new request is also sent by email to an address of your choice (XICflow documentation). How to explain the path from request to confirmation on the page is shown in Show your work process: steps that make requests easier.
Two settings deserve special care in winter. The first is the confirmation after submitting. According to the documentation, the ready-made contact form block confirms with “Message sent successfully.” and the line “We typically respond within one business day.” (XICflow documentation). During a winter closure, that is a promise nobody may be able to keep. Both form blocks have a field for your own text after submission; in winter, it states when you will actually reply. What such a text sounds like for a closure is shown in Business closure over Christmas: staying reachable, which covers the short break at the turn of the year. The second is retention: by default, requests are kept for 180 days and then deleted automatically, archived ones included (XICflow documentation). An early booking that arrives at the beginning of November is therefore no longer in the requests area in June. Transfer confirmed dates to your calendar or reservation book; the CSV export is there for your records.
Opening day itself is news your regulars want to hear. The newsletter block is a lightweight sign-up that lands as a request in your account; according to the documentation, the sending itself requires consent under the GDPR (XICflow documentation). German unfair competition law is strict here: advertising by email without the recipient's prior express consent is an unreasonable nuisance under Section 7(2) No. 2 UWG (UWG). The exception in Section 7(3) UWG is tied to four conditions that must all be met, including that the address was obtained in connection with the sale of goods or services and that the customer is told about the right to object both when the address is collected and every time it is used (UWG). An email address from a table reservation does not automatically meet these conditions. If you want to tell everyone in March, collect sign-ups from the fall through the block and say in the sign-up text what it is about: opening day, new menu, events. Because sign-ups are requests too and are deleted after 180 days by default, save them in good time with the CSV export (XICflow documentation). Separately, anyone who advertises on the basis of consent has to be able to prove it (GDPR). How a provable sign-up is set up is shown in Newsletter Signup: Double Opt-In Done Right.
The schedule up to opening day
- Last week of the season: create a checkpoint in the version history with “Save current state”, for example “Summer season 2026”
- Last day open: place the announcement bar on the homepage and the most visited pages, activate the popup as a bottom banner shown once per session, set the countdown with its expiry text to the first day of the season
- Same day: update the opening hours block and, if you use it, the JSON-LD with validFrom and validThrough, select “Temporarily closed” in the business profile, then publish
- Also at the start of the break: hide same-day reservations and summer dates instead of deleting them; add a form for groups and early bookings with an honest confirmation text
- During the winter: check requests regularly, transfer confirmed dates to your calendar or reservation book, save newsletter sign-ups and early bookings with the CSV export, prepare the new menu and prices in hidden sections
- A few weeks before opening: show the new menu and dates, prepare the message to your newsletter subscribers
- Opening day: remove the announcement bar and popup, switch the opening hours to the season, reset the JSON-LD and the profile status, publish and check the live version in the browser
If your website runs on XICflow, you handle everything that concerns the website in the Flow Builder, without touching a server: the announcement bar, countdown, opening hours, form and newsletter are blocks, the popup is a section under brand and design, and on publishing, the website is built as a static site and switched live atomically, so visitors do not see a half-finished state (XICflow). The features page gives an overview of the editor and delivery. The website of a seasonal business does not take a break in winter, it changes its job: it tells people when things start again, takes requests for next season and stays findable where guests search in spring.