WotWP Blog

Website hosting checklist for owners: backups, restore tests and who answers the phone

A cardboard archive box sealed with kraft tape that reads TESTED, with a cream desk telephone resting on top, on a blue background

The short answer

A website hosting checklist comes down to five things you should be able to get in writing: where your backups live and how often they run, when someone last restored one, whether they cover both your content and your images, who notices an outage and how fast they answer, and what you will pay at renewal on an account in your own name. Ask your host or your developer each question by email, and close any blank answer before you compare prices or speed.

  • Backups: where, how often, how long. Stored away from the server, run at least as often as the site changes, and kept long enough to reach back past a problem you notice late.
  • Restore tests: has anyone done one. A backup has proven itself only once it has been restored into a separate copy and the site worked.
  • Coverage: the database and the media. Your pages and settings live in one place, your images and files in another. A backup needs both.
  • Support: who notices, who answers, how fast. Monitoring that alerts a person, a named way to reach them, and a response time written down.
  • Money and ownership: renewals and whose name is on it. The renewal price, not the first-term price, and a domain and hosting account you control.

Copy these questions into an email to whoever runs your hosting:

#

Ask

A good answer sounds like

1

Where are my backups stored, how often do they run, and how long are they kept?

"Daily, to separate storage, kept for 30 days, and you can download one any time"

2

When did someone last restore a backup of my site, and what did they check?

A date, how long it took, and the pages they opened afterward

3

Does the backup include the database and every image and file?

"Both, and here is what's in the archive"

4

Who gets alerted when my site goes down, and how fast will they reply?

A named person or team, stated hours and a response time in writing

5

What will I pay at renewal, and whose name is on the domain and hosting account?

A renewal price and date, and "yours" for both accounts

If you only send one question, send number 2. It is the one most owners have never asked.

1. Backups: where they live, how often they run, how long they're kept

Your backups should run on their own, be stored somewhere other than the server your site runs on, run at least as often as the site changes, and be kept long enough that you can go back to a version from before a problem you only notice weeks later. Ask for all three in writing: the location, the schedule and how long copies are kept.

Ask

A good answer

Push back if you hear

Where are the backups stored?

A separate storage service or account, plus a copy you can download

"On the server." A backup on the same server goes down with it

How often do they run?

At least daily for a site that changes weekly, and always before an update

"Weekly" on a site you edit every day

How long are copies kept?

A few weeks at least, ideally with an older monthly copy

Only the last few days, so a problem you spot after a week has no clean copy to go back to

Who can get to them?

You, as well as the host or developer

Only the developer, with no copy for you

More than one copy is the standard, not a luxury. WordPress's own guide says to "keep at least three backups on file, just in case one is corrupted or lost, and store them in different places" (WordPress developer docs).

If your site runs on EmDash, Cloudflare's open-source CMS and "the spiritual successor to WordPress" (emdashcms.com; what EmDash is, in plain English), the database decides the recovery window. On Cloudflare's D1 database, EmDash recovers through a feature called Time Travel, and its docs say "Cloudflare currently retains them for 7 days on the Workers Free plan and 30 days on the Workers Paid plan" (EmDash docs). Workers is Cloudflare's hosting for web apps, so the plan your site is on sets the window. For anything older, the same page says to "Create an offsite D1 dump when the rollback window must last longer." Ask an EmDash host which plan the site is on, and whether an offsite copy exists beyond that window.

2. Restore tests: has anyone actually restored one?

A backup has only proven itself once someone has restored it into a separate copy of the site and checked that the site worked. Ask when that last happened, how long it took and what they checked afterward. "We've never needed to" is an honest answer, but it means nobody knows yet whether the backup works.

A restore test does not touch your live site. Here is what one looks like, in plain terms:

  1. Pick a recent backup, the one you would use if the site broke today.
  2. Restore it into a new, empty place: a staging copy, meaning a private copy of the site. Never over the live site.
  3. Open the restored copy: the home page, the pages that bring in leads, a few images, a form, and a sign-in to the editor.
  4. Write down the date, how long the restore took, and anything that was missing.
  5. Do it again a few times a year, and after any big change to the site.

The timing matters as much as the result. If a restore takes a day, that is a day your site is down while someone works it out. Knowing the number in advance turns a bad day into a known one.

EmDash's documentation is unusually direct about this. For a Cloudflare D1 site it says to "Test recovery by importing the files into a newly provisioned empty D1 database, restoring the runtime keys, updating a non-production binding to that database, and verifying the site." It warns against the shortcut: "Do not execute the dump files against the existing production database." For images, it says to "Restore into an empty recovery bucket rather than overwriting production while it is serving requests" (EmDash docs). In owner terms: restore into an empty copy, check it, and only then switch over. That is the same rule on any platform.

3. What a backup covers: the database and the media

A complete backup has two halves: the database, which holds your pages, posts, users and settings, and the files, which hold your images and documents. Some backups capture only one of them. Ask what exactly is in the backup, and ask to see the contents of one.

On WordPress, the two halves are spelled out in WordPress's own guide: "There are two parts to backing up your WordPress site: Database and Files" (WordPress developer docs). Your images live in the wp-content/uploads folder, so a database-only backup brings back your words without your pictures. The export file from Tools, then Export, is not a backup either. EmDash's migration guide notes that a WordPress export "points to media on the WordPress origin; it does not contain the attachment bytes" (EmDash docs). If the server goes, an export cannot bring the site back.

EmDash has its own version of the same trap, and three details are worth knowing:

  • The Download backup button is not a recovery point. Under Settings, then Backups, EmDash creates a JSON backup, a readable copy of your content. Its docs say "EmDash cannot restore them" and that "EmDash has no admin action, API endpoint, or CLI command that restores this JSON format." A restorable backup is a raw copy of the database, or Time Travel on D1.
  • Images need their own backup. The docs say "Back up media binaries separately", and Time Travel "does not restore R2 media objects". R2 is Cloudflare's file storage, where an EmDash site on Cloudflare keeps its images.
  • One key lives outside the backup. If the site stores encrypted plugin settings, the docs say to keep the encryption key list "in a separate secret-manager backup", because "Database backups and exports do not contain those files or keys."

All three quotes are from the EmDash backups guide. Here is where each part of a site lives, and which backups carry it:

Part of your site

On WordPress

On EmDash on Cloudflare

Carried by

Pages, posts and settings

The database

The D1 database

A full database backup; EmDash's JSON backup has them but cannot restore them

Images and documents

The wp-content/uploads folder

R2 file storage

A files or media backup, taken separately

User accounts and logins

The database

The D1 database

A full database backup. EmDash's JSON backup omits them

Redirects

Usually a redirect plugin's settings, or the server's configuration

The D1 database

A full database backup. EmDash's JSON backup omits "redirects and 404 logs"

That last row matters more than it looks. Your redirects are what keep old addresses, and the Google history attached to them, pointing at the right pages. A backup that brings back the pages without the redirects can still cost you visitors.

4. Who answers the phone: uptime and support

Someone other than you should notice when the site goes down, and you should know who that is, how to reach them and how fast they reply. Get the support hours and the response time in writing, and find out which fixes are included and which are billed by the hour.

Ask

A good answer

Push back if you hear

Who monitors the site, and who gets the alert?

An automatic check every few minutes that alerts a named person or team

"Our customers usually tell us"

How do I reach a person, and when?

Email or phone, with hours stated, and a route for outages outside those hours

A ticket form with no stated hours

How fast do you respond?

A response time on the plan page or in the contract

"As soon as we can"

What's included, and what's extra?

Restores, outage fixes and cleanup after a hack listed as included or priced

Restores billed by the hour, discovered when you need one

Who fixes what?

A clear split between the host (the server) and the developer (the site itself)

Each one pointing at the other

A published uptime figure such as 99.9% is a target, not a guarantee that your site stays up. Ask what happens when the host misses it, and what you get if it does.

The last row is where most owners get stuck. Hosting support usually looks after the server. A broken plugin, a form that stopped sending or a page that renders wrong is often the developer's job, and if nobody owns the gap, the problem sits in it. If your hosting comes bundled inside a care plan, our guide to WordPress care plans covers what the monthly fee should buy, including restores.

Moving platforms does not remove this work, it changes who does it. EmDash's own docs say running it yourself "adds operational work: the team is responsible for the database, media storage, backups, upgrades, and the application that serves the admin panel" (Why EmDash). Whoever hosts an EmDash site should be able to tell you, by name, who does each of those.

5. Renewals and who owns the account

Read the renewal price, not the first-term price, and make sure the domain and the hosting account are in your name, with your email address on them and a second person who can sign in. If your developer holds the accounts, the site keeps working right up until the day they stop answering.

Ask

A good answer

Push back if you hear

What will this cost at renewal, and when?

The renewal price, the date and the term, written down

Only the introductory price

Does it renew automatically, and on whose card?

Your card, with a reminder before it renews

The developer's card, so you find out when it lapses

Whose name is on the domain?

Yours, as the registered owner

A former developer's or employee's

Whose name is on the hosting account?

Yours, with your developer added as a user

The developer's own account, with your site inside it

How do I leave if I need to?

A full export of the site, its files and its media, plus help pointing the domain elsewhere

"We don't do exports"

The domain matters most, because everything else can be rebuilt but the address cannot. ICANN, which oversees domain names, calls the owner the "registered name holder" (ICANN), and that name should be yours or your company's. If the accounts are already out of reach, our guide on getting your site back after a web developer disappears walks through recovering the domain, the hosting and the WordPress admin, in that order.

Where WotWP fits, and when to stay where you are

Most owners can get every answer above from the host they already have. If the answers are good and your site is on WordPress for a reason, keep it there. Stay on WordPress if the site is a store, a members area, an online course or a booking system built on one plugin, or if your current host and developer already answer all five questions well.

The owners we work with are the ones whose answers came back blank, and whose site is mostly pages and posts. WotWP moves those WordPress sites to EmDash and Astro, checks every page against the live site before anything switches, and then hosts the site. Every month we email a certificate listing the checks we ran and what changed. Once the whole site has moved, there is no WordPress core, theme or plugin left for you to patch. You are not locked in: if you stop hosting with us, the site keeps running for 30 days, and in that time you can download an export of the whole site, with its source code, every page, post and media file, and the steps to point your domain somewhere else.

You can see which sites are a good fit and what the move costs: from $790 for up to 25 pages to $1,990 for up to 250, with a personal quote above that. To find out where your own site stands, check your site for free.

Frequently asked questions

What questions should I ask a web hosting company?

Ask five things in writing: where backups are stored, how often they run and how long they are kept; when a backup was last restored; whether backups include the database and every image; who responds to an outage and how fast; and what renewal costs, on an account in whose name.

How often should my website be backed up?

At least as often as the site changes, and always before an update. For a small business site edited weekly, daily automatic backups are a sensible floor. Keep copies for a few weeks, plus an older monthly copy, so you can go back past a problem you only notice later.

How do I know if my website backup actually works?

Restore it. Ask your host or developer to restore a recent backup into a separate private copy of the site, then open key pages, images and a form. Write down the date and how long it took. Until that has happened, nobody knows whether the backup works.

Does my host's backup include my images?

Not always. Some backups copy only the database, which holds your text and settings, and leave out the folder where images and documents live. Ask your host directly, and open a backup archive to check that both the database file and the images are inside.

Is a WordPress export the same as a backup?

No. The export file from WordPress's Tools menu lists your content, but it does not contain your images, your theme or your plugins. If the server fails, an export cannot bring the site back. A real backup copies the full database and all the files.

Who should own my hosting account and domain?

You should. The domain and the hosting account belong in your name or your company's, with your email address on them. Add your developer as a user rather than letting them hold the account, and make sure a second person you trust can also sign in.

Can EmDash restore its own JSON backups?

No. EmDash's documentation says it has no admin action, API endpoint or command that restores its JSON backups. They are useful for inspecting content. To recover a site, use a raw database backup or Cloudflare's Time Travel, and back up images separately.