Web60 Features
What Your Website Backup Does Not Include, and Where Those Pieces Actually Live

A website backup is a removal van for the contents of one building. Everything inside the walls travels with it: the furniture, the filing cabinets, the photographs on the wall. What it cannot carry is the lease, the electricity account, the post redirected to another address, or the spare key a former manager still has in a coat pocket.
Most owners only discover where the walls are on the day they press restore. The site comes back, the homepage looks right, and then something that was never inside the building fails. Payments are declined at checkout. The booking calendar is empty. Search Console says you no longer own your own website.
This article is a map of those edges. It sets out what a WordPress backup genuinely contains, every common piece that lives somewhere else, what a restore does to each one, and a short routine for keeping the outside pieces under your control. Keep it somewhere you can find it. It is meant to be used, not read once.
What a WordPress Backup Actually Contains
WordPress's own administration handbook is precise about this. A backup has two parts, the database and the files, and you need both to fully restore a typical site [1]. In business terms, that covers:
- The database. Every page and blog post, every product and price, WooCommerce orders and customer accounts up to the moment the backup ran, user logins, and the settings for your theme and plugins.
- The files. WordPress itself, your theme, your plugins, and every photo, PDF and menu you have uploaded.
That is a lot. For most sites it is the part that took longest to build and would hurt most to lose, which is why it gets most of the attention in any complete guide to WordPress security and backups. A site with no backup at all means rebuilding every page from memory and old emails, product by product, while competitors carry on trading.
What the list does not contain is anything that lives on another company's systems. A WordPress backup can only capture what is on the server. Your website, though, depends on a ring of outside accounts that make it work as a business tool rather than a brochure.
The Map: Inside the Backup and Outside It
The table below is the reference. Each row is covered in detail in the sections that follow.
| Piece | Where it actually lives | What a restore does to it |
|---|---|---|
| Pages, products, orders, settings, photos | Your hosting backup | Returns them as they were when the backup ran |
| Domain name | Your registrar account | Nothing. Renewal and logins sit elsewhere |
| Business email | Your email provider | Nothing. Mailboxes are not part of the site |
| Payment account and keys | Stripe, PayPal or similar, with a copy of the keys in your site settings | Restores the old copy of the keys, which may since have been revoked |
| Premium plugin and theme licences | The vendor's customer account | Restores the key, not the subscription behind it |
| Search Console and Business Profile | Your Google account | Restores the verification file only if it existed when the backup ran |
| Booking calendars and other embedded tools | The booking or widget provider | Restores the embed code, not the bookings |
| Contact form messages and newsletter signups | Often only an inbox or a mailing service | Nothing, unless the site stored them itself |

The Pieces That Live With Other Companies
Your domain name
Your domain is rented from a registrar, renewed yearly, and controlled through a login that has nothing to do with your hosting. Restoring a backup does not touch it. If the domain lapses, no restore brings the site back for customers.
For .ie addresses the rules are clear. The .IE Domain Registry auto-renews every .ie domain on its renewal date for one year, and if the fee remains unpaid the domain is suspended on the 45th day, at which point your website and emails stop working [5]. The failure here is quiet: the renewal invoice goes to an email address nobody reads any more, and the first warning is a customer saying your site has vanished.
What to record: the registrar's name, the account email, who can log in, and the renewal date.
Your business email
Mailboxes almost always live with a separate email provider, such as Microsoft 365 or Google Workspace, and they are not part of a WordPress backup. Restoring your site does not restore a deleted inbox, and losing your email account does not affect the website.
The link between the two is subtle. Your website sends order confirmations and form notifications to an address. If that address stops existing, the website keeps working and quietly sends every enquiry into nothing.
Your payment account and its keys
This one causes the most confusion after a restore, because it lives in two places at once. The money, the transactions, refunds and payouts all sit in your payment provider's account. Your website keeps only a copy of the connection keys in its settings, which means the backup contains whichever keys were in use the night it ran.
Now consider what happens if those keys changed in between. Stripe's documentation explains that rotating an API key revokes it and generates a replacement, with an optional grace period of up to seven days in which both work; once the old key expires, requests using it fail [4]. Stripe also states plainly that it cannot recover a key you have lost [4]. Keys get rotated for good reasons, such as a staff member leaving. Restore a backup from before that rotation and your checkout is presenting a key Stripe has already retired. The site looks perfect. Every payment fails, and by the time anyone notices, the afternoon's sales have gone to a competitor.
What to record: who owns the payment account, how to reach it, and the date of any key change. After any restore, push one low-value test transaction through the production checkout before you call the job finished.
Premium plugin and theme licences
Paid plugins and themes come with a licence key. That key sits in your site's settings, so it is in the backup. The subscription behind it lives in the vendor's customer account, under whichever email address bought it.
Barn2, one WordPress plugin vendor, describes what typically happens when a licence lapses: the plugin keeps working on the front end, but updates stop until the licence is active again, and support stops with them [6]. Policies vary between vendors, so treat that as one example rather than a rule. The pattern is common, though, and it matters, because a plugin that cannot be updated eventually becomes a plugin with an unpatched security flaw.
Ownership is the sharper question. If a designer bought the licence on their own account years ago, the key is in your backup and the account is in their inbox.
Search Console and your Business Profile
Your Google Search Console property and your Google Business Profile both live in Google accounts. A restore does not touch them, with one exception that catches people out.
Search Console proves you own a site by looking for a verification token, often a small HTML file or a tag in your site's header. Google states that it periodically confirms the token is still present, that removing the verification file will cause you to lose verification, and that permissions expire after a grace period if the problem is not fixed [3]. Restore a backup taken before that file was uploaded and the token disappears with the rollback. Nothing breaks on the site. Weeks later, an email says you are no longer a verified owner, and the search data you rely on is out of reach.
What to record: which Google account owns each property, and the verification method used.
Booking calendars and embedded tools
Booking systems, review widgets, live chat and online menus are usually embedded from another service. Your site holds a snippet of code that displays them. The bookings, reviews and conversations stay with the provider.
Consider a typical case, a composite of a pattern that comes up often. A boat hire business on Lough Ree in Westmeath rolls back its website after a plugin update breaks the layout in early spring. The restore completes in minutes and the site looks right. Its booking calendar, embedded from a third-party service, shows an error, because the account behind it was set up under a former manager's email address and the provider has since asked for re-verification. Nothing is wrong with the website. The business cannot take bookings for the first warm weekend of the season, and the fix depends on recovering an account that was never registered to the business in the first place.
No hosting backup could have prevented that. A one-line entry on a recovery sheet would have.
The Pieces That Never Reached Your Server
Some business data passes through your website without ever being stored on it.
Contact forms are the clearest example. Contact Form 7, one of the most widely used WordPress form plugins, does not store submitted messages at all; that gap is the reason a separate storage plugin, Flamingo, exists, with more than 800,000 active installations [2]. Unless your form plugin keeps entries, the only copy of every enquiry is the notification email. Back up the website as often as you like. Those enquiries are not in it.
Newsletter signups behave the same way when the form is embedded from an email marketing service. Each subscriber goes straight to the service's own list. Your website never holds the record, so it cannot lose it, and it cannot restore it either.
Neither of these is a defect. They are design choices worth knowing about before you need a message from three weeks ago and discover it lived only in an inbox someone has since deleted.
The Pieces That Changed After the Backup Ran
Even the data that genuinely lives in your database has a time limit. A nightly backup captures the state of your site once a day. Anything that happens after that run exists only in the production environment.
One honest limitation applies here. If your shop takes a handful of orders in the morning and you restore last night's backup at lunchtime, those orders are not in the restored site. Your customers have paid. The payment provider has the transactions. Your WooCommerce order list does not. A restore is a rollback of the whole database, not a selective undo.
A sensible platform reduces the damage without pretending it away. Web60 takes a pre-restore safety snapshot automatically, so the state you are rolling back from is preserved rather than overwritten. In practice, the morning's orders still exist in a recoverable copy instead of vanishing. Getting them back into the restored site, or reconciling them against the payment provider, is still manual work. Know that before you choose a full restore over a narrower fix, and read why a backup is not the same as a restore before you have to make that call under pressure.
What a Properly Run Website Layer Looks Like
Strip the brand names away and the standard for the part a host can control is straightforward:
- Automatic backups every night, with no one having to remember to run them.
- On-demand backups before any significant change, taken by you in a single action.
- Automatic safety snapshots before updates and before restores, so a bad decision can itself be rolled back.
- A one-click restore that does not involve a support ticket and a two-day wait.
- A staging environment, so risky changes are tested away from production and restores become rarer in the first place.
- People you can reach when a restore does not go to plan, ideally in your own timezone.
Web60 meets each of those. Backups run nightly with one-click restore, manual backups are there when you want them, pre-update and pre-restore snapshots happen automatically, and one-click staging lets you test a change before you deploy it. All of it runs on Web60's Irish-hosted infrastructure, with backups and restore included in the €60 a year, and support comes from an Irish-based team of real people. Because it is full WordPress rather than a closed builder, the content, theme and plugins in those backups remain yours. If your current setup falls short on that list, Web60's free migration service will move an existing WordPress site across, and a brand-new site can be built by describing your business to the AI builder in under a minute.
A fair concession belongs here. If you run a regulated business where an auditor expects a documented disaster recovery plan covering every system, with contractual recovery times and an account manager who maintains the runbook alongside you, enterprise managed WordPress providers sell exactly that service, at enterprise prices. That workload genuinely suits them. Most local firms do not need it. They need a host that handles the website layer properly and a single page that covers the rest.
No host, at any price, can restore a domain you have let lapse, a Stripe account you cannot log into, or a licence bought on someone else's email. That part of the map belongs to you.

Building Your Recovery Sheet in Five Steps
This is usually an afternoon's work at most, and it only needs revisiting when something changes.
- Inventory. Go through every row of the table above and write down which of those services your site actually uses, from the registrar to the booking widget.
- Record ownership. For each one, note the company, the login email, who holds the password and any renewal date, and move anything registered to a former employee or designer onto an address the business controls.
- Verify. Log in to each account once to confirm the details work today, rather than assuming they will work on the day you need them.
- Store off-site. Keep the sheet in a password manager or as a printed copy in the office, never only on the website or in a single person's inbox.
- Rehearse. After your next restore, or in a staging environment, run a test payment, submit the contact form and load the booking page to confirm every outside dependency still connects.
Conclusion
A backup protects what sits on your server, and on a well-run platform it does that job reliably. The pieces that cause trouble after a restore are almost always the ones that were never in it: the domain renewal, the payment keys, the licence on someone else's account, the enquiries that only ever existed as emails.
None of those need technical skill to protect. They need a list, a login that works, and an owner who is the business rather than a person who might leave. With the website layer handled and that one page written, a restore becomes what it should be: a few minutes of disruption, then back to serving customers.
Frequently Asked Questions
Does a WordPress backup include my emails?
No. Business email almost always lives with a separate provider such as Microsoft 365 or Google Workspace, and mailboxes are not part of a WordPress backup. The backup contains your site's database and files. It may contain the setting that tells your website where to send notifications, but not the messages in your inbox.
Will restoring a backup lose orders placed since the backup?
Yes, in the restored site. A restore returns the whole database to the moment the backup ran, so orders, enquiries or account sign-ups after that point are not in it. The payments still exist in your payment provider's account. On Web60, a pre-restore safety snapshot preserves the state you rolled back from, so those orders are not lost outright, though bringing them back into the restored site is manual work.
Does a website backup include my domain name?
No. Your domain is registered through a registrar and renewed separately, usually once a year. A backup cannot renew it or recover it. For .ie domains, an unpaid renewal leads to suspension on the 45th day after the renewal date, at which point the website and email stop working.
Do premium plugins keep working after I restore a backup?
Usually, yes. The plugin files and licence key are in the backup, so the plugin returns as it was. Whether it keeps receiving updates depends on the licence subscription held in the vendor's account, which a restore does not touch. If the licence has lapsed, updates typically stop even though the plugin still runs.
Why did Search Console say my site is no longer verified after a restore?
If you verified ownership with an HTML file or a tag in your site's header, and the backup you restored was taken before that token was added, the restore removed it. Google periodically confirms the token is still present. Upload the file again or re-add the tag, then verify in Search Console before the grace period runs out.
Where should I keep the list of accounts my website depends on?
Somewhere that does not depend on the website or on one person. A business password manager shared with at least one other trusted person works well, as does a printed copy kept securely in the office. Avoid storing it only on the website, in one employee's inbox, or with an outside designer.
Sources
Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.
More by Ian O'Reilly →Ready to get your business online?
Describe your business. AI builds your website in 60 seconds.
Build My Website Free →More from the blog
Payment Test Mode Left On: The Staging Push That Took No Money
Payment test mode left on after a staging push leaves a shop that looks open but takes no money. Where the switch hides and what to verify after every change.
ChatGPT WordPress Fixes: Five Myths That Break Business Websites
ChatGPT WordPress fixes look easy: ask, copy, paste. Five myths about AI code and plugin advice, and the safe way to try a fix before customers see it.
