A freelance translator paid for her hosting once a year. It was the sort of expense she only thought about when it appeared, and for four years it appeared reliably: an email, a card payment, a receipt. The system worked well enough that she stopped thinking about it at all.
Then the renewal notice went to an old email address she no longer used. The plan expired, and after a grace period the host removed the account and its backups. She had her texts, but the site itself, its design and years of testimonials were gone, along with the search ranking it had earned.
How the lapse happened
When she first signed up, she used an email address from her university days. A couple of years later she moved to a new address, and changed the contact details in most of the places she could think of: the bank, the tax office, her clients' invoicing systems. The hosting account was not on that list, because it never asked her for anything. The invoice came, the card was charged, and she did not log in.
This year, the card had been replaced after a loss, and the old number no longer worked. The host's billing system tried to charge it automatically, failed, and sent a series of emails to the address on file. Those reminders went to an inbox she had not opened in over a year. The messages followed a standard pattern:
- A heads-up some weeks before the renewal date.
- A failed payment notice on the day itself.
- Further reminders over the next two weeks, each a little more insistent.
- A suspension notice, when the site stopped loading.
- A final notice that the account and its data would be deleted after a set number of days.
Every one of them went to the abandoned address. Her first real hint was that a client wrote to say the website was down. By then, the account had been suspended for nearly three weeks.
What was lost
She did have her translations. The actual work product lived in her own files, organised by client, and invoices were tracked separately. That limited the damage to her business. What the hosting account held was the public face of it.
The site itself was gone, including the theme she had customised, a page of testimonials gathered from clients over several years, and a few articles about translation topics that had been bringing in steady enquiries. Many of those clients had left kind words in the form of comments or emailed quotes that she had pasted in, and she did not have the originals. A few were retrievable by asking.
The hidden loss was the search ranking. The domain was still hers, since it was registered separately, but the pages that had earned links over the years no longer existed. When a search engine fetched them, it received an error. After a few weeks, the pages dropped out of the results altogether, and with them went the steady trickle of enquiries from people who had never heard of her.
The host's backups were not a way back. The provider's backups had been made for its own recovery needs, for the account while it existed. Once the account was removed, those copies were removed with it, according to the terms she had accepted. Some hosts keep copies for a short time after deletion and will restore for a fee; hers did not, and she was told so politely.
The rebuild
She rebuilt over about a month of evenings. The first job was recovering whatever existed elsewhere, and there was more than she expected:
- The Internet Archive's Wayback Machine had snapshots of her homepage and several articles, which gave her the text and the structure.
- Search engine caches held a few other pages for a short time.
- Her email contained original testimonials, once she searched for words like "thank you" and "great work" in her sent and received mail.
- Her images were all on her computer, because she had edited them there before uploading.
She then picked a simpler design, bought a new hosting plan, and reinstalled the content management system. Because the domain was still hers, it was only a matter of pointing the DNS at the new server, and the search engines started to find her again. The redirect of old addresses to the same pages on the new site mattered a great deal for regaining ranking, and she was careful to keep the old URL structure wherever she could. The redirect generator helped with the pages whose addresses had to change.
It took the best part of a year for her enquiries to return to their earlier level, and some topics never fully recovered.
The cost, in plain terms
Nothing in this story involved a large sum. The hosting itself cost less per month than a few cups of coffee. The expensive part was her time: roughly forty evening hours of rebuilding, a quiet few months without new enquiries from search, and the awkward emails to former clients asking whether they still had their kind words about her work. She estimated afterwards that the lost work was worth many times a year of hosting. That ratio is why copies and reminders are cheap insurance.
What she changed
This time the setup was designed for the days she would not be paying attention. Four changes made the difference.
- Auto-renewal is on, with a card that does not expire in the next three years, and a second payment method on file as a backup.
- The contact address on the hosting account and on the domain registration is one she checks daily, and a second address, belonging to a trusted colleague, is listed as a secondary contact.
- A calendar reminder, set one month before the renewal date, says: check the hosting account, the domain, the card and the contact address.
- A downloadable copy of the site is stored in her own cloud drive. That means the files and a database export, refreshed monthly and after any big change.
That last item is the one that would have saved her. A copy in your own possession does not depend on any provider remembering you.
Look at your own configuration
Allow ten minutes and go through your own list. Log into the hosting control panel and read the account email address, which is usually under "profile" or "account". Do the same for your domain registrar. Confirm the renewal date, the payment method and its expiry date. Look at whether auto-renewal is switched on, and what the host says will happen if payment fails.
You can also see what a domain's registration record says, including its expiry date:
whois example.com | grep -iE "expir|registrar"Finally, test a restore. A backup you have never opened is a hope, not a backup. Download your latest copy, unpack it, and check that the database export and the uploads folder are both present. The troubleshooting guide has more on what to look for when sites go missing.
Things people ask
Is it the host's fault?
Partly a matter of process: a host that sends five emails to one stale address has met its obligations on paper. Many hosts will also contact you by other routes if you give them a phone number, so it is worth adding one.
Would a longer plan have helped?
Paying for several years ahead delays the problem, but does not remove it. The same renewal comes round in the end.
Can the host restore a deleted account?
Sometimes, within a short window. Ask quickly and ask politely, but do not count on it.
What about the domain itself?
Domains have their own lifecycle, including a redemption period, so a lapsed domain may be recoverable for a while at an extra cost. Keep that registration separate from the hosting account.
What changed afterwards
Renewals fail because nobody is looking, not because anyone is careless. Keep the contact address current, leave auto-renewal on, and hold your own copy of the site in a place the host cannot delete.