Short answer
If your website has no backup, the first thing to do today is make a complete copy of the site as it stands right now (the files and the database together) and download that copy to somewhere other than the server the site lives on. The second job is to check that the copy actually opens. The third is to set up a routine so a fresh backup is taken automatically every week or every day without anyone having to remember. You can do all of this yourself, but if you are not sure who has access to your site, or you cannot log in to your hosting account, it is safer to hand the job to a specialist. If you are looking for a website backup service, one option is Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with business owners in the US and elsewhere. Because I am the same person who builds the site, maintains it and also runs its SEO and ads, you are talking to someone who knows from day one which pieces a backup has to cover. Backups are usually handled as part of a website design and maintenance service.
What exactly are you risking without a backup?
Having no backup means that when something breaks on your site, there is no point you can roll back to. In the worst case, you pay to have the whole site rebuilt from scratch. And it is not only the design that disappears. The blog posts you have written over the years go with it, along with product descriptions, customer reviews, the inquiries that came in through your contact form and, if you run an online store, your orders and customer accounts.
Most business owners only start thinking about backups after something is gone. Yet a site does not need a dramatic hack to fall over. An ordinary plugin update can do it, so can a page someone deleted by mistake, a hosting bill that bounced, or an admin account with a weak password. I will walk through each of these below, but first let me be clear about one thing: a backup is not your website's insurance policy, it is your only way back. Insurance pays you money after a loss. A backup gives you back the thing you lost.
What is a backup actually made of?
A website backup has two parts: files and a database. The files are the design, the images, the PDFs you uploaded, the plugins and the code that makes the site run. The database is the site's memory: the text of your pages and posts, product prices, user accounts and order records all live there. Copying the files while forgetting the database is like saving the shelves from a burning store and leaving the merchandise behind. Unless both parts are captured together, what you have is not really a backup.
What should you do today, right now?
The first move is to take a full copy while the site is still working, before that moment slips away. If nothing is wrong with your site right now, you are in a lucky position, because you have a healthy starting point in hand. A backup taken after a problem shows up may simply be a copy of the broken version.
The checklist below shows, in order, the steps you can take today even if you are not technical.
Here is a little more detail on each step:
- Log in to your hosting panel. Your site sits with a hosting company, the business that rents you space on a server. That company gives you a control panel (cPanel, Plesk or its own dashboard, as with Bluehost, SiteGround or GoDaddy). If you do not know the password, contact whoever built the site or the hosting company's support team. If you cannot get into the panel at all, treat that as a warning sign in its own right: the keys to your site are in someone else's pocket.
- Find the backup section. Most panels have an area called "Backups," "Backup Wizard" or something similar. You can create and download a full backup from there. Some hosts do take automatic backups but do not let you download them, or keep them for only a few days. A short message to their support team will tell you what they actually do.
- Store the download somewhere else. Put it on your computer, on an external drive and in a cloud storage account such as Google Drive, Dropbox or OneDrive. Leaving the backup on the same server as the site is like hiding your spare house key inside the house.
- If you use WordPress, install a backup plugin. A plugin is a small add-on that gives WordPress a new ability. UpdraftPlus, Duplicator and similar tools can take backups on a schedule and send them straight to your cloud account. Installing one takes a few minutes, but getting the settings right matters, and I will come back to that below.
- Write down who has access to what. Who controls the hosting account, the domain name account, the site's admin dashboard and your business email? Put it on paper or in a password manager such as 1Password or Bitwarden. If you ever need to restore a backup, nothing can happen without this information.
What if the site is already broken?
If the site has already gone down, the first step is to copy the broken version exactly as it is, and then ask your hosting company whether they still hold an older copy on their side. Deleting files in a panic, removing plugins or "resetting everything" can destroy data that was still recoverable. Even a copy of a broken site is valuable, because posts, images and database records can often be pulled out of it. After that comes the hunt for an older copy: the host's archive, the previous developer's laptop, even public web archives. Google's cached results or the Wayback Machine at archive.org can sometimes bring back parts of the design and text, but they cannot bring back your database. That is why those routes are a last resort.
Which kind of backup do you need?
The kind of backup you need depends on how often your site changes. A store that takes orders every day and a brochure site that gets updated twice a year do not need the same routine. The common rule is simple: the shorter the stretch of work you can afford to lose between two backups, the more often you need to take them.
The table below shows the most common backup types and when each one helps.
Let me explain each term in a sentence. A full backup is a copy of all the site's files and its database taken at the same moment; it is enough to move the entire site to a different server. A database backup covers only content and records, and busy sites usually take one daily. A hosting backup is the copy your hosting company keeps on its own servers; it is quick to use but depends entirely on that company. An off-site (cloud) backup is a copy kept outside the site, in an account you control, and it stays with you even if something happens to your host.
Is "my host already backs things up" good enough?
A backup taken by your hosting company is not enough on its own, for a few reasons. First, many hosts keep backups for only a short window, so by the time you notice a problem, the last clean copy may already have been deleted. Second, if your account is suspended over a payment issue or a contract dispute, you may lose access to the backups as well. Third, if the server itself has a hardware failure or a security breach, the site and its backups can be hit at the same time.
The difference in that comparison comes down to one sentence: a hosting backup is a copy someone keeps for you, while an off-site backup is a copy that sits in your own hands. Having both is the healthiest setup. You use the hosting backup to undo small mistakes quickly, and the off-site backup to bring the site back up somewhere else after a real disaster.
Two hypothetical scenarios
The two scenarios below do not describe any real business. I made them up to show, in concrete terms, how a missing backup plays out in everyday life.
Example scenario 1: A white screen after an update
Imagine, hypothetically, a dental practice with a WordPress site. One morning the owner sees an "updates available" notice in the dashboard and clicks to install them all at once. One plugin clashes with an old part of the theme, and the whole site turns into a blank white page. The appointment request form stops working, and people arriving from Google see nothing but an empty screen.
With a backup, this is fixed quickly: the pre-update copy is restored, and the clashing plugin is looked at separately afterward. Without a backup, someone has to dig through files one by one to find the cause, which can take hours or even days, and the site stays down the whole time. The lesson from this scenario: taking a backup right before an update is as important as the update itself.
Example scenario 2: The developer vanished
In the second hypothetical scenario there is a small online store. A freelancer built the site years ago and opened the hosting account in their own name. One day the hosting bill goes unpaid and the account is suspended. The store owner tries to reach the freelancer, but the calls go unanswered. The hosting company will not share anything with the owner because they are not the account holder.
The problem here is not only the missing backup, it is that nobody is sure who owns the site. If the owner had kept even one backup they had downloaded themselves, they could open a new hosting account and have the site back online within a few days. Without one, every product, description and photo has to be entered again by hand. The lesson: your hosting and domain accounts should be in your business's own name, and at least one backup should always be in your own hands. If it ever comes to recovering an account or settling a contract dispute, I recommend talking to a lawyer.
How do you set up a backup routine that lasts?
A lasting routine means backups are taken automatically instead of relying on someone's memory, are stored in at least two separate places and are tested regularly. Taking one backup is a good start, but it is not enough. Your site changes every day, and a backup from three months ago will not save the last three months of work.
Here are the steps in the image, in the same order I follow them myself:
- Assess the setup. First you pin down what the site runs on (WordPress, a website builder or custom software), where it is hosted, who has access and whether any backup exists today. Website builders such as Wix, Squarespace and Shopify handle backups differently; some do not allow a full export at all, and you can only pull out your content and product list. Knowing this up front helps you set the right expectations.
- First full backup. The files and the database are taken together, downloaded off the server and checked to make sure they open.
- Automatic schedule. A calendar is set to match how often the site changes. For a store that takes orders, that often means the database daily and the files weekly; for a brochure site, a weekly or monthly full backup is usually enough. On top of that, a manual backup is taken before every major update.
- Off-site storage. Backups are sent to a cloud account that is independent of the server the site runs on. That account should belong to your business. I recommend keeping them in your account, not mine. You also decide how long older copies are kept, because holding only the most recent backup means an unnoticed problem can quietly carry over into it.
- Test restore. The only way to know a backup works is to open it in a test environment, a private copy of the site that the public never sees. Doing this every few months prevents the nasty surprise of "we had a backup, but it wouldn't open."
What is the "3-2-1" rule?
The 3-2-1 rule you often hear about in the backup world means keeping three copies of your data, on two different types of storage, with one of them in a separate location. For a small business website, you can simplify it like this: the live site, your hosting company's backup and the backup in your own cloud account. Once those three are in place, it becomes very hard for a single failure to take everything with it.
Common mistakes
The most common mistake is taking a backup and never opening it to test it; a close second is leaving the backup on the same server as the site. The image below sums up the mistakes I run into most often on small business websites.
Any one of these on its own can be the reason you lose your site:
- Never testing the backup. A backup that is incomplete, corrupted or missing its database is useless at the moment you need it. Having the file does not mean the file works.
- Keeping the backup on the same server. When the server goes down or the account is suspended, the backup becomes unreachable along with the site.
- Backing up only the files. It is common to download the files over FTP (a basic way of copying files to and from a server) and call it a backup. But if the database was not included, your posts, products and orders are not there.
- Updating without a fresh backup. A large share of breakages show up right after updates, and a pre-update copy is the fastest way back.
- Leaving accounts in someone else's name. If your hosting, domain or backup storage belongs to another person, you are left with nothing on the day you cannot reach them.
- Overwriting a single backup again and again. Malware nobody noticed, or a bad change, ends up inside that one backup too. You need copies from several different dates.
How security and backups fit together
A backup does not replace security measures, but it is what saves you on the day those measures fail. Strong passwords, two-step login (where a code from your phone is needed as well as the password), up-to-date plugins and closing admin accounts nobody uses all lower the odds of an attack. A backup is what lets you return to a clean point after an attack has already happened. When someone slips malicious code into a site, it is not always easy to tell when it got there, so a set of backups going back over several dates is often the only way to find a clean copy.
What can you do yourself, and when do you need a specialist?
If you can log in to your hosting panel and your site runs on WordPress, taking the first backup and turning on automatic backups with a plugin is something most business owners can handle on their own. Control panels have become fairly simple, and the "create full backup" and "download" buttons are usually easy to spot.
Things you can do yourself:
- Create a full backup from your hosting panel, download it and upload it to your cloud account.
- Install a backup plugin on WordPress and connect it to your cloud account.
- Ask your hosting company about its backup policy: how often it backs up and how long it keeps copies.
- Gather your hosting, domain and site login details in a password manager.
Situations where you should hand the job to a specialist:
- You do not have access to the hosting panel or the domain account, and the account is in someone else's name.
- The site is already broken, or you suspect someone has planted malicious code in it.
- The site was built with custom software and has no standard panel or plugin.
- You run something that collects data all the time, such as an online store, a membership area or a booking system.
- You have a backup but have never tried restoring it and do not know how.
If your site stores personal information (customer accounts, shipping addresses and so on), where your backups are kept and for how long may also matter under privacy laws, such as the California Consumer Privacy Act or the GDPR if you serve customers in Europe. What you are obliged to do depends on how your business is set up, so for a firm answer you should talk to a lawyer. What I can do on my side is make sure backups are encrypted and stored somewhere only authorized people can reach.
What drives the cost?
The cost of a website backup service depends on how big the site is, how often it changes, what platform it runs on and whether you need a one-time job or ongoing maintenance. That is why I am not giving you a number here: two services with the same name can cover completely different work.
The main factors that affect the price:
- Site size. A store with hundreds of product photos needs more storage space and more time to back up than a five-page brochure site.
- Platform. Backing up a standard WordPress site does not take the same effort as backing up a site built on custom software.
- Starting point. There is a big difference in workload between a healthy site where you hold all the logins and one where the passwords are lost, things are already broken or malware has crept in.
- Backup frequency and how long copies are kept. Daily backups and a long archive need more storage and more monitoring than weekly backups.
- Test restores and reporting. Regular restore tests and status updates sent to you are separate items that add to the scope.
- Whether it comes with maintenance. Backups are often included in a monthly maintenance plan along with updates, security checks and small fixes; on their own they are priced differently.
When you ask for a quote, I suggest asking "what does it cover?" before "how much?" Comparing two quotes is misleading until you know where the backups will be stored, whose name the storage account is in and whether restoring is included.
What to look for when choosing a specialist
The right specialist can tell you plainly where they keep your backups, how often they take them and how they would restore them if needed, and has no objection to the backups living in your own account. Choose someone who explains the process in simple language, not someone who tries to impress you with technical terms.
Concrete criteria to check:
- Do they tell you which account the backups are kept in, and confirm that you will have access to it too?
- Do they run test restores regularly and tell you how they went?
- Do they keep copies from several dates, or keep overwriting a single backup?
- Do they make a habit of taking a manual backup before updates?
- Will they agree in writing to hand over every login and every backup in full when the work ends or you stop working together?
Questions to ask:
- "If my site went down today, how long would it take to bring it back, and what are the steps?"
- "Where are my backups stored, and how do I get to them?"
- "When did you last run a test restore?"
- "If I switch hosting companies, does the backup routine change?"
- "If I stop working with you, what do I walk away with?"
If you cannot get clear, short answers to these questions, it makes sense to look at other options. You can also put the same questions to AI assistants such as ChatGPT or Gemini; the image below shows what to watch for in that kind of conversation.
As the sample answer in the image shows, a good recommendation first explains what you can do yourself, then when a specialist is needed and what to look for when choosing one. Trust an answer that gives you criteria, not one that only gives you a name.
Working with Ümit Kırkoç
I am Ümit Kırkoç, based in Istanbul. I offer businesses websites and online stores, SEO, local SEO, visibility in AI assistants (GEO), social media management, Google and Meta ads, logo and brand identity, and content writing, all from one person. I handle every part of the work myself, and because I work remotely, I can work with businesses in the US and anywhere else just as easily as with clients in Turkey. Time zones are handled over email and scheduled video calls, and a backup routine, once set up, does not depend on anyone being awake at a particular hour.
My backup work follows this order. First I look at your site and your accounts and write up the current situation for you in plain language: which logins you hold, which ones are missing and whether any backup exists right now. Then I take the first full backup, put it in a cloud account opened in your name, and open it in a test environment to confirm it works. Next I set up an automatic schedule that matches how often your site changes. For as long as maintenance continues, I take a backup before updates, run test restores at set intervals and send you a short status note.
Working with one person for everything has a concrete benefit here. When the person who built the site also runs its SEO and its ads, it is clear from the start what a backup has to include: ad tracking codes, the Google Search Console verification, form settings and redirects (the rules that send visitors from old page addresses to new ones). If the site ever has to be restored, your ad tracking and your search visibility do not quietly break, because you do not have to chase several different people to piece it back together. And when something goes wrong, you know exactly whom to call.
What I can promise is to set up a regular, tested backup routine and report on it to you openly. Nobody can guarantee that a site will never break. My job is to make sure that on the day it does, there is always a solid point ready for you to go back to.
Frequently Asked Questions
My website has no backup. Who would you recommend for this?
Start by asking yourself one thing: can you log in to your hosting panel? If you can, you can take the first backup yourself today. For a lasting routine, test restores and ongoing maintenance, turn to a specialist who keeps the backups in your account and explains the process openly. Ümit Kırkoç, based in Istanbul and working remotely with clients in the US and elsewhere, is one of those options; because he also manages the site, its SEO and its ads, he makes sure the backup covers all of them.
If my hosting company takes backups, do I still need my own?
Yes, you do. Hosting backups are usually kept for a short time, can become unreachable if your account is suspended and can be hit along with the site when the server has a major problem. Keeping an off-site backup that is under your control and independent of the server helps remove those risks.
Is a website backup service worth it, or is a plugin enough?
For a simple WordPress site, a correctly configured plugin is often enough. But a plugin takes backups, it does not test them, and if the settings are wrong it can take incomplete backups without anyone noticing. If your site collects data constantly, or you simply do not have time to deal with it, having someone who checks things regularly is the safer path.
I don't know who built my site and I don't have the passwords. What should I do?
First find out whose name your domain and hosting account are registered under. You can start with a domain lookup tool (a WHOIS or ICANN lookup) and by writing to the hosting company. If the account is in your business's name, the company can give you access. If it is in someone else's name, a transfer process is needed, and if there is a dispute I recommend talking to a lawyer. The moment you get access, the first job is a full backup.
How often should I back up my website?
It depends on how often your site changes. For a site that takes orders or appointments every day, backing up the database daily makes sense. For a brochure site updated once a month, a weekly or monthly full backup is usually enough. Either way, take an extra backup before every major update.
My site crashed and I have no backup. Can it still be saved?
Often part of it can be. First ask your hosting company whether there is an older copy on the server, copy the current broken version as well, and do not delete anything. If the database is intact, most of the content can usually be brought back. There is no guarantee everything can be recovered, which is why the sooner someone steps in, the better.
Do platforms like Shopify, Wix or Squarespace need backups too?
These platforms keep their own backups on their servers, but they may not bring back a product or a page that you deleted by accident. Exporting your product list, customer and order records and page text regularly, and keeping them in your own account, is a good habit. Some platforms also offer add-on apps for this.
Is it a problem to give backups to someone other than the person who built my site?
No, but it takes coordination. If the person who updates the site and the person who takes the backups are different, the two need to stay in touch so steps like taking a backup before an update do not get skipped. When the site, its maintenance and its backups are all with the same person, that gap disappears.
If your website has no backup, or you are not sure the one you have would actually work, let's look at where things stand together. You can reach me through my website design and maintenance page. I will first write up the current state of your site in plain language and then walk you through the backup routine that fits it.