WordPress Timezone Setting: Why Your Bookings Drift an Hour Twice a Year

The instructor was parked outside the pupil's house at nine, because that is what the phone calendar said. Ten o'clock was when the pupil came out, because that is what the booking confirmation said. Both had come from the same website.

That scene is a composite, not one customer's story, but we see versions of it every spring and every autumn. Call the business a driving school in Roscommon: one instructor, one car, lessons booked online through a WordPress booking plugin that syncs to Google Calendar. Back in April the owner noticed that lessons in the synced calendar did not match the times in the confirmation emails. A helpful nephew went into Settings, saw "UTC+0", changed it to "UTC+1", and the problem went away. Everyone forgot about it.

On Sunday 25 October, at 2am, the clocks go back. The website will not notice. It will carry on running an hour ahead of every clock in the country until somebody works out why customers keep arriving at the wrong time. I want to walk through that story properly, because the fix takes about two minutes and the failure can cost a business a week of confused appointments, refunds and apologies.

One Dropdown, Two Kinds of Answer

Every WordPress site has a single setting that decides what time it thinks it is. You will find it under Settings, then General, then Timezone. The dropdown offers two very different kinds of answer, and most people do not realise they are different.

The first kind is a city. Europe, then Dublin. When you pick a city, WordPress uses the official timezone rules for that place, including the dates the clocks change. It moves forward in March and back in October on its own, every year, with nobody touching it. The second kind is a fixed UTC offset: UTC+0, UTC+1 and so on. These do exactly what they say. A fixed offset is a number, not a place, and a number does not know that Ireland changes its clocks twice a year.

WordPress's own documentation is clear about which one it wants you to use. The official guide to the General Settings screen says to choose a city in the same timezone as you, and only fall back to a GMT offset if you cannot find one ^[3]. Most site owners never read that page. They never had a reason to.

Why so many sites start on the wrong one

A fresh WordPress install in US English does not ask where you are. In the WordPress core source code, the default timezone for that language is set to an offset of zero, which shows in the dashboard as UTC+0 ^[4]. Some translated versions ship with a city instead, but plenty of Irish sites are installed in US English, by developers, plugins or one-click installers that never revisit the setting.

So the site starts life on UTC+0. In winter, that happens to match Irish time, because from late October to late March we are on Greenwich Mean Time. Everything looks right. Then the clocks go forward at the end of March and the site quietly falls an hour behind for seven months.

What Actually Runs on Your Website's Clock

This is the part that turns a settings quirk into a business problem. The timezone is not cosmetic. Plugins read it to decide when things happen. When it is wrong, the consequences land in places owners do not expect.

• Booking and appointment plugins. Available slots, confirmation emails and reminder emails are calculated from the site clock. WooCommerce's own documentation for its Bookings extension states that, from version 3.6.0, booking events always follow your site's configured timezone ^[5]. Correct timezone, correct appointments. Wrong timezone, every reminder lands an hour adrift.
• Calendar sync. When a booking is pushed to Google Calendar or Outlook, it travels as an exact moment in universal time. Your phone then converts that moment into Irish time correctly. If the website mislabelled the moment in the first place, your phone faithfully shows the wrong hour. That is the driving school story in one sentence.
• Scheduled sales and offers. WooCommerce reads sale start and end dates in your site's timezone. Set a Black Friday offer to end at midnight on a site running on the wrong offset and it ends at 11pm, or runs until 1am, depending on which way the error goes.
• Scheduled posts and announcements. Blog posts, holiday opening notices and event pages set to publish at a given time will deploy an hour early or late.
• Order timestamps. "Order before 2pm for same-day dispatch" means nothing if the order record says 1.15pm when the customer actually ordered at 2.15pm. Disputes start with timestamps.
• "Open now" badges and opening-hours widgets. These compare your published hours against the site clock, not the customer's phone.

None of this throws an error. Nothing turns red in the dashboard. The site works perfectly; it just works on the wrong time. In operations terms, that is the worst kind of fault: silent, plausible, and discovered by customers rather than by monitoring.

Back to the Driving School: Why the Fix Made It Worse

Return to that April conversation. The site was on UTC+0, it was summer, and Irish time was UTC+1. Changing the setting to UTC+1 genuinely fixed the symptom. Bookings lined up, the calendar agreed, the owner moved on. What it actually did was swap one fixed number for another. From 2am on 25 October, Ireland goes back to UTC+0 and the website stays on UTC+1. The error has not gone away. It has flipped direction and gone to sleep for six months.

There is a small irony in this that I enjoy more than I probably should. Under the Standard Time (Amendment) Act 1971, the period from late October to March is legally defined as "winter time", during which the time in the State is Greenwich Mean Time ^[2]. Irish law treats summer time as the standard and winter as the exception. WordPress, of course, has no opinion on Irish statute. It just needs to be told the right city.

It is an easy mistake to make, and operations teams are not immune to it. A clock that is verified in July and set to a fixed offset passes every check until the first Monday of winter, when scheduled jobs start firing an hour out. That is why every timezone check we run asks two questions: is the time right today, and will it still be right after the next change?

Will the Clocks Ever Stop Changing?

Owners sometimes ask whether this is worth fixing at all, given the talk about Europe abolishing clock changes. Short answer: yes, fix it.

The European Parliament voted in 2019 to end seasonal time changes, but according to Citizens Information, EU institutions have made no progress implementing that decision, the European Commission has said it does not plan to submit a new proposal, and no changes are expected to summer and winter time in the coming years ^[1]. Irish clocks go forward on the last Sunday of March and back on the last Sunday of October, as they have for decades ^[1].

Even if that changed tomorrow, a city setting would still be the right answer. When a country changes its timezone rules, the shared timezone database used by PHP and WordPress is updated to match, and a site set to Dublin picks up the new rules through routine software updates. A site set to a bare number does not.

How to Verify and Correct the Setting

This takes minutes. Do it on a quiet morning, not at the end of a busy day.

1. Verify the current setting. In your WordPress dashboard, open Settings, then General, and look at the Timezone field. If it shows anything starting with "UTC", it is a fixed offset.
2. Select the city. Change it to Dublin, which sits under the Europe section of the list. Save the changes.
3. Verify the local time. Below the dropdown, WordPress displays the Universal time and the Local time. The Local time should match the clock on your wall to the minute.
4. Verify the plugins that keep their own clock. Some booking, events and shop plugins have a separate timezone or "use site timezone" option in their own settings. Open each one and confirm it follows the site setting or is also set to Dublin.
5. Run one test booking. Make a booking for next week, then confirm the time in the customer email, the admin email and your synced calendar all agree. Cancel it afterwards.

If your site takes real bookings or orders, make the change in a staging environment first, because some plugins behave differently when the clock moves underneath them. Our guide to using a staging environment to protect your production site covers how to test a change like this without customers seeing the half-finished version. And if your site is new, add the timezone to the list of first things to configure after your AI website builder creates your site, alongside your contact details and opening hours.

The limitation you need to know about

Changing the setting fixes the future. It does not always fix the past.

Some booking plugins store each appointment as a local time label, not as an exact moment. When you correct the timezone, bookings made under the old wrong setting may suddenly display an hour out, even though they were showing correctly a minute ago. Others convert everything properly. You will not know which kind you have until you look.

So after the change, open the bookings list and verify every upcoming appointment, paying particular attention to anything booked in summer for a date after 25 October. If any have moved, contact those customers directly to confirm the time. A slightly awkward phone call, yes. Much less awkward than a customer standing outside a closed door.

When a Wrong Clock Actually Costs You

Not every website is affected equally. If your site is a brochure with a phone number and your bookings come in by phone, a wrong timezone mainly affects post dates and the occasional scheduled notice. Annoying, not serious.

Appointment-based services feel it hardest. Clinics, salons, instructors and consultants live on their diaries, and a one-hour error means missed sessions, double bookings and customers who quietly stop trusting your booking system. Online shops running timed offers come next: a sale that ends early produces complaints, while one that runs late gives away margin you never intended to. Hospitality is the third group, because table reservations and collection slots are time-critical and the people affected are usually standing in front of you when it goes wrong.

There is an honest concession here too. If your appointments run entirely through a dedicated hosted booking service that manages its own timezone, and your website simply links out to it, that service is doing the timekeeping. For a single-chair salon happy with that arrangement, it is a perfectly reasonable setup, and the WordPress setting matters far less. You pay for it in other ways, such as monthly fees and customer data living on someone else's platform, but the clock is their problem.

Where Your Host Fits In

Most servers run on universal time. That is deliberate and correct: servers should not change their clocks twice a year. WordPress then converts that universal time into your local time using the setting you have just checked. Keeping the underlying clock accurate is the host's job. The timezone setting is yours.

What a good host gives you is the ability to make a change like this safely, and someone to call if it goes sideways. Before you touch a setting that booking and payment plugins depend on, you want a fresh backup and a rollback path. You want a staging copy so you can verify the booking flow before you deploy the change to production. And you want to ring a support team in the same timezone as you, because a timezone question asked at 9am Irish time should not wait for a team eight hours away.

That is how Web60 is set up. Every site is full WordPress, so the timezone dropdown, the booking plugin settings and everything else in this article are in your hands from day one. Automatic nightly backups and on-demand manual backups mean you can take a restore point before changing anything, and one-click staging lets you verify the change before it reaches customers. Support comes from a real Irish-based team, and all of it is included in €60 a year. If you are setting up a new site, you can see how a Web60 site is built from a plain description of your business and then work through this check as part of your launch.

The Two-Minute Job Worth Doing This Month

You have until 2am on Sunday 25 October. Open Settings, then General. If the Timezone field says UTC anything, change it to Dublin, verify the local time matches your wall clock, and check your upcoming bookings.

Then the clocks can do whatever they like, in October, in March, or in whatever year Europe finally makes up its mind, and your website will keep the same time as your customers.

Frequently Asked Questions

Does WordPress automatically change the time when the clocks go back?

Only when your timezone is set to a city. If Settings, then General, then Timezone shows Dublin, WordPress adjusts automatically on the last Sunday of March and the last Sunday of October. If it shows a fixed offset such as UTC+0 or UTC+1, it never adjusts, and the site will be an hour out for half of every year.

Which timezone should an Irish business choose in WordPress?

Choose Dublin, listed under the Europe section of the dropdown. It follows Irish time all year, including the switch between Irish Standard Time in summer and Greenwich Mean Time in winter. Avoid the UTC offset options at the bottom of the list, even if one happens to show the correct time today.

Why are my booking confirmation emails an hour out?

The most common cause is a site timezone set to a fixed UTC offset rather than a city, so it drifts by an hour when the clocks change. A second cause is a booking plugin with its own separate timezone setting. Verify both, then make a test booking and confirm the customer email, admin email and synced calendar all show the same time.

Will changing the timezone affect bookings I already have?

It can. Some plugins store appointment times in a way that shifts when the site timezone changes, while others convert them correctly. After making the change, review every upcoming booking, especially those made in summer for dates after 25 October, and contact any customer whose appointment appears to have moved.

When do the clocks go back in Ireland in 2026?

At 2am on Sunday 25 October 2026, when the time becomes 1am. They go forward again on the last Sunday of March. According to Citizens Information, no changes to this arrangement are expected in the coming years despite the 2019 European Parliament vote to end seasonal clock changes.

Is my website's timezone the same as my hosting server's time?

No. Servers generally keep their clocks on universal time all year, and WordPress converts that into your local time using its own timezone setting. Your host is responsible for keeping the server clock accurate; the WordPress timezone setting is something you control in the dashboard.

Sources